"Command not found!" messages

Dreide

I have Firmware v1.0.2(dev) installed and Repetier host v2.1.3 shows rather frequently the message "Command not found!". What command(s) might Repetier refer to?
It seems to occur more often when more stuff has to be sent to the printer (via USB), but the message appears occasionally also when printing from SD card while Repetier host is still connected. The same happens with an older Repetier host version (v2.1.0 I think it was).

22:31:26.255 : ok 7336
22:31:26.255 : N7342 G1 X95.436 Y119.884 E26.8713*105
22:31:26.255 : Command not found!
22:31:26.271 : Echo:N7336 G1  X95.14 Y124.18 E26.6458
22:31:26.271 : ok 7337
22:31:26.271 : N7343 G1 X95.550 Y119.721 E26.8817*98
22:31:26.287 : Echo:N7337 G1  X95.25 Y123.76 E26.6686
22:31:26.287 : ok 7338
22:31:26.287 : N7344 G1 X95.675 Y119.589 E26.8911*102
22:31:26.302 : Echo:N7338 G1  X95.27 Y120.40 E26.8430
22:31:26.302 : ok 7339
22:31:26.302 : Echo:N7339 M532  X82.90 L18.00
22:31:26.302 : N7345 G1 X95.905 Y119.425 E26.9058*109
22:31:26.302 : ok 7340
22:31:26.302 : N7346 G1 X96.084 Y119.343 E26.9160*96
22:31:26.318 : Echo:N7340 G1  X95.30 Y120.25 E26.8511
22:31:26.318 : ok 7341
22:31:26.318 : N7347 G1 X96.264 Y119.294 E26.9257*97
22:31:26.333 : Echo:N7341 G1  X95.36 Y120.05 E26.8617
22:31:26.333 : ok 7342
22:31:26.333 : N7348 G1 X98.670 Y119.270 E27.0508*110
22:31:26.333 : Echo:N7342 G1  X95.44 Y119.88 E26.8713
22:31:26.333 : ok 7343
22:31:26.333 : N7349 G1 Y80.505 E29.0654*57
22:31:26.349 : Echo:N7343 G1  X95.55 Y119.72 E26.8817
22:31:26.349 : ok 7344
22:31:26.349 : N7350 G1 X98.721 Y79.774 F4800*125
22:31:26.349 : N7351 G1 X98.77 Y79.512*32
22:31:26.365 : Echo:N7344 G1  X95.68 Y119.59 E26.8911
22:31:26.365 : ok 7345
22:31:26.365 : N7352 G1 X99.296 Y79.422 F15000*79
22:31:27.815 : Echo:N7345 G1  X95.90 Y119.43 E26.9058
22:31:27.815 : ok 7346
22:31:27.815 : N7353 M532 X83.1 L18*28
22:31:27.831 : Echo:N7346 G1  X96.08 Y119.34 E26.9160
22:31:27.831 : ok 7347
22:31:27.831 : N7354 G92 E0*114
22:31:27.847 : Echo:N7347 G1  X96.26 Y119.29 E26.9257
22:31:27.847 : ok 7348
22:31:27.847 : N7355 G1 X99.436 Y78.938 E0.0262 F3288*11
22:31:27.847 : Command not found!
22:31:27.847 : Echo:N7348 G1  X98.67 Y119.27 E27.0508
22:31:27.847 : ok 7349
22:31:27.847 : N7356 G1 X99.551 Y78.643 E0.0427*107

Repetier

Are you sure you are using Repetier-Firmware? Or is it a fork? Haven't found the message in host so it must come from the firmware. If you enable logging and check the real log it would be clear as you can see the direction.

Would guess it refers to M532 which is a fairly new status update so printers can show progress in display. It is no big deal if this is ignored as it has no printing function just information update.

Dreide

I downloaded the firmware Tuesday from https://github.com/repetier/Repetier-Firmware/tree/development, but I cannot find the string anywhere in there. Log confirms that it comes from the firmware indeed - digging further.

> 21:56:43.515 : busy:processing
> 21:56:44.467 : T:23.00 /0 B:23.75 /0 B@:0 @:0
> 21:56:45.512 : busy:processing
> 21:56:45.559 : T:22.62 /0 B:24.03 /0 B@:0 @:0
> 21:56:45.918 : X:110.00 Y:110.00 Z:20.000 E:0.0000
> 21:56:45.918 : ok 23
> 21:56:45.918 : X_OFFSET:0.000 Y_OFFSET:0.000 Z_OFFSET:0.000
> 21:56:45.918 : ok 24
> 21:56:45.918 : ok 25
< 21:56:45.918 : N30 M117 ETE 14m 03s*123
< 21:56:45.918 : N31 G1 X58.567 Y76.212 E0.0490*100
> 21:56:45.918 : ok 26
> 21:56:45.918 : ok 27
< 21:56:45.918 : N32 G1 X59.070 Y75.942 E0.0787*109
< 21:56:45.918 : N33 G1 X59.472 Y75.763 E0.1015*106
> 21:56:45.918 : ok 28
< 21:56:45.918 : N34 G1 X60.012 Y75.571 E0.1313*97
> 21:56:45.918 : Command not found!
> 21:56:45.933 : ok 29
< 21:56:45.933 : N35 G1 X60.716 Y75.394 E0.1691*97
> 21:56:45.933 : ok 30
< 21:56:45.933 : N36 G1 X61.718 Y75.276 E0.2215*107
> 21:56:45.949 : Command not found!
> 21:56:45.949 : ok 31
< 21:56:45.949 : N37 G1 X66.997 Y75.270 E0.4959*103
> 21:56:45.965 : ok 32
< 21:56:45.965 : N38 G1 X67.725 Y75.324 E0.5338*98
> 21:56:45.965 : ok 33
< 21:56:45.965 : N39 G1 X68.268 Y75.428 E0.5626*97
> 21:56:45.965 : ok 34
< 21:56:45.965 : N40 G1 X68.638 Y75.534 E0.5826*108
> 21:56:45.965 : ok 35

Repetier

Yes mysterious. Firmware would send 

Unknown Command:M532 .....

Dreide

Solved it. The message was sent by the USB bridge (Atmega32u2 on the Einsy board of a Prusa Mk3), but ultimately, the message must have been triggered by the main firmware, because with Prusa-Marlin or Original-Marlin I have never seen it. Anyway, I got rid of this annoyance by flashing the USB bridge with the standard Arduino firmware.

Repetier

So you have the Prusa MK3 original working with our software:-) Can you send me the configuration as I'm also now having this printer. I still have your other thread open where you explain how to modify it so I can include that.

Repetier

Do you know the sources for the original version? I searched here
https://github.com/prusa3d/rambo-32u2-usbserial
bit did not find the string. Wanted to know what triggers the command not found on the bridge. After all it is not supposed to send any extra data - that is quite unexpected behaviour when you are talking.

Dreide

Unfortunately, I managed to put my printer in an unusable state. Wanted to go back to Marlin to check something, but couldn't because Repetier host would now receive different unknown commands, like "" and "?", and block communication completely. Tried to fix this by flashing also the bootloader (ATmege2560) - didn't help. Went back to Repetier firmware - now the BLtouch doesn't deploy when homing (yes, no PINDA anymore), ... :-(

Anyway, I couldn't find any sources of the USB bridge either - so far for Prusa & Open source. I just found the string in the firmware dump (attached). Also dumped the EEPROM. I have no idea what is going on; I suspect one of Prusa's numerous "Extrawürste".

Dreide

The unknown commands ("" and "?") with Marlin were caused by Repetier-host detecting Repetier protocol. After having forced it to ASCII it works much better now :-)

Repetier

Yes, binary and marlin do not match. Our firmware shoudl also be able to activate BLTouch if you put the server activate command in the start script before each probe.