Topics created by Vinculum

@Vinculum See https://github.com/Duet3D/RepRapFirmware/wiki/HTTP-requests#get-rr_thumbnail

@chrishamm Great, I'm waiting to experience. I see on Github : https://github.com/Duet3D/DuetPrintFarm

Each time this happens can you gather a M122 report and share it here? That would be most helpful in isolating the issue. It would also help to share the config.g file set and sample gcode to help in duplicating it.

The only other thing I can suggest in the meantime is to try updating to 3.4.1 in case a fix in there helps.

@dc42 Looking forward to it! Thank you all for the help.

@hbm-3d Most of the SBC's should work. As long as it has a kernal newer than 4.19 you should be fine.
We have an all in one board on the STM32 port than uses an Allwinner H5 chip and that runs DSF fine. You'll just need to do a bit of work to work out which port to use for the transfer ready pin.
We also have instructions here for getting DSF installed on Armbian https://teamgloomy.github.io/dsf_on_armbian.html

@hackinistrator
You dir sir are my hero of the day. Turned the bed heater off after the first layer et voila:
Foto 28-12-2021 10 32 26.jpg

So i checked the config with the other printers. It is not completely the same (others are Duet 2 with RRF2) but i missed 1 tiny thing.
This line: M307 H0 B1 S1.00
The B1 had to be a B0... 😤

Problem solved, case closed. I thank you all for your time and input!

@hbm-3d
I'd guess you have a CAN bus problem; interference from other wiring, bad termination or a bad connection, so some data is being corrupted and causing the system to misbehave.

A power brownout that did not cause a full reset at the toolboard could also give a similar effect, again possibly a bad connection somewhere?

Are the CAN connections either twisted pair in each run, or well separated from other wiring ?

@jay_s_uk
Nope.

@zemlin https://github.com/Duet3D/RepRapFirmware/releases

@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.