Red background in web controller


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



  • @dc42:

    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.

    @fulg:

    Try to debug this one step at a time.

    IMO, to do so I will require to do and redo some testing
    Let me know if you have any idea on how to do this correctly…
    Since I am using the Duet 0.8.5:
    Wire configuration:

    • White (OUT) to AD12 (Z-probe section)

    • Black (GND) to GND (Z-probe section)

    • Red (+5V) to 5v Pin 1 (+5V)

    • Orange (Control) to pin 21 (heater 3)

    • Brown (GND) to pin 2 (GND)

    For the Connections:

    • I will move the BLTouch to be plugged almost directly on the board (require room to plug the multi-meter

    • I will remeasure the voltage for the white wire for the pins in and out

    Is there any more verification that I can run on the BLTouch or the duet 0.8.5 hardware directly?

    Software wise, Firmware is up to date (Duet 0.8.5 & Web Controller)

    Until I can make sure that I can get the value in Z-Probe down to zero I will not look at other files then the config.g

    Added to config.g:

    • M307 H3 A-1 C-1 D-1

    • M558 P5 X0 Y0 Z1 H5 F100 T2000

    • G31 X30 Y18 Z1 P25

    For the Commissioning and testing:

    • M280 P3 S10 I1 deploys the probe

    • M280 P3 S60 I1, retract the probe

    Config.g files:

    ; Configuration file for Duet WiFi (firmware version 1.17)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool on Sat Sep 09 2017 20:34:25 GMT-0400 (Eastern Standard Time)

    ; General preferences
    M111 S0 ; Debugging off
    G21 ; Work in millimetres
    G90 ; Send absolute coordinates…
    M83 ; ...but relative extruder moves
    M555 P1 ; Set firmware compatibility to look like RepRapFirmare
    M667 S1 ; Select CoreXY mode
    M208 X0 Y0 Z0 S1 ; Set axis minima
    M208 X300 Y300 Z335 S0 ; Set axis maxima

    ; Endstops
    M574 X2 Y2 Z0 S0 ; Define active high microswitches
    M558 P5 X0 Y0 Z1 H5 F100 T2000
    G31 X30 Y18 Z1 P25 ; Set Z probe trigger value, offset and trigger height

    ; Drives
    M569 P0 S1 ; Drive 0 goes forwards
    M569 P1 S1 ; Drive 1 goes forwards
    M569 P2 S1 ; Drive 2 goes forwards
    M569 P3 S1 ; Drive 3 goes forwards
    M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
    M92 X160 Y160 Z796 E420 ; Set steps per mm
    M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
    M203 X6000 Y6000 Z180 E1200 ; Set maximum speeds (mm/min)
    M201 X500 Y20 Z250 E250 ; Set accelerations (mm/s^2)
    M906 X800 Y800 Z800 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent
    M84 S30 ; Set idle timeout

    ; Heaters
    M307 H3 A-1 C-1 D-1
    M143 S305 ; Set maximum heater temperature to 305C
    M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
    M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1

    ; Tools
    M563 P0 D0 H1 ; Define tool 0
    G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
    G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

    ; Network
    M550 PMy printer ; Set machine name
    M540 PBE:EF:DE:AD:FE:ED ; Set MAC address
    M552 P192.168.2.50 S1 ; Enable network and set IP address
    M553 P255.255.255.0 ; Set netmask
    M554 P192.168.2.254 ; Set gateway
    M586 P0 S1 ; Enable HTTP
    M586 P1 S0 ; Disable FTP
    M586 P2 S0 ; Disable Telnet

    ; Fans
    M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
    M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
    M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

    ; Custom settings are not configured

    Is there anything that I should test or take a look at?

    Thanks you



  • @Nylkos:

    For the Connections:

    • I will move the BLTouch to be plugged almost directly on the board (require room to plug the multi-meter

    • I will remeasure the voltage for the white wire for the pins in and out

    I redid the test, I can confirm the value that I have on the white wire while retracted = 0.103V
    However when I boot, after the "testing", while retracted I have 3.20V…

    Is there any test that I could do on the board itself to validate that I just don't have a damaged board? I already had to reweld 2 pins on this board. I visually checked pins 1-2 & 21, they seem fine... I am afraid to cause damage if I go check anything with the multi-meter without proper instructions...

    Thanks you


  • administrators

    Try P1 instead of P5 in the M558 command, in case it makes a difference.



  • You say you added the proper G31 command in your config.g but in the file you showed, the G31 is missing its P25 parameter, which is required to get the BLTouch to work.

    Since you can measure a voltage between 0.1 and 3.2V on the white wire, it means the 3.3V trace was correctly cut.

    Out of curiosity, which pins did you have to reweld on your Duet? Was it the Zprobe input? 🙂

    If the Zprobe input is damaged on your Duet, you could always use probe type 4 or 6 to use the E0/E1 endstop pins instead.



  • @fulg:

    You say you added the proper G31 command in your config.g but in the file you showed, the G31 is missing its P25 parameter, which is required to get the BLTouch to work.

    Since you can measure a voltage between 0.1 and 3.2V on the white wire, it means the 3.3V trace was correctly cut.

    Out of curiosity, which pins did you have to reweld on your Duet? Was it the Zprobe input? 🙂

    If the Zprobe input is damaged on your Duet, you could always use probe type 4 or 6 to use the E0/E1 endstop pins instead.

    Sorry the P25 was an oversight, I redid the complete settings. I added the correction on the file and in the above thread.

    for the rewelding, no it was for the E0 hotend



  • @dc42:

    Try P1 instead of P5 in the M558 command, in case it makes a difference.

    I changed To P1 in the M558, should I change any other thing?

    M558 P1 X0 Y0 Z1 H5 F100 T2000
    G31 X30 Y18 Z1 P25 ; Set Z probe trigger value, offset and trigger height
    M307 H3 A-1 C-1 D-1

    Automatically the value in Z-Probe dropped to 0 and when retracted at 990.

    I see this as good news!!!

    I sadly did not have the time to do the proper testing (multi-meter test, homez & homeall)

    Thanks you


  • administrators

    Looks good! Although I don't understand why P5 in the M558 command isn't working, because the pullup resistor that P5 activates is high value, around 100K. I still suspect a bad connection at one end of the white wire.

    I suggest you choose a P parameter of about 100 or 200 in your G31 command instead of 25, to give a bit more noise immunity.



  • Good news… it works, the P1 did the job.

    However I had to go with the deployprobe.g and retractprobe.g, the M401 & M402 didn't work with Probe Type 1.
    All I did was change to these

    M558 P1 X0 Y0 Z1 H5 F100 T2000
    G31 X30 Y18 Z1 P200 ; Set Z probe trigger value, offset and trigger height

    and Replace M401 by M98 Pdeployprobe.g and M402 by Pretractprobe.g

    Thanks you for your help!


Locked
 

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