IDEX 500 Orbiter V2 Smart Sensor issues.
I am trying to get this setup right on my IDEX, I loaded filament into T0 and T1 and the green LED is on. In GUI shows empty. Any ideas?
31 Replies
Send pic of your toolboard, specifically where the smart sensor is plugged in
Best can get
You wired it wrong
really?
green and yellow wrong?
Yes
Refer to image
k. going to pull it and try again
same
Send printer.cfg
Also do a firmware restart, see if that reinitializes it
Now load filament, should turn green and show on ratos
In GUI shows detected.
Ok, so it's working
No, It is RED so no filament but GUI shows detected
You do not need orbiter-sensor.cfg
Orbiter 2 Smart Sensor
Smart filament sensor for the Orbiter V2 extruder! The assembly guide walks you through the steps necessary to prepare your printer for the upgrade.
Please follow the docs
I think found it. I got the cfg from @Jessica and I think the pins are wrong.
Yeah this is just my specific way of referencing all the RatRig values for the sensor. It's definitely not necessary to do it that way.
PB4 and PB3 should be used
working now I believe. Just need to start print and run it out.
this seems to work
If you had them reversed from what I did, yes, then your pin settings should be fine.
Ah gotchya, I've been seeing people add both the orbiter-sensor.cfg that is referenced elsewhere on klipper docs, and the details to printer.cfg so everything gets mixed and it's chaos lol
I can see that. Also since new kits come with it guessing RatOS will add it to printer.cfg at some point. Cut filament to see if pauses here in a few
I just prefer to have add ons as a separate cfg file so it doesn't get fully overwritten in the case that updates happen that rewrite printer.cfg.
Thanks. Works now!
So now here is next odd issue. When I but include the orbiter-sensor.cfg file and home printer then click IDEX Copy I can print a copy like normal. When I include orbiter-sensor.cfg file when I home but when click IDEX copy T1 heats up to 220 and then this: 12:08 PM
Move out of range: 554.016 250.000 15.000 [-150.000]
12:08 PM
Move out of range: 554.016 250.000 15.000 [-150.000]
12:08 PM
Move out of range: 554.016 250.000 15.000 [-150.000]
12:08 PM
Move out of range: 554.016 250.000 15.000 [-150.000]
12:08 PM
Move out of range: 554.016 250.000 15.000 [-150.000]
12:08 PM
Move out of range: 554.016 250.000 15.000 [-150.000]
Also same thing happens when put this code into printer.cfg. [filament_switch_sensor toolhead_filament_sensor_t0]
Pause_on_runout: False
event_delay: 0.1
switch_pin: ^toolboard_t0:PB4
runout_gcode:
_ON_TOOLHEAD_FILAMENT_SENSOR_RUNOUT TOOLHEAD=0
insert_gcode:
_ON_TOOLHEAD_FILAMENT_SENSOR_INSERT TOOLHEAD=0
[gcode_button toolhead_filament_sensor_button_t0] pin: ^!toolboard_t0:PB3 release_gcode:
{% if (printer.print_stats.state == "printing") %} _ON_TOOLHEAD_FILAMENT_SENSOR_CLOG TOOLHEAD=0 {% else %} _ON_FILAMENT_SENSOR_BUTTON_PRESSED TOOLHEAD=0 {% endif %} press_gcode: [filament_switch_sensor toolhead_filament_sensor_t1] pause_on_runout: False event_delay: 0.1 switch_pin: ^toolboard_t1:PB4 runout_gcode: _ON_TOOLHEAD_FILAMENT_SENSOR_RUNOUT TOOLHEAD=1 insert_gcode: _ON_TOOLHEAD_FILAMENT_SENSOR_INSERT TOOLHEAD=1
[gcode_button toolhead_filament_sensor_button_t1] pin: ^!toolboard_t1:PB3 release_gcode:
{% if (printer.print_stats.state == "printing") %} _ON_TOOLHEAD_FILAMENT_SENSOR_CLOG TOOLHEAD=1 {% else %} _ON_FILAMENT_SENSOR_BUTTON_PRESSED TOOLHEAD=1 {% endif %} press_gcode:
[gcode_button toolhead_filament_sensor_button_t0] pin: ^!toolboard_t0:PB3 release_gcode:
{% if (printer.print_stats.state == "printing") %} _ON_TOOLHEAD_FILAMENT_SENSOR_CLOG TOOLHEAD=0 {% else %} _ON_FILAMENT_SENSOR_BUTTON_PRESSED TOOLHEAD=0 {% endif %} press_gcode: [filament_switch_sensor toolhead_filament_sensor_t1] pause_on_runout: False event_delay: 0.1 switch_pin: ^toolboard_t1:PB4 runout_gcode: _ON_TOOLHEAD_FILAMENT_SENSOR_RUNOUT TOOLHEAD=1 insert_gcode: _ON_TOOLHEAD_FILAMENT_SENSOR_INSERT TOOLHEAD=1
[gcode_button toolhead_filament_sensor_button_t1] pin: ^!toolboard_t1:PB3 release_gcode:
{% if (printer.print_stats.state == "printing") %} _ON_TOOLHEAD_FILAMENT_SENSOR_CLOG TOOLHEAD=1 {% else %} _ON_FILAMENT_SENSOR_BUTTON_PRESSED TOOLHEAD=1 {% endif %} press_gcode:
Nothing about that code has anything to do with the print bed movement range.
I'm having the same problem as you. What code did you end up using?
This is what using now: