That error should go away if you tune the bed heater using M303.

@ludisnet said in RRF3.0 & z-probe:

so, i reduce speed (z-probe), and work without error ....
with :
M558 P8 C"zprobe.in+zprobe.mod" H4 F500 T8000 ; R0.2 S0.02 A5

Ludis

You could increase the R parameter, to allow the effector more time to settle before probing starts.

@jens55 I did!
Learnt how to use RFM backup.

All sorted, just need to search and sort my BL Touch Issue 😞

I did the configuration in the configurator, now I have a "clean" config.g, ...... everything is fine ...with RRF3.

thank you for your help!

Ludis

That's the one I used, & shows as 1.22.6, but if I clean the browser cache & revert to the "DWC" view it shows as 2.0.6. But I tend not to use\like the view as its too "spread-out" on laptop screens....

Thanks for letting me know.

It looks like it uses fairly standard components and uses a cartesian layout.

There is some documentation that should give you an idea of what's required.

Adapting an existing printer to Duet and RepRapFirmware

Example printer upgrade:
https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+1:+Wiring/37

https://duet3d.dozuki.com/

While I am talking to myself here and reporting bugs .... the temperature chart shows a dashed line for the extra sensor but the legend on the graph shows some weird thing that might have some relation to a dashed line before it fell into a pot of chocolate andScreenshot from 2020-01-14 00-54-12.png had to eat it's way out of it getting real fat in the process (sorry, that's the only way that I can describe it)

I should add that I appreciate the support that you give even though your resources are very limited !

Also, thank you to all the other people that help in supporting the whole Duet system! I am sure that it wouldn't be half as successful without the effort of a lot of people!

Thank you !

@Phaedrux Thanks. The DWC v1.20 in my second post was a mistake, that was my previous version. I'm on DWC 2.04 now, but good point, I'll upload the full 2.05 zip file in case I missed anything.

Everything seems to be working okay otherwise which is a surprise since I had to piece together what the original manufacturer did to get it set up by looking at the wiring and old .g files. 24V supply, 220V heated bed supply, self driven servos....way more complicated than the simple i3 style cartesian I setup previously. I'm really thankful for resources here and in the wiki. I wouldn't have been able to do this otherwise.

@christophe31 said in BL TOUCH CONFIGURATION:

i'm too happy lol:)

You are wellcome

@droftarts
thanks! That was the problem

@gtj0 ok thanks for the info. didn’t found it.
regards Tobias

@dc42
Hi David, could you please take a look here again?

@Veti Thank you, this fixed the thermistor problem.

@MrInka
Have you seen that...
https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Fallback_procedure_Num_1

@jrsphoto For testing, I have folders in the sys folder named RRF2 and RRF3. These hold config files specific to each firmware version, including homing and tool change files; basically all the .g files. In the main sys folder I have a simple config.g that switches between these using M505 Set configuration file folder:

M505 P"RRF2" ;M505 P"RRF3" M98 P"config.g"

The sys folder also holds the iap files (used for updating firmware), the firmware .bin files and the heightmap.csv file. When I want to switch firmware, I edit the semi-colon comment mark in front of the relevant command in sys/config.g, and upload the firmware binary that I want to use, and allow it to install the firmware. The Duet resets after flashing the firmware, and runs the relevant config.g file.

Using this you can experiment with RRF3, while maintaining a working setup with RRF2 you can swap back to.

Edit: FAO @jens55 too!

Ian

That was it!

M584 without arguments at the console result was "X0 Y1 Z2 E3"

I had to add the following line to the config file:

M584 X0 Y1 Z2 E3:4 ; Map Drives

Now everything is working.

Thank you!

ah ok thank you