glasspusher
Active member
Hi Paul et. al.,
I'm having a maddening problem with a teensy 3 I'm using in a couple of custom, paid for projects I've made-
It seems like occasionally, on my own apps (written on a mac but running on windows, Cocotron) and on ones the client is using, written with LabView- and this is my guess- something, perhaps a bit of noise on the line from other parts of the widget- causes the teensy to hang in windows, requiring a complete unplug/replug. The device manager still recognizes it, but neither the LabView written app nor my Cocotron created app can access it again. I don't have many details from my client as far as the LabView VISA errors, but my app ends up giving a
Get*Overlapped*Result
error from the windows OS. I looked this up and find some information on it- this one seemed most helpful- but the fact that it's happening on different computers, different apps written with different stuff makes me wonder if either
a) both the app I wrote and the other one written with LabView are making the same boneheaded mistake
b) something with the teensy driver? I don't know, because I don't know what's behind it
c) windows sucks, because I can run the same app I wrote for windows, the mac version, on my mac, and it never, never loses contact with the teensy.
I spent the whole weekend shielding the USB cable, putting in ferrite beads, replacing the usb receptacle on the project chassis, and no love from windows. I have to assume they'll see the same problem when I ship it, and if it's a software issue, so be it, I'll work around it on the windows version, better error checking and so on, but I'd like to know if that sounds reasonable before I sink more time into this. I wanted to ship this down to them last week and I've blown the weekend. Ah, life. At least my Red Sox cheered me up
Thanks in advance for any and all help. I'd be happy to post the windows serial port code, error messages and so on.
I'm having a maddening problem with a teensy 3 I'm using in a couple of custom, paid for projects I've made-
It seems like occasionally, on my own apps (written on a mac but running on windows, Cocotron) and on ones the client is using, written with LabView- and this is my guess- something, perhaps a bit of noise on the line from other parts of the widget- causes the teensy to hang in windows, requiring a complete unplug/replug. The device manager still recognizes it, but neither the LabView written app nor my Cocotron created app can access it again. I don't have many details from my client as far as the LabView VISA errors, but my app ends up giving a
Get*Overlapped*Result
error from the windows OS. I looked this up and find some information on it- this one seemed most helpful- but the fact that it's happening on different computers, different apps written with different stuff makes me wonder if either
a) both the app I wrote and the other one written with LabView are making the same boneheaded mistake
b) something with the teensy driver? I don't know, because I don't know what's behind it
c) windows sucks, because I can run the same app I wrote for windows, the mac version, on my mac, and it never, never loses contact with the teensy.
I spent the whole weekend shielding the USB cable, putting in ferrite beads, replacing the usb receptacle on the project chassis, and no love from windows. I have to assume they'll see the same problem when I ship it, and if it's a software issue, so be it, I'll work around it on the windows version, better error checking and so on, but I'd like to know if that sounds reasonable before I sink more time into this. I wanted to ship this down to them last week and I've blown the weekend. Ah, life. At least my Red Sox cheered me up
Thanks in advance for any and all help. I'd be happy to post the windows serial port code, error messages and so on.