• Tags
  • Documentation
  • Order
  • Register
  • Login
Duet3D Logo Duet3D
  • Tags
  • Documentation
  • Order
  • Register
  • Login
  1. Home
  2. AndrewStaines
  • Profile
  • Following 2
  • Followers 1
  • Topics 5
  • Posts 17
  • Best 0
  • Controversial 0
  • Groups 0

AndrewStaines

@AndrewStaines

0
Reputation
8
Profile views
17
Posts
1
Followers
2
Following
Joined 22 Nov 2023, 06:10 Last Online 30 Nov 2024, 11:45

AndrewStaines Unfollow Follow

Latest posts made by AndrewStaines

  • RE: Problem in endstop triggering

    @droftarts said in Problem in endstop triggering:

    Are you sure both 1XDs are running the same version of the firmware as the 6XD?

    Checked the firmware version on main board and expansion board, both are running at 3.4.4

    @jay_s_uk said in Problem in endstop triggering:

    looks like you have them wired as normally open and they're picking up interference. Wire the normally closed instead

    I have tried with the normally closed connection. But when triggered it goes to the floating state even triggered all the time.

    All the motors are in ON state in the case 1;(Without connecting the expansion board). During which no floating state occur, so I think its not a interference problem.

    Here is my Diagnostics report

    edit: I have changed my CAN address of both board as 40 and 41

    code_text

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6XD version 3.4.4 (2022-10-20 16:19:15) running on Duet 3 MB6XD v1.0 or later (standalone mode)
    Board ID: 0JD2M-999AL-D25S4-7JKD8-3SJ6Q-K41H3
    Used output buffers: 1 of 40 (14 max)
    === RTOS ===
    Static ram: 151264
    Dynamic ram: 95092 of which 0 recycled
    Never used RAM 104244, free system stack 190 words
    Tasks: NETWORK(ready,38.1%,251) ETHERNET(notifyWait,0.1%,451) HEAT(notifyWait,0.0%,374) Move(notifyWait,0.0%,266) CanReceiv(notifyWait,0.0%,773) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,340) MAIN(running,60.9%,951) IDLE(ready,0.9%,29), total 100.0%
    Owned mutexes: USB(MAIN)
    === Platform ===
    Last reset 00:14:46 ago, cause: power up
    Last software reset at 2024-11-17 10:37, reason: User, GCodes spinning, available RAM 104244, slot 1
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
    Error status: 0x00
    Aux0 errors 0,0,0
    Step timer max interval 669
    MCU temperature: min 36.3, current 44.8, max 45.0
    Supply voltage: min 0.1, current 23.4, max 23.6, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 0.0, current 12.2, max 12.2, under voltage events: 0
    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: ok
    Driver 1: ok
    Driver 2: ok
    Driver 3: ok
    Driver 4: ok
    Driver 5: ok
    Date/time: 2024-11-17 11:40:46
    Slowest loop: 999.85ms; fastest: 0.05ms
    === Storage ===
    Free file entries: 10
    SD card 0 detected, interface speed: 25.0MBytes/sec
    SD card longest read time 2.3ms, write time 0.0ms, max retries 0
    === Move ===
    DMs created 125, segments created 3, maxWait 123085ms, bed compensation in use: none, comp offset 0.000
    === MainDDARing ===
    Scheduled moves 8, completed 8, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 8], 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 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 ready with "M122" 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
    SBC is idle in state(s) 0
    Daemon is idle in state(s) 0
    Aux2 is idle in state(s) 0
    Autopause is idle in state(s) 0
    Code queue is empty
    === CAN ===
    Messages queued 4449, received 12831, lost 0, boc 0
    Longest wait 1ms for reply type 6024, peak Tx sync delay 2662, free buffers 50 (min 49), ts 4435/4008/0
    Tx timeouts 0,0,426,6,0,0 last cancelled message type 30 dest 127
    === Network ===
    Slowest loop: 4.01ms; fastest: 0.03ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8
    = Ethernet =
    State: active
    Error counts: 0 0 0 0 0 0
    Socket states: 2 2 2 2 2 0 0 0
    === Multicast handler ===
    Responder is inactive, messages received 0, responses 0
    ok
    
    
    
    
    
    M122 B41
    Diagnostics for board 41:
    Duet EXP1XD firmware version 3.4.4 (2022-10-14 11:45:39)
    Bootloader ID: SAMC21 bootloader version 2.4 (2021-12-10)
    All averaging filters OK
    Never used RAM 5556, free system stack 88 words
    Tasks: Move(notifyWait<null>,0.0%,153) HEAT(notifyWait<null>,0.1%,115) CanAsync(notifyWait<null>,0.0%,64) CanRecv(notifyWait<null>,0.0%,77) CanClock(notifyWait<null>,0.0%,64) MAIN(running<null>,96.5%,441) IDLE(ready<null>,0.0%,40) AIN(delaying<null>,3.4%,142), total 100.0%
    Last reset 00:01:38 ago, cause: power up
    Last software reset data not available
    Driver 0: pos 0, 9.0 steps/mm, steps req 0 done 0
    Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
    Peak sync jitter 2/6, peak Rx sync delay 192, resyncs 0/0, no step interrupt scheduled
    VIN voltage: min 23.5, current 23.9, max 24.1
    MCU temperature: min 32.0C, current 33.6C, max 33.6C
    Last sensors broadcast 0x00000000 found 0 199 ticks ago, 0 ordering errs, loop time 0
    CAN messages queued 810, send timeouts 0, received 505, lost 0, free buffers 37, min 37, error reg 0
    dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
    ok
    
    
    M122 B40
    Diagnostics for board 40:
    Duet EXP1XD firmware version 3.4.4 (2022-10-14 11:45:39)
    Bootloader ID: SAMC21 bootloader version 2.4 (2021-12-10)
    All averaging filters OK
    Never used RAM 5556, free system stack 88 words
    Tasks: Move(notifyWait<null>,0.0%,153) HEAT(notifyWait<null>,0.1%,115) CanAsync(notifyWait<null>,0.0%,64) CanRecv(notifyWait<null>,0.0%,77) CanClock(notifyWait<null>,0.0%,64) MAIN(running<null>,96.5%,443) IDLE(ready<null>,0.0%,40) AIN(delaying<null>,3.4%,142), total 100.0%
    Last reset 00:01:44 ago, cause: power up
    Last software reset data not available
    Driver 0: pos 0, 90.0 steps/mm, steps req 0 done 0
    Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
    Peak sync jitter 1/5, peak Rx sync delay 201, resyncs 0/0, no step interrupt scheduled
    VIN voltage: min 23.8, current 23.8, max 23.8
    MCU temperature: min 32.9C, current 34.3C, max 34.4C
    Last sensors broadcast 0x00000000 found 0 217 ticks ago, 0 ordering errs, loop time 0
    CAN messages queued 206, send timeouts 0, received 122, lost 0, free buffers 37, min 37, error reg 0
    dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
    ok
    posted in Duet Hardware and wiring
    undefined
    AndrewStaines
    17 Nov 2024, 07:12
  • Problem in endstop triggering

    Hi, I am using Duet mainboard 6XD and 2 1XD expansion boards operates with the firmware version 3.4.4. My endstop is configured in main board at I/O port 1 and 2 for X and Y axis.
    Using a switch type endstop which is connected to input pin and ground of each specified port(i/o port 1 and 2) with an pullup enabled(by firmware).

    Case 1: DUET MB 6XD with no expansion board connected
    Endstop works normal and finding no issues.

    Case 2: DUET MB 6XD with expansion board.
    Works fine when endstop triggered. If not the endstop is in floating state(which means showing triggered and not triggered randomly).
    These state changes randomly even the endstop is not triggered all the time of this process.

    Endstop wiring remains same for both the cases which is 1wire to input pin and another to GND.
    Below is my config file.

    G90 ; absolute coordinates
    M83 ; relative extruder moves
    M550 P"Xtrud" ; set hostname
    
    ; Accessories
    M575 P1 S0 B57600 ; configure PanelDue support
    
    ; Network
    M551 P"password" ; set machine password
    M552 P0.0.0.0 S1 ; configure Ethernet adapter
    M586 P0 S1 ; configure HTTP
    
    ; Wait a moment for the CAN expansion boards to become available
    G4 S2
    
    ; Motor Idle Current Reduction
    M906 I30 ; set motor current idle factor
    M84 S30 ; set motor current idle timeout
    
    ; External Drivers
    M569 P0.0 S1 R0 T5:5:10:0 ; driver 0.0 goes forwards and requires an active-low enable signal (Y axis)
    M569 P0.1 S0 R0 T5:5:10:0 ; driver 0.1 goes backwards and requires an active-low enable signal (Y axis)
    M569 P0.2 S1 R0 T5:5:10:0 ; driver 0.2 goes forwards and requires an active-low enable signal (Z axis)
    M569 P0.3 S1 R0 T5:5:10:0 ; driver 0.3 goes forwards and requires an active-low enable signal (Z axis)
    M569 P0.4 S1 R0 T5:5:10:0 ; driver 0.4 goes forwards and requires an active-low enable signal (Z axis)
    M569 P0.5 S1 R0 T5:5:10:0 ; driver 0.5 goes forwards and requires an active-low enable signal (Z axis)
    M569 P122.0 S1 R0 T5:5:10:0 ; driver 122.0 goes forwards and requires an active-low enable signal (X axis)
    M569 P123.0 S1 R0 T5:5:10:0 ; driver 123.0 goes forwards and requires an active-low enable signal (extruder 0)
    
    ; Axes
    M584 X122.0 Y0.0:0.1 Z0.2:0.3:0.4:0.5 ; set axis mapping
    M350 X16 Y16 Z16 I0 ; configure microstepping without interpolation
    M92 X9 Y9 Z9 ; configure steps per mm
    M208 X0:3800 Y0:5000 Z0:4000 ; set minimum and maximum axis limits
    M566 X900 Y900 Z12 ; set maximum instantaneous speed changes (mm/min)
    M203 X6000 Y6000 Z180 ; set maximum speeds (mm/min)
    M201 X500 Y500 Z20 ; set accelerations (mm/s^2)
    
    ; Extruders
    M584 E123.0 ; set extruder mapping
    M350 E1 I0 ; configure microstepping without interpolation
    M92 E9 ; configure steps per mm
    M566 E120 ; set maximum instantaneous speed changes (mm/min)
    M203 E3600 ; set maximum speeds (mm/min)
    M201 E250 ; set accelerations (mm/s^2)
    
    ; Kinematics
    M669 K0 ; configure Cartesian kinematics
    
    ; Endstops
    M574 X1 P"!^io1.in" S1 ; configure X axis endstop
    M574 Y1 P"!^io2.in" S1 ; configure Y axis endstop
    M574 Z0 ; configure Z axis endstop
    
    ; Tools
    M563 P0 D0 H1 F0 ; create tool #0
    M568 P0 R0 S0 ; set initial tool #0 active and standby temperatures to 0C
    

    Tried inverting the S parameter by 1 to 0.

    ; Endstops
    M574 X1 P"!^io1.in" S0 ; configure X axis endstop
    M574 Y1 P"!^io2.in" S0 ; configure Y axis endstop
    M574 Z0 ; configure Z axis endstop
    

    Also tried not to invert the input pin.

    ; Endstops
    M574 X1 P"^io1.in" S1 ; configure X axis endstop
    M574 Y1 P"^io2.in" S1 ; configure Y axis endstop
    M574 Z0 ; configure Z axis endstop
    

    I don't know what's the mistake if it works fine when no expansion boards are connected.

    Any help is appreciated. Thanks in advance.
    @dc42 ,@T3P3Tony ,@Phaedrux

    posted in Duet Hardware and wiring
    undefined
    AndrewStaines
    16 Nov 2024, 16:28
  • RE: Connection of Servo with DuetMainboard 6HC

    @Phaedrux
    Yes, the driver has step/dir signal.

    cd9c5790-497c-4097-8fbe-66ebc9e5a10d-image.png

    07c84afe-38c0-44ec-9407-8d44a9f502be-image.png

    We need to connect the following driver with the duet mainboard 6HC. How should I connect the driver with the mainboard? After going through some documentation, GPIO can be used to generate PWM signals. If so, how do I generate PWM signals in the GPIO pin?
    @T3P3Tony @dc42

    posted in Duet Hardware and wiring
    undefined
    AndrewStaines
    15 Jun 2024, 17:16
  • Connection of Servo with DuetMainboard 6HC

    We are required to connect a servo motor with the following specs,

    50 W to 22 kW,
    Input power supply for Driver: Voltage DC 24 V/48 V・AC 100 V/200 V/400 V,
    23 bit Absolute/Incremental・battery-less Absolute/Incremental encoder,
    Frequency response 3.2 kHz

    How do I connect this servo with my duet board(Duet MainBoard 6HC)? How to configure this in the RepRap Firmware?

    @dc42

    posted in Duet Hardware and wiring
    undefined
    AndrewStaines
    2 Apr 2024, 09:06
  • RE: Configuration of RepRap Firmware for 7 axis Robotic Arm

    @JoergS5 Thanks for the knowledge, will look into it and respond

    posted in Config Tool
    undefined
    AndrewStaines
    13 Mar 2024, 03:28
  • Configuration of RepRap Firmware for 7 axis Robotic Arm

    We are currently developing a robotic arm 3D printer. We have to configure the RepRap firmware for the Robotic Arm. We need help in how to start configuring? Also I have doubt that how these 3D models are sliced for the Robotic Arm 3D printing?
    Thank you in advance
    @dc42 @robm

    posted in Config Tool
    undefined
    AndrewStaines
    8 Mar 2024, 10:22
  • RE: Wifi Module remains idle error

    @fcwilt
    Thank You for the clarification. Now I get it. I have tried it via router and now it works fine.

    posted in Duet Hardware and wiring
    undefined
    AndrewStaines
    25 Nov 2023, 05:39
  • RE: Unable To Open DWC

    @droftarts
    Thank You for the clarification. I was connecting the ethernet cable directly with my laptop. Now I have connected through the router and It works fine now. Thank You once again.

    posted in Duet Web Control
    undefined
    AndrewStaines
    25 Nov 2023, 05:38
  • RE: Unable To Open DWC

    @jay_s_uk
    It says This site can't be reached

    posted in Duet Web Control
    undefined
    AndrewStaines
    24 Nov 2023, 13:59
  • Unable To Open DWC

    We recently bought the Duet 3 mainboard 6HC. I tried to connect through it via Ethernet and I was able to do so. But when I enter the IP address in the browser, the DWC doesn't open. Here are the output about firmware and network.

    M552 S1
    ok
    Ethernet running, IP address = 192.168.1.50
    
    M115
    FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.5.0-rc.1 ELECTRONICS: Duet 3 MB6HC v1.02 or later FIRMWARE_DATE: 2023-08-31 16:19:24
    ok
    
    M122
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC version 3.5.0-rc.1 (2023-08-31 16:19:24) running on Duet 3 MB6HC v1.02 or later (standalone mode)
    Board ID: 0JD4M-958L1-M24T8-6JTDG-3S46R-11V9X
    Used output buffers: 1 of 40 (2 max)
    === RTOS ===
    Static ram: 154852
    Dynamic ram: 120180 of which 0 recycled
    Never used RAM 70960, free system stack 189 words
    Tasks: NETWORK(1,ready,31.7%,182) ETHERNET(5,nWait,0.0%,317) HEAT(3,nWait,0.0%,369) Move(4,nWait,0.0%,340) CanReceiv(6,nWait,0.0%,941) CanSender(5,nWait,0.0%,335) CanClock(7,delaying,0.0%,344) TMC(4,nWait,0.0%,71) MAIN(1,running,68.2%,444) IDLE(0,ready,0.0%,30), total 100.0%
    Owned mutexes: USB(MAIN)
    === Platform ===
    Last reset 00:04:28 ago, cause: software
    Last software reset time unknown, reason: User, Gcodes spinning, available RAM 68852, slot 2
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
    Error status: 0x00
    Aux0 errors 0,0,0
    MCU temperature: min 41.2, current 41.8, max 42.0
    Supply voltage: min 0.2, current 0.2, max 0.3, under voltage events: 0, over voltage events: 0, power good: no
    12V rail voltage: min 0.1, current 0.2, max 0.2, under voltage events: 0
    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: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
    Driver 1: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
    Driver 2: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
    Driver 3: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
    Driver 4: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
    Driver 5: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
    Date/time: 1970-01-01 00:00:00
    Slowest loop: 5.38ms; fastest: 0.07ms
    === Storage ===
    Free file entries: 20
    SD card 0 detected, interface speed: 25.0MBytes/sec
    SD card longest read time 2.3ms, write time 0.0ms, max retries 0
    === Move ===
    DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00
    no step interrupt scheduled
    Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
    === DDARing 0 ===
    Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === DDARing 1 ===
    Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === Heat ===
    Bed heaters -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
    === GCodes ===
    Movement locks held by null, null
    HTTP is idle in state(s) 0
    Telnet is idle in state(s) 0
    File is idle in state(s) 0
    USB is ready with "M122" 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
    SBC is idle in state(s) 0
    Daemon is idle in state(s) 0
    Aux2 is idle in state(s) 0
    Autopause is idle in state(s) 0
    File2 is idle in state(s) 0
    Queue2 is idle in state(s) 0
    Q0 segments left 0, axes/extruders owned 0x0000000
    Code queue 0 is empty
    Q1 segments left 0, axes/extruders owned 0x0000000
    Code queue 1 is empty
    === CAN ===
    Messages queued 1343, received 0, lost 0, boc 0
    Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 1343/0/0
    Tx timeouts 0,0,1342,0,0,0 last cancelled message type 30 dest 127
    === Network ===
    Slowest loop: 0.47ms; fastest: 0.00ms
    Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 0 of 8
    = Ethernet =
    Interface state: active
    Error counts: 0 0 0 1 0 0
    Socket states: 2 2 2 2 2 0 0 0
    === WiFi ===
    Interface state: disabled
    Module is disabled
    Failed messages: pending 0, notrdy 0, noresp 0
    Socket states: 0 0 0 0 0 0 0 0
    === Multicast handler ===
    Responder is inactive, messages received 0, responses 0
    ok
    
    
    posted in Duet Web Control
    undefined
    AndrewStaines
    24 Nov 2023, 11:26
Unless otherwise noted, all forum content is licensed under CC-BY-SA