Cannot connect through Pronterface
-
When I try to connect through Pronterface with the USB cable on my Duet Wifi's, it works totally fine. But then I try it with Duet Ethernet - it doesn't work. Strangely though, Pronterface reports the temperatures of my extruders, but I can't actually send any data - I get the error below (and the temperatures continue to be reported):
M552
[ERROR] Printer is not online.
T0:112.2 /0.0 T1:112.3 /0.0 T2:1.6 /0.0 B:24.2 /0.0
T0:112.1 /0.0 T1:112.3 /0.0 T2:1.6 /0.0 B:24.2 /0.0
T0:112.2 /0.0 T1:112.3 /0.0 T2:1.6 /0.0 B:24.2 /0.0 -
DWC works fine though when I connect through the network.
-
The Duet does show up in the Mac System Information as "Duet"
-
@jml but pronterface just will not connect. Only will receive the temperature data.
-
Are the WiFi and Ethernet Duets running the same firmware version? Are both set to Marlin compatibility mode in the M555 command in config.g?
-
They are the same firmware on each. Probably slightly different config.g files though. In the Duet Ethernet config.g file, I have:
M555 P1 ; Set firmware compatibility to look like RepRapFirmareBut now that I'm checking, I see that the other Duet's config.g has M555 P2 because it has the SD card that shipped with the Duet Ethernet (because I was replacing the Duet Wifi with the Duet Ethernet so switched their SD cards).
Is that a problem to have M555 P1?
On the Duet Wifi, from the M115 command (via pronterface):
FIRMWARE_VERSION: 2.01beta3(RTOS) ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2018-07-25b1Duet Ethernet won't connect to Pronterface. But if I remove the SD card, unplug the USB, restart Pronterface, plug USB back in, it will connect!
On the Duet Ethernet from the M115 command (via Pronterface with no SD card inserted):
FIRMWARE_VERSION: 2.01beta3(RTOS) ELECTRONICS: Duet Ethernet 1.02 or later + DueX5 FIRMWARE_DATE: 2018-07-25b1 -
@jml said in Cannot connect through Pronterface:
Is that a problem to have M555 P1?
Yes, that will stop Pronterface working, because Pronterface expects an "ok" response after each command is processed.
-
Ok I'll change it back to M555 P2 and try Pronterface again. I don't remember ever adding or changing it to P1, but I probably just saw M555 there one day, googled its function and thought that it would make sense to be P1 since it is running reprapfirmware so might as well have output that looks like reprapfirmware.
-
M555 P2 in the config file allowed me to connect to pronterface. Thanks!
In what scenario would M555 P1 be useful or necessary?
-
@jml said in Cannot connect through Pronterface:
M555 P2 in the config file allowed me to connect to pronterface. Thanks!
In what scenario would M555 P1 be useful or necessary?
The scenario is that you want to send GCodes at a higher rate and get better status reports back than you can with Pronterface.
Years ago we had a patch for Pronterface to stop it waiting for 'ok' after sending every line, and that patch greatly increased the maximum sending speed.
