Unsolved Bad command & Missing characters in Gcode since firmware upgrade

[norbs12]

@T3P3Tony It does seem to be only while printing though I have not had a chance to confirm that it's not related to temperature of the board. Meaning I have not tried uploading immediately after a long print.

[T3P3Tony]

@norbs12 ahh ok, if its only during a print thats still an issue but less of an issue!

[Vinculum]

I tried it right after week-long prints and no issue. Only while the printer is running while uploading I get this situation. Uploading when idle never gives issues.

[chrishamm]

@HBM-3D Maybe a trivial question but was there a deviation of the file sizes between your original and the uploaded file (in plain bytes)?

[kmhudgins]

Hi,
I am starting to have the same issue with bad commands. Was this problem every resolved?

[norbs12]

@kmhudgins said in Bad command & Missing characters in Gcode since firmware upgrade:

Hi,
I am starting to have the same issue with bad commands. Was this problem every resolved?

I ended up just avoiding uploading during a print that seems to have solved the issue for one board. I still have another board somewhere that it happens to all the time no matter if I'm printing or not that I gave up on.

[droftarts]

Optional CRC checking when uploading was added with RRF 2.04 and DWC 2.0.4, but otherwise there has been little progress on this, as far as I am aware.

@kmhudgins What firmware are you using? Are you uploading while the printer is printing?

Ian

[BlueDust]

@droftarts

I assume the CRC checking is enabled by default. How do you enable/disable them?
Can you have the Duet2 log the pass CRC codes confirming it is good, and not just the failed ones?

2019-11-04 21:06:28 Error: Uploaded file CRC is different (65e13ff3 vs. expected bcc41d9a)
2019-11-04 21:07:27 Error: Uploaded file CRC is different (9401d30a vs. expected bcc41d9a)
2019-11-04 21:08:17 Error: Uploaded file CRC is different (d7835b84 vs. expected bcc41d9a)

A month or so ago, I remember having trouble uploading files with a pop up saying that the CRC failed.
I don't remember what I did to correct it, but just thought it was my slicer having issues. Happy to know this is actually a "thing" and it wasn't just me.

[dc42]

@BlueDust said in Bad command & Missing characters in Gcode since firmware upgrade:

I assume the CRC checking is enabled by default. How do you enable/disable them?

It's at the bottom left of the Settings/Machine Specific page of DWC 2.04.

If the CRC errors only occur if you upload while printing, then maybe we need to reduce the SPI transfer speed to the Ethernet module if you upload while a print is active, or else adjust the bus priorities.

[norbs12]

@dc42 said in Bad command & Missing characters in Gcode since firmware upgrade:

@BlueDust said in Bad command & Missing characters in Gcode since firmware upgrade:

I assume the CRC checking is enabled by default. How do you enable/disable them?

It's at the bottom left of the Settings/Machine Specific page of DWC 2.04.

If the CRC errors only occur if you upload while printing, then maybe we need to reduce the SPI transfer speed to the Ethernet module if you upload while a print is active, or else adjust the bus priorities.

Would be possible to somehow make the SPI speed user configurable? I've got two boards, one that I just stopped using because of this and another that only works as long as I'm not printing. Would be awesome to recover the other board and use it for something.