Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. phoenix
    • Profile
    • Following 0
    • Followers 0
    • Topics 11
    • Posts 36
    • Best 5
    • Controversial 0
    • Groups 0

    phoenix

    @phoenix

    7
    Reputation
    3
    Profile views
    36
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    phoenix Unfollow Follow

    Best posts made by phoenix

    • Smart Orbiter 3 setup (filament Sensor, RGB and hotend LED)

      Encouraged by the post by @cdoe on setting up the Orbiter 2 filament sensor, I gave it a hard try to set up the Smart Orbiter 3. All features are working and I come amazed at the power of RRF 🙂

      The Smart Orbiter 3 has 8 connections at the base, containing a RGB Matrix LED connection, a simple hotend LED and 2 outputs (FS for sensing if filament is present) and FTU (outputs if filament is tangled or filament unload button is pressed). (check the website https://www.orbiterprojects.com/so3/ in section 3.3 Integrated Smart Features for polarity: I spent a day trying to figure out why nothing was working only to discover that blue and red wires are NOT GND and 3V 🙂 )

      Similar to the Orbiter 2 Sensor, the set up is slightly more elaborate than just a sensor since both outputs have 2 functions and logic is not straightforward as well. FS output works as expected as in changing state when filament is present or runs out, FTU output only changes state if filament is already present.

      I am running a e3d toolchanger with Duet 2 Wifi and DueX5. I connected the cables to the pins 1 -6 of the LCD connector. (all works just fine on 3.3V) and reused triggers developed by @cdoe for things to work.

      This is a section in config.g

      ; Filament Sensor & Smart H2
      M950 J3 C"^connlcd.enca"            ; define logical input for filament auto load
      M581 P3 T5 S1 R0                    ; define trigger for filament auto load triggers trigger5.g
      M581 P3 T2 S0 R0                    ; define trigger for filament sensing triggers trigger2.g
      M950 J4 C"^connlcd.encb"            ; define logical input for filament unload
      M581 P4 T6 S1 R0                    ; define trigger for filament auto unload triggers trigger6.g
      M950 P5 C"connlcd.rs"              	; define logical output for hotend LED
      M950 E0 C"connlcd.5" T1 U1          ; create a RGB Neopixel LED strip on the LCD Connector 5 port (RRF 3.5 and later)
      M98 P"0:/macros/h2led"              ; Set LED Colour according to state of H2
      M42 P5 S0					        ; Turn Hotend LED off
      

      Obviously the most important part is getting the matrix LED to work 😁 with a macro I called h2led.g

      ; Sets MatrixLED according to filament Sensor status
      if sensors.gpIn[3].value = 1
          M150 E0 R000 U255 B000 P255			; set LEDs to green, full brightness
      else
          M150 E0 R255 U000 B000 P128			; set LEDs to red, half brightness
      

      Triggers 2, 5 & 6 reuse the macros developed for the smart orbiter

      ; trigger2.g
      if state.status == "processing"
          M300 S2000 P100                                     ; play beep sound
          M291 P"Ran out of filament while printing" S0 T3    ; display message
          M25
      elif state.status == "pausing" || state.status == "paused"
          M291 P"Retriggered filament sensor during pause" ; display message
      else
          M300 S2000 P100                     ; play beep sound
          M291 P"Ran out of filament" S0 T3   ; display message
      

      For the load and unload triggers, I am using a single printer macro for all toolheads for loading and unloading. As such, I pass on a parameters representing the toolhead to the macro for addressing the right toolhead. And then obviously triggering the color LED macro at the end of it to adjust LED according to status.

      ; trigger5.g
      M150 E0 R000 U000 B255 P128			; set LEDs to blue, half brightness
      M98 P"0:/macros/filament-load" X2   ; Load Filament for T2
      M98 P"0:/macros/h2led"              ; Set LED Colour according to state of H2
      T-1                                 ; Park tool
      
      ; trigger6.g
      if state.status = "processing"
          M300 S2000 P100                                                     ; play beep sound
          M291 P"Filament is stuck or filament unload button pressed" S0 T3   ; display message
          M150 E0 R000 U000 B255 P128			                                ; set LEDs to blue, half brightness
          M25
      else
          M150 E0 R000 U000 B255 P128			                                ; set LEDs to blue, half brightness
          M98 P"0:/macros/filament-unload" X2					                ; Call Unload Macro and pass Tool number using X parameter
          M98 P"0:/macros/h2led"                                              ; Set LED Colour according to state of H2
          T-1
      

      Hope this helps somebody else - it's a nifty little extruder and I'm stoked the electronics are now fully integrated!

      posted in Third-party add-ons
      phoenixundefined
      phoenix
    • RE: Solved - Accelerometer connected causing temperatures fluctuate

      When I opened up to take a picture of the wiring, I noticed a piece of unconnected wire that had fallen off and was resting on the Duex. I guess I'm lucky not to have shortened anything, but the issue is definitely resolved 🙂

      Thanks @gloomyandy for your indirect help 🙂

      posted in General Discussion
      phoenixundefined
      phoenix
    • RE: Orbiter V3.0, Can the "smart" hardware be used with Duet2/RRF?

      just in case OP is still interested: I posted my working config here
      https://forum.duet3d.com/topic/37868/smart-orbiter-3-setup-filament-sensor-rgb-and-hotend-led

      posted in Duet Hardware and wiring
      phoenixundefined
      phoenix
    • RE: Orbiter filament sensor v2 setup

      Just want to say thanks - this works a treat!!

      posted in Third-party add-ons
      phoenixundefined
      phoenix
    • RE: Passing Parameters - unknown variable

      @fcwilt @jay_s_uk thanks for your help! I have now my first macros running 🙂

      posted in General Discussion
      phoenixundefined
      phoenix

    Latest posts made by phoenix

    • RE: Orbiter V3.0, Can the "smart" hardware be used with Duet2/RRF?

      just in case OP is still interested: I posted my working config here
      https://forum.duet3d.com/topic/37868/smart-orbiter-3-setup-filament-sensor-rgb-and-hotend-led

      posted in Duet Hardware and wiring
      phoenixundefined
      phoenix
    • Smart Orbiter 3 setup (filament Sensor, RGB and hotend LED)

      Encouraged by the post by @cdoe on setting up the Orbiter 2 filament sensor, I gave it a hard try to set up the Smart Orbiter 3. All features are working and I come amazed at the power of RRF 🙂

      The Smart Orbiter 3 has 8 connections at the base, containing a RGB Matrix LED connection, a simple hotend LED and 2 outputs (FS for sensing if filament is present) and FTU (outputs if filament is tangled or filament unload button is pressed). (check the website https://www.orbiterprojects.com/so3/ in section 3.3 Integrated Smart Features for polarity: I spent a day trying to figure out why nothing was working only to discover that blue and red wires are NOT GND and 3V 🙂 )

      Similar to the Orbiter 2 Sensor, the set up is slightly more elaborate than just a sensor since both outputs have 2 functions and logic is not straightforward as well. FS output works as expected as in changing state when filament is present or runs out, FTU output only changes state if filament is already present.

      I am running a e3d toolchanger with Duet 2 Wifi and DueX5. I connected the cables to the pins 1 -6 of the LCD connector. (all works just fine on 3.3V) and reused triggers developed by @cdoe for things to work.

      This is a section in config.g

      ; Filament Sensor & Smart H2
      M950 J3 C"^connlcd.enca"            ; define logical input for filament auto load
      M581 P3 T5 S1 R0                    ; define trigger for filament auto load triggers trigger5.g
      M581 P3 T2 S0 R0                    ; define trigger for filament sensing triggers trigger2.g
      M950 J4 C"^connlcd.encb"            ; define logical input for filament unload
      M581 P4 T6 S1 R0                    ; define trigger for filament auto unload triggers trigger6.g
      M950 P5 C"connlcd.rs"              	; define logical output for hotend LED
      M950 E0 C"connlcd.5" T1 U1          ; create a RGB Neopixel LED strip on the LCD Connector 5 port (RRF 3.5 and later)
      M98 P"0:/macros/h2led"              ; Set LED Colour according to state of H2
      M42 P5 S0					        ; Turn Hotend LED off
      

      Obviously the most important part is getting the matrix LED to work 😁 with a macro I called h2led.g

      ; Sets MatrixLED according to filament Sensor status
      if sensors.gpIn[3].value = 1
          M150 E0 R000 U255 B000 P255			; set LEDs to green, full brightness
      else
          M150 E0 R255 U000 B000 P128			; set LEDs to red, half brightness
      

      Triggers 2, 5 & 6 reuse the macros developed for the smart orbiter

      ; trigger2.g
      if state.status == "processing"
          M300 S2000 P100                                     ; play beep sound
          M291 P"Ran out of filament while printing" S0 T3    ; display message
          M25
      elif state.status == "pausing" || state.status == "paused"
          M291 P"Retriggered filament sensor during pause" ; display message
      else
          M300 S2000 P100                     ; play beep sound
          M291 P"Ran out of filament" S0 T3   ; display message
      

      For the load and unload triggers, I am using a single printer macro for all toolheads for loading and unloading. As such, I pass on a parameters representing the toolhead to the macro for addressing the right toolhead. And then obviously triggering the color LED macro at the end of it to adjust LED according to status.

      ; trigger5.g
      M150 E0 R000 U000 B255 P128			; set LEDs to blue, half brightness
      M98 P"0:/macros/filament-load" X2   ; Load Filament for T2
      M98 P"0:/macros/h2led"              ; Set LED Colour according to state of H2
      T-1                                 ; Park tool
      
      ; trigger6.g
      if state.status = "processing"
          M300 S2000 P100                                                     ; play beep sound
          M291 P"Filament is stuck or filament unload button pressed" S0 T3   ; display message
          M150 E0 R000 U000 B255 P128			                                ; set LEDs to blue, half brightness
          M25
      else
          M150 E0 R000 U000 B255 P128			                                ; set LEDs to blue, half brightness
          M98 P"0:/macros/filament-unload" X2					                ; Call Unload Macro and pass Tool number using X parameter
          M98 P"0:/macros/h2led"                                              ; Set LED Colour according to state of H2
          T-1
      

      Hope this helps somebody else - it's a nifty little extruder and I'm stoked the electronics are now fully integrated!

      posted in Third-party add-ons
      phoenixundefined
      phoenix
    • RE: Passing Parameters - unknown variable

      @fcwilt @jay_s_uk thanks for your help! I have now my first macros running 🙂

      posted in General Discussion
      phoenixundefined
      phoenix
    • Passing Parameters - unknown variable

      Hello, I am trying to create a filament load macro, that gets called by the respective filament load button, or if called manually (which hotend was pressed is unknown) asks for which hotend to work with.

      I can't crack one final step - when running the macro (triggered, or called manually), I get an error: when triggered by the button it returns
      Error: in file macro line 4 column 23: meta command: unknown variable 'hotendselect'

      The sequence is first that the button triggers the trigger5.g file to pass on the value "2" :

      ; trigger5.g
      M98 P"0:/macros/filament-load" X2   ; Load Filament for T2
      

      then, the error is in Line 4 of the filament-load macro:

      ;Autoload filament macro. Press button then insert filament to load
      if exists(param.X)
        ; Parameter X was passed
        set var.hotendselect = param.X
        echo "Autoload for Extruder " ^ var.hotendselect
        else
        ; Parameter X was NOT passed, display screen for selecting one of the hotends
        M291 R"Unload Filament" P"Request for Extruder #" S4 K{0,1,2,3} J1
        set var.hotendselect = {input}
      endif
      
      T{var.hotendselect}                       ; Select Tool as passed on
      M300 S2000 P100   				              	; play beep sound
      M291 P"Insert filament in Tool!" S0 T3   	; display message
      M302 P1   	        				            	; enable cold extrusion
      G4 S5 						                      	; wait for 5 seconds to insert filament
      G1 E15 F500  				                   		; load filament inside the gears
      M109 S235 T0 					        	          ; set hotend temperature and wait
      G1 E100 F300 				          	        	; extrude 100mm, you may need to reduce speed for very soft TPU
      M104 S0 T0 					                    	; set hotend temperature to 0
      M302 P0 					                      	; disable cold extrusion
      M291 P"Filament autoload complete!" S0 T3 ; display message
      
      unset var.hotendselect                    ; Erase variable
      

      Apologies with what I assume is a noob question - I tried search, the GCode manual and chatGPT to no avail...

      posted in General Discussion
      phoenixundefined
      phoenix
    • RE: Orbiter V3.0, Can the "smart" hardware be used with Duet2/RRF?

      @dbenhart said in Orbiter V3.0, Can the "smart" hardware be used with Duet2/RRF?:

      I'm wondering whether anyone made progress on this topic, connecting a Smart Orbiter 3 to a Duet board. I have a Duet3 MB6HS and am trying to with up the SO3 to it. Specifically, I'm trying to connect the filament sensor and LED. I've got it wired up to IO4, with the yellow/LED being on IO4.out, and brown/filament-sensing being on io4.in. I've got blue/GND and red/+5v wired up to the corresponding pins on IO4 as well. I'm not getting anything from the LED, and the voltage change on the filament sensor doesn't make any sense either. I'm using a multimeter to measure IO4.in to GND, but the voltage change is only 0.1V when I put filament in. Anyone have any thoughts on this?

      Have you been able to make any sense of this? I just finished mounting the SO3 to my Toolchanger, and now need to tackle the electronic side: printing works, but would be nice to have the filament sensor working. I understand that the LED matrix is not addressable in Duet2 but hopefully the triggers/button can be read?

      posted in Duet Hardware and wiring
      phoenixundefined
      phoenix
    • RE: Orbiter filament sensor v2 setup

      Just want to say thanks - this works a treat!!

      posted in Third-party add-ons
      phoenixundefined
      phoenix
    • RE: Bed temperature dropdown does not match setting

      @jay_s_uk The first screenshot in my original post shows the Machine Settings Tab: on the bottom you see the presets (90 / 85 / 65 / 60). The dropdown (250 /235 / 220 /205 / 195 / 160 / 120 ) is what I get as choices when I go to set Bed temperature

      posted in Duet Web Control
      phoenixundefined
      phoenix
    • RE: Bed temperature dropdown does not match setting

      @jay_s_uk thanks - deleted the file but it came back the same way 😞

      posted in Duet Web Control
      phoenixundefined
      phoenix
    • RE: Bed temperature dropdown does not match setting

      @Phaedrux Sorry I forgot to mention... 3.5.3 both
      debb1a8d-8834-4872-b82e-0bfd1c4f23bf-{67270B0C-9F25-43A6-AA74-57D90511C179}.png

      posted in Duet Web Control
      phoenixundefined
      phoenix
    • Bed temperature dropdown does not match setting

      Hello, I have noticed that in the Web interface, the dropdown for Bed temperatures does not match its preset list: instead it lists the same temperatures as for the Tools. I assume there's a config file that has failed to update - can somebody point me in the right direction?
      69cd14ff-3636-438c-8654-44048b59984b-{F76D6C92-95D0-4E5A-8A48-EFF83334D616}.png

      The "Machine Specific Settings":
      457af88d-917b-482b-b9e4-d9460f984f3c-{B6E2BC07-EBC9-400B-99A3-B327C98C2B1C}.png

      posted in Duet Web Control
      phoenixundefined
      phoenix