Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order
    1. Home
    2. SonnyD1
    • Profile
    • Following 0
    • Followers 0
    • Topics 14
    • Posts 69
    • Best 6
    • Controversial 0
    • Groups 0

    SonnyD1

    @SonnyD1

    8
    Reputation
    4
    Profile views
    69
    Posts
    0
    Followers
    0
    Following
    Joined Last Online
    Location Fort Lee, Virginia

    SonnyD1 Unfollow Follow

    Best posts made by SonnyD1

    • RE: Warning: Driver 1 warning: over temperature warning

      @dc42 336113310_543608657758529_1691986418586856314_n.jpg 335957639_250863380607540_514005489904937907_n.jpg

      Like this?

      posted in General Discussion
      SonnyD1
      SonnyD1
    • RE: Input Shaping

      @jay_s_uk Apparently that was the issue. I bought a USB 3.0 cable and made it up and now its working. Don't know what to do with that data yet but thats a different issue. I'm making progress thanks to the help. Thank you.

      posted in General Discussion
      SonnyD1
      SonnyD1
    • RE: I am at a loss

      @Phaedrux so that was one thing I just figured out. I unplugged one motor and homed Y. I repeated this for each motor and discovered how the obvious escapes me sometimes. The motors are mirrored so obviously one would be backwards. Fixed that now moving on. Still trying to get a complete homing cycle. Thank you very much for the reply.

      posted in General Discussion
      SonnyD1
      SonnyD1
    • RE: WIFI Antenna Mounting

      @Phaedrux Yes I found it. I had two wires swapped on the U axis endstop. Thank you very much. I'm still not up and running but its progress. WIFI Module fires right up now.

      posted in General Discussion
      SonnyD1
      SonnyD1
    • RE: Warning: Driver 1 warning: over temperature warning

      @moth4017 so I lowered it to 1900. Repeated the G32 that was triggering the error and it completed this time. I'm pretty sure that will be enough current. If not, now I know I will have to add additional cooling to the boards. I may end up doing that anyway. Thank you for the help but I think you've solved my issue for now.

      posted in General Discussion
      SonnyD1
      SonnyD1
    • RE: Warning: Driver 1 warning: over temperature warning

      @Phaedrux Ok so my board is mounted horizontally with 10mm of air on the bottom side. I am going to raise that amount as much as I can and add a 24v blower wired to "Always on" that will blow across the bottom of the board on the drivers. Also, I turned down the current to 65%. I don't plan on speed printing with this printer so I will run some tests to see if that's enough. Based on your advice these items will resolve my issue. It will take some time to complete the hardware adjustments so for now I will consider this issue solved until I can run some additional tests. That is, unless you disagree?

      posted in General Discussion
      SonnyD1
      SonnyD1

    Latest posts made by SonnyD1

    • RE: Accelerometer orientation

      @droftarts I read it but I didn't completely understand it. I knew after looking at the data that it was reading wrong. Thank you for the help.

      posted in General Discussion
      SonnyD1
      SonnyD1
    • Accelerometer orientation

      2ACA7EB5-DBFD-4F34-981D-744357985948.jpeg

      Is the orientation in the photo in line with the following line of code? M955 P0 I56 C"spi.cs4+spi.cs3" I'm getting some weird spikes on my Z axis.

      C6E59B1D-0381-4D99-9061-EE595A0B7568.png

      posted in General Discussion
      SonnyD1
      SonnyD1
    • RE: Input Shaping

      @jay_s_uk Apparently that was the issue. I bought a USB 3.0 cable and made it up and now its working. Don't know what to do with that data yet but thats a different issue. I'm making progress thanks to the help. Thank you.

      posted in General Discussion
      SonnyD1
      SonnyD1
    • RE: Input Shaping

      @jay_s_uk How much does the length matter and how long should I aim for?

      posted in General Discussion
      SonnyD1
      SonnyD1
    • RE: Wifi Module error

      @Phaedrux said in Wifi Module error:

      G4 S10

      So after doing that and running several tests...it appears that worked. Its weird I don't have to do that on my Railcore. It starts up just fine. The paneldue reads "starting up" and after about 10 seconds it starts and a couple seconds later it connects. It looks as though that solved my problem. Thank you. Would you be willing to explain that to me so I have a better understanding?

      posted in General Discussion
      SonnyD1
      SonnyD1
    • RE: Input Shaping

      @Phaedrux I’m using 1.5m stepper wires.

      posted in General Discussion
      SonnyD1
      SonnyD1
    • RE: Input Shaping

      @Phaedrux
      Like so...hopefully this makes sense.

      LIS3DH.jpg
      Duet Accelerator.jpg

      posted in General Discussion
      SonnyD1
      SonnyD1
    • RE: Wifi Module error

      @Phaedrux

      ; Configuration file for Duet WiFi (firmware version 3.4.5)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.15 on Sun Feb 19 2023 17:01:06 GMT-0500 (Eastern Standard Time)

      ; General preferences
      G21 ; work in milimeters
      G90 ; send absolute coordinates...
      M83 ; ...but relative extruder moves
      M550 P"IDEX" ; set printer name
      M111 S0 ; debug off

      ; Network
      M552 S1 ; enable network
      M586 P0 S1 ; enable HTTP
      M586 P1 S1 ; enable FTP
      M586 P2 S0 ; disable Telnet
      M575 P1 B57600 S1 ; enable support for PanelDue

      ; Drives
      M569 P0 S1 ; physical drive 0 goes forwards - X stepper
      M569 P1 S1 ; physical drive 1 goes forwards - Z stepper (left)
      M569 P2 S1 ; physical drive 2 goes forwards - Z stepper (right)
      M569 P3 S1 ; physical drive 3 goes forwards - E0 stepper
      M569 P6 S1 ; physical drive 6 goes forwards - Y stepper (left)
      M569 P7 S0 ; physical drive 7 goes backwards - Y stepper (right)
      M569 P8 S1 ; physical drive 8 gows forwards - U stepper
      M569 P9 S1 ; physical drive 9 goes forwards - E1 stepper
      M584 X0 Y6:7 Z1:2 U8 E3:9 ; set drive mapping
      M350 X16 Y16 Z16 U16 E16:16 I1 ; configure microstepping with interpolation
      M92 X80.00 Y80.00 Z800.00 U80.00 E408.21:408.21 ; set steps per mm
      M566 X600.00 Y600.00 Z60.00 U600.00 E120.00:120.00 ; set maximum instantaneous speed changes (mm/min) - jerk
      M203 X6000.00 Y6000.00 Z180.00 U6000.00 E1200.00:1200.00 ; set maximum speeds (mm/min)
      M201 X800.00 Y800.00 Z20.00 U800.00 E250.00:250.00 ; set accelerations (mm/s^2)
      M906 X1750 Y1750 Z1750 U1750 E600:600 I30 ; set motor currents (mA) and motor idle factor in per cent
      M84 S30 ; Set idle timeout

      ; Axis Limits
      M208 X-26 Y0 U0 Z0 S1 ; set axis minima
      M208 X290 Y305 U320 Z300 S0 ; set axis maxima

      ; Endstops
      M574 X1 S1 P"e1stop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin e1stop
      M574 U2 S1 P"duex.e6stop" ; configure switch-type (e.g. microswitch) endstop for high end on U via pin exp.e6stop
      M574 Y1 S1 P"duex.e5stop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin exp.e5stop
      M574 Z1 S2 ; configure Z-probe endstop for low end on Z
      M591 D0 P1 C"xstop" S0 ; configure filament monitor (simple switch) for E0
      M591 D1 P1 C"duex.e4stop" S0 ; configure filament monitor (simple switch) for E1

      ; Emergency Stop
      M950 J1 C"e0stop" ; identify pin number for emergency stop
      M581 P1 T0 S1 R0 ; invoke trigger 0 when an inactive-to-active edge is detected on input 0 or input 3 and a file is being printed from SD card

      ; BLTouch
      M950 S0 C"duex.pwm1" ; create servo pin 0 for BLTouch
      M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch, connected to zprobe.in and the dive height + speeds
      G31 P500 X-31 Y-14.5 Z3.34 ; set Z probe trigger value, offset and trigger height. If you have to move the nozzle closer to the bed, increase the G31 Z value by the amount of baby stepping used. If you have to move the nozzle farther away from the bed, decrease the G31 Z value by the amount of baby stepping used.
      M557 X35:259 Y25:290 P5:5 ; define mesh grid
      M376 H10 ; taper off bed compensation over 10mm

      ; Heaters
      M308 S0 P"duex.e4temp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin duex.e4temp
      M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
      M307 H0 R0.901 K0.249:0.000 D1.86 E1.35 S1.00 B0 ; enable bang-bang mode for the bed heater and set PWM limit
      M140 H0 ; map heated bed to heater 0
      M143 H0 S120 ; set temperature limit for heater 0 to 120C
      M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp
      M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
      M307 H1 R4.899 K0.886:0.346 D1.80 E1.35 S1.00 B0 V24.0 ; disable bang-bang mode for heater and set PWM limit
      M143 H1 S300 ; set temperature limit for heater 1 to 300C
      M308 S2 P"duex.e3temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 2 as thermistor on pin duex.e3temp
      M950 H2 C"duex.e6heat" T2 ; create nozzle heater output on duex.e6heat and map it to sensor 2
      M307 H2 R4.493 K0.675:0.344 D2.01 E1.35 S1.00 B0 V24.1 ; disable bang-bang mode for heater and set PWM limit
      M143 H2 S300 ; set temperature limit for heater 2 to 300C

      ; Fans
      M950 F0 C"fan2" Q500 ; create fan 0 on pin fan0 and set its frequency
      M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
      M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
      M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on at 45c
      M950 F2 C"duex.fan3" Q500 ; create fan 2 on pin duex.fan3 and set its frequency
      M106 P2 S0 H-1 ; set fan 2 value. Thermostatic control is turned off
      M950 F3 C"duex.fan4" Q500 ; create fan 3 on pin duex.fan4 and set its frequency
      M106 P3 S1 H2 T45 ; set fan 3 value. Thermostatic control is turned on at 45c

      ; Tools
      M563 P0 D0 H1 F0 ; define tool 0 that used low end X carriage
      G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
      G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
      M563 P1 D1 H2 F2 ; define tool 1 that used high end U carriage
      G10 P1 X320 Y0 Z0 ; set tool 1 axis offsets
      G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C

      ; Configure Accelerometer
      M955 P0 I56 C"spi.cs4+spi.cs3"

      ; IDEX
      ; Create a tool that prints 2 copies of the object using both carriages
      ;M563 P1 D0:1 H1:2 X0:3 F0:2 ; tool 2 uses both extruders, hot end heaters and fans, and maps X to both X and U
      ;G10 P1 X50 Y0 U-50 S0 R0 ; set tool offsets and temperatures
      ;M567 P1 E1:1 ; set mix ratio 100% on both extruders

      ; Custom settings are not defined

      ; Miscellaneous
      T0 ; select first tool

      posted in General Discussion
      SonnyD1
      SonnyD1
    • RE: Input Shaping

      @Phaedrux

      Version 3.4.1-b1

      I am getting a wifi module error that I have another thread on. I believe they are unrelated though. Otherwise, everything is functioning normally. I'm not sure if it matters but, the toolhead does move from the home position (middle of the bed) to the 20 position and then stops. It doesn't move the the requested 200.

      posted in General Discussion
      SonnyD1
      SonnyD1
    • RE: Wifi Module error

      @Phaedrux

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later + DueX5v0.11
      Board ID: 0JD0M-9P6B2-NJ4S4-6JKFJ-3SJ6Q-T82AK
      Used output buffers: 1 of 26 (22 max)
      === RTOS ===
      Static ram: 23836
      Dynamic ram: 78456 of which 12 recycled
      Never used RAM 9776, free system stack 172 words
      Tasks: NETWORK(notifyWait,29.9%,242) ACCEL(notifyWait,0.0%,348) HEAT(notifyWait,0.1%,333) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,69.9%,438) IDLE(ready,0.1%,30), total 100.0%
      Owned mutexes: WiFi(NETWORK)
      === Platform ===
      Last reset 02:14:09 ago, cause: software
      Last software reset at 2023-03-17 15:01, reason: HeatTaskStuck, GCodes spinning, available RAM 9704, slot 2
      Software reset code 0x4143 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200129c4 Task ACCE Freestk 334 ok
      Stack: 0045d7a1 0045d046 6100f000 00000000 0045d7a1 00000000 00000019 20012363 2000d31c 20012430 2000d31c 00000019 00000000 00000028 0045d8bf 20012340 20012340 00000006 0045af57 7c000000 00434fd7 7c000000 20012340 20012340 00456b8b 7c000000 20012340
      Error status: 0x08
      Aux0 errors 0,0,0
      Step timer max interval 0
      MCU temperature: min 29.5, current 29.9, max 31.4
      Supply voltage: min 23.8, current 24.1, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
      Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
      Events: 0 queued, 0 completed
      Driver 0: standstill, SG min n/a
      Driver 1: standstill, SG min n/a
      Driver 2: standstill, SG min n/a
      Driver 3: standstill, SG min n/a
      Driver 4: standstill, SG min n/a
      Driver 5: standstill, SG min n/a
      Driver 6: standstill, SG min n/a
      Driver 7: standstill, SG min n/a
      Driver 8: standstill, SG min n/a
      Driver 9: standstill, SG min n/a
      Driver 10:
      Driver 11:
      Date/time: 2023-03-17 17:15:38
      Cache data hit count 4294967295
      Slowest loop: 11.49ms; fastest: 0.19ms
      I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
      === Storage ===
      Free file entries: 10
      SD card 0 detected, interface speed: 20.0MBytes/sec
      SD card longest read time 3.8ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === AuxDDARing ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === Heat ===
      Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
      Heater 1 is on, I-accum = 0.0
      === GCodes ===
      Segments left: 0
      Movement lock held by null
      HTTP is idle in state(s) 0
      Telnet is idle in state(s) 0
      File is idle in state(s) 0
      USB is idle in state(s) 0
      Aux is idle in state(s) 0
      Trigger is idle in state(s) 0
      Queue is idle in state(s) 0
      LCD is idle in state(s) 0
      Daemon is idle in state(s) 0
      Autopause is idle in state(s) 0
      Code queue is empty
      === Filament sensors ===
      Extruder 0 sensor: no filament
      Extruder 1 sensor: no filament
      === DueX ===
      Read count 1, 0.01 reads/min
      === Network ===
      Slowest loop: 30.60ms; fastest: 0.00ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
      HTTP sessions: 1 of 8
      = WiFi =
      Network state is active
      WiFi module is connected to access point
      Failed messages: pending 0, notready 0, noresp 0
      WiFi firmware version 1.27
      WiFi MAC address f4:cf:a2:68:3b:2f
      WiFi Vcc 3.39, reset reason Power up
      WiFi flash size 2097152, free heap 20616
      WiFi IP address 192.168.1.243
      WiFi signal strength -43dBm, mode 802.11n, reconnections 0, sleep mode modem
      Clock register 00002002
      Socket states: 0 0 0 0 0 0 0 0

      posted in General Discussion
      SonnyD1
      SonnyD1