Teensy 3.2 : Error opening serial port 'COMx' (Port busy).

Status
Not open for further replies.
Po Ting

Po Ting

Well-known member
Okay, I'm using Arduino&teensyduino totally fine until I updated my IDE. / on Win10

Few days ago I updated my my arduino/teensyloader to 1.68/1.28
then I couldn't start the serial moniter on my arduino IDE,
and found something unusual: my each teensy 3.2 board has a different COM number(I think they are not different before?)
All results with "Error opening serial port 'COMx'."
something to do with Win10 ?

portbusy.JPG

uploading the program is fine, with a 2~5 second delay after pressing the program button , and the new USB device sound is also fine
the port is visible and selectable in IDE (not visible while programming), I just can't use my serial monitor.

What I've tried:
Restarting the computer, with power totally cut off : tried a few times, not helping
Reinstall arduino/teensyloader : tried a few times, not helping
Change the USB port/cable : not helping

Working solution: change the driver?
with pressing "uninstall driver" (not sure the english is, the pointed button in the picture),
The serial moniter will be working fine with correct printed texts,
but everytime I program the teensy, replug, I had to "uninstall" the driver :(

uninstall.JPG

the picture is the drivers USB port using,
not sure if something to do with Kasper :(
driver1.JPG

I also tried accidentally deleted some file in system32/driver folder (good thing I did backup before doing this...)
and found of all USB devices, there's only keyboard working (oh, this reminded me my keyboard was not using USB port)


Also there's a minor problem on my computer,
while compiling with anything with #include <SD.h> with board arduino NANO , (etc, SD/example/listfiles.ino )
the first compile everytime I start the Arduino IDE is fine, but every second or further compile I'll get a error
GetFileAttributesEx D:\Arduino\libraries\SD\src\File.cpp D:\Arduino\libraries\SD\src/SD.h: The filename, directory name, or volume label syntax is incorrect.
Click to expand...
not always the same file, but something under the SD library folder.

I had to restart the IDE or swap the build setting(etc. board mini, or teensy) to compile again, which is annoying.

Not sure if its related with the problem above or not, and not a really problem for teensy since i don't need to compile any sketch twice.

Sorry for the Chinese interfaces, :(
Thanks for any help

----edited----

another try : I reinstalled the IDE/teensyduino with a previous version 1.67/1.27
and the serial monitor is fine now
 
Last edited:
Maybe try on a different PC?

Something may be very wrong with that computer. Maybe hardware problems or root-level malware?
 
thanks,
will try 1.68/1.28 on a different PC tomorrow,

also another discover : with my unmonitorable IDE 1.68/1.28

shortly after programming a teensy 3.2/ or replug the USB device
if I continuously click on serial monitor button,
there's a high chance that I took the priority to use serial monitor (and functioned with correct text printed)
before some other program makes the Port busy and return
"Error opening serial port 'COM7'. (Port busy)"
 
On Linux, for years we had many problems with the Gnome Modem Manager. It would try to open any Teensy serial device and send AT commands to initialize a modem.

Maybe there's something similar on your Windows system? Or maybe malware doing it?
 
Posting here because I have a similar sounding issue.

I use my Win7 PC with no problems on Arduino Pro Micro. Initially, Teensy 3.2 seemed to also work fine via the Arduino IDE. However, for some unknown reason the COM port does not act as expected in the Arduino IDE. The symptoms are:

. After connecting Teensy 3.2 via USB, Arduino IDE lists the port under Tools > Port even after the USB cable is removed. The Arduino IDE cannot open a serial monitor ("Port Busy") regardless if Teensy is plugged in, but can load new programs manually with button (verified via Blink program).

. The Arduino/hardware/tools/listComPorts and Windows device manager both accurately show whether the Teensy is plugged in via USB. I.e., while the Arduino IDE gets 'stuck', the actual Arduino background tool (not sure if it's used for Tools > Port) as well as Win7 both detect USB connection as expected.

. This is the error message when trying to load new program:
Found serial '\\.\COM4', but unable to open for reboot request
Windows Error Info: The system cannot find the file specified.
more ideas... https://forum.pjrc.com/threads/40632-Teensyduino-USB-issue?p=126667&viewfull=1#post126667
Teensy did not respond to a USB-based request to automatically reboot.
Please press the PROGRAM MODE BUTTON on your Teensy to upload your sketch.

. I have tried messing with the registry/reassigning COM ports, but to no success. I have not tried re-installing Arduino, but would really prefer not to as I have made some modifications to the Arduino files.

I tried using the Teensy 3.2 on my Win10 PC with Arduino IDE (same version of all Arduino/Teensy files) and currently have no issues. Would like to move back to my Win7 PC, and also hoping things don't stop working on Win10 in the meantime.
 
Last edited:
Has the Win7 machine been rebooted and retried?
Using TyCommander works better for me and I use it almost exclusively instead of the IDE SerMon for a few reasons. If TyComm doesn't work then something is not right on the system.
 
Yes, I have definitely tried restarting Windows. Have also tried Putty serial with no success ("port unavailable"). Could you elaborate on what TyCommander is/where to get it? I couldn't find it in Google.

However, my hunch is that the issue is not with Windows, but rather with the way Teensy is advertising itself to Windows on USB, which seems to be confusing the Arduino IDE (v1.6.5-r5). I am not familiar with the bus protocol/driver details though, so can't confirm.
 
Windows is caching USB descriptors and that cache can be outdated / corrupted. Try to purge it with USBDeview (uninstall all devices, then unplug/replug your USB stuff so that it gets rediscovered).

Arduino v1.6.5-r5 is ancient. Serial port handling has improved.

TyTools / TyCommander is here:
https://github.com/Koromix/tytools
 
I have uninstalled all USB descriptors with USBDeview. That did not solve the issue or change the behavior as far as I can tell.

I have downloaded TyCommander, and when I open it, it sees the Teensy on COM5. There are bi-directional arrows with a slash through them (meaning comm port detected but serial not enabled?). When I try to 'enable serial', I get a red exclamation mark and 'Device COM5 not found.' Also, no output is showing in the serial tab, even though I expect it to. So I believe it doesn't work with TyCommander either.

Also, the same issue eventually occurred on a separate Win10 PC, so now Teensy doesn't work on either computer. I don't know what causes the issue to spontaneously start occurring, nor how to reset the system to get rid of it. I have tried all solutions listed on these forums (including changing/resetting COM port assignments in the registry), so I'm not sure what else I could do.
 
Last edited:
The Teensy is already talking to another app, or doesn't have a valid running USB/Serial interface would be the normal reasons for that behavior from TyCommander.

Open the "View / Show Application Log" perhaps the Full Log tab as well as 'Errors' - press the button and it should show the Teensy - then press the GUI Reset button and see what happens.
 
defragster: I am guessing the issue is that the Teensy USB/serial is tied up with something else, but I'm not sure what that would be (I have no other applications running). Below is the 'Full Log' with reset performed at the end, if that lends any insight. 'Errors' is just a subset of this.

MarkzP: Thanks for that. As far as I recall, I only connect the device after Windows has booted, but I may look into this further.

----

Listing USB host controllers and root hubs
Found root USB hub 'USB\ROOT_HUB20\4&DA1E41F&0' with ID 0
Found root USB hub 'USB\ROOT_HUB20\4&BF209D4&0' with ID 1
Found root USB hub 'IUSB3\ROOT_HUB30\4&2162133&0' with ID 2
Examining device node 'USB\VID_16C0&PID_0483\2592070'
Found port number of 'USB\VID_16C0&PID_0483\2592070': 2
Found controller ID for 'IUSB3\ROOT_HUB30\4&2162133&0': 3
Add serial device 'USB\VID_16C0&PID_0483\2592070' on iface 0
- USB VID/PID = 16c0:0483, USB location = usb-3-2
- USB manufacturer = Teensyduino, product = USB Serial, S/N = 2592070
Examining device node 'BTHENUM\{00001124-0000-1000-8000-00805F9B34FB}_VID&000217EF_PID&6038\8&2938F271&0&0002763D82B2_C00000000'
Unknown device type for 'BTHENUM\{00001124-0000-1000-8000-00805F9B34FB}_VID&000217EF_PID&6038\8&2938F271&0&0002763D82B2_C00000000'
Ignoring duplicate HID collection device 'HID\{00001124-0000-1000-8000-00805F9B34FB}_VID&000217EF_PID&6038&COL02\9&981E972&0&0001'
Examining device node 'USB\VID_046D&PID_C535&MI_00\7&2C49E626&1&0000'
Device 'USB\VID_046D&PID_C535&MI_00\7&2C49E626&1&0000' has no 'PortName' registry property
Examining device node 'USB\VID_046D&PID_C535&MI_01\7&2C49E626&1&0001'
Device 'USB\VID_046D&PID_C535&MI_01\7&2C49E626&1&0001' has no 'PortName' registry property
Examining device node 'BTHENUM\{84A1E9B8-12BA-4A9C-8AB0-A43784E0D149}_LOCALMFG&0000\8&2938F271&0&000000000000_00000000'
Unknown device type for 'BTHENUM\{84A1E9B8-12BA-4A9C-8AB0-A43784E0D149}_LOCALMFG&0000\8&2938F271&0&000000000000_00000000'
Examining device node 'HID\VID_046D&PID_C535&MI_01&COL01\8&11684E9C&0&0000'
Found port number of 'USB\VID_046D&PID_C535\6&9439DA6&0&2': 2
Found port number of 'USB\VID_8087&PID_0024\5&13461BF4&0&1': 1
Found controller ID for 'USB\ROOT_HUB20\4&BF209D4&0': 2
Add HID device 'HID\VID_046D&PID_C535&MI_01&COL01\8&11684E9C&0&0000' on iface 1
- USB VID/PID = 046d:c535, USB location = usb-2-1-2
- USB manufacturer = Logitech, product = Dell Wireless Mouse WM123, S/N = (none)
- HID usage page = 0xc, HID usage = 0x1
Ignoring duplicate HID collection device 'HID\VID_046D&PID_C535&MI_01&COL02\8&11684E9C&0&0001'
Ignoring duplicate HID collection device 'HID\VID_046D&PID_C535&MI_01&COL03\8&11684E9C&0&0002'
Device 'COM5' not found
[reset@2592070-Teensy] Resetting board '2592070-Teensy' (Teensy 3.2)
[reset@2592070-Teensy] Triggering board reboot
[reset@2592070-Teensy] Device 'COM5' not found
 
As a quick sanity check, try setting Tools > USB Type to one of the non-serial options, like MIDI. In those modes, HID is used to emulate serial so you can still use Serial.print(). Try running a program in that mode and see if you can print to the serial monitor. Yeah, I know even if this works it doesn't solve the COM port issue you're having. But at least knowing there is a non-serial way can help your sanity a bit and maybe give you a way to move forward.
 
Indeed do what Paul suggests - since TyComm can address the Teensy for RESET it is connected and working and coming up as HID will get registered in TyComm (with reported serial ###) so you can see it work - without exposing it as Serial where it is apparently being picked up by 'something' else. Then that should work until you can get to the root of the problem.
 
Okay, thanks for the suggestion. Using MIDI mode did in fact work when using TyCommander (though not with the Arduino SerMon: 'no connection'). The interface was given as 'Seremu' with path: \\.\HID#VID_16C0&PID_0485&MI_01#7&BDF7D36&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}. I then ran reset, which changed the interface name to 'HalfKay', and resulted in the Teensy waiting in bootloader mode.

Listing USB host controllers and root hubs
Found root USB hub 'USB\ROOT_HUB20\4&DA1E41F&0' with ID 0
Found root USB hub 'USB\ROOT_HUB20\4&BF209D4&0' with ID 1
Found root USB hub 'IUSB3\ROOT_HUB30\4&2162133&0' with ID 2
Examining device node 'BTHENUM\{00001124-0000-1000-8000-00805F9B34FB}_VID&000217EF_PID&6038\8&2938F271&0&0002763D82B2_C00000000'
Unknown device type for 'BTHENUM\{00001124-0000-1000-8000-00805F9B34FB}_VID&000217EF_PID&6038\8&2938F271&0&0002763D82B2_C00000000'
Examining device node 'USB\VID_16C0&PID_0485&MI_01\6&2FCCA65B&0&0001'
Device 'USB\VID_16C0&PID_0485&MI_01\6&2FCCA65B&0&0001' has no 'PortName' registry property
Examining device node 'HID\VID_16C0&PID_0485&MI_01\7&BDF7D36&0&0000'
Found port number of 'USB\VID_16C0&PID_0485\2592070': 2
Found controller ID for 'IUSB3\ROOT_HUB30\4&2162133&0': 3
Add HID device 'HID\VID_16C0&PID_0485&MI_01\7&BDF7D36&0&0000' on iface 1
- USB VID/PID = 16c0:0485, USB location = usb-3-2
- USB manufacturer = Teensyduino, product = Teensy MIDI, S/N = 2592070
- HID usage page = 0xffc9, HID usage = 0x4
Ignoring duplicate HID collection device 'HID\{00001124-0000-1000-8000-00805F9B34FB}_VID&000217EF_PID&6038&COL02\9&981E972&0&0001'
Examining device node 'USB\VID_046D&PID_C535&MI_00\7&2C49E626&1&0000'
Device 'USB\VID_046D&PID_C535&MI_00\7&2C49E626&1&0000' has no 'PortName' registry property
Examining device node 'USB\VID_046D&PID_C535&MI_01\7&2C49E626&1&0001'
Device 'USB\VID_046D&PID_C535&MI_01\7&2C49E626&1&0001' has no 'PortName' registry property
Examining device node 'BTHENUM\{84A1E9B8-12BA-4A9C-8AB0-A43784E0D149}_LOCALMFG&0000\8&2938F271&0&000000000000_00000000'
Unknown device type for 'BTHENUM\{84A1E9B8-12BA-4A9C-8AB0-A43784E0D149}_LOCALMFG&0000\8&2938F271&0&000000000000_00000000'
Examining device node 'HID\VID_046D&PID_C535&MI_01&COL01\8&11684E9C&0&0000'
Found port number of 'USB\VID_046D&PID_C535\6&9439DA6&0&2': 2
Found port number of 'USB\VID_8087&PID_0024\5&13461BF4&0&1': 1
Found controller ID for 'USB\ROOT_HUB20\4&BF209D4&0': 2
Add HID device 'HID\VID_046D&PID_C535&MI_01&COL01\8&11684E9C&0&0000' on iface 1
- USB VID/PID = 046d:c535, USB location = usb-2-1-2
- USB manufacturer = Logitech, product = Dell Wireless Mouse WM123, S/N = (none)
- HID usage page = 0xc, HID usage = 0x1
Ignoring duplicate HID collection device 'HID\VID_046D&PID_C535&MI_01&COL02\8&11684E9C&0&0001'
Ignoring duplicate HID collection device 'HID\VID_046D&PID_C535&MI_01&COL03\8&11684E9C&0&0002'


[reset@2592070-Teensy] Resetting board '2592070-Teensy' (Teensy 3.2)
[reset@2592070-Teensy] Triggering board reboot
Received removal notification for device 'HID\VID_16C0&PID_0485&MI_01\7&BDF7D36&0&0000'
Remove device 'HID\VID_16C0&PID_0485&MI_01\7&BDF7D36&0&0000'
Received removal notification for device 'USB\VID_16C0&PID_0485&MI_00\6&2FCCA65B&0&0000\{6994AD04-93EF-11D0-A3CC-00A0C9223196}\GLOBAL'
Received removal notification for device 'USB\VID_16C0&PID_0485&MI_00\6&2FCCA65B&0&0000\{65E8773E-8F56-11D0-A3B9-00A0C9223196}\GLOBAL'
Received removal notification for device 'USB\VID_16C0&PID_0485&MI_00\6&2FCCA65B&0&0000\{65E8773D-8F56-11D0-A3B9-00A0C9223196}\GLOBAL'
Received removal notification for device 'USB\VID_16C0&PID_0485\2592070'
Received arrival notification for device 'USB\VID_16C0&PID_0478\0003F487'
Examining device node 'USB\VID_16C0&PID_0478\0003F487'
Device 'USB\VID_16C0&PID_0478\0003F487' has no 'PortName' registry property
Received arrival notification for device 'HID\VID_16C0&PID_0478\6&7CB1E93&0&0000'
Examining device node 'HID\VID_16C0&PID_0478\6&7CB1E93&0&0000'
Found port number of 'USB\VID_16C0&PID_0478\0003F487': 2
Found controller ID for 'IUSB3\ROOT_HUB30\4&2162133&0': 3
Add HID device 'HID\VID_16C0&PID_0478\6&7CB1E93&0&0000' on iface 0
- USB VID/PID = 16c0:0478, USB location = usb-3-2
- USB manufacturer = (none), product = (none), S/N = 0003F487
- HID usage page = 0xff9c, HID usage = 0x21
Identified 'Teensy 3.2' with usage value 0x21
[reset@2592070-Teensy] Sending reset command
[reset@2592070-Teensy] Timed out while writing to '\\.\HID#VID_16C0&PID_0478#6&7CB1E93&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}'
[send@2592070-Teensy] Board '2592070-Teensy' is not available for serial I/O
 
That shows some signs of life - though I'm not the one to interpret the Koromix TyComm output or general device connection spew as shown. Maybe unplug - pause and plug in again. Not sure why RESET would go to 'bootloader' - there is a 'bootloader' GUI button that would do that? Perhaps having TeensyLoader open then 'Help / Verbose Info' might show something in Paul's format?

Try to compile with RAW HID? I've not done much outside of Serial - but the time I did have a HID Teensy it was good that TyComm would talk with it, where the IDE would not.

It seems there is something open in your system that is assuming/taking the Serial USB when it appears. Not sure if 'Task Manager' would point that out if not seen otherwise?
 
tni said:
Reset always goes into bootloader mode first. It's a 2-stage process, the bootloader can be instructed to do a reset. There is no direct reset function.
Click to expand...

opps - not sure why TyComm RESET would go to Bootloader and STICK in Bootloader. In my TyCommander(TyQt) use RESET always results in the device coming back online - not sticking in Bootloader. The GUI bootloader goes to bootloader - and Reset results in a restart through setup().
 
defragster said:
opps - not sure why TyComm RESET would go to Bootloader and STICK in Bootloader. In my TyCommander(TyQt) use RESET always results in the device coming back online - not sticking in Bootloader.
Click to expand...
Yes, the bootloader is immediately instructed to do the reset after it's enumerated.

That's the bootloader having come online:
Add HID device 'HID\VID_16C0&PID_0478\6&7CB1E93&0&0000' on iface 0

For some reason, sending the reset command to the bootloader doesn't work:
[reset@2592070-Teensy] Timed out while writing to '\\.\HID#VID_16C0&PID_0478#6&7CB1E93&0&0000#{4d1e5 5b2-f16f-11cf-88cb-001111000030}'

The serial emulation interface is PID_0486.
 
@tni - Thanks for the breakdown.

For reference here is a T_3.6 with simple sketch and MIDI serial to show where the above steps compare and diverge with TyComm Log:
[reset@2272860-Teensy] Resetting board '2272860-Teensy' (Teensy 3.6)
[reset@2272860-Teensy] Triggering board reboot
Received removal notification for device 'SWD\MMDEVAPI\MIDII_EF49EB23.P_0000'
Received removal notification for device 'SWD\MMDEVAPI\MIDII_EF49EB23.P_0001'
Received removal notification for device 'USB\VID_16C0&PID_0485&MI_00\7&21446228&0&0000\{6994AD04-93EF-11D0-A3CC-00A0C9223196}\GLOBAL'
Received removal notification for device 'USB\VID_16C0&PID_0485&MI_00\7&21446228&0&0000\{65E8773E-8F56-11D0-A3B9-00A0C9223196}\GLOBAL'
Received removal notification for device 'USB\VID_16C0&PID_0485&MI_00\7&21446228&0&0000\{65E8773D-8F56-11D0-A3B9-00A0C9223196}\GLOBAL'
Received removal notification for device 'HID\VID_16C0&PID_0485&MI_01\8&1D8F7108&0&0000'
Remove device 'HID\VID_16C0&PID_0485&MI_01\8&1D8F7108&0&0000'
Received removal notification for device 'USB\VID_16C0&PID_0485\2272860'
Received arrival notification for device 'USB\VID_16C0&PID_0478\000377D6'
Examining device node 'USB\VID_16C0&PID_0478\000377D6'
Device 'USB\VID_16C0&PID_0478\000377D6' has no 'PortName' registry property
Received arrival notification for device 'HID\VID_16C0&PID_0478\7&31331857&0&0000'
Examining device node 'HID\VID_16C0&PID_0478\7&31331857&0&0000'
Found port number of 'USB\VID_16C0&PID_0478\000377D6': 2
Found port number of 'USB\VID_0424&PID_2504\5&34472DFD&0&2': 2
Found controller ID for 'USB\ROOT_HUB20\4&37566865&0': 5
Add HID device 'HID\VID_16C0&PID_0478\7&31331857&0&0000' on iface 0
- USB VID/PID = 16c0:0478, USB location = usb-5-2-2
- USB manufacturer = (none), product = (none), S/N = 000377D6
- HID usage page = 0xff9c, HID usage = 0x22
Identified 'Teensy 3.6' with usage value 0x22
[reset@2272860-Teensy] Sending reset command
Received removal notification for device 'HID\VID_16C0&PID_0478\7&31331857&0&0000'
Remove device 'HID\VID_16C0&PID_0478\7&31331857&0&0000'
Received removal notification for device 'USB\VID_16C0&PID_0478\000377D6'
Received arrival notification for device 'USB\VID_16C0&PID_0485\2272860'
Examining device node 'USB\VID_16C0&PID_0485\2272860'
Device 'USB\VID_16C0&PID_0485\2272860' has no 'PortName' registry property
Received arrival notification for device 'USB\VID_16C0&PID_0485&MI_00\7&21446228&0&0000\{6994AD04-93EF-11D0-A3CC-00A0C9223196}\GLOBAL'
Device node 'USB\VID_16C0&PID_0485&MI_00\7&21446228&0&0000\{6994AD04-93EF-11D0-A3CC-00A0C9223196}\GLOBAL' does not exist: 0x1e
Received arrival notification for device 'USB\VID_16C0&PID_0485&MI_00\7&21446228&0&0000\{65E8773E-8F56-11D0-A3B9-00A0C9223196}\GLOBAL'
Device node 'USB\VID_16C0&PID_0485&MI_00\7&21446228&0&0000\{65E8773E-8F56-11D0-A3B9-00A0C9223196}\GLOBAL' does not exist: 0x1e
Received arrival notification for device 'USB\VID_16C0&PID_0485&MI_00\7&21446228&0&0000\{65E8773D-8F56-11D0-A3B9-00A0C9223196}\GLOBAL'
Device node 'USB\VID_16C0&PID_0485&MI_00\7&21446228&0&0000\{65E8773D-8F56-11D0-A3B9-00A0C9223196}\GLOBAL' does not exist: 0x1e
Received arrival notification for device 'HID\VID_16C0&PID_0485&MI_01\8&1D8F7108&0&0000'
Examining device node 'HID\VID_16C0&PID_0485&MI_01\8&1D8F7108&0&0000'
Found port number of 'USB\VID_16C0&PID_0485\2272860': 2
Found port number of 'USB\VID_0424&PID_2504\5&34472DFD&0&2': 2
Found controller ID for 'USB\ROOT_HUB20\4&37566865&0': 5
Add HID device 'HID\VID_16C0&PID_0485&MI_01\8&1D8F7108&0&0000' on iface 1
- USB VID/PID = 16c0:0485, USB location = usb-5-2-2
- USB manufacturer = Teensyduino, product = Teensy MIDI, S/N = 2272860
- HID usage page = 0xffc9, HID usage = 0x4
Received arrival notification for device 'SWD\MMDEVAPI\MIDII_EF49EB23.P_0000'
Examining device node 'SWD\MMDEVAPI\MIDII_EF49EB23.P_0000'
Unknown device type for 'SWD\MMDEVAPI\MIDII_EF49EB23.P_0000'
Received arrival notification for device 'SWD\MMDEVAPI\MIDII_EF49EB23.P_0001'
Examining device node 'SWD\MMDEVAPI\MIDII_EF49EB23.P_0001'
Unknown device type for 'SWD\MMDEVAPI\MIDII_EF49EB23.P_0001'
Click to expand...

And here is what TeensyLoader VERBOSE info shows when TyComm does the reset:
20:29:25.282: Device came online, code_size = 1048576
20:29:25.282: Board is: Teensy 3.6 (MK66FX1M0), version 1.03
20:29:25.283: set background IMG_ONLINE
20:29:25.532: HID/win32: HidD_GetPreparsedData failed, device assumed disconnected
20:29:25.533: Device went offline
20:29:25.777: HID/win32: vid:1B80 pid:B410 ver:0131
20:29:25.779: HID/win32: vid:1B80 pid:B410 ver:0131
20:29:25.780: HID/win32: vid:1B80 pid:B410 ver:0131
20:29:25.782: HID/win32: vid:1B80 pid:B410 ver:0131
20:29:25.783: HID/win32: vid:0764 pid:0501 ver:0001
20:29:25.784: HID/win32: vid:1B80 pid:B406 ver:0100
20:29:25.786: HID/win32: vid:1B80 pid:B406 ver:0100
20:29:25.788: HID/win32: vid:1B80 pid:B406 ver:0100
20:29:25.789: HID/win32: vid:1B80 pid:B406 ver:0100
20:29:25.789: HID/win32: vid:16C0 pid:0485 ver:0200
Click to expand...
 
Note: Above post worked with MIDI - when I went RAW HID it failed to come online - even with button press? I had to Press and plug in on a different USB port when to reprogram as MIDI.
 
Anyone find a solution to this? I am experiencing the same behavior on a Windows 10, Arduino IDE 1.8.3, Teensy loader 1.37. Basically I can upload a sketch but I can't communicate over serial com port.
One very un-scientific behavior. When I start up the IDE, I can open the Serial Monitor interface although it reports port is closed/busy. Close it. Then I try to open the plotter and nothing again seems to happen. Then I go back to open the Monitor and it says it can't open while plotter is open. Now I don't know what the plotter is, but nothing seems to be different in the GUI to indicate a plotter is open. I'm assuming the plotter is the Teensy loader but that doesn't appear to be open.
Steve
 
stevedog69 said:
Anyone find a solution to this? I am experiencing the same behavior on a Windows 10, Arduino IDE 1.8.3, Teensy loader 1.37. Basically I can upload a sketch but I can't communicate over serial com port.
Click to expand...
I assume both of you are talking about the SW serial port over USB.

At work I'm using Win 10, and the SW serial over USB either work or doesn't, and I couldn't figure out why it fails for no apparent reason, or find any pattern to those failures.

One bulletproof solution is to simply use the HW serial port (Serial1 on pin 2 and pin 3) -- that works flawlessly and reliably. You do need a MAX232 or similar chip, five 1 uF capacitor, a DB9 connector and a serial cable if your PC has a serial port, or a DB9 and a serial to USB adapter if it doesn't.
 
Stevedog69, unsure if you are using Teensy 3.2?

First off Serial plotter is not the teensy loader, but is a tool for allowing you to plot out values... There are several places on the web that talk about this, including: https://learn.adafruit.com/experimenters-guide-for-metro/using-the-arduino-serial-plotter

Don't have any information here like what program you are trying to run? How is your Teensyduino configured? like what is tools->usb type configured too?

If you are having problems opening the Serial terminal program, things to verify:
a) Did you configure the Port in the tools menu to be the one associated with your Teensy?
b) Have you tried rebooting to see if that resolves the issue.
c) Do you have some other apps running that may be talking to serial ports?
...

Good luck
 
KurtE said:
Stevedog69, unsure if you are using Teensy 3.2?

First off Serial plotter is not the teensy loader, but is a tool for allowing you to plot out values... There are several places on the web that talk about this, including: https://learn.adafruit.com/experimenters-guide-for-metro/using-the-arduino-serial-plotter

Don't have any information here like what program you are trying to run? How is your Teensyduino configured? like what is tools->usb type configured too?

If you are having problems opening the Serial terminal program, things to verify:
a) Did you configure the Port in the tools menu to be the one associated with your Teensy?
b) Have you tried rebooting to see if that resolves the issue.
c) Do you have some other apps running that may be talking to serial ports?
...

Good luck
Click to expand...

KurtE

Thanks for your reply, mine is a Teensy-LC and A) Yes, B) Yes and C) Not sure.
I'm trying to communicate via serial on a Windows 10 laptop to a Teensy-LC with a 12 LED Neopixel Ring. The only program I am running at the time of the effort is the Arduino IDE desktop app. Having said that, could it be that because at first I tried the web editor (and then learned it doesn't support Teensy)...even if I don't have a browser open somehow the online editor leaves a hook in place that would seem to act like another process? Just a wild thought? I don't want to clear all my web history just to test but maybe I will if you think the idea has merit.
Steve
 
Status
Not open for further replies.
Back
Top