Hey Man,
I just noticed I had never responded to thank you for sending me these files. I wanted to apologize.
I know you probably don't Remember, but either way, it bothered me that I had not acknowledged you...
So again Thanks so much!
Being able to see how you had it set up really helped me to understand how the different instruction sets interacted.
Take care!
Steve
I'm not a discord user, I mean, I occasionally log in if I have to, but I can't stand the platform. I have been seeking help in the railcore group, and a couple other 3d printing groups. I didn't know there was an official support discord.
My probe is behaving as it should. Probe value is zero if it's connected, and 1000 if button is depressed, or probe is removed.
I actually want to use the conditional code, I just don't understand it. I have the example .g files you provide, but I don't know what to uncomment, or any of that.
I build CNC tool changers, I'm quite aware that errant debris can cause huge problems in devices. I realize a probe will probably just break, or fall off, but I'm used to a 3 LB razor blade going 25,000 rpm.... one of those gets away from you, and it's a real shit show. So I'm a big fan of safety checks.
I'll follow your link for the meta commands.
If I can't sort it out, I'll bite the bullet, and hop on discord I guess.
@arnold_r_clark
Thank you very much! The conditional code is what I'm struggling with. I'm concerned about it crashing if it doesn't get stowed before it gets turned off, or if a print fails, and I re-start it remotely, or whatever.
Your code is basically how I started off.... Just a series of movements.
Then everyone started telling me that I was going to destroy my machine, and I had to set it up to detect the presence of the probe.
I think at 48 years old, considering that I've never stepped in front of a moving train, or fallen off a building, or anything like that, It's probably safe to say that I'm capable of checking the head before I start a print.. 
It would just be nice to have the safety of the code.
@zapta Thanks for the second set of eyes on this dude!
That's kind of where I'm at... I can make the machine move anywhere I want, moves are easy... it's the conditional code as you guys call it, that's got me twisted. I understand that it's supposed to be an "If This, Then That" type of flow, but That's kind of above My pay grade. I'm not finding much in the manual to outline how that type of code works.
Like I always do, I'll at least document, and share My working code with others if I ever get it sorted.
I'm almost 100% certain that My problem is that I need to either uncomment, or change variables in the conditional stuff. The problem is, the example scripts provided by Euclid don't really make it clear to a non-coder like me, what variables are there for reference, and which ones should be changed.
@alex-cr said in Euclid Probe / Railcore frustration. Any advice?:
Can you please re-submit your code from your first5 post but using the code insert function of the forum? (The button looks like </>).
Fixed! Submitted as requested.
I have a sneaking suspicion that your code is not indented properly so your if commands are not working properly so it is just aborting instead of jumping past the abort.
This is the 2nd time someone has mentioned indentation today... I'm not clear as to what the rules are for indent.
@zapta Probe value is reading properly as you asked.
This is what it's showing for probe value in console:
1/16/2022, 12:48:55 AM G28
Object Model deployuser token =false
Lift Z in advance of deploy
1/16/2022, 12:49:00 AM Probe Value =0
deployprobe start value Probe already picked up. Manually return probe to the dock
Object Model deployuser token =true
Lift Z in advance of deploy
1/16/2022, 12:49:05 AM Probe Value =0
deployprobe start value Probe already picked up. Manually return probe to the dock
Error: Homing failed
@alex-cr My apologies... I didn't even know that was a thing.... I fixed it! I can see where this makes it much easier.. again, sorry about that.
This is the error I keep getting....
1/15/2022, 9:23:15 PM deployprobe start value Probe already picked up. Manually return probe to the dock
Error: Homing failed
I was told that the script setup as I have it, should be able to tell whether or not the probe is already picked up, and simply act accordingly.
That does not appear to be the case.
Using the three wires, My probe lights are on all of the time, and turn off when it probes.
Normal probe state shows "not triggered" and changes if I hit the micro switch.
My homeall.g is the only script that runs all the way through.
If I try to home only Z, it defaults to the above error.
Euclid provides a 4 point bed leveling example, I have a railcore, which uses 3 point tramming, so I pointed the script to My Bed.g script.
I assume that is correct?
sorry for the huge post.
Hey all!
I've been running absolutely fine for quite some time, so I decided to make life interesting, and change probes.
I've been reading for days.
Running: Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.1.1 (2020-05-19b2)
Duet WiFi Server Version: 1.23
I tried about 3 different people's scripting for the euclid, and I still cannot complete a homing cycle.
I was finally pointed to the euclid example firmware files for the probe, and while they get "most of the way there", they continually tell me I have to replace the probe to it's dock manually"
If I post My files, would anyone mind checking to see where I'm going wrong?
Thanks so much!
-Steve
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.1 on Tue Jun 09 2020 01:46:51 GMT-0400 (Eastern Daylight Time)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"RailCore II ZL" ; set printer name
M669 K1 ; select CoreXY mode
;Paneldue
M575 P1 B57600 S1 ; paneldue comms parameters
; Network
M552 S1
M557 S"Lynch WiFi Main" P"internet4u"
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet
;Filament Sensor
M591 D0 P1 C"e0_stop" S1 D0; Simple Filament sensor for extruder drive 0 is connected to E0 endstop input, enabled,
M591 D0 ; display filament sensor parameters for extruder drive 0
;Leadscrew locations
M671 X-16.22:-16.22:290 Y23:274:150 S10 ;Front left,(-10,22.5) Rear Left (-10.,227.5) , Right (333,160) S7.5 is the max correction - measure your own offsets, to the bolt for the yoke of each leadscrew
; Drives
M569 P0 S0 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes backwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S0 ; physical drive 3 goes backwards
M569 P5 S0 ; Drive 5 goes backwards Front Left Z
M569 P6 S0 ; Drive 6 goes backwards Rear Left Z
M569 P7 S0 ; Drive 7 goes backwards Right Z
M584 X0 Y1 Z5:6:7 E3
; set drive mapping
M350 ; configure microstepping without interpolation
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X201.50 Y201.50 Z800.00 E386 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z500.00 E1200.00 ; 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
; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X320 Y320 Z280 S0 ; set axis maxima
; Endstops
M574 X1 S1 P"xstop" ; configure active-low endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-low endstop for low end on Y via pin ystop
; EUCLID Probe
M574 Z1 S2 ; configure Z-probe endstop for low end on Z
;
M558 K0 P5 C"^zprobe.in" H8 F300 60 T9000 A3 S0.01
; K0 for probe 0, P5 for NC switch, C for input pin,
; ^ for enabling the native pullup resistor on Duet 2
; hardware running RRF3
; H dive height of 8mm, F300 probing speed 6mm/sec,
; T9000 travel speed 150mm/sec,
; A3 number of probes 1, S0.01 max tolerance of 0.01
;
G31 K0 P500 X-16.4 Y-29.4 Z0.90 ; CHECK for LOOSE things first! set Z probe trigger
; value, offset and trigger height. Higher numbers
; makes nozzle closer to bed
; switch plunger is 16.4mm to the LEFT and 29.27mm in
; FRONT of the nozzle. Switch triggers 0.9mm BELOW nozzle
;
; if you have to move the nozzle away from the bed,
; decrease the G31 Z value by the amount of baby stepping used.
M557 X7:305 Y1:303 S20 ; define mesh grid
; 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 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
; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S0 H1 T45 ; set fan 1 value. Thermostatic control is turned on
;M950 F2 C"fan1" Q500 ; create fan 2 on pin fan1 and set its frequency
;M106 P2 S1 H1 T45 ; set fan 2 value. Thermostatic control is turned on
; Tools
M563 P0 S"Extruder" D0 H1 F0 ; 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
; Custom settings are not defined
M950 F3 C"duex.fan3"
M950 F4 C"duex.fan4"
M106 P3 S0.5 ; LED half brightness
M106 P4 S0.5 ; LED half brightness
; Miscellaneous
T0 ; select first tool
; ***********************************************************
; Euclid Probe Fixed Dock M401 Deploy Probe Macro
; RRF3.X Firmware Example
; saveas system/deployprobe.g
; comments and echo statements throughout are provided for convenience
; ***********************************************************
; echo "Running deployprobe.g"
; if !move.axes[0].homed || !move.axes[1].homed ; If the printer hasn't been homed, home it
; M98 P"0:/sys/homexy.g"
; uncomment next line to echo the probe deploy state
echo "Object Model deployuser token =" ^sensors.probes[0].deployedByUser
M564 H1 S0 ; Allow movement BEYOND axes boundaries (for Y to reach probe dock)
G91 ; relative positioning
echo "Lift Z in advance of deploy"
G1 H2 Z15 F3000 ; move Z 15 for clearance above dock.
; ; need to figure out some safety check on this
G90 ; absolute positioning
; echo "Probe Value =" ^sensors.probes[0].value[0]
if sensors.probes[0].value[0]!=1000 ; if sensor is value other than 1000 do this
; uncomment next line to echo the probe deploy state
; echo "deployuser token = " ^sensors.probes[0].deployedByUser
; echo "Probe State = " ^sensors.probes[0].value[0]
abort "deployprobe start value Probe already picked up. Manually return probe to the dock"
; if we're here we know it's becasue the above is true which I assume is because you have an NC switch as a probe.
; echo "Passed first logic test to deploy probe"
;G1 x17 y292 ; Stow Clear point
;G1 x17 Y295 ; Stow Home Point
;G1 X48 Y295 ; Stow Enter Point
G1 x17 y292 F6000 ; move adjacent to probe dock location
M400 ; wait for moves to finish
; echo "Probe Pickup while loop running"
; uncomment next line to echo the probe deplot state
; echo "Object Model Deployuser token (before while loop) = " ^sensors.probes[0].deployedByUser
while sensors.probes[0].value[0]=1000
G1 x17 Y295 F3000 ; move over dock
G4 S1 ; pause for pickup
echo "Probe Value =" ^sensors.probes[0].value[0]
G1 X48 Y295 F1200 ; slide probe out of dock - slowly
M400
; G4 S1 ; pause 1 seconds
; the following check is to halt the while loop from repeating after 1 try at deploying the probe
echo "Iteration = " ^iterations
if iterations=1
break
echo "Probe Pickup while loop complete"
; uncomment to echo the probe deplot state
; echo "Object Model Deployuser token (after while loop) = " ^sensors.probes[0].deployedByUser
G90 ; absolute positioning
G1 X150 Y150 Z10 F3000 ; move bed to clear probe from build surface
M400 ; wait for moves to finish
if sensors.probes[0].value[0]!=0
; uncomment to echo the probe deploy state
echo "Object Model Deployuser token (in abort if section)= " ^sensors.probes[0].deployedByUser
abort "Deployprobe endvalue not 0 Probe not picked up! Deploy cancelled."
M564 H1 S1 ; Restrict movement to within axes boundaries (for normal Y movement)
echo "Macro deployprobe.g complete"
; ***********************************************************
; Euclid Probe homez.g Example Macro
; RRF3.X Firmware Example
; saveas system/homez.g
; comments and echo statements throughout are provided for convenience
; ***********************************************************
if !move.axes[0].homed || !move.axes[1].homed ; If the printer hasn't been homed, home it
M98 P"0:/sys/homexy.g"
M561 ; clear any bed transform
M290 S0 R0 ; clear baby steps per Wes C
G91 ; relative positioning
M400
; G1 H2 Z6 F6000 ; lift Z relative to current position
G90 ; absolute positioning
; echo "Call deployprobe.g macro"
M401 P0 ; This runs macro file deployprobe
; echo "Return"
G1 X145 Y162.5 F9000 ; go to first probe point
M400
; echo "G30 S-2 Command"
G30 -2
G1 Z10
M400
G4 P500
; echo "Call bed.g macro"
M98 P"0:/sys/bed.g" ; tram bed
; echo "Return"
G1 X145 Y165 F9000 ; go back to the first probe point and reprobe 0 in case it moved
G30
; echo "Call retractprobe.g macro"
M402 P0 ; retract probe
; echo "Return"
G1 Z10 F600 ; lift Z relative to current position
G90 ; absolute positioning
M564 S1 H0
; G1 X150 Y0 F9000 ; move carraige to center front
I'm 97% into an almost 40 hour print of about 150 small parts on My 500 x 500 corexy. The filament sensor never allows a print to make it completely through without stopping at least 2 or 3 times. This particular print is using ironing (which I inadvertently sliced the file with) and each part is erroring 6-7 times before advancing to the next. I've literally been sitting here for 5 hours hitting resume, and I'm about to go batty!
Is there a way to disable this thing so the print can finish on it's own?
Also, I've worked on this thing for over a year, and I've never gotten it to survive an entire print. I've tried every suggestion you guys had.
Before I simply put an open / close switch in, is there a way to set this so that it basically will be bulletproof, and only tell me when filament runs out? That's all I care about. Is there filament, or not?
what settings would I need to change to ensure that I can finish a print without multiple interventions?
Thanks so much!
Thanks guys... I kind of figured it was just the size of the bed... 1 degree tilt on a 220mm bed is big... double that, and I guess you're right... it's exceeding the max correction value... raising that value almost always leads to a bed crash. I've learned that.. Nothing I can't live with... I just wondered if I needed to set up the maths or something.
I appreciate the reply!
I was wondering.... my Railcores âtrue levelâ the bed in the first pass, and really donât do much the 2 and third time around. I built this new machine for fun, as I wanted a ginormous corexy. Itâs not totally done, as I didnât have the 1/2â aluminum to mill my Carriage parts. I kind of appropriated the Railcore style for the Y carriage for now, but I designed a more rigid gantry using a 15mm linear guide. Itâs a mosh mash if my FT-5 upgrade parts I designed a few years ago, a little Railcore, and a whole lot of last minute changes. 550mm of Mic6 goodness! I milled all the parts the other night.
Anyhow, when I do a âtrue levelâ, , I have to throw a round bubble level in the bed to get it close before itâll complete. Otherwise I get one corner that doesnât trigger the BL touch. I assume this is just due to the fact that the bed is longer, so a variation in height compounds. But hereâs the deal. When it levels, itâs still way off after the first adjustment. Then it gets better for the second, and pulls it flat on the third pass. Is that normal? Or should it try to fix it in the first pass?
Either way, it works, but my correction is progressive, rather than immediate!
Thanks guys!!!
Thanks man! I'm on 3.1, so I guess It'll just work then. 
I have a very large, very High Wattage Silicone heater I'm using, and it has it's own pid control box and thermistor.
I was wondering If I can simply Tell RepRap not to look for a bed heater?
This is a machine for a specific purpose, it's always going to run at the same temp for the most part. It takes about 7 minutes to heat up, so I'd just rather set it by it's box, and use it, without it cooling down between plate changes..
How would one go about this? telling The Firmware I have no heated bed I mean?
Thanks sooooo much!
@bearer Well, thanks a million! I'm all upgraded now... I'm still looking.... I'll not stop trying, But I really appreciate you helping me out!
Ok, I'm impressed, but how the hell did you find it? I see no links on the release pages... If I search in github, I never could find that.. You obviously understand how github works, would you mind letting me in on the secret? lol
And thanks!
Do you happen to know where I can find a binary for the 3.0 build? I can only find the raw code, and i have no idea how to build it. I already have all my config files and macros made for the machine, but nothing works, as it's using the new language for 3.x.
Thanks again!