Just a little lost re: upgrading to 3.0 firmware.

dc42

@Steve-Lynch said in Just a little lost re: upgrading to 3.0 firmware.:

M950 S0 C"duex.pwm5" ; define GPIO/Servo Pin

That's correct if you have connected the PWM servo input of the BLTouch to output PWM5 on the DueX.

Do the M401 and M402 command deploy and retract the pin?

Steve Lynch

No, they do not. I am definitely in PWM5 on the duex, with the orange on the left, red in the center, and brown on the right, as seen in the instructions. My white and black leads are plugged into the "probe" port, to the left of the 50 pin duex ribbon. I'm in the first two pinsfrom left to right. white, then black. the same way It's been set up in 2.5.

Steve Lynch

I was a little sketchy on the whole servo pin angle entry below it as well. does that look ok?

dc42

What do you have in your deployprobe.g and retractprobe.g files?

Steve Lynch

this is deploy:

; generated by RepRapFirmware Configuration Tool v3.1.1 on Tue Jun 09 2020 01:46:51 GMT-0400 (Eastern Daylight Time)
M280 P0 C"duex.pwm5" S10 ; deploy BLTouch

this is retract:

; generated by RepRapFirmware Configuration Tool v3.1.1 on Tue Jun 09 2020 01:46:51 GMT-0400 (Eastern Daylight Time)
M280 P0 C"duex.pwm5" S90 ; retract BLTouch

I tried reaching out to the railcore group, and as it turns out, there are 8 guys who couldn't get it to work, so they went back to 2.5, and one guy who says he can share his config with me, but he doesn't use a BL Touch.

I went back to 2.5 last night so I could print, everything was fine, then I did the configurator again this morning. Still no Joy, though this time, it did add the BL Touch Info.

So I guess I have to stick with this for everyone else, once we get mine right, I'll share the info.

Does anyone have a CoreXY running E3D heater / thermistors, and BL Touch?

If I can at least look at how it's set up, I can model mine after that.

Thanks so much!

Phaedrux

@Steve-Lynch said in Just a little lost re: upgrading to 3.0 firmware.:

C"duex.pwm5"

Remove that from your M280.

The M950 in your config.g creates the servo pin. M280 P0 targets that servo pin.

Phaedrux

; Z-Probe
M950 S0 C"duex.pwm5"                           ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000            ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y0 Z2.5                            ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20                       ; define mesh grid

; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.1.3 on Tue Jun 09 2020 12:35:40 GMT-0600 (Central Standard Time)
M280 P0 S10 ; deploy BLTouch

; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.1.3 on Tue Jun 09 2020 12:36:12 GMT-0600 (Central Standard Time)
M280 P0 S90 ; retract BLTouch

That's right out of the configurator.

Steve Lynch

@Phaedrux
I had it set up just like you just posted, and this is the error I get every time.

"Invalid servo index 0 in M280 Command."

I'm in the port labeled PWM5 on the duex board. This really is PWM5, correct? PWM5 isn't really PWM7 or something like that, right? I'm just trying to figure out why I cannot deploy the probe. Everything try yields some error or another when I try the M401...

dc42

@Phaedrux said in Just a little lost re: upgrading to 3.0 firmware.:

M950 S0 C"duex.pwm5"

That looks correct to me. If you send that command from the console, what response do you get?

Please verify using M115 that you are running firmware 3.1.1.

Steve Lynch

@dc42
6/9/2020, 3:40:31 PM M401
Error: M280: Invalid servo index 0 in M280 command
6/9/2020, 3:40:11 PM Upload of config.g successful after 0s
6/9/2020, 3:37:03 PM M401
Error: M280: Invalid servo index 0 in M280 command
6/9/2020, 3:36:49 PM M401
Error: M280: Invalid servo index 0 in M280 command

Two tries, then cleared out, saved, re-opened blank deploy and retract g codes, and made them from scratch.. still same thing..

Steve Lynch

; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.1.1 on Tue Jun 09 2020 01:46:51 GMT-0400 (Eastern Daylight Time)

M280 P0 S10 ; deploy BLTouch

That's my deploy.....

Phaedrux

And you have this exactly in config.g?

M950 S0 C"duex.pwm5"                           ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000            ; set Z probe type to bltouch and the dive height + speeds

dc42

@Steve-Lynch said in Just a little lost re: upgrading to 3.0 firmware.:

@dc42
6/9/2020, 3:40:31 PM M401
Error: M280: Invalid servo index 0 in M280 command
6/9/2020, 3:40:11 PM Upload of config.g successful after 0s
6/9/2020, 3:37:03 PM M401
Error: M280: Invalid servo index 0 in M280 command
6/9/2020, 3:36:49 PM M401
Error: M280: Invalid servo index 0 in M280 command

Two tries, then cleared out, saved, re-opened blank deploy and retract g codes, and made them from scratch.. still same thing..

The command I wanted you to send from the console was the M950 command that I quoted.

Steve Lynch

This is my exact BL Touch Section:

; BLTouch
M950 S0 C"duex.pwm5" ; Define the bltouch servo on duex.pwm5
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y28.8 Z4.9 ; set Z probe trigger value, offset and trigger height
M557 X4:300 Y27:300 S20 ; define mesh grid

Steve Lynch

@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

dc42

Looks like you are running RepRapFirmware 2.x then. Send M115 to check.

Steve Lynch

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

Note: 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...

Steve Lynch

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

Steve Lynch

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

Steve Lynch

@dc42 @Phaedrux

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" Q0

Both 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!