Red background in web controller



  • What could cause the red background in web controller?

    My Z probe is a BLTouch and it has always been red, never been able to have a 0 there either…

    Any suggestion?


  • administrators

    It changes to red when the value in the box is above the trigger threshold set in the G31 command.

    If it never reads 0 then you have the Z probe incorrectly wired, or incorrectly configured with M558.



  • I unplugged everything, check the resistance in each wire and reinstalled…
    I am using Duet 0.8.5
    Black wire to the GND pin in the Z Probe section
    White wire to the AD12 pin in the Z Probe section
    Orange wire to the pin 21 in the expansion section
    Red wire to the pin 1 in the expansion section
    Brown wire to the pin 2 in the expansion section

    Here are my config.g modifications...

    M307 H3 A-1 C-1 D-1
    M558 P5 X0 Y0 Z1 H5 F100 T2000
    G31 X3 Y-1.8 Z2 P25 ; Set Z probe trigger value, offset and trigger height
    M557 X15:285 Y15:285 S20 ; Define mesh grid

    I did notice one thing… while I had nothing wired up and no modification in my config.g, I had some 433 in the Z-Probe sensor and it wasn't red... could my board be damaged or defective?



  • With my IR Probe disconnected, I still have a reading of 236 (P500 trigger), so I doubt your board is bad.



  • Thanks you, I will contact BLTouch



  • I rechecked the wire and the Config.g / Bed.g / Homez.g /…
    Still Red Background...
    The only way that I found not to have the red background was to add I1 to the

    M558 P5 X0 Y0 Z1 H5 F100 T2000

    But then I never get anything in Z-probe sensor, even when triggered.

    Do we have to declare the BLTouch as active low or high?
    do we need anything that isn't in https://duet3d.com/wiki/Connecting_a_Z_probe?

    Thanks you for your help.



  • Hi,

    I had a BL unit and after one bed strike (not that hard) it ceased to work correctly.

    Frederick



  • I am going through the same problem. New build with a Duet Wifi and BLTouch - the BLTouch was working with ramps 1.4. When I get a chance (and can't get anywhere with the Duet), I will plug it back into the ramps and see if it's the device or the settings. Any updates on your situation are much appreciated.


  • administrators

    I don't have a Bl touch however there is a long thread here with loads of people's experiences:
    https://www.duet3d.com/forum/thread.php?id=459#p13924



  • One thing to remember is that with the newest firmware revisions, deployprobe and retract probe folders are not needed any more.



  • Try to debug this one step at a time. Is the BLTouch getting 5V, can you manually deploy/retract, did you use the resistor for 3.3V logic (as per the BLTouch documentation)? If you forgot the resistor then the BLTouch sent 5V into a 3.3V input and possibly damaged it. This could be why you are seeing a triggered probe all the time.

    On my setup I did not have to invert the input for my BLTouch (no I1 on M558).

    BTW emailing me directly was not ok, I did not sell the Duet nor the BLTouch to you. I am happy to help here but if you want private support I will send you an invoice for my time.

    Cheers,
    Ben.



  • can you manually deploy/retract,

    Yes

    did you use the resistor for 3.3V logic

    No, I cut the wire for the 3.3V logic.

    I apologize if my message was unwanted… you just seemed active, knowledgeable, you posted your files... Worst case scenario I expected to be treated like spam. Do not worry, I won't contact you again.

    But thanks you for the answer.


  • administrators

    @number40fan:

    One thing to remember is that with the newest firmware revisions, deployprobe and retract probe folders are not needed any more.

    The change in the 1.19 firmware is that those files are invoked automatically if you do a G29 or G30 command and the probe is not already deployed. The files are needed if you use a probe that needs to be deployed, such as the Bltouch, and need to be set up correctly for whatever type of probe it is.


  • administrators

    @Nylkos:

    I unplugged everything, check the resistance in each wire and reinstalled…
    I am using Duet 0.8.5
    Black wire to the GND pin in the Z Probe section
    White wire to the AD12 pin in the Z Probe section
    Orange wire to the pin 21 in the expansion section
    Red wire to the pin 1 in the expansion section
    Brown wire to the pin 2 in the expansion section

    Here are my config.g modifications...

    M307 H3 A-1 C-1 D-1
    M558 P5 X0 Y0 Z1 H5 F100 T2000
    G31 X3 Y-1.8 Z2 P25 ; Set Z probe trigger value, offset and trigger height
    M557 X15:285 Y15:285 S20 ; Define mesh grid

    I did notice one thing… while I had nothing wired up and no modification in my config.g, I had some 433 in the Z-Probe sensor and it wasn't red... could my board be damaged or defective?

    Check the connection from the Bltouch to the input pin on the Z probe connector (white wire).

    With probe type 5 selected (P5 in the M558 command), with nothing connected to the input pin you should get a reading of 1000. If you connect that pin to ground, you should get a reading of zero. But with probe type 1 selected, when nothing is connected to the input pin you might see anything between 0 and 1000 because the pin is floating.



  • @dc42:

    Check the connection from the Bltouch to the input pin on the Z probe connector (white wire).

    With probe type 5 selected (P5 in the M558 command), with nothing connected to the input pin you should get a reading of 1000. If you connect that pin to ground, you should get a reading of zero. But with probe type 1 selected, when nothing is connected to the input pin you might see anything between 0 and 1000 because the pin is floating.

    I will do the test.
    I will also try with a 240 Ohms transistor… it's really hard to see if the connection was properly cut for the 3.3V logic, Worst case scenario with the 240 Ohms, I assume that I would see a red blinking light...

    @fulg:

    I did not sell the Duet nor the BLTouch to you.

    Do you have a store?



  • @dc42:

    Check the connection from the Bltouch to the input pin on the Z probe connector (white wire).

    With probe type 5 selected (P5 in the M558 command), with nothing connected to the input pin you should get a reading of 1000. If you connect that pin to ground, you should get a reading of zero. But with probe type 1 selected, when nothing is connected to the input pin you might see anything between 0 and 1000 because the pin is floating.

    I must admit that I am a little embarrassed, but when you are asking to check the connection, I assume that you are asking me to measure the Amps. To measure the amps, I require to add in my multi-meter into a closed circuit. So how could I read the amps of the white wire while it's unplugged?

    While being unsure of what you meant here is what I did…
    Resistance Black to white wire 1000 Ohms
    Amps on the black wire while the white is not connected will be of 10-20ma when triggered
    Volt on the red wire (pins 1) 4.89V
    Amps on the red wire (pin 1) varies 2.2-3.5
    I noticed something weird... IF I unplug the BLTouch completely, I still get the 1000 in the Z-Probe sensor... with the red background...

    I tried adding the 240 transistor and got a red blinking light.



  • @dc42:

    @number40fan:

    One thing to remember is that with the newest firmware revisions, deployprobe and retract probe folders are not needed any more.

    The change in the 1.19 firmware is that those files are invoked automatically if you do a G29 or G30 command and the probe is not already deployed. The files are needed if you use a probe that needs to be deployed, such as the Bltouch, and need to be set up correctly for whatever type of probe it is.

    Ah, sorry about that. I thought they needed to be deleted no matter what. I'll keep that in mind in the future when trying to help out when/if I can.


  • administrators

    No problem, I have seen that your replies have been very helpful to a number of Duet users. Please keep it up!



  • I had the time to run some additional testing:
    Voltage for the white wire, when pin is down 3,2V, pin up 0,10V
    For the Amps on the white I assume that the pulse is coming too fast I can't seem to catch it on the multi-meter

    From that and the 240 homs resistor causing the blinking red led, I assume that the wire for the 3.3v logic was properly cut.

    The Z-Probe sensor in the web controller, it's source, I assume would be the In pin from the Z-Probe (duet Wifi or Ethernet) or the AD12 (duet 0.8.5 & 0.6).

    How come is the Z-Probe background remain with 1000 value when my BLTouch is unplugged…

    I was able to remove the red background by changing the P value in the G31
    The background turned yellowish around P1000 and back to white around P1500

    However I can't seem to get the value to 0 with any of the M280 commands.


  • administrators

    When the output voltage is 0.10V, you should get a reading of around 30 if the connections are good and the configuration is correct.


Locked
 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.