@dc42
at my first try, the sensors didn´t work(3.3beta1/3). One day later, without any changes they did work(3.3beta3and 3.3RC1). Since then they do work and only the M122 readout is wrong(3.3RC1).

@mauricem Perfect!
Happy printing! 👍

@fcwilt its an anycubic chiron ultrabase

this is what i got when i ran m997 b1

12/31/2020, 10:26:56 PM m997 b1
Error: M997: Response timeout: CAN addr 1, req type 6024, RID=0
12/31/2020, 10:26:56 PM Connection to Duet established
12/31/2020, 10:26:55 PM Warning: Lost connection to Duet (Timeout while waiting for transfer ready pin)

@pgoellner in your screenshot you use reprapFirmware 3.2Beta4.1, but for 3.1.1 you need a different version. Go to github, go to tags, download the zip of tag version 3.1.1. This version will fit to the 3.1.0 libraries. DuetWifiSocketServer is not needed for compilation.

If you want to use the newest beta build instead, I would choose a version which is tagged for RRF and all libraries. CoreNG is replaced by CoreN2G, so this is probably to be used instead for the newest builds.

When compiling, is is sufficient to set the target in RRF, clean the project and compile. It will start compiling all libraries with the target and with the original set targets of the libraries (a bug), then RRF.

@dc42 Ohhh thankyou i did not know that i was just using the info from my generator and my well pump starting load vs running load lol

@dc42 Thanks, that solve my Problem 🙂 . This should perhaps be covered by a "DEBUG-BUILD-FLAG".

All I can add is that there is a bug fix release for 2.05.1 that you should probably update to.

https://github.com/Duet3D/RepRapFirmware/releases/tag/2.05.1

Yes, you can use the same update process as normal to go to whatever version you like. Keep in mind the difference in config between the two.

@Danal
The heater erratic behavior is on the configurator page only at https://configtool.reprapfirmware.org/Mapping
It's perfectly fine on the printer itself! I actually managed to finally get a calibration cube out of it 😄

Thanks for confirming the case of M500.. Yeah 😛 I ended up doing the M307 for H0 and H1 by hand and filling them up there and then doing the M665 and M666 as well. (I'll move them to the config.g since they don't really need to live in the override either.)

So far so good!

I'm all new to RepRapFirmware and coming from old Repetier 8 bit world. 😆

Have you disconnectede everything from the Duet except USB?

Are any components getting hot? In particular, check the SD card, W5500 chip, and main processor.

maybe the 5mm requirement makes this possible by means of a trigger

try creating a M581 E0 T2 trigger for E0 endstop, and in the /sys/trigger2.g file do

G0 E5 M582 T2

that should make it move 5mm, and if the trigger condition is still asserted then it should run the trigger again, and again. You may have to experiment with the S parameter for rising or falling edge of the trigger to get the desired effect.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M581_Configure_external_trigger

I may just get some shielded cable off Ali express and put that in.

Another though, would ferrite beads work on the endstops to shield noise?

Kind Regards,

Sam

I tried a different cable, and every USB port on my computer with no success. I went through the “what to do if your duet won’t respond” guide on the website too. I didn’t have a different computer to use but it’s possible that would’ve fixed the problem. After rebooting the computer multiple times and rebooting the duet multiple times, it did eventually get a connection and I was able to reflash the firmware. Not sure why though.

It's good to have friends nearby that can help out quickly (-:

$ "C:\Program Files (x86)\BOSSA\bossac.exe" --port=COM3 -e -w -v -b PanelDue-5.0i-7.0i.bin Erase flash Done in 1.038 seconds Write 168276 bytes to flash (329 pages) [==============================] 100% (329/329 pages) Done in 5.911 seconds Verify 168276 bytes of flash [==============================] 100% (329/329 pages) Verify successful Done in 4.854 seconds Set boot flash true

Thank you to everyone for the help I'm getting decent prints now I'll probably hooking up the bltouch in a day or so hope u can handle that by my self but I'm not holding my breath. Lol

I think this is the same issue as reported here: https://github.com/dc42/PanelDueFirmware/issues/39

nikscha created this issue in dc42/PanelDueFirmware closed wrong layout when using only heater 2 #39