[beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

One last thing I forgot to reply to: >> Something else to consider: does your data need to be (ASCII) strings? Not really, they are just easy to read. If I hit further performance issues I will switch format. -- For more options, visit http://beagleboard.org/discuss --- You received this

[beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

>>And I will finally learn a python ;) Thanks for using my language. I read and thought about your code but in the end I chose to use SSH rather then telnet. SSH support is already present in the debian distribution I am using so I could get it working without writing any more code on the

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

>> Why you want to use RS232, i would choose TCP ,UDP or WebServer Personal preexisting skill set. I have been using serial connections for 4 years on multiple projects with multiple pieces of hardware. I wrongly believed that it would be easy to just use serial again. And I will finally

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

> > $ python3.6 ~/reusable/BBB_pressure_streamer.py > some_log_file.txt > > When I view the log file I can't see any errors > So, actually, scripting languages in general can be far slower, that their native code counterparts. Firstly, because there is an interpreter, and secondly because of code

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

Sorry for double posting last time, this is my first time using google groups. >> I wonder if you run the application that failing for you there is you pipe that data to a file, >> instead of to stdout, if you would be experiencing the same problem ? The data loss problem also happens when the

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

Hi, I plugged the micro USB port on the BBB into my USB hub. The USB hub is currently attached to a windows PC but the same fault happens when the USB cable is plugged into my mac book running OSX. Which, since there is no FTDI chip on the BBB, is effectively an emulated serial port...

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

On Thu, May 4, 2017 at 5:42 PM, Graham Haddock wrote: > So, the COM port on Windows is talking to a virtual serial port in the BBB > USB widget. > There is no hardware UART involved, and no hardware clocks anywhere to > throttle or pace anything. > Then, you push this for

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

Dennis, keep your comments directed at helping the OP, and stop worrying about what I'm saying. We're obviously not talking about the same thing, and your comments to me are not helping the OP solve his problem. David, As an example if I run the following program there is no data loss: > >

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

So, the COM port on Windows is talking to a virtual serial port in the BBB USB widget. There is no hardware UART involved, and no hardware clocks anywhere to throttle or pace anything. Then, you push this for transfer rate, while running it under a non realtime OS. I guess I am not surprised that

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

On Thu, May 4, 2017 at 3:32 PM, Dennis Lee Bieber wrote: > On Thu, 4 May 2017 15:10:07 -0700, William Hermans > declaimed the following: > > > >I think it's important to note that the OP is not sending data from the > >beaglebone, but receiving it. At

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

>> I am confused as to what your actual hardware configuration is, with respect to the "serial communications." The actual hardware used in the final project with the i2c connectors soldered on to a prototyping cape looks like this: I have repeated the exact same fault on this: >> Are you

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

On Thu, May 4, 2017 at 3:10 PM, William Hermans wrote: > > > On Thu, May 4, 2017 at 3:02 PM, arsi wrote: > >> Hi, >> >> call *flush* after write command!!! >> >> *flush**(**)* >> >> *Flush of file like objects. In this case, wait until all data is >> written.*

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

On Thu, May 4, 2017 at 3:02 PM, arsi wrote: > Hi, > > call *flush* after write command!!! > > *flush**(**)* > > *Flush of file like objects. In this case, wait until all data is written.* > Arsi > I think it's important to note that the OP is not sending data from the

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

Hi, call *flush* after write command!!! *|flush|**(**)* *Flush of file like objects. In this case, wait until all data is written.* Arsi -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

On Thu, May 4, 2017 at 9:32 AM, David Howlett wrote: > >> First, you're going to need to learn how to use systemd, and > specifically, you're going to need to learn how to create, and use a > startup service. > > I happen to have used systemd startup services in a

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

David: I am confused as to what your actual hardware configuration is, with respect to the "serial communications." Are you using a COM port in Windows to talk to a USB to serial cable, which is talking to a hardware serial port in the BBB? Or, are you doing something else? If so, please

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

>> First, you're going to need to learn how to use systemd, and specifically, you're going to need to learn how to create, and use a startup service. I happen to have used systemd startup services in a previous project so I can see how it would be useful for setting settings on startup. >>

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

On Tue, May 2, 2017 at 6:26 AM, David Howlett wrote: > I couldn't easily find documentation on how to enable flow control on the > beaglebone side so I chose to add a CRC32 checksum to each line. The data > now looks like: > > This is not really so much a beaglebone

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

I couldn't easily find documentation on how to enable flow control on the beaglebone side so I chose to add a CRC32 checksum to each line. The data now looks like: 102.04541 125 1186 3665238047 102.04588 125 1273 3232659341 102.04635 125 1273 3345150538 102.04708 125 1245 4074941927 102.04756

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

} return 0; } Arsi *From:* David Howlett *Sent:* Thursday, April 27, 2017 6:54PM *To:* Beagleboard *Subject:* [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection. Reply to arsi = If I und

[beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

Thanks for all the replies. Reply to Przemek Klowoski = I agree it is almost certainly a serial buffer overflow somewhere. By filling and emptying the buffers between my code on the BBB and my code on the PC I can detect a 12KB buffer. I believe that this 12KB buffer

Re: [beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

It looks like the serial output buffer overflow. I think you're using the USB serial port, so it's probably not lost in the USB link, but on the Windows side the USB serial driver is presumably overwriting the output buffer. Would you have a Linux system somewhere to cross-check it by using a

[beagleboard] Re: Repeatable bug where beaglebone black loses bytes from it's serial connection.

I should mention I am using: - Windows 10 - Drivers from about 2 weeks ago - A beaglebone image from about 2 weeks ago On Friday, April 21, 2017 at 5:18:37 PM UTC+1, David Howlett wrote: > > I have spent about two days tracking down an issue in one of my machines. > I am streaming