USB to Serial adapter - receive works OK for a limited time










0















I borrowed much of the following code from the Linux Serial HOWTO pages to create my program to read characters endlessly from the serial port. I'm using a USB to serial port adapter (made by micro innovations) so I can get a serial port. Linux recognizes the device as /dev/ttyUSB0.



When I use the device in other native linux programs (such as the output dump program), the adapter works flawlessly and data continuously comes in. However, with my program, the data comes in for roughly 10 seconds, then I receive no more data, yet I know the hardware that the adapter is connected to has more data to process.



Is there something in this code I can fix to allow me to receive unlimited characters as they arrive without me having to restart the program to receive more characters?



I still want to make the mainline code asynchronous to the serial routine as I will be adding more code later on.



#include <termios.h>
#include <stdio.h>
#include <unistd.h>
#include <fcntl.h>
#include <sys/signal.h>
#include <sys/types.h>

#define BAUDRATE B57600
#define MODEMDEVICE "/dev/ttyUSB0" /* My USB to serial converter */
#define _POSIX_SOURCE 1 /* POSIX compliant source */
#define FALSE 0
#define TRUE 1

void signal_handler_IO (); /* definition of signal handler */
int wait_flag=TRUE; /* TRUE while no signal received */

int main()
int fd,res;
struct termios oldtio,newtio;
struct sigaction saio; /* definition of signal action */
char buf[255];

/* open the device */
fd = open(MODEMDEVICE, O_RDWR

/***************************************************************************
* signal handler. sets wait_flag to FALSE, to indicate above loop that *
* characters have been received. *
***************************************************************************/

void signal_handler_IO ()

wait_flag = FALSE;










share|improve this question


























    0















    I borrowed much of the following code from the Linux Serial HOWTO pages to create my program to read characters endlessly from the serial port. I'm using a USB to serial port adapter (made by micro innovations) so I can get a serial port. Linux recognizes the device as /dev/ttyUSB0.



    When I use the device in other native linux programs (such as the output dump program), the adapter works flawlessly and data continuously comes in. However, with my program, the data comes in for roughly 10 seconds, then I receive no more data, yet I know the hardware that the adapter is connected to has more data to process.



    Is there something in this code I can fix to allow me to receive unlimited characters as they arrive without me having to restart the program to receive more characters?



    I still want to make the mainline code asynchronous to the serial routine as I will be adding more code later on.



    #include <termios.h>
    #include <stdio.h>
    #include <unistd.h>
    #include <fcntl.h>
    #include <sys/signal.h>
    #include <sys/types.h>

    #define BAUDRATE B57600
    #define MODEMDEVICE "/dev/ttyUSB0" /* My USB to serial converter */
    #define _POSIX_SOURCE 1 /* POSIX compliant source */
    #define FALSE 0
    #define TRUE 1

    void signal_handler_IO (); /* definition of signal handler */
    int wait_flag=TRUE; /* TRUE while no signal received */

    int main()
    int fd,res;
    struct termios oldtio,newtio;
    struct sigaction saio; /* definition of signal action */
    char buf[255];

    /* open the device */
    fd = open(MODEMDEVICE, O_RDWR

    /***************************************************************************
    * signal handler. sets wait_flag to FALSE, to indicate above loop that *
    * characters have been received. *
    ***************************************************************************/

    void signal_handler_IO ()

    wait_flag = FALSE;










    share|improve this question
























      0












      0








      0








      I borrowed much of the following code from the Linux Serial HOWTO pages to create my program to read characters endlessly from the serial port. I'm using a USB to serial port adapter (made by micro innovations) so I can get a serial port. Linux recognizes the device as /dev/ttyUSB0.



      When I use the device in other native linux programs (such as the output dump program), the adapter works flawlessly and data continuously comes in. However, with my program, the data comes in for roughly 10 seconds, then I receive no more data, yet I know the hardware that the adapter is connected to has more data to process.



      Is there something in this code I can fix to allow me to receive unlimited characters as they arrive without me having to restart the program to receive more characters?



      I still want to make the mainline code asynchronous to the serial routine as I will be adding more code later on.



      #include <termios.h>
      #include <stdio.h>
      #include <unistd.h>
      #include <fcntl.h>
      #include <sys/signal.h>
      #include <sys/types.h>

      #define BAUDRATE B57600
      #define MODEMDEVICE "/dev/ttyUSB0" /* My USB to serial converter */
      #define _POSIX_SOURCE 1 /* POSIX compliant source */
      #define FALSE 0
      #define TRUE 1

      void signal_handler_IO (); /* definition of signal handler */
      int wait_flag=TRUE; /* TRUE while no signal received */

      int main()
      int fd,res;
      struct termios oldtio,newtio;
      struct sigaction saio; /* definition of signal action */
      char buf[255];

      /* open the device */
      fd = open(MODEMDEVICE, O_RDWR

      /***************************************************************************
      * signal handler. sets wait_flag to FALSE, to indicate above loop that *
      * characters have been received. *
      ***************************************************************************/

      void signal_handler_IO ()

      wait_flag = FALSE;










      share|improve this question














      I borrowed much of the following code from the Linux Serial HOWTO pages to create my program to read characters endlessly from the serial port. I'm using a USB to serial port adapter (made by micro innovations) so I can get a serial port. Linux recognizes the device as /dev/ttyUSB0.



      When I use the device in other native linux programs (such as the output dump program), the adapter works flawlessly and data continuously comes in. However, with my program, the data comes in for roughly 10 seconds, then I receive no more data, yet I know the hardware that the adapter is connected to has more data to process.



      Is there something in this code I can fix to allow me to receive unlimited characters as they arrive without me having to restart the program to receive more characters?



      I still want to make the mainline code asynchronous to the serial routine as I will be adding more code later on.



      #include <termios.h>
      #include <stdio.h>
      #include <unistd.h>
      #include <fcntl.h>
      #include <sys/signal.h>
      #include <sys/types.h>

      #define BAUDRATE B57600
      #define MODEMDEVICE "/dev/ttyUSB0" /* My USB to serial converter */
      #define _POSIX_SOURCE 1 /* POSIX compliant source */
      #define FALSE 0
      #define TRUE 1

      void signal_handler_IO (); /* definition of signal handler */
      int wait_flag=TRUE; /* TRUE while no signal received */

      int main()
      int fd,res;
      struct termios oldtio,newtio;
      struct sigaction saio; /* definition of signal action */
      char buf[255];

      /* open the device */
      fd = open(MODEMDEVICE, O_RDWR

      /***************************************************************************
      * signal handler. sets wait_flag to FALSE, to indicate above loop that *
      * characters have been received. *
      ***************************************************************************/

      void signal_handler_IO ()

      wait_flag = FALSE;







      string io serial-port usb byte






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 11 '18 at 4:55









      MikeMike

      1,329716




      1,329716






















          1 Answer
          1






          active

          oldest

          votes


















          2














          Classic race condition:



          The signal_handler_IO() may be called before your code sets wait_flag = TRUE; e.g. during those printf() calls.



          At this point your program will simply stop.



          A remedy could be setting the wait_flag immediately after the if - but I would recommend looking into linux poll() call for async I/O.






          share|improve this answer






















            Your Answer






            StackExchange.ifUsing("editor", function ()
            StackExchange.using("externalEditor", function ()
            StackExchange.using("snippets", function ()
            StackExchange.snippets.init();
            );
            );
            , "code-snippets");

            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "1"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53245965%2fusb-to-serial-adapter-receive-works-ok-for-a-limited-time%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            2














            Classic race condition:



            The signal_handler_IO() may be called before your code sets wait_flag = TRUE; e.g. during those printf() calls.



            At this point your program will simply stop.



            A remedy could be setting the wait_flag immediately after the if - but I would recommend looking into linux poll() call for async I/O.






            share|improve this answer



























              2














              Classic race condition:



              The signal_handler_IO() may be called before your code sets wait_flag = TRUE; e.g. during those printf() calls.



              At this point your program will simply stop.



              A remedy could be setting the wait_flag immediately after the if - but I would recommend looking into linux poll() call for async I/O.






              share|improve this answer

























                2












                2








                2







                Classic race condition:



                The signal_handler_IO() may be called before your code sets wait_flag = TRUE; e.g. during those printf() calls.



                At this point your program will simply stop.



                A remedy could be setting the wait_flag immediately after the if - but I would recommend looking into linux poll() call for async I/O.






                share|improve this answer













                Classic race condition:



                The signal_handler_IO() may be called before your code sets wait_flag = TRUE; e.g. during those printf() calls.



                At this point your program will simply stop.



                A remedy could be setting the wait_flag immediately after the if - but I would recommend looking into linux poll() call for async I/O.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 11 '18 at 10:12









                Turbo JTurbo J

                6,52711733




                6,52711733



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53245965%2fusb-to-serial-adapter-receive-works-ok-for-a-limited-time%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    𛂒𛀶,𛀽𛀑𛂀𛃧𛂓𛀙𛃆𛃑𛃷𛂟𛁡𛀢𛀟𛁤𛂽𛁕𛁪𛂟𛂯,𛁞𛂧𛀴𛁄𛁠𛁼𛂿𛀤 𛂘,𛁺𛂾𛃭𛃭𛃵𛀺,𛂣𛃍𛂖𛃶 𛀸𛃀𛂖𛁶𛁏𛁚 𛂢𛂞 𛁰𛂆𛀔,𛁸𛀽𛁓𛃋𛂇𛃧𛀧𛃣𛂐𛃇,𛂂𛃻𛃲𛁬𛃞𛀧𛃃𛀅 𛂭𛁠𛁡𛃇𛀷𛃓𛁥,𛁙𛁘𛁞𛃸𛁸𛃣𛁜,𛂛,𛃿,𛁯𛂘𛂌𛃛𛁱𛃌𛂈𛂇 𛁊𛃲,𛀕𛃴𛀜 𛀶𛂆𛀶𛃟𛂉𛀣,𛂐𛁞𛁾 𛁷𛂑𛁳𛂯𛀬𛃅,𛃶𛁼

                    Crossroads (UK TV series)

                    ữḛḳṊẴ ẋ,Ẩṙ,ỹḛẪẠứụỿṞṦ,Ṉẍừ,ứ Ị,Ḵ,ṏ ṇỪḎḰṰọửḊ ṾḨḮữẑỶṑỗḮṣṉẃ Ữẩụ,ṓ,ḹẕḪḫỞṿḭ ỒṱṨẁṋṜ ḅẈ ṉ ứṀḱṑỒḵ,ḏ,ḊḖỹẊ Ẻḷổ,ṥ ẔḲẪụḣể Ṱ ḭỏựẶ Ồ Ṩ,ẂḿṡḾồ ỗṗṡịṞẤḵṽẃ ṸḒẄẘ,ủẞẵṦṟầṓế