First place to look when serialCommunication fails?

First place to look when serialCommunication fails?

in Using Cinder • 1 year ago

Hello,

I running cinder 0.8.6 for mac. I am pulling in serial data via usb from an Arduino Uno and it is displaying without error in the Arduino serial monitor. I am trying to run the SerialCommunication example and am stuck at

Device: cu.Bluetooth-Incoming-Port

Device: tty.Bluetooth-Incoming-Port

Device: cu.Bluetooth-Modem

Device: tty.Bluetooth-Modem

Device: cu.usbmodem1451

Device: tty.usbmodem1451

There was an error initializing the serial device!

What would be a good next step?

Replies(3)

marie

Re: First place to look when serialCommunication fails?

1 year ago

I've found that replacing

Serial::Device dev = Serial::findDeviceByNameContains( "tty.usbserial" );

with

Serial::Device dev = Serial::findDeviceByNameContains( "tty.usbmodem" );

helps. The SerialCommunication app opens, but then hangs. The data coming from the Arduino looks like this:

E2: D=3 V=21

E3: D=-1 V=-1

E3: D=1 V=0

E3: D=-1 V=-1

E3: D=1 V=0

E3: D=-1 V=-1

E1: D=3 V=3

E1: D=3 V=6

The SerialCommunication app has found the port, but isn't reading in the data.

marie

Re: First place to look when serialCommunication fails?

1 year ago

The final missing piece: Note the use of the "*" in SerialCommunicationApp::setup(). The serial data must pass "*" in order for the app to begin reading the data that follows.

Denis

Re: First place to look when serialCommunication fails?

2 months ago

Saved my life!
Thanks! -.-

Top Reply

Response title

Attachments