Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Communication Problems

    Firmware installation
    4
    30
    2638
    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.
    • Kuhly10
      Kuhly10 last edited by

      I keep getting the message from my printer saying this whenever i try and send a Gcode :

      G28
      SENDING:G28
      Attempt to move the head of a delta printer before homing the towers

      or… when I hit the interface buttons in pronterface
      [ERROR] Traceback (most recent call last):
      File "printrun\printcore.pyc", line 241, in _readline
      File "printrun\pronterface.pyc", line 1713, in recvcb
      File "printrun\pronterface.pyc", line 1669, in update_pos
      ValueError: could not convert string to float:

      would you happen to know what im missing or not doing right?

      1 Reply Last reply Reply Quote 0
      • Jackal
        Jackal last edited by

        what's in your homeall.g or homedelta.g?

        1 Reply Last reply Reply Quote 0
        • Kuhly10
          Kuhly10 last edited by

          I'm still getting those same messages above from the printer whenever i tell it a command. everything on the SD is right and in place because i had it moving before I accidentally hit erase.
          Would anyone know what exactly is causing the printer to send those errors or what the errors mean?
          Any help would be appreciated!

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

            This message:

            G28
            SENDING:G28
            Attempt to move the head of a delta printer before homing the towers

            suggests that either something is seriously wrong with your homedelta.g file, or that the motors are not responding to movement commands - perhaps because the motor currents are not set. Try sending these commands:

            G91
            G1 S2 X10

            and see whether it causes the X carriage to move up 10mm. If the X carriage doesn't move, run M906 to see what motor currents are set.

            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
            • Kuhly10
              Kuhly10 last edited by

              I tried G91 and G1 S2 X10 but no response from either,
              M906 gave me this:
              SENDING:M906
              Motor current (mA) - X:1000, Y:1000, Z:1000, E:800:800:800:800:800:800:800, idle factor 60%

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

                Are you sure that your Duet is receiving 12V or 24V power - is the blue LED lit?

                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
                • Kuhly10
                  Kuhly10 last edited by

                  Yes, I have it plugged into a regular wall outlet and the blue led is lit on the board.

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

                    Please post the contents of your config.g and homedelta.g files.

                    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
                    • Kuhly10
                      Kuhly10 last edited by

                      This is the gcode for homedelta.g

                      ; Homing file for RepRapFirmware on Mini Kossel
                      G91 ; use relative positioning
                      ;******* Change F250 in the following line to F2500 when you are finished commissioning
                      ;******* Change 320 in the following to a higher value if your Kossel has taller towers
                      G1 S1 X320 Y320 Z320 F2500 ; move all carriages up 320mm, stopping at the endstops
                      G1 S2 X-3 Y-3 Z-3 ; move all carriages down 3mm
                      G1 S1 X6 Y6 Z6 F250 ; move carriages slowly up 6mm, stopping at the endstops
                      G1 Z-5 F2000 ; down a few mm so that we can centre the head
                      G90 ; back to absolute positioning
                      G1 X0 Y0 F2000 ; centre the head and set a reasonable feed rate

                      This is the Gcode for the config file

                      ; Configuration file for Mini Kossel kit from Think3DPrint3D for testing Duet WiFi

                      ; Communication and general
                      M111 S0 ; Debug off
                      M550 PMiniKosselWiFiTest ; Machine name and Netbios name (can be anything you like)
                      M551 Preprap ; Machine password (used for FTP)
                      ;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits
                      M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED ; MAC Address
                      ;*** Wifi Networking
                      ; M552 S1 ; Enable WiFi

                      M555 P2 ; Set output to look like Marlin
                      M575 P1 B57600 S1 ; Comms parameters for PanelDue

                      G21 ; Work in millimetres
                      G90 ; Send absolute coordinates…
                      M83 ; ...but relative extruder moves

                      ; Axis and motor configuration
                      M569 P0 S1 ; Drive 0 goes forwards
                      M569 P1 S1 ; Drive 1 goes forwards
                      M569 P2 S1 ; Drive 2 goes forwards
                      M569 P3 S1 ; Drive 3 goes forwards
                      M569 P4 S1 ; Drive 4 goes forwards
                      M574 X2 Y2 Z2 S1 ; set endstop configuration (all endstops at high end, active high)
                      ;*** The homed height is deliberately set too high in the following - you will adjust it during calibration
                      M665 R105.6 L215.0 B85 H240 ; set delta radius, diagonal rod length, printable radius and homed height
                      M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them
                      M350 X16 Y16 E16 I1 ; Set 16x microstepping with interpolation
                      M92 X80 Y80 Z80 ; Set axis steps/mm
                      M906 X1000 Y1000 Z1000 E800 I60 ; Set motor currents (mA) and increase idle current to 60%
                      M201 X1000 Y1000 Z1000 E1000 ; Accelerations (mm/s^2)
                      M203 X20000 Y20000 Z20000 E3600 ; Maximum speeds (mm/min)
                      M566 X1200 Y1200 Z1200 E1200 ; Maximum instant speed changes mm/minute

                      ; Thermistors
                      M305 P0 T100000 B3950 R4700 H30 L0 ; Put your own H and/or L values here to set the bed thermistor ADC correction
                      M305 P1 T100000 B3974 R4700 H30 L0 ; Put your own H and/or L values here to set the first nozzle thermistor ADC correction
                      M305 P2 T100000 B3974 R4700 H30 L0 ; Put your own H and/or L values here to set the second nozzle thermistor ADC correction
                      M570 S180 ; Hot end may be a little slow to heat up so allow it 180 seconds

                      ; Fans
                      M106 P1 H-1 ; disable thermostatic mode for fan 1

                      ; Tool definitions
                      M563 P0 D0 H1 ; Define tool 0
                      G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures
                      ;*** If you have a single-nozzle build, comment the next 2 lines
                      M563 P1 D1 H2 ; Define tool 1
                      G10 P1 S0 R0 ; Set tool 1 operating and standby temperatures
                      M92 E663:663 ; Set extruder steps per mm

                      ; Z probe and compensation definition
                      ;*** If you have a switch instead of an IR probe, change P1 to P4 in the following M558 command
                      M558 P1 X0 Y0 Z0 ; Z probe is an IR probe and is not used for homing any axes
                      G31 X0 Y0 Z4.80 P500 ; Set the zprobe height and threshold (put your own values here)

                      ;*** If you are using axis compensation, put the figures in the following command
                      M556 S78 X0 Y0 Z0 ; Axis compensation here

                      M208 S1 Z-0.2 ; set minimum Z
                      ;
                      T0 ; select first hot end

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

                        I didn't spot any obvious problems with those files. So something is stopping the motors moving. Please run M122 and see what supply voltage it reports, If the supply voltage doesn't reach 10.0V initially, or subsequently falls below 9.5V, then the motors won't run.

                        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
                        • Kuhly10
                          Kuhly10 last edited by

                          SENDING:M122
                          === Diagnostics ===
                          Used output buffers: 1 of 32 (1 max)
                          === Platform ===
                          Memory usage:
                          Program static ram used: 20304
                          Dynamic ram used: 74064
                          Recycled dynamic ram: 3936
                          Current stack ram used: 3288
                          Maximum stack ram used: 4120
                          Never used ram: 28648
                          Last reset 00:00:20 ago, cause: power up
                          Last software reset code not available
                          Error status: 0
                          [ERROR] Error status: 0

                          Free file entries: 10
                          SD card 0 detected, interface speed: 20.0MBytes/sec
                          SD card longest block write time: 0.0ms
                          MCU temperature: min 17.5, current 20.9, max 22.5
                          Supply voltage: min 0.0, current 1.1, max 1.1, under voltage events: 0, over voltage events: 0
                          Driver 0: ok
                          Driver 1: ok
                          Driver 2: ok
                          Driver 3: ok
                          Driver 4: ok
                          Current date and time: 1970-01-01 00:00:00
                          Slowest main loop (seconds): 0.000668; fastest: 0.000032
                          === Move ===
                          MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
                          Bed compensation in use: none
                          Bed probe heights: 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
                          Probe change coordinates:
                          === Heat ===
                          Bed heater = 0, chamber heater = -1
                          Heater 1 is on, I-accum = 0.0
                          === GCodes ===
                          Segments left: 0
                          Stack records: 1 allocated, 0 in use
                          Movement lock held by null
                          http is idle
                          telnet is idle
                          file is idle
                          serial is ready with "M122"
                          aux is idle
                          daemon is idle
                          === Network ===
                          WiFiServer is disabled
                          SPI underruns 0, overruns 0
                          === Webserver ===
                          HTTP sessions: 0 of 8

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

                            This is wrong:

                            Supply voltage: min 0.0, current 1.1, max 1.1, under voltage events: 0, over voltage events: 0

                            It should be around 12V or whatever your VIN voltage is.

                            Please check with a multimeter that you really are getting 12V or 24v (depending on your power supply at the VIN terminal block.

                            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
                            • Kuhly10
                              Kuhly10 last edited by

                              I tested my power cord that plugged into a regular wall socket at 110V and the multimeter read 113V. I then plugged the cord into the power supply for the printer and tested the wires that hook up to the board and they read about 21V.
                              Does that seem like a normal reading?

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

                                Was that 21V reading with the board connected to the power supply?

                                What power supply are you using?

                                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
                                • Kuhly10
                                  Kuhly10 last edited by

                                  No that reading was from the leads from the power supply which was plugged into a wall socket.
                                  I am using the power supply that came with the D300VS printer. The number on it is DA16082403420. It has a built in fan that automatically turns on and off and has the option of changing the input voltage that it receives from the outlet (115/230V)

                                  Also if this helps at all, when the power supply is hooked up to the board and I turn it on the printers LED lights do come on along with the hot end fan,

                                  1 Reply Last reply Reply Quote 0
                                  • Kuhly10
                                    Kuhly10 last edited by

                                    Does anybody have any suggestions?

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

                                      When you mean M122 and got the voltage reading of 1.1V in the report, did you definitely have VIN power applied, and was the blue LED definitely lit? Please run that test again to make sure.

                                      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
                                      • Kuhly10
                                        Kuhly10 last edited by

                                        What do you mean by VIN power?

                                        1 Reply Last reply Reply Quote 0
                                        • elmoret
                                          elmoret last edited by

                                          He means external power connected to the screw terminals, something between 12v and 24v.

                                          1 Reply Last reply Reply Quote 0
                                          • Kuhly10
                                            Kuhly10 last edited by

                                            Hey guys!
                                            I have come to the conclusion that my multimeter was broken! I borrowed my buddies and it is giving me a reading of 27.3 DC volts at the terminals on the board. I believe that is normal right?

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

                                              Yes, although 27v is a little high, we recommend 25V maximum.

                                              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
                                              • Kuhly10
                                                Kuhly10 last edited by

                                                This is the new M122 Command, I believe everything looks right
                                                Used output buffers: 1 of 32 (1 max)
                                                === Platform ===
                                                Memory usage:
                                                Program static ram used: 20304
                                                Dynamic ram used: 74064
                                                Recycled dynamic ram: 3936
                                                Current stack ram used: 3288
                                                Maximum stack ram used: 4120
                                                Never used ram: 28648
                                                Last reset 00:00:52 ago, cause: power up
                                                Last software reset code not available
                                                Error status: 0
                                                [ERROR] Error status: 0

                                                Free file entries: 10
                                                SD card 0 detected, interface speed: 20.0MBytes/sec
                                                SD card longest block write time: 0.0ms
                                                MCU temperature: min 10.3, current 15.1, max 16.7
                                                Supply voltage: min 0.0, current 23.7, max 23.8, under voltage events: 0, over voltage events: 0
                                                Driver 0: standstill
                                                Driver 1: standstill
                                                Driver 2: standstill
                                                Driver 3: standstill
                                                Driver 4: standstill
                                                Current date and time: 1970-01-01 00:00:00
                                                Slowest main loop (seconds): 0.000656; fastest: 0.000031
                                                === Move ===
                                                MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
                                                Bed compensation in use: none
                                                Bed probe heights: 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
                                                Probe change coordinates:
                                                === Heat ===
                                                Bed heater = 0, chamber heater = -1
                                                Heater 1 is on, I-accum = 0.0
                                                === GCodes ===
                                                Segments left: 0
                                                Stack records: 1 allocated, 0 in use
                                                Movement lock held by null
                                                http is idle
                                                telnet is idle
                                                file is idle
                                                serial is ready with "M122"
                                                aux is idle
                                                daemon is idle

                                                1 Reply Last reply Reply Quote 0
                                                • Kuhly10
                                                  Kuhly10 last edited by

                                                  I sent the G28 command and hit send and the head started going down towards the bed until it randomly stopped about 5 inches down. I tried it again and the same thing keeps happening.
                                                  Any suggestions?

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

                                                    I suggest you test X, Y and Z homing individually until they are all working. Make sure that your M574 command in config.g is correct, and make sure that your homez.g file is correct according to whether you are using a microswitch or a Z probe to home Z. See https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer#Homing_files.

                                                    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
                                                    • First post
                                                      Last post
                                                    Unless otherwise noted, all forum content is licensed under CC-BY-SA