@phaedrux Yea my problem was the USb cable I was using, apparently it was power only, I tried a thicker one and it worked, from my pc at least. I also tried it from the pi, but it keeps saying it could not communicate with the duet, at least it recognized it this time. So I just used my pc and now everything works fine, no more of that looping.
Thank you very much, I really appreciate you taking the time to help me.
@phaedrux Yea my problem was the USb cable I was using, apparently it was power only, I tried a thicker one and it worked, from my pc at least. I also tried it from the pi, but it keeps saying it could not communicate with the duet, at least it recognized it this time. So I just used my pc and now everything works fine, no more of that looping.
Thank you very much, I really appreciate you taking the time to help me.
@chrishamm I tried updating via Bossa, however, I can't get my pc or pi to recognize the duet. I have erased the firmware on the duet with the erase pins. I even followed the instruction on this page https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7 to the best of my ability, but nothing seems to work. Most of the instructions on the duet website absolutely suck, they are very short and leave many questions unanswered. Such as does the duet need a sd card in the sd card slot when doing the firmware upgrade?
@chrishamm Ok thanks, I'll try that. Just one question, how can you tell? This can get very confusing, the is the OS for the pi, the DWC software, the printer/cnc files (like the config), and the firmware itself, it all seems a little overwhelming.
@phaedrux I fixed the low voltage issue, the power from the duet is not enough, but it did not fix the looping problem.
@phaedrux
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.01-RC9 running on Duet 3 MB6HC v1.01 or later
Board ID: 08DJM-956BA-NA3TJ-6JTDL-3SS6J-9TB2VUsed output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 154572
Dynamic ram: 160848 of which 52 recycled
Exception stack ram used: 216
Never used ram: 77528
Tasks: NETWORK(ready,2076) HEAT(blocked,1412) CanReceiv(suspended,3824) CanSender(suspended,1484) CanClock(blocked,1432) TMC(blocked,216) MAIN(running,5036) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 14:55:08 ago, cause: software
Last software reset at 2021-05-01 19:00, reason: User, spinning module LinuxInterface, available RAM 77248 bytes (slot 1)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 48.9, current 49.4, max 50.1
Supply voltage: min 22.7, current 22.8, max 22.8, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.9, current 12.0, max 12.1, under voltage events: 0
Driver 0: standstill, reads 13874, writes 14 timeouts 0, SG min/max 0/0
Driver 1: standstill, reads 13877, writes 11 timeouts 0, SG min/max 0/0
Driver 2: standstill, reads 13875, writes 14 timeouts 0, SG min/max 0/0
Driver 3: standstill, reads 13875, writes 14 timeouts 0, SG min/max 0/0
Driver 4: standstill, reads 13876, writes 14 timeouts 0, SG min/max 0/0
Driver 5: standstill, reads 13876, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2021-05-02 09:56:24
Slowest loop: 3.56ms; fastest: 0.14ms
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is ready with "M122" 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 assembling a command 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
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 1.47ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8
@phaedrux Okay I did the sudo apt update and upgrade, then restarted everything, but it made no difference.
@phaedrux I'm powering the pi with the power from the Duet, I tried to connect the power via the USBC cable, but when I did that, the duet disconnected for some reason. No, I have not tried updating the pi, I'll give it a try and see if it makes any difference.
Hi, I have a CNC I decide to add the duet 3 6HC. For my setup, I have the duet paired with a raspberry pie 4 B. I have a large desktop monitor connected to it. For some reason it tends to stall, I can home one axis one time, or all of them at once one time, then the little circle that forms on the homing button during homing, dos not stop or go away. It seems like the process never stops, and it keeps going on an infinite loop. At first, every time I tried homeing for the 2nd time, it would home, but it would keep homeing. The axis would hit the end stop, then pull away, then come back and hit it again, and just keep repeating over and over again until I hit the emergency stop button. So I changed some of the settings in the homing files, not it just homes and stalls. Once it homes the first time, I can run one more command, but then it stops responding, and the little circle keeps on spinning, even though nothing is happening. Does anyone have any idea what could be going on?
I'm getting a low voltage warning from the raspberry pi, but no issue from the pi as far as I can tell. Could that be the problem?
When I try to run g-code files, it homes and makes a few moves before stalling, it seems to run the first few lines of code, then just stalls.
Here is my config file, and my homeing files, I messed around with the homeing files to try and fix the problem, while it changed the way the homeing behaved, nothing I did ever fixed the looping problem.
My firmware ver is 3.01
; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Apr 13 2021 21:05:18 GMT-0400 (Eastern Daylight Time)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Duet 3" ; set printer name
; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.5 S1 ; physical drive 0.5 goes forwards
M569 P0.4 S1 ; physical drive 0.4 goes forwards
M569 P0.3 S1 ; physical drive 0.3 goes forwards
M569 P0.2 S1 ; physical drive 0.2 goes forwards
M584 X0.0:0.5 Y0.4 Z0.3 E0.2 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X600.00 Y600.00 Z600.00 E420.00 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X2000.00 Y2000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X2000 Y2000 Z2000 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X7000 Y5000 Z500 S0 ; set axis maxima
; Endstops
M574 X1 S1 P"!io0.in" ; configure active-high endstop for low end on X via pin !io0.in
M574 Y1 S1 P"!io1.in" ; configure active-high endstop for low end on Y via pin !io1.in
M574 Z1 S1 P"!io2.in" ; configure active-high endstop for low end on Z via pin !io2.in
; Custom settings are not defined
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Apr 13 2021 21:05:19 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z0 F6000 ; lift Z relative to current position
G1 H1 X-235 Y-215 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000 ; go back a few mm
G1 H1 X-235 Y-215 F360 ; move slowly to X and Y axis endstops once more (second pass)
G1 H1 Z-205 F360 ; move Z down stopping at the endstop
G90 ; absolute positioning
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)
; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning
; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Apr 13 2021 21:05:19 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
;G1 H2 Z0 F6000 ; lift Z relative to current position
G1 H1 X-235 F1800 ; move quickly to X axis endstop and stop there (first pass)
;G1 H2 X5 F6000 ; go back a few mm
;G1 H1 X-235 F360 ; move slowly to X axis endstop once more (second pass)
;G1 H2 Z0 F6000 ; lower Z again
G91 ; absolute positioning
; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Apr 13 2021 21:05:19 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z0 F6000 ; lift Z relative to current position
G1 H1 Y-215 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y5 F6000 ; go back a few mm
G1 H1 Y-215 F360 ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z0 F6000 ; lower Z again
G90 ; absolute positioning
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Apr 13 2021 21:05:19 GMT-0400 (Eastern Daylight Time)
G91 ; relative positioning
G1 H2 Z0 F6000 ; lift Z relative to current position
G1 H1 Z-205 F1800 ; move Z down until the endstop is triggered
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)
; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning
If I unplug the thermistors the reading goes to -273.1. It is no longer doing that thing where it was reading one thermistor and using that reading for both. I the board is starting to do some other funny things, for example earlier the wifi shutoff when I disconnected the one thermistor, just a few minutes go it did that when I plugged it in. I think the board is messed up, my guess is there is something wrong with the fan motors I'm using to cool the hotend, everything was find until I tried to turn them on, but still it just does not make sense. Maybe the board is haunted ; )
@Veti The temperature seems to be right, when they work they show the same temperature as my other printers in the same room.