Some parts of DCS are broken in v3.4.0?
-
Hello everyone,
We use a Repetier Server frontend to communicate with DCS through the interceptor RS implemented in their 1.1.0 server version which was fully working in RRF 3.3 in SBC mode.
This way we have access to DWC on ex:192.168.2.100:3000 for advanced and tech support and Repetier Server on 192.168.2.100:3344 for enduser limited enviromental though a bidirectional communication between them through the serial port shared by both Duet and SBC boards. 6HC is conected with the flat cable to the RPI.
This was fully functional in RRF3.3, but with 3.4 it no longer works.
This is a console example of the behaviour from RS:
Send:12:05:16.916: N43 M105 Send:12:05:17.913: N44 M105 Send:12:05:18.905: N45 M105 Send:12:05:19.896: N46 M105 Send:12:05:20.888: N47 M105 Send:12:05:21.880: N48 M105 Send:12:05:22.873: N49 M105 Send:12:05:23.865: N50 M105 Send:12:05:24.857: N51 M105 Send:12:05:25.849: N52 M105 Send:12:05:26.840: N53 M105 Send:12:05:27.831: N54 M105 Send:12:05:28.823: N55 M105 Send:12:05:29.821: N56 M105 Send:12:05:30.817: N57 M105 Send:12:05:31.813: N58 M105 Send:12:05:32.803: N59 M105 Send:12:05:33.793: N60 M105 Send:12:05:34.789: N61 M105 Recv:12:05:42.686: The height map was loaded when the current Z=0 datum was not determined. This may result in a height offset. Height map loaded from file heightmap.csv (2) Recv:12:05:53.091: pos absolute true Recv:12:06:00.952: pos relative true Recv:12:06:09.389: X:0.000 Y:0.000 Z:20.010 E:0.000 E0:-0.0 E1:-0.0 E2:-0.0 Count 0 0 2003 Machine 0.000 0.000 20.010 Bed comp 0.000 (2) Recv:12:06:12.041: pos relative true Recv:12:06:12.063: pos absolute true Recv:12:06:12.484: X:0.000 Y:0.000 Z:79.748 E:0.000 E0:-0.0 E1:-0.0 E2:-0.0 Count 0 0 7984 Machine 0.000 0.000 79.748 Bed comp 0.000 (2) Recv:12:06:12.557: Mesg:12:07:05.794: Warning: Communication timeout - resetting communication buffer. Mesg:12:07:05.794: Connection status: Buffered:288, Manual Commands: 5, Job Commands: 0 Mesg:12:07:05.794: Buffer used:288 Enforced free byte:9 lines stored:32 Send:12:07:05.794: N62 M114 Send:12:07:05.795: N63 M114 Send:12:07:05.795: N64 M114 Send:12:07:05.795: N65 M114 Send:12:07:05.795: N66 M105 Send:12:07:05.795: N67 M105 Recv:12:07:05.869: ok T0:24.1 /0.0ok T0:24.1 /0.0 T1:24.4 /0.0 T2:24.7 /0.0ok T0:24.0 /0.0 T1:24.4 /0.0 T2:24.7 /0.0 B:23.4 /0.0 C:22.9 /0.0ok T0:23.9 /0.0 T1:24.6 /0.0 T2:24.5 /0.0 B:23.4 /0.0 C:22.7 /0.0ok T0:24.1 /0.0 T1:24.3 /0.0 T2:24.7 /0.0 B:23.3 /0.0 C:22.8 /0.0ok T0:24.0 /0.0 T1:24.4 /0.0 T2:24.7 /0.0 B:23.4 /0.0 C:22.8 /0.0ok T0:23.9 /0.0 T1:24.6 /0.0 T2:24.5 /0.0 B:23.4 /0.0 C:22.8 /0.0ok T0:24.1 /0.0 T1:24.4 /0.0 T2:24.7 /0.0 B:23.4 /0.0 C:22.8 /0.0ok T0:23.9 /0.0 T1:24.6 /0.0 T2:24.5 /0.0 B:23.3 /0.0 C:22.8 /0.0ok T0:23.9 /0.0 T1:24.6 /0.0 T2:24.5 /0.0 B:23.3 /0.0 C:22.8 /0.0ok T0:24.0 /0.0 T1:24.5 /0.0 T2:24.6 /0.0 B:23.3 /0.0 C:22.8 /0.0ok T0:24.1 /0.0 T1:24.3 /0.0 T2:24.7 /0.0 B:23.4 /0.0 C:22.9 /0.0ok T0:23.9 /0.0 T1:24.6 /0.0 T2:24.6 /0.0 B:23.3 /0.0 C:22.8 /0.0ok T0:23.9 /0.0 T1:24.6 /0.0 T2:24.5 /0.0 B:23.3 /0.0 C:22.8 /0.0ok T0:24.1 /0.0 T1:24.3 /0.0 T2:24.7 /0.0 B:23.3 /0.0 C:22.8 /0.0ok T0:24.1 /0.0 T1:24.3 /0.0 T2:24.7 /0.0 B:23.4 /0.0 C:22.9 /0.0ok T0:23.9 /0.0 T1:24.6 /0.0 T2:24.5 /0.0 B:23.3 /0.0 C:22.7 /0.0ok T0:23.9 /0.0 T1:24.5 /0.0 T2:24.5 /0.0 B:23.4 /0.0 C:22.8 /0.0ok T0:24.1 /0.0 T1:24.3 /0.0 T2:24.7 /0.0 B:23.4 /0.0 C:22.8 /0.0ok T0:24.0 /0.0 T1:24.6 /0.0 T2:24.6 /0.0 B:23.3 /0.0 C:22.8 /0.0ok T0:23.9 /0.0 T1:24.6 /0.0 T2:24.5 /0.0 B:23.4 /0.0 C:22.8 /0.0ok T0:24.1 /0.0 T1:24.2 /0.0 T2:24.7 /0.0 B:23.4 /0.0 C:22.8 /0.0ok T0:24.1 /0.0 T1:24.3 /0.0 T2:24.7 /0.0 B:23.3 /0.0 C:22.8 /0.0ok T0:23.9 /0.0 T1:24.6 /0.0 T2:24.5 /0.0 B:23.4 /0.0 C:22.8 /0.0ok T0:23.9 /0.0 T1:24.5 /0.0 T2:24.5 /0.0 B:23.4 /0.0 C:22.8 /0.0ok T0:24.1 /0.0 T1:24.3 /0.0 T2:24.8 /0.0 B:23.3 /0.0 C:22.8 /0.0ok T0:24.0 /0.0 T1:24.5 /0.0 T2:24.5 /0.0 B:23.4 /0.0 C:22.9 /0.0ok T0:24.0 /0.0 T1:24.3 /0.0 T2:24.6 /0.0 B:23.4 /0.0 C:22.8 /0.0ok T0:24.1 /0.0 T1:24.2 /0.0 T2:24.8 /0.0 B:23.4 /0.0 C:22.8 /0.0ok T0:23.9 /0.0 T1:24.4 /0.0 T2:24.6 /0.0 B:23.4 /0.0 C:22.8 /0.0ok T0:23.9 /0.0 T1:24.4 /0.0 T2:24.6 /0.0 B:23.4 /0.0 C:22.8 /0.0ok T0:24.2 /0.0 T1:24.2 /0.0 T2:24.8 /0.0 B:23.4 /0.0 C:22.9 /0.0ok T0:24.1 /0.0 T1:24.2 /0.0 T2:24.8 /0.0 B:23.4 /0.0 C:22.8 /0.0ok T0:24.0 /0.0 T1:24.4 /0.0 T2:24.6 /0.0 B:23.4 /0.0 C:22.8 /0.0ok T0:24.0 /0.0 T1:24.3 /0.0 T2:24.7 /0.0 B:23.4 /0.0 C:22.9 /0.0ok T0:24.1 /0.0 T1:24.2 /0.0 T2:24.8 /0.0 B:23.3 /0.0 C:22.8 /0.0ok T0:24.0 /0.0 T1:24.4 /0.0 T2:24.6 /0.0 B:23.2 /0.0 C:22.8 /0.0ok T0:24.0 /0.0 T1:24.4 /0.0 T2:24.6 /0.0 B:23.4 /0.0 C:22.8 /0.0ok T0:24.1 /0.0 T1:24.2 /0.0 T2:24.8 /0.0 B:23.3 /0.0 C:22.8 /0.0ok T0:24.1 /0.0 T1:24.2 /0.0 T2:24.8 /0.0 B:23.3 /0.0 C:22.8 /0.0X:0.000 Y:0.000 Z:79.748 E:0.000 E0:-0.0 E1:-0.0 E2:-0.0 Count 0 0 7984 Machine 0.000 0.000 79.748 Bed comp 0.000 Recv:12:07:05.871: ok Recv:12:07:05.871: X:0.000 Y:0.000 Z:79.748 E:0.000 E0:-0.0 E1:-0.0 E2:-0.0 Count 0 0 7984 Machine 0.000 0.000 79.748 Bed comp 0.000 Recv:12:07:05.871: ok Recv:12:07:05.872: X:0.000 Y:0.000 Z:79.748 E:0.000 E0:-0.0 E1:-0.0 E2:-0.0 Count 0 0 7984 Machine 0.000 0.000 79.748 Bed comp 0.000 Recv:12:07:05.872: ok
You can see that the M105 queries get no "ok“ response directly.
Only once other gcode is sent an "ok“ with a return gets sent and all is received.The problem is that the M105 responses have no final new line ("\n“) so it does not get sent to server, And then we get a command block, which is handled as one command, so it stop the commands being sent until timeout. Then it starts again.
So most essential is to make M105 answer add a return at end of line as the standard requires. M114 for example does that, and other commands as well.
When issued the commands from DWC use a different channel and method communicating with DCS and DCS probably does not use the same communication method than before in RRF3.3.
Repetier guys develop the comunication on a marlin compatible channel listing that in theory should provide same communication as direct usb connection for better standarization and use the DSF socket conection.This used to work previously so I guess it was broken it unexpectedly.
Can you please check this problem, help to troubleshoot and if possible fix it soon?
-
@marcossf Thanks for the note, it will be fixed in the upcoming v3.4-b5.