Just a little lost re: upgrading to 3.0 firmware.
-
@dc42 Sorry sir... This is what it says:
6/9/2020, 3:48:23 PM M950 S0 C"duex.pwm5"
Warning: M950 command is not supported
6/9/2020, 3:48:06 PM M950 S0 C"duex.pwm5"
Warning: M950 command is not supported -
Looks like you are running RepRapFirmware 2.x then. Send M115 to check.
-
Here's what's in the "Machine specific" section...
Electronics
Diagnostics
Board: Duet WiFi 1.02 or later + DueX5
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.0 (2020-01-03b3)
Duet WiFi Server Version: 1.23Note: You can install updates on the System page.
Is there any merit to just starting completely fresh? I've upgraded / downgraded several times, and god only knows what could be mismatched. Again, not your fault, I'm just stumbling through this...
-
actually, It was waiting for a restart.... I may have created that problem myself... I was in 3.0 when I originally posted. I switched back down for last night, so I could print, and re-loaded from the configurator a little bit ago... I must not have re-specified my firmware version in the configurator when I uploaded My JSON. Sorry... I've been trying so may things, that I lost track...
-
I just started fresh.... Probe deploys and retracts now! It was the extra C"duex.pwm5" that was in my "deploy probe" that was causing the problem. Just removed it, and I Heard it click!
So I was sooo close... Just had extra crap in the command.. Drats!
Now to figure out My heaters.... I think I probably have to specify ports and stuff for them. I'll go try that, and leave you alone unless I can't get it!
Also, the Configurator inserted extra lines in My BLTouch section. Stuff about Mod Probe, and servo angle and such.. It was not in the lines @Phaedrux sent me, so I deleted it.
I appreciate your patience...
-
Thanks for helping me get this far. I'm down to 2 little dilemmas now... Well, Possibly three, but We'll just stick with the two...
I've asked all around, and cannot seem to find an answer. What is the Gcode in 3.0 to release a BLTouch Alarm, and Pull Pin Up? I know thew old code was:
M280 P0 S160.
That's changed, and I tried replacing the P0 with C"duex.pwm5" but that doesn't seem to work.
What's happening is that my BLTouch deploys, homes, then goes into "Flashing Mode" saying the pin was already triggered. Any Ideas?
Lastly, I've always controlled lights Via PWM fan ports.
I'm in Fan/LED 3 and Fan/LED 4 on the duex.
If I make a macro with:
M950 F3 C"!duex.fan3" Q0
M950 F4 C"!duex.fan4" Q0Both Lights Turn Off
any Q number over "1" results in full brightness.
I used to be able to dim the lights using an integer between 1-255. any number I put in there now results in Full Brightness. These LEDS are extremely high output, so To avoid the extreme heat they put off, I simply dim them to 50%
Any suggestions on how to change the dimming value? I believe it was reducing the voltage the way it used to do it. Do you know what the new way is? Thanks!
-
@Steve-Lynch said in Just a little lost re: upgrading to 3.0 firmware.:
I used to be able to dim the lights using an integer between 1-255
Can you try a decimal number between 0 and 1? 0.1, 0.2, etc?
-
@Steve-Lynch said in Just a little lost re: upgrading to 3.0 firmware.:
Thanks for helping me get this far. I'm down to 2 little dilemmas now... Well, Possibly three, but We'll just stick with the two...
I've asked all around, and cannot seem to find an answer. What is the Gcode in 3.0 to release a BLTouch Alarm, and Pull Pin Up? I know thew old code was:
M280 P0 S160.
Assuming you are using servo index 0 to control the BLTouch, that should still work.
Lastly, I've always controlled lights Via PWM fan ports.
I'm in Fan/LED 3 and Fan/LED 4 on the duex.
If I make a macro with:
M950 F3 C"!duex.fan3" Q0
M950 F4 C"!duex.fan4" Q0Both Lights Turn Off
any Q number over "1" results in full brightness.
I used to be able to dim the lights using an integer between 1-255. any number I put in there now results in Full Brightness. These LEDS are extremely high output, so To avoid the extreme heat they put off, I simply dim them to 50%
Any suggestions on how to change the dimming value? I believe it was reducing the voltage the way it used to do it. Do you know what the new way is? Thanks!
Remove the ! and the Q0 parameters in those two M950 commands.
-
BL Touch - Solved
Light control: The lights will only light up of I invert the pins with !
I tried removing them, and even tried swapping polarity. they will not trigger without the ! character.
They work fine without the "Q" value, but will not dim. Is a fan output the best way to do this? should I specify it as something else? say, a Heater? Either way, what would be the method to reduce the power to the lights, for, say, 50% brightness?
thanks so much!
-
The M950 command just assign fan number to the fan ports. To control the PWM, use M106 as usual. For example:
M950 F3 C"duex.fan3"
...
M106 P3 S0 ; LED off
M106 P3 S1 ; LED on
M106 P3 S0.5 ; LED half brightness -
OK, thanks.. I was trying to use M42, as specified in the documentation. I got everything else working now. Thanks a lot! This new system is a lot easier to wrap my head around
-
@Steve-Lynch said in Just a little lost re: upgrading to 3.0 firmware.:
OK, thanks.. I was trying to use M42, as specified in the documentation. I got everything else working now. Thanks a lot! This new system is a lot easier to wrap my head around
You can either use M950 Fn to create a fan port, then M106 Pn Sn to control it; or you can use M950 Pn to create a GpOut port, then use M42 Pn Sn to control it.
Using a fan port gives you a slider to control it in DWC, and options for direct thermostatic control. Using a GpOut port gives you neither of these, however you can still use the daemon.g file to have the LEDs change automatically in response to e.g. temperature or printer state.
-
Excellent info! Thanks! I've worked my way up to 3.1.1, and actually got 2 other people upgraded and configured now as well. Thanks for all of the help!
I realize it can be frustrating, when people like me who don't really have a solid grasp of the language are trying to learn. But I am learning, and I'm always willing to help others when I can, so I will pass the knowledge on to others at every opportunity..
And again, I understand this new naming convention a lot better. i like what you did. It was a bit confusing at first, but the more I read, the more it makes sense! Kudos!
I do have one small issue left, and I've put a day into it myself, without trying to bother you... I'm just stumped though.
My bed heater keeps erroring out.... I've pid tuned several times... It's just not liking it.. It reaches about 50 degrees, and then errors...
Here are My 2.5 values, which work fine in 2.5....
; Thermistors
M305 P0 T100000 B3950 R4700 H0 L0 ; Put your own H and/or L values here to set the bed thermistor ADC correction
M305 P1 T100000 B4725 R4700 H0 L0 C7.06e-8 ; Put your own H and/or L values here to set the first nozzle thermistor ADC correctionM307 H0 A240.3 C608.7 D8.2 S1.00 V24.1 B0 ; Bed Heater
M307 H1 A270.7 C90.4 D6.7 B0 S1.0 ;Heater 1 model
M570 S360 ; Hot end may be a little slow to heat up so allow it 180 seconds
M143 S285Here are My 3.1.1 values. Do you see any problem?
; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
;M307 H0 B0 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4725 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
;M307 H1 B0 S1.00 ;Temp Comment out for experimentation ; disable bang-bang mode for heater and set PWM limitM307 H0 A340.0 C140.0 D8.2 S1.00 V0.0 B0
M307 H1 A622.1 C260.5 D3.1 S1.00 V24.0 B0Also, should bed be in PID mode? I've not used Bang Bang before.. Pid seems safer..
Thanks!
-
@Steve-Lynch No bother at all.
Yes PID for bed. Just say no to bang-bang.
What error message are you getting?
When you do the PID tune for the bed, are you saving the values to config-override with M500? Do you have M501 in config.g to load them? Or are you transferring them over to config.g?
-
Have you tried using the same M307 H0 command for RRF 3.1.1 that you used for RRF 2.05? The values shouldn't have changed significantly.
-
Trying now!
-
It's telling me that it's heating slower than expected... Trying my 2.5 variables now.
-
Well, son of a gun! The 2.5 variables work...
I wonder why the pid tune numbers are so different?
Is there any particular Pid tune regimen you recommend?
Preheat heaters? Nozzle to the bed? fans full on?
I try to do it with the "real world" environment it will be printing in. (e.g. fans on) is that the wrong train of thought?
-
@Steve-Lynch said in Just a little lost re: upgrading to 3.0 firmware.:
I try to do it with the "real world" environment it will be printing in. (e.g. fans on) is that the wrong train of thought?
That's how I do it too. Not sure why the values would be so different.
What are your 2.5 values?
-
Let's Mark this Bad Boy Solved!
