repetier
commented
6 years ago New update might have set a different baud rate causing the connection problem. So fix is use new baud rate. If it has a lcd you can see baud rate in config.
Open jstockton opened 6 years ago
repetier
commented
6 years ago New update might have set a different baud rate causing the connection problem. So fix is use new baud rate. If it has a lcd you can see baud rate in config.
jstockton
commented
6 years ago Thanks for the idea. I checked the baud rates before I flashed and they matched. For kicks I tried changing it both on the printer and OctoPi to see if that got any results. I dropped it to 9600 and still had the same results.
I do have a LCD so I can change some settings, but since I can't connect via USB (tried a new USB cable as well) I won't be able to flash any different settings.
repetier
commented
6 years ago When you change in LCD you need to select store to eeprom afterwards or the setting will be lost on next reset which is required to make the change effective. Normally on connect it resets but some boards don't. So make sure you see in lcd a reset when connection is tried and check baud rate then to see if it was really taken.
jstockton
commented
6 years ago I did store to EEPROM and confirmed the setting stuck by rebooting the printer. Original baud was 115200. I tried 9600 and 250000. No luck.
I did notice some messed up information in the log that I didn't see before:
2017-12-22 22:45:52,195 - Connecting to: /dev/ttyUSB0
2017-12-22 22:45:52,206 - Changing monitoring state from 'Offline' to 'Opening serial port'
2017-12-22 22:45:52,211 - Connected to: Serial
shaiss
commented
5 years ago under serial connection > Firmware & Protocal > Protocal Fine Tuning > Blocked Commands add M110. Alternatively, M110 could be added to repetier fw to have the same behaviour like marlin.
I have a Tronxy/Zonestar P802M and recently updated the firmware to 0.92.9 and now cannot connect to my printer through either Repetier Host or Octopi. I didn't see anything in the logs that would indicate any issues, but could have missed something or not looked in the correct spot for logs.
Any suggestions on what I can do to fix the connection issue?