Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Software package 3.3beta3 released

    Scheduled Pinned Locked Moved
    Beta Firmware
    34
    96
    10.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • droftartsundefined
      droftarts administrators @TheBasedDoge
      last edited by

      @thebaseddoge I think a pin has been enabled for controlling the Neopixels on 12864 displays. But I don’t know if it works outside this use case. Will need some @dc42 guidance.

      Ian

      Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

      TheBasedDogeundefined 1 Reply Last reply Reply Quote 1
      • TheBasedDogeundefined
        TheBasedDoge @droftarts
        last edited by

        @droftarts I didn't think the Duet 2 Wifi supported the 12864 either, only the Maestro? Hopefully dc42 can clarify everything.
        thanks.

        1 Reply Last reply Reply Quote 0
        • Print3dundefined
          Print3d @dc42
          last edited by

          @dc42 I upgraded and noticed user variables in SBC mode are not showing up. I know integration was pulled in b2 and a fix was in the works for 3.3b3... Is this is a bug or have plans changed for user variable integration in SBC mode?

          dc42undefined 1 Reply Last reply Reply Quote 0
          • dc42undefined
            dc42 administrators @Print3d
            last edited by

            Global variables appear in the Object Model Explorer in 3.3beta3 but changes to their values are not picked up. That is fixed in the forthcoming 3.3RC1.

            Duet WiFi hardware designer and firmware engineer
            Please do not ask me for Duet support via PM or email, use the forum
            http://www.escher3d.com, https://miscsolutions.wordpress.com

            1 Reply Last reply Reply Quote 1
            • TheBasedDogeundefined
              TheBasedDoge @TheBasedDoge
              last edited by

              @thebaseddoge said in Software package 3.3beta3 released:

              @phaedrux Right, but this line in the 3.3beta3 changelog implies that Duet 2 can now do it. That is where my confusion comes from.

              Bit-banged NeoPixel LED strips are supported on Duet WiFi/Ethernet. On these boards RRF will wait stop movement while updating the LED strip, so M150 commands should not be issued while the machine is printing, other than at places where a short pause is acceptable such as at layer change and in the start and end scripts.
              

              @droftarts said in Software package 3.3beta3 released:

              @thebaseddoge I think a pin has been enabled for controlling the Neopixels on 12864 displays. But I don’t know if it works outside this use case. Will need some @dc42 guidance.

              Ian

              @dc42 do you have any more info on this? thank you!

              dc42undefined 1 Reply Last reply Reply Quote 0
              • dc42undefined
                dc42 administrators @TheBasedDoge
                last edited by dc42

                @thebaseddoge these are the pins to use when connecting a 12864 LCD to a Duet WiFi/Ethernet:

                constexpr Pin EncoderPinB = PortCPin(7);		// connlcd.3	-> exp2.6
                constexpr Pin EncoderPinA = PortAPin(8);		// connlcd.4	-> exp2.8
                constexpr Pin LcdNeopixelOutPin = PortDPin(18);	        // connlcd.5	-> exp1.5
                constexpr Pin LcdResetPin = PortCPin(28);		// connlcd.6	-> exp1.6
                constexpr Pin LcdA0Pin = PortDPin(19);			// connlcd.7	-> exp1.7
                constexpr Pin LcdCSPin = PortAPin(25);			// connlcd.8	-> exp1.8
                constexpr Pin EncoderPinSw = PortDPin(20);		// connlcd.9	-> exp1.9
                constexpr Pin LcdBeepPin = PortDPin(21);		// connlcd.10	-> exp1.10
                
                // Additional spi wiring for FYSETC Mini 12864 display:
                // connlcd.2 (gnd)	-> exp1.2
                // connsd.1 (+5V)	-> exp1.1
                // connsd.2 (gnd)	-> exp2.2
                // connsd.3 (SD CS)	-> exp2.7
                // connsd.4 (sck)	-> exp2.9
                // connsd.5 (mosi)	-> exp2.5
                // connsd.6 (miso)	-> exp2.10
                

                Warning! Some displays have the EXP1 and EXP2 connectors the other way round. So don't rely on the exp1 and exp2 pin numbers in the above.

                Duet WiFi hardware designer and firmware engineer
                Please do not ask me for Duet support via PM or email, use the forum
                http://www.escher3d.com, https://miscsolutions.wordpress.com

                droftartsundefined 1 Reply Last reply Reply Quote 0
                • droftartsundefined
                  droftarts administrators @dc42
                  last edited by

                  @dc42 I think the question was what pin to use to control Neopixels independently. Is connlcd.5 always available for Neopixels, or only when a 12864 is connected and defined in config.g?

                  Ian

                  Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                  dc42undefined 1 Reply Last reply Reply Quote 0
                  • dc42undefined
                    dc42 administrators @droftarts
                    last edited by

                    The support in RRF is intended for driving the LEDs on 7567 displays, however I think it should work without a display being configured provided that you don't try to use drivers 10 and 11. You will need to level shift the signal from 3.3v to 5V.

                    Duet WiFi hardware designer and firmware engineer
                    Please do not ask me for Duet support via PM or email, use the forum
                    http://www.escher3d.com, https://miscsolutions.wordpress.com

                    nmsmith89undefined TheBasedDogeundefined 2 Replies Last reply Reply Quote 0
                    • nmsmith89undefined
                      nmsmith89 @dc42
                      last edited by

                      @dc42
                      The RGBW Neopixels don't seem to work in 3.3b3 even though it's in the release notes. Is it not implemented yet or am I doing something wrong?

                      dc42undefined 1 Reply Last reply Reply Quote 0
                      • dc42undefined
                        dc42 administrators @nmsmith89
                        last edited by

                        @nmsmith89, it is implemented. There are new M150 X parameter values for RGBW. I have just updated the documentation at https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M150_Set_LED_colours.

                        Duet WiFi hardware designer and firmware engineer
                        Please do not ask me for Duet support via PM or email, use the forum
                        http://www.escher3d.com, https://miscsolutions.wordpress.com

                        nmsmith89undefined 1 Reply Last reply Reply Quote 0
                        • TheBasedDogeundefined
                          TheBasedDoge @dc42
                          last edited by

                          @dc42 I do have a PanelDue 5" display, but i dont have anything on stepper 10/11. so do I just need to use pin 5? what fw config changes are required?

                          1 Reply Last reply Reply Quote 0
                          • nmsmith89undefined
                            nmsmith89 @dc42
                            last edited by

                            @dc42 Thank You!!!

                            1 Reply Last reply Reply Quote 0
                            • Diamondbackundefined
                              Diamondback @SIam
                              last edited by

                              @siam Finally managed to get the accelerometer connected... I'm currently using about 3m of USB 3 extension cable and that seems to work ok, was just a lot of pain to wire up...
                              It looks like shielding is way more effective here than just twisted wire pairs (which I tried before and didn't work on its own)

                              dc42undefined 1 Reply Last reply Reply Quote 1
                              • dc42undefined
                                dc42 administrators @Diamondback
                                last edited by

                                @diamondback said in Software package 3.3beta3 released:

                                @siam Finally managed to get the accelerometer connected... I'm currently using about 3m of USB 3 extension cable and that seems to work ok, was just a lot of pain to wire up...
                                It looks like shielding is way more effective here than just twisted wire pairs (which I tried before and didn't work on its own)

                                The SPI frequency is currently 4MHz. I'll try reducing it, that may make it easier to use long cables.

                                Duet WiFi hardware designer and firmware engineer
                                Please do not ask me for Duet support via PM or email, use the forum
                                http://www.escher3d.com, https://miscsolutions.wordpress.com

                                1 Reply Last reply Reply Quote 1
                                • Diamondbackundefined
                                  Diamondback
                                  last edited by

                                  @dc42 said in Software package 3.3beta3 released:

                                  @diamondback said in Software package 3.3beta3 released:

                                  @siam Finally managed to get the accelerometer connected... I'm currently using about 3m of USB 3 extension cable and that seems to work ok, was just a lot of pain to wire up...
                                  It looks like shielding is way more effective here than just twisted wire pairs (which I tried before and didn't work on its own)

                                  The SPI frequency is currently 4MHz. I'll try reducing it, that may make it easier to use long cables.

                                  Thanks for looking into this. Is there any advantage to the higher frequency in practical use? If so, maybe offer te higher speeds as an option still?

                                  1 Reply Last reply Reply Quote 1
                                  • dc42undefined
                                    dc42 administrators
                                    last edited by

                                    3.3RC1 will default to 2MHz and allow the frequency to be changed using a new Q parameter on the M955 command.

                                    Duet WiFi hardware designer and firmware engineer
                                    Please do not ask me for Duet support via PM or email, use the forum
                                    http://www.escher3d.com, https://miscsolutions.wordpress.com

                                    1 Reply Last reply Reply Quote 2
                                    • snagit007undefined
                                      snagit007
                                      last edited by

                                      Thanks all for your great work!
                                      I have updated my BLV Cube with Duet3 and SBC to 3.3beta3 and everything works flawlessly. It is just incredible that the software can support individual configured systems providing first class prints.

                                      1 Reply Last reply Reply Quote 1
                                      • MintyTreborundefined
                                        MintyTrebor
                                        last edited by

                                        I have had a couple of instances of SBC users experiencing issues with the duetpluginservice not running by default, which is preventing 3rd party plugins being installed/run.

                                        Running

                                        sudo systemctl enable duetpluginservice
                                        

                                        and rebooting the sbc seems to clear the issue.

                                        Not sure if its the right thing to do or not.

                                        Adding it here by way of feedback.

                                        NodeDSF - Native Node-Red integration with Duet boards.
                                        BtnCmd - Customise DWC with user defined buttons/layouts/panels (DWC Plugin)
                                        ReleaseMgr - Duet update info inside DWC.
                                        Repo

                                        1 Reply Last reply Reply Quote 1
                                        • A Former User?
                                          A Former User @Phaedrux
                                          last edited by

                                          @phaedrux said in Software package 3.3beta3 released:

                                          @thebaseddoge said in Software package 3.3beta3 released:

                                          I see that Duet 2 can now do neopixel LEDs, which is super cool, but how do I wire them up and configure? Which pins should I use?

                                          https://duet3d.dozuki.com/Wiki/Neopixel_and_DotStar_LEDs

                                          Does it support only original Adafruit NeoPixel stripes or other brands of RGBW stripes?

                                          cosmowaveundefined dc42undefined 2 Replies Last reply Reply Quote 0
                                          • cosmowaveundefined
                                            cosmowave @A Former User
                                            last edited by

                                            @thedragonlord In the dozuki is written:
                                            Duet 3 MB6HC supports both DotStar and NeoPixel LED strips. Duet 3 Mini supports NeoPixel only. Duet 2 and Duet Maestro do not support these LED strips directly, but you can use an Arduino to interface them to a Duet.

                                            Mankati FSXT+, DeltaTowerV2, E3D MS/TC

                                            A Former User? 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Unless otherwise noted, all forum content is licensed under CC-BY-SA