Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
Serial.list() error
This is a issue with the Serial.list(), when you are connected to a port as in
myPort = new Serial(this, Serial.list[1], 9600);
and you pull the COM cable your connected to, the Serial.list() has some kind of runtime error and will never clear out the old ports.
I can add to the Serial.list() array by adding more COM ports but the old ones never get removed like they would before you improperly disconnected.
Meaning if Serial.list()[1] is COM3, and you pull the connection, Serial.list()[1] will forever have COM3 listed, if you add a different COM like Serial.list()[2] is COM4 that adds but it also will never remove that listing.
I've proven this to be true over several tests, most noticeable being that Serial.list().length will never get shorter, only longer.
How do you get processing to recover from this without a restart?
Note: I can still myPort.stop() and then reconnect to the ports if I plug them back in, but without the Serial.list() updating correctly I'm finding it really hard to detect the cable pull while in the running loop. Having a timeout counter for serial data is sloppy and not always relevant to the application.