Posts made by Sniffle

the name BLTouch classic has nothing to do with the 240ohm resistor being on the board, it's dependent on MFG date. you just have to look and see if the trace is on the PCB of the BLtouch

does it use a switch mounted on the rails on the back or does it have a probe?

If it has a switch on the back do you see wires coming off of that switch or have they come unplugged?

A probe will be mounted to the XY carriage that holds the hotend. Can you post pics of your printer? I have a C-bot myself, and there is also a facebook group for the C/D bots that may be able to help if it is an actual hardware issue and not firmware or controller.

@AaronGreen:

I'm still not 100% on the calibration because I don't have a conclusive idea of the config information.

If we're all using a BLTouch with the DuetWiFi, every bit of information should be the same except the bed size and carriage height parameters.

Currently, my Auto Home process checks X and Y, then when the probe touches the bed it sets off the Alarm and rams the bed indefinitely.

–------------
; General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X340 Y250 Z280 S0 ; Set axis maxima

; Endstops
M574 X1 Y1 Z1 S0 ; Define active low and unused microswitches
M558 P5 X0 Y0 Z1 H5 F200 T6000 ; Set Z probe type to modulated, the axes for which it is used and the probe + travel speeds
G31 X-40 Y7 Z0.9 P1 ; Set Z probe trigger value, offset and trigger height

;Z-offset (Z0.9). Higher value LOWER nozzle height
; Lower value RAISE nozzle height

M557 X10:340 Y10:240 S68 ; Define mesh grid

M307 H3 A-1 C-1 D-1 ; disable heater 3, which makes it available for use to control the BLTouch

; Drives
M569 P0 S1 ; Drive 0 goes forwards - X
M569 P1 S0 ; Drive 1 goes backwards - Y
M569 P2 S0 ; Drive 2 goes backwards - Z
M569 P3 S1 ; Drive 3 goes forwards - Extruder

M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation 16
M92 X160 Y160 Z1600 E800 ; Set steps per mm 16

M566 X600 Y420 Z12 E120 ; Set maximum instantaneous speed changes (mm/min) - (JERK)

M203 X6000 Y6000 Z500 E400 ; Set maximum speeds (mm/min)

M201 X1000 Y1000 Z1000 E250 ; Set accelerations (mm/s^2)

M204 P1000 T1000 ; Set Max acceleration for P=printing moves and T=travel moves
M906 X1600 Y1600 Z900 E1000 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Heaters
M143 S285 ; Set maximum heater temperature to 285C
;M305 P1 X101

M305 P1 T107000 B10832 C4.891620e-7 R4700 ; Set thermistor + ADC parameters for heater 0 - BED
M305 P0 T99600 B4388 C0 R4700 ; Set thermistor + ADC parameters for heater 1 - HOTEND E3d

M307 H0 P96.0, I3.285, D603.9 ;Bed
M307 H1 P1.1, I0.011, D51.5 ;Hotend pid

;M307 H1 P17.8, I0.055, D74.9 ;Hotend E3d pid

; 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 CLU ; Set machine name
M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP

; 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

this does not show your homeall.g and homez.g, those files are what control your homing process, and most likely the procedure needs to be changed from the G1 command to lower indefinately to G30 which will amke it stop

correct, and if you have a Z-min endstop that is in use on the printer, and the height that the nozzle needs to reach is below that Z-min endstop, you will crash into and possibly dmamage the Z-min endstop. it is better to not use one when using a probe to home and probe the bed. you are better off to use the probe to home and physically remove the Z-min endstop as it is being physically replaced and functionally replaced by the Z-probe.

It wasnt stated if you use a Z-min endstop, I am just stating the reason why you don't need one, just in case you do.

you should probably post your config, also what is your Z offset set to?

edit: missed the config link, let me look

have you tried homing X and Y only, and then moving the probe to the center of the bed then using G30 to home with the probe, I dont see G30 used in your homing files, this tells the firmware to home l;istening for the probe to trigger, and then measuring the distance from the nozzle to the bed. If you still are still you a Z endstop as well as a Z-probe, you wont be able to use compensation or probe homing as it conflicts with the use of those features.

I have them setup in custom macros on the web interface, so that If i need them they are they are easily accessed without the need to type gcodes.

here's my one question for you, and this is the main reason most of us home with the bltouch or other probing solutions in the center of the bed.

What will happen to your Z endstop when a location of a point on the bed is lower than the location of your Z endstop?

As far as the setup of the settings goes I would say you have it pretty well worked out.

free up the heater pin, asign, the heater pin for the probe, set the x/y/z offsets, set the probing dimensions(be sure that your probing dimensions compensate for the offset usually by >10 just to make sure that it will probe inside a reachable boundary), setup macro's for retract(90), deploy(10), reset(160), and self test(120)

The big thing after this is setting it all up and testing the fool out of it hooked up to make sure that you have signal fromt eh bltouch when it is in an error state(it defaults to showing triggered when in error state) and run it though its paces before you ever tell the machine to depend on it, while homing, probing etc

Ive had my bltouch setup for so long now I have to refer back to the large post i made on the original BLTouch forum post, as well. Mine is still setup on P4 as well… I just havent seen the need to change it. If i remeber correctly I made that post as a type of overall information gather for the wiki page. I'm sure some of it needs to be updated to be correct, which I think is the parts already on the wiki.

are you trying to home the printer with the Z probe?

in your homeall.g and homez.g files what is the command you use when telling the printer to dive for the Z height?

you should probably look at

http://reprap.org/wiki/G-code#G30:_Single_Z-Probe

edit:
If you are jsut testing the probe, the standard motion of the probe is to trigger and drop back down, so that it is ready to probe the next point. At the end of any probe using script you must use the Gcode to store the probe or use a macro like retractprobe.g that has the store gcode in it to retract the probe back up to get it out of the way.

As a way to test the output of the probe

In my experience witht eh BLtouch, the web interface rarely responds fast enough for the probes super fast pulse, to get it to register occasionally i would have to deploy the probe, and then manually press the pin multiple times to get it to register once. Also, unlike a mechanical switch, 2-wire output for the touch seems to be polarity sensitive. On both my Rambo boards and the duet, polarity has mattered.

DC42, with the current 1.19Beta3, are the flashing instructions still the same as with the previous 1.19 versions that require the firmware and wifi to be updated simultaneously?

https://www.duet3d.com/forum/thread.php?id=247#p2462

This is the fix/workaround i used. you will need a .25A fuse. about the only place to find them is on amazon. I went to my local automotive supplier(O'reilly auto) and picked up a tube fuse holder. and soldered that inline as per the link and then added the fuse when it came in and she powered up like a champ and if it ever blows again due to a wierd short, i can just swap in a new one.

I just had this happen as well,

you most likely had a short between the thermistor and your heater wire on the hotend(that tends to be what causes it) and blew your VSSA fuse.

you can search for VSSA in the forums as its happened to multiple people, to see how to diagnose it if that is the case as well as how to fix it, if you dont have the capabilities to SMD solder, there is a work around, but still requires soldering, you'll find it with your search and if i am able i will post some links.

at the start/end points of an outer layer, when you find the right balance there should be little to no artifcat(blobs) at the beginning or end of the outer layer line. when perfect you might see the start/end point but not really feel it.

edit: with too much pressure advance you'll get a blob at the start of the outer most layer of a print
with too little youll get a blob at the end of the outer most layer of a print

So i was having the same issue of 0's in the first column, and only displaying part of the mesh in the mesh visualizer, I had unwittingly made my X start point value for the probe grid below my X offset and the first column was 0'd out for the 16 point grid.

DC42, now that the baby is here and we've moved houses, I can do a little testing.

What do you need tested to confirm CoreXY Kinematics, or I should say, How do you want CoreXY kinematics to be tested?

I have a C-Bot with a 7" Panel Due and a BLTouch probe, All are currently working properly now with 1.18.1 firmware, and with a little effort I maybe will be able to get it on video. When I am able I will gladly help with testing.

When it goes to probe, it checks the probe and sees that the probe is already triggered, so you need to invert the logic of the Z endstop. To do so change this:
line 18:

M574 Z1 S0 ; Define active low and unused microswitches

to:

M574 Z1 S1 ; Define active low and unused microswitches

This will change it so that the firmware doesnt see the probe as triggered until it actually is.

To verify this and prevent a bed crash, move the bed far away from the nozzle, home Z, and manually trigger the probe if you are able to, and if it work the bed should stop still quite far away from the printer nozzle but all will be safe. and if it does not work you then have enough time to unplug or turn off the machine

sounds like your Z endstop logic needs to be inverted,

When the BLTouch is in an error state it holds itself as being triggered. Thats at least part of your problem.

As to the signal pin to trigger the BLtouch you should try M280 P# S10 I1 replace # with whatever P you are trying to use and maybe try others as well. That gcode command should drop the pin on the bltouch is raised

S90 will raise it
S120 will self test
S160 will reset an error state(blinking)

Hey guys so i have an odd problem, I was working on the bed of my corexy printer, after turning it on both my bed and hotend thermistors are reading open circuit. I can understand on the bed if i might have knocked something loose but the extruder as well seems very unlikely. I've since isolated the thermistor wiring, for both the hotend and bed, as well as replaced the bed thermistor as it looked like the fiberglass sleeving could have frayed and caused a short, this was not the case.

In the open circuit state the hotend fan run constantly as I have it thermostaticaly controlled, and occasionally you can hear it wind down, it just completely quit spinning for half a second, as if it momentarily finds ground and loses its open circuit state. Is there a test point I can check could it perhaps be a cold solder joint somewhere expanding and contracting.

I'm at a loss and this is really frustrating…

Thanks for your time

https://www.youtube.com/watch?v=DiCKHPRGRKc

Edit: further digging and checking(had to find my meter,)
The disconnected thermistor circuits from the connector through the thermistor and back for the bed reads 110K Ohms, the Hotend reads 108K Ohms, which is where they should be, (checking for a bad wire)

Here is the M122 output

=== Diagnostics ===
Used output buffers: 1 of 32 (13 max)
=== Platform ===
Memory usage:
Program static ram used: 20304
Dynamic ram used: 73872
Recycled dynamic ram: 32
Current stack ram used: 3288
Maximum stack ram used: 4120
Never used ram: 32744
Last reset 00:00:42 ago, cause: power up
Last software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Spinning module during software reset: GCodes, available RAM 33048 bytes (slot 3)
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 14.1, current 20.3, max 23.2
Supply voltage: min 12.2, current 12.3, max 12.4, under voltage events: 0, over voltage events: 0
Driver 0: standstill
Driver 1: standstill
Driver 2: standstill
Driver 3: standstill
Driver 4: standstill
Current date and time: 2017-05-12 22:51:59
Slowest main loop (seconds): 0.011509; fastest: 0.000037
=== Move ===
MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is ready with "M122"
telnet is idle
file is idle
serial is idle
aux is idle
daemon is idle
=== Network ===
WiFiServer is running
SPI underruns 0, overruns 0
=== Webserver ===
HTTP sessions: 1 of 8

Next up is reflashing firmware in case it might be a corrupted eeprom as suggested by a friend in the field

Edit2:
So flashing firmware to 1.18.1(from 1.18 beta3) had no change

here's the M122 output from after the update.

=== Diagnostics ===
Used output buffers: 1 of 32 (4 max)
=== Platform ===
Static ram used: 20320
Dynamic ram used: 72808
Recycled dynamic ram: 1080
Stack ram used: 968 current, 3816 maximum
Never used ram: 33048
Last reset 00:06:09 ago, cause: software
Last software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Spinning module during software reset: GCodes, available RAM 33032 bytes (slot 4)
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 22.8, current 26.3, max 28.8
Supply voltage: min 12.2, current 12.3, max 12.4, under voltage events: 0, over voltage events: 0
Driver 0: standstill
Driver 1: standstill
Driver 2: standstill
Driver 3: standstill
Driver 4: standstill
Date/time: 1970-01-01 00:00:00
Slowest main loop (seconds): 0.004193; fastest: 0.000037
=== Move ===
MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
Code queue is empty.
=== Network ===
WiFiServer is running
SPI underruns 0, overruns 0
=== Webserver ===
HTTP sessions: 1 of 8

I'm at a loss and going to bed