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

    RepRapFirmware 3.0beta 11 released

    Scheduled Pinned Locked Moved
    Beta Firmware
    13
    72
    3.7k
    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.
    • dc42undefined
      dc42 administrators
      last edited by

      @smece, which model of Duet are you running RRF3 on?

      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 0
      • A Former User?
        A Former User
        last edited by

        duet2eth, iirc 1.0.2 was on the board

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

          Thanks. I found the problem, ir affects type 8 (unfiltered digital) and 9 (BLTouch) Z probes. The reading when triggered is 250 instead of 1000. So setting the G31 P parameter to less than 250 should fix it. The machine with a Duet WiFi that I used for testing has a type 8 probe (Smart Effector) but the G31 P parameter is set to 100. So that's why I didn't experience the problem.

          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 0
          • A Former User?
            A Former User
            last edited by

            sorry no 1.2 was on the small ethernet board that I lost so I got a replacement from aliexpress, no clue if any version is on the board itself, will try to check but not easy to get to it now 🙂

            dc42undefined 1 Reply Last reply Reply Quote 0
            • dc42undefined
              dc42 administrators @A Former User
              last edited by

              @smece said in RepRapFirmware 3.0beta 11 released:

              sorry no 1.2 was on the small ethernet board that I lost so I got a replacement from aliexpress, no clue if any version is on the board itself, will try to check but not easy to get to it now 🙂

              No need, I've found the reason.

              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 0
              • A Former User?
                A Former User
                last edited by

                cool, but I'm not triggering with a 100 neither 😞

                lemme try again with new config.g uploaded and restarted 😄

                dc42undefined 1 Reply Last reply Reply Quote 0
                • A Former User?
                  A Former User
                  last edited by

                  don't work 😞 I'm back to 3b10 (works ok with 3b10)
                  homex.g homey.g config.g homez.g homeall.g

                  1 Reply Last reply Reply Quote 0
                  • TLASundefined
                    TLAS @dc42
                    last edited by

                    @dc42 said in RepRapFirmware 3.0beta 11 released:

                    • Added DotStar LED support on Duet 3 main board

                    Any documentation on this yet?

                    TLASundefined 1 Reply Last reply Reply Quote 0
                    • TLASundefined
                      TLAS @TLAS
                      last edited by

                      Disregard that last - looked through the code and found it in the gcode documentation under:
                      M150: Set LED colours

                      1 Reply Last reply Reply Quote 0
                      • dc42undefined
                        dc42 administrators @A Former User
                        last edited by

                        @smece said in RepRapFirmware 3.0beta 11 released:

                        cool, but I'm not triggering with a 100 neither 😞

                        lemme try again with new config.g uploaded and restarted 😄

                        It works for me. Tested using a BLTouch connected to zprobe.in and exp.heater3, G31 P value set to 100.

                        It's possible that you have a G31 command in config-override.g.

                        btw you don't need the M401 and M402 commands in your homez file, because probe deployment/retraction is done automatically (this has been the case for many firmware versions).

                        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

                        A Former User? 1 Reply Last reply Reply Quote 0
                        • stereoundefined
                          stereo
                          last edited by stereo

                          How to update Duet 3? Upload Duet3Firmware_MB6HC.bin on web.. and nothing.
                          M997 S0
                          Error: In-application programming binary "Duet3iap_sd_MB6HC.bin" not found
                          where Duet3iap_sd_MB6HC.bin?
                          not have rapsberry pi...

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

                            @stereo said in RepRapFirmware 3.0beta 11 released:

                            where Duet3iap_sd_MB6HC.bin?

                            https://github.com/dc42/RepRapFirmware/releases/tag/3.0beta10 ?

                            stereoundefined 1 Reply Last reply Reply Quote 0
                            • stereoundefined
                              stereo @A Former User
                              last edited by

                              @bearer 3.0beta10.. need 3.0beta11

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

                                @stereo said in RepRapFirmware 3.0beta 11 released:

                                @bearer 3.0beta10.. need 3.0beta11

                                the IAP file is probably the same if its not listed on the beta11 release

                                stereoundefined 1 Reply Last reply Reply Quote 0
                                • stereoundefined
                                  stereo @A Former User
                                  last edited by

                                  @bearer yes, work. install beta11

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

                                    @dc42 said in RepRapFirmware 3.0beta 11 released:

                                    It works for me. Tested using a BLTouch connected to zprobe.in and exp.heater3, G31 P value set to 100.

                                    hm, that's not good

                                    It's possible that you have a G31 command in config-override.g.

                                    I did not create it, I don't see it trough web interface..

                                    btw you don't need the M401 and M402 commands in your homez file, because probe deployment/retraction is done automatically (this has been the case for many firmware versions).

                                    so G30 auto deploy/retract? nice.. but I'm now more concerned that after G30 I touch the probe, the probe detects me, bed still moves, the probe deploy again, touch again, detect again, deploy again .. bed still moving etc etc.. so no bed stop and no retraction happening at all (G30 not finishing) .. exactly the same config on b10 works, b11 don't. tried G31 P10, P100, P200 .. It's not a working printer (yet) so not a big deal but if there's anything I can help debug lemme know 🙂 (I can hook up oscilloscope or .. ) .. this is supposedly original bltouch v3 .. but "original" when bltouch is can be tricky 😞 ... I have 2 "original" (from "original aliexpress store" paid original price), I have 2-3 clones too that I can try also .. might be the timing issue and not only the trigger level?

                                    1 Reply Last reply Reply Quote 0
                                    • Danalundefined
                                      Danal
                                      last edited by

                                      @smece said in RepRapFirmware 3.0beta 11 released:
                                      It's possible that you have a G31 command in config-override.g.

                                      I did not create it, I don't see it trough web interface..

                                      If you don't see it via the web interface, it is likely not there.

                                      But just to help understand the full picture: That file is created and/or updated when you issue an M500. That is often documented in other firmware as "save settings to EEPROM". Duets do not have EEPROM, so they save settings to /sys/config-override.g

                                      Anyway, sounds like you don't have one.

                                      Delta / Kossel printer fanatic

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

                                        @Danal thanks for explanation! ... did not do M500 yet 😄 since this is a work in progres conversion to duet, and I never used duet before, i'm trying to setup everything directly in main config's for now 😄 .. that's also why I started with RRF3 and not gone with stable version 😄 (still don't have thermistors nor heaters in the hotends so..)

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

                                          @smece, just to confirm:

                                          • You are using RRF3 on a Duet WiFi
                                          • You have connected the BLTouch white wire to IN on the ZProbe connector, and the black wire to GND on the ZProbe connector
                                          • You are getting a reading of 0 for the Z probe in DWC
                                          • If you disconnect the BLTouch from the Z probe connector, you get a reading of 250 for the Z probe
                                          • If you send G31 without parameters, it reports the P parameter is 100 (or whatever you set it to, less than 250)
                                          • You had the BLTouch working with firmware 3.0beta10

                                          Is that all correct?

                                          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

                                          A Former User? 2 Replies Last reply Reply Quote 0
                                          • stereoundefined
                                            stereo
                                            last edited by stereo

                                            On update 10->11 not work homex(y)(all) files. Change S1 to H1..

                                            G91 ; relative positioning
                                            G1 H1 X-355 F1800 ; move quickly to X axis endstop and stop there (first pass)
                                            no reaction to the command at least earlier moved where necessary.

                                            Immediately provide 0.

                                            G91
                                            G1 X-5
                                            NOT WORK TO! IF X = 0

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