Here is what I use to choose machine type at startup depending on what tool is connected.
I include a resistor connected to the sensor pin inside the tool connector. This gives a fixed temperature reading and lets the machine choose its type depending on what is connected at startup.

M308 S23 P"e2temp" Y"thermistor" T100000 B3950 A"ModeSelector"   ;setup a thermistor input as config selection sensor 


;wait for the sensor to start returning meaningful values (don't know if there is a better approach for this) 
while sensors.analog[23].lastReading==0||sensors.analog[23].lastReading==2000
  echo

;print the value detected (useful when adding a new mode)
;M117 ModeSelector value:{sensors.analog[23].lastReading}

;depending on sensor reading choose a system folder
if sensors.analog[23].lastReading==-273.1
  M117 No Attachment Detected.
elif sensors.analog[23].lastReading<155
  M117 Going to be a CNC.
  M505 P"CNC"
else 
  M117 Going to be a 3D printer.
  M505 P"Printer"

;load config.g from the chosen system folder
M98 P"config.g"

OK, I figured it out. The config-override.g file was setting up the heaters again after i disabled them in the config file.

@taconite that's a cool design. Where did you get the tapered metal parts?

@fma I also ordered the same set but i don't think it's ever coming.
I'm using this pump and it's silent unless you put your ear next to it.

My solution is a mix of mosquito style and water cooling. I used a silicon tube (like Marc Peltier) to circulate water around the heat-brake. See the post here: https://groups.google.com/d/msg/deltabot/n3PImRPtmOo/i8WCxQ1kBgAJ

I punctured the silicon tube with a smaller (than the heat-brake) dimeter steel tube. I also noticed that I had to put another peace of tube under the one I was puncturing. Puncturing against a hard surface did not produce watertight holes. I used the same tubes for the standoffs.

I have been running the setup for months now with no leaks.

Maybe you could use a single tube too cool several heat-brakes?

Here is what I use to choose machine type at startup depending on what tool is connected.
I include a resistor connected to the sensor pin inside the tool connector. This gives a fixed temperature reading and lets the machine choose its type depending on what is connected at startup.

M308 S23 P"e2temp" Y"thermistor" T100000 B3950 A"ModeSelector"   ;setup a thermistor input as config selection sensor 


;wait for the sensor to start returning meaningful values (don't know if there is a better approach for this) 
while sensors.analog[23].lastReading==0||sensors.analog[23].lastReading==2000
  echo

;print the value detected (useful when adding a new mode)
;M117 ModeSelector value:{sensors.analog[23].lastReading}

;depending on sensor reading choose a system folder
if sensors.analog[23].lastReading==-273.1
  M117 No Attachment Detected.
elif sensors.analog[23].lastReading<155
  M117 Going to be a CNC.
  M505 P"CNC"
else 
  M117 Going to be a 3D printer.
  M505 P"Printer"

;load config.g from the chosen system folder
M98 P"config.g"

Thank you all for your answers.
I was wondering since im trying to use the filament config.g but it doesn't seem to be called when the printer starts up. I figured out i need to put M703 in the main config.g after selecting the tool. I think this should be mentioned in the docs since just putting it in tpost0.g doesn't seem to do the job on startup .

Hello,

I'm wondering if there is any documentation that describes an overview of how the different gcode scrpits are executed on startup and any later user input. I know all of this is described somewhere in the documentation, but it seems hard to get an overview of all of it. A simple chart of what happens when would be useful imho.

@jay_s_uk said in Conditional GCode and object model variables:

The most useful thing for me would being able to detect a voltage on an input to identify which tool is fitted.
E.g. tool 1 is 1V, tool 2 is 2V and so on.
Then the machine would be aware of what tool is fitted and apply offsets accordingly etc.

I would also find this very useful. Probably the only thing i would need conditional gcode for.
Would need this to load a different config depending on what is connected on machine boot.

OK, I figured it out. The config-override.g file was setting up the heaters again after i disabled them in the config file.

Hello,

I am trying to set up my fans and LEDs. I made a small board with mosfets for the expansion connector. In my config file I have:

M307 H2 A-1 C-1 D-1 ;disable heaters
M307 H3 A-1 C-1 D-1 ;
M307 H4 A-1 C-1 D-1 ;
M307 H5 A-1 C-1 D-1 ;
M307 H6 A-1 C-1 D-1 ;
M307 H7 A-1 C-1 D-1 ;

; Fans
M106 P0 A2 S0 I0 F500 C"Part" ;
M106 P1 S0 I0 F500 H1 T45 C"Hotend" ;
M106 P2 A3 S0 I1 F500 H104 T45:50 C"PSU" ;
M106 P3 A4 S0 I1 F500 H100:101:102 T45:65 C"BOARD" ;
M106 P4 A5 S0 I1 F500 C"LED1"
M106 P5 A6 S0 I1 F500 C"LED2"
M106 P6 A7 S0 I1 F500 C"LED3"

The problem I am having is that whenever I set the fan speed for the lets say LED1 fan it only works for a moment and then switches back to full speed. I don't think its a problem with my board because i can see the same behaviour on the output pin if i measure with an oscilloscope. the same thing happens on the PART fan which is connected to the Heater2 port. Its as if something is reseting the fans to full speed periodically.
Any help with this would be appreciated. Thanx