Update CR-10+Duet wifi from 2.05.1 to 3.0 firmware
-
It was my fault... I thought the access point was restored, but no! Now i think i have some changes to do on the config file and home settings to right? can you tell me where can i fin help to see the changes i have to do?
-
https://configtool.reprapfirmware.org/Start
For your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3. Compare what it generates to your existing config.
You can find some additional details on what is different about RRF3 here: https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
If you post your old config.g and new config.g we can note anything else that would need to change.
-
@Phaedrux
you are tireless, but maybe we will leave it for tomorrow. I was seeing a toturial left by Chris Basement about those changes, where he does it directly in the files. It doesn't seem bad, considering what I went through to understand the previous RRF I tried, but I couldn't do it, because there are many steps I don't understand on the RRF panel!
Also, wouldn't I have to change all access to my board via wifi to be able to work from RFF3? -
Yes 's not too bad. Having a config from the web tool to compare against is still really handy though.
@Hélder-Rocha said in Update CR-10+Duet wifi from 2.05.1 to 3.0 firmware:
Also, wouldn't I have to change all access to my board via wifi to be able to work from RFF3?
I'm not sure what you mean by this.
-
@Phaedrux good morning. when you refere to RRF3 you are talking about the RepRap Configurating tooll, right? Or you suggest to go directly to the files and change one by one?
-
@Hélder-Rocha said in Update CR-10+Duet wifi from 2.05.1 to 3.0 firmware:
RRF3
reprap firmware 3
the firmware that runs on the duet
-
@Veti good morning. Yes, ok, but now, to make the changes i nead because of the new commands etc, do i do it directly on the configuration files or do i do it on the reprap configurating tool?
-
if you made no changed to your config after the config tool, you can upload the json
or read
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Summary_of_what_you_need_to_do_to_convert_your_configuration_and_other_files
and make the changes by hand -
@Veti ok... its decided... i ll make by hand. My first doubt is:
what kind of termistor do i have? I know is a 24V hotend heater and my bed is heated with a silicon heater of 240W connected to KS 1-25DA rele. I dont undestand about the values i have to imput on the config.g! Can you help me on this? Sorry
-
@Hélder-Rocha said in Update CR-10+Duet wifi from 2.05.1 to 3.0 firmware:
I know is a 24V hotend heater and my bed is heated with a silicon heater of 240W connected to KS 1-25DA rele
best to ask the seller.
most of the time those are B3950 -
@Veti is that for the hotend heater or for the bed?
-
the bed.
on the hotend it is probably easier to just buy a know thermistors.
-
@Veti i ll try to check it out... tks
-
so i have this on the new rules:
M143
In RRF 2 the optional P parameter of the M143 command is the number of the global heater protection element instance, and it defaults to the heater number (H parameter). Valid values are 0..(MaxHeaters-1) and 100..(MaxHeaters-1). The optional X parameter is the number of a heater or virtual heater whose sensor is used to monitor the heater.
In RRF 3.01-RC2 and later the optional P parameter is the number of the monitor for that particular heater. Valid values are 0..2 and the default is 0. The optional T parameter is the number of the sensor used to monitor the heater.
In my config.g i have the M143 for the bed like this:
M143 H0 S120and for the hotend heater:
M143 H1 S290What should i change?
-
what i do in that case, is generate a config in the online configurator and have a look at that layout
-
@Veti ok...i ll keep it for now
-
Veti, i find out i have a "G10" on tools, setting the axis offsets to 0. Could that be the problem when i was trying to define a different offset on G31 when i was calibrating my BLTouch?
On TOOLS i have this:G10 P0 X0 Y0 Z0
-
no the first tool should not have an offset
-
@Veti so... i should erase it?
-
no. compare to the config that the configuration generates. its there.
