Teensy 4.1 - Serial Monitor stops reporting, and have to restart monitor?

Status
Not open for further replies.

jdredd

Active member
I am send/recv serial data from A device.

Serial monitor showing stuff that I am outputting via Serial while its running.

Serial monitor eventually stops showing anything I am outputting to Serial.

If I close it down the Serial Monitor and reopen it, it works again.

Is this an issue you think the Arduino IDE 1.8.16 ... or whatever background magic to show Serial between Teensy devices and the Arduino IDE?

Video @ https://www.youtube.com/watch?v=LvQCr9EynZ8 , showing what I am talking about.

Like to think its Arduino IDE I hope.

Only seems to happen when spitting lots of data out to it repeatedly.
 
What OS? { shows Win 10 in the vid }

What version of TeensyDuino?

If using the Teensy Serial Monitor choice from ports?

The output in the vid didn't look super fast ... that can cause it sometimes.

Running current much faster than that doesn't typically exhibit those issues. Not sure if maybe the computer or cable ?
 
What OS? { shows Win 10 in the vid }

What version of TeensyDuino?

If using the Teensy Serial Monitor choice from ports?

The output in the vid didn't look super fast ... that can cause it sometimes.

Running current much faster than that doesn't typically exhibit those issues. Not sure if maybe the computer or cable ?

-Windows 11
-TeensyDuino 1.55

Don't quite get this? "If using the Teensy Serial Monitor choice from ports?"

com1.png

SOMETIMES it seems ok and go 10-15+ minutes and it is happy.

Data wise, no its not a lot, and not very fast either.

Code wise.. nothing to crazy.

Code:
  while (1) {
    delay(1);
    if (ir.available()) { // check IR sensor for input
      irV = ir.readPacket();
      if (irV == hexSTAR) { // * key = abort
        break;
      }
    } else if (Serial1.available()) { // dump out Serial1 input.
      char c = Serial1.read();
      Serial.print(c);
    } 
    
    checktime = millis();
    elapsedtime = checktime - starttime;
    if (elapsedtime >= 2500) {
      send("", 50); // force the STN to stop
      delay(50);
      send("3F", 50); // 3F to keep PCM dumping data
      starttime = millis(); // reset clock
    }
  }
 
Yes, that 'Teensy Ports uses the PJRC Teensy Serial Monitor code.

You can try the other 'Com## (Teensy)' - it may show something different - though the Teensy version is generally faster and better choice.
 
com2.png

If I switch to the other Com... COM13 (Teensy) in this case, I left it up for over 20 minutes and no problem.

Switch back to COM13 Serial (Teensy 4.1) and pretty much "dies" in under A minute.

Go back and forth and same results. One goes on forever it seems ok, other one stops in under a minute.

I've rebooted the system and such since and still the same results.
 
Please try 1.56-beta2.

https://forum.pjrc.com/threads/68386-Teensyduino-1-56-Beta-2

1.56-beta1 has a "Fix serial monitor stall on Windows" and 1.56-beta2 also has "Fix rare serial monitor stall on Windows". Difficult to know if the specific problem you're experiencing is due to either of these 2 bugs, or maybe a previously unknown problem. But before spending a lot of time on this, at least try 1.56-beta2 because 2 bugs on Windows were recently found and fixed.
 
Please try 1.56-beta2.

https://forum.pjrc.com/threads/68386-Teensyduino-1-56-Beta-2

1.56-beta1 has a "Fix serial monitor stall on Windows" and 1.56-beta2 also has "Fix rare serial monitor stall on Windows". Difficult to know if the specific problem you're experiencing is due to either of these 2 bugs, or maybe a previously unknown problem. But before spending a lot of time on this, at least try 1.56-beta2 because 2 bugs on Windows were recently found and fixed.

Oh nice! Sorry I didn't look at Beta notes. I was figuring something I broke since I am new to this.
 
Please try 1.56-beta2.

https://forum.pjrc.com/threads/68386-Teensyduino-1-56-Beta-2

1.56-beta1 has a "Fix serial monitor stall on Windows" and 1.56-beta2 also has "Fix rare serial monitor stall on Windows". Difficult to know if the specific problem you're experiencing is due to either of these 2 bugs, or maybe a previously unknown problem. But before spending a lot of time on this, at least try 1.56-beta2 because 2 bugs on Windows were recently found and fixed.

Well the 1.56-beta2 seems ok.

Program still compiles and runs and been over 10 minutes and still going strong.
 
Good news, TD 1.56 b2 was where it seemed this was heading.

The output seemed slow enough that seeing IDE SerMon work would prove all else was well.
 
Status
Not open for further replies.
Back
Top