On Wed, Sep 3, 2014 at 2:29 AM, Michael M mmcdani...@gmail.com wrote:
The frequency of your data(based on your sample) doesn't necessarily
require a 115kbps transmission rate.
Good point. People from 3D printing word normally use 250Kbps because this
is fast and has lower error rate than
Hi everyone!
I've got my BBB rev. C set up as a data logger for a serial data stream
from an Arduino. It basically takes this data, uploads it to xively, and
checks certain values for exceeded thresholds and sends an email if found.
This works fine. However, after the script has been running
Hi Chris,
I don't think the problem is related to the serial port itself. I have a
python code that uses 4 serial ports of BBB (tty01, tty02, tty04, tty05)
running without any problem for months.
I saw your code. If it reaches the Dropping out due to an error: , I
don't think it will keep
I think Miguel's logging idea is the best way to know exactly what's going
on. Some additional thoughts:
Based on code, if your program stops receiving data but still runs then it
is probably infinitely blocking at arduino.readline(). The fact that you
don't see output from print(line) or
I should add that the timeout should be larger than the largest expected
gap between each data transmission. For example if you expect data coming
in every minute, then set the timeout to be 2 minutes. If no data comes in
for 2 minutes, then you know something is wrong.
On Tuesday, September
