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

Refresher Needed: 1.17 to 1.19.2

Scheduled Pinned Locked Moved
Firmware installation
6
11
1.4k
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.
  • undefined
    Martin_S
    last edited by 30 Oct 2017, 04:41

    Hi, I don't know how to set a static ip, but my network paramerters are like this:

    M550 PDuetDelta ; Set machine name
    M552 S1 ; Enable network
    M587 S"YourNetworkSSID" P"YourNetworkPASSWORD" ; Configure access point and IP addresses.
    M586 P0 S1 ; Enable HTTP
    M586 P1 S0 ; Disable FTP
    M586 P2 S0 ; Disable Telnet
    M575 P1 B57600 S1 ; Comms parameters for PanelDue

    I can access the printer by its name, in this case it's called DuetDelta, so it connects by just typing http://DuetDelta.local/

    As for the other issue, sorry I wouldn't know.
    You can try by generating a new file using the RRF tool and compare it with the old one. Maybe you can spot something.

    Best of luck.

    If it ain't broke, fix it till it is =)

    1 Reply Last reply Reply Quote 0
    • undefined
      dc42 administrators
      last edited by 30 Oct 2017, 10:20

      On the Duet WiFi you set up a static IP address in the M587 command where you define the router SSID and password.

      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
      • undefined
        KeeganB
        last edited by 30 Oct 2017, 13:25

        Here are the instruction for David's answer.

        https://duet3d.com/wiki/G-code#M587:_Add_WiFi_host_network_to_remembered_list.2C_or_list_remembered_networks

        Pay close attention to the capitalization of the network name and pass; this will require some added single quotes in your M587 command. Note too that spaces and semicolon characters in the password need special attention.

        Artemis
        Rostock Max v2
        Orion

        1 Reply Last reply Reply Quote 0
        • undefined
          lasakro
          last edited by 31 Oct 2017, 01:48

          Thanks for all the suggestions but without code that responds to my end stops it's useless. I need to figure that out first unless I need to print which will just mean reverting back to 1.17.

          1 Reply Last reply Reply Quote 0
          • undefined
            deckingman
            last edited by 31 Oct 2017, 08:11

            @lasakro:

            Thanks for all the suggestions but without code that responds to my end stops it's useless. I need to figure that out first unless I need to print which will just mean reverting back to 1.17.

            Could do with a little more info about how and when the end stops are ignored. From what I can gather, they worked on 1.17 but something is amiss using 1.19? If that's correct then from the release notes we can see that deploy probe and retract probe files need to be deleted from the "sys" directory otherwise they will be acted on. So assuming that you have a probe that does not need to be deployed, and assuming that the behaviour only occurs during homing, then that might be a possible explanation. Otherwise, a bit more info about what is happening will help.

            Ian
            https://somei3deas.wordpress.com/
            https://www.youtube.com/@deckingman

            1 Reply Last reply Reply Quote 0
            • undefined
              Dougal1957
              last edited by 31 Oct 2017, 09:46

              also I couldn't see a definition for the Z Endstop in your Config.G file either now it may not be needed depending on type of Z Probe you have so that is also info we need

              1 Reply Last reply Reply Quote 0
              • undefined
                dc42 administrators
                last edited by 31 Oct 2017, 11:07

                End stop detection has not changed between version 1.17 and 1.19. Use the M119 command or the Machine Properties page of DWC to check whether the firmware is reading your endstops correctly. Also look at the endstop LEDs on the Duet. If they turn on when the endstop witches are triggered, your configuration is correct. If they are normally on but turn off when the endstops are triggered, you need S1 instead of S0 in your M574 command. If they don't change when the endstop is triggered, then you have a wiring issue, or incompatible endstop sensors.

                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
                • undefined
                  lasakro
                  last edited by 11 Feb 2017, 00:35 2 Nov 2017, 00:33

                  Have you on of those days where you look back and say "boy was I an idiot"? Tried my printer today and the end stops are working fine. I know I had to rush to the power switch after one of the axis wouldn't stop. Well moving on, sorry about that.

                  As for the M587 command I tried it under 4 circumstances and still can't set an IP:

                  1. Putting Wifi idle at the Pronterface command line with M552 S0. Sending M587 I192.168.1.2
                  2. With Wifi running sending M587 I192.168.1.2
                  3. Placed M587 I192.168.1.2 in my config.g before the M552 S1 command.
                  4. Placed M587 I192.168.1.2 in my config.g after the M552 S1 command.

                  So where is the correct location for this and what am I missing? The SSID and DHCP are working fine. I'm just tired of having to guess which address got leased out.

                  Edit: I removed the old M552 I192.168.1.2 from my config.g before trying the above.

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    dc42 administrators
                    last edited by 2 Nov 2017, 07:29

                    With M587 you have to give the IP address at the same time as you give the SSID and password, because the IP address is specific to when you connect to that SSID.

                    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
                    • undefined
                      lasakro
                      last edited by 3 Nov 2017, 02:39

                      I put the Wifi idle. Needed to delete my current SSID with M588. Sent SSID, PW and IP this time and it worked. Thanks for your help.

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