Recent content by RussNelson

Anybody got one for the Teensy 3.5 and 3.6?

My current setup was Arduino 1.0.6 and Teensyduino 1.20. I wasn't able to program a Teensy 3.2. I upgraded to Arduino 1.6.5 and Teensyduino 1.25 and it programs fine. Don't know when the change was made, but I didn't see any mention of it after looking in all the obvious places (3.1 -> 3.2...

Tested with current 64-bit Ubuntu 14.04 against current 64-bit Arduino code. Solves a problem I was having with Teensy 3.1 where the USB serial ports weren't appearing. Well done!

Oh. My. God. Kill me now before I make another misteak like this.

I'm running Ubuntu 12.04 (important, because it works on 10.04), and I can't program a Teensy -- neither 2.0 nor 3.0. I'm running Teensyduino 1.15 against Arduino 1.05. The teensy is programmed with sensor code that writes output to Serial(). When I plug it in, it creates /dev/ttyACM0, and I...

Awesome again, as usual. Take two pats on the back out of petty cash, and call it a day! Yes, this fixes the problem, thanks so much.

Is there anything I can do to help fix this problem? Going to implement a relay to drop power, but that offends my engineering sensibility. Sadly, I don't have a USB protocol analyzer, so my options are limited to 1) gazing at it quizzically, 2) staring at it with furrowed brow, and 3) glaring...

Yes. Seemingly, anyway. I tried changing the permissions granted to 0654 and that's what /dev/ttyACM0 got, so I presume that the entire rules file is being applied.

Hrm. Simply reading from Serial is not sufficient to work around this problem. If you reboot with the test Teensy code from #15 above still running, it goes mute again. Something happens during the reboot to cause it to stop transmitting. I reproduced this using the same version of Raspbian...

I believe that you have hit the ball on the nose (or something like that). Here's what Ubuntu says about /dev/ttyACM0: speed 57600 baud; line = 0; eof = ^A; min = 1; time = 0; -brkint -icrnl -imaxbel -opost -onlcr -icanon -echo -echoe And here's what the Raspberry Pi running Raspbian says: speed...

I tried running the Python program, figuring what the hell, it's practically the same as my program, but might give me different results. I'm getting a stream of lines, but not all of them. It will just pause, as if some of the lines are going into the bit-bucket. Finally, after a minute or so...

Interesting! I bashed the Blink and AnalogReadSerial code together so it would blink on every Serial.println(). In the setup() function, I waited until Serial.read() returned a space. Then on the Linux side, I did "cat </dev/ttyACM0 &" and then "echo " ">/dev/ttyACM0", the LED started blinking...

Thanks! I'm desperate here. We've got a sonde we have to get into the water and the customer keeps calling. I agree with what you say about cat finding EOF early. In this case, cat just sits there. "dd if=/dev/ttyACM0 bs=1 count=1" will also sit there forever once it's gone silent. On the off...

That Python script looks suspiciously short. Could the forum software have helpfully "compressed" it? Yes, the Serial2 and Serial3 fixes have nothing to do with transmitting via USB.

Further, there is nothing logged in /var/log/syslog at the time it goes silent. And it goes silent after a short period of time whether you read the output or not. Closing and re-opening /dev/ttyACM0 doesn't make it start talking again.