Duet 3 - New user - few quires
-
@Dan1990 said in Duet 3 - New user - few quires:
Btw: Should the Diagnostic LED blink all the time? I have Duet 3.
I have read that is normal but prefer to confirmyes that is normal
-
The PID from yesterday tunning as follow:
; config-override.g file generated in response to M500 at 2021-01-05 16:59
; Heater model parameters
M307 H0 R0.000 C140.000:140.000 D5.50 S1.00 V0.0 B0
M307 H1 R0.000 C167.200:140.000 D4.50 S1.00 V24.1 B0
M307 H2 R0.000 C231.100:140.000 D4.60 S1.00 V24.1 B0
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00I have runout into one problem. When I tried to do homing the all axis are behaving kind of strange. They are doing normal homing, moving towards endstop, engaging them and repreating that like in the loop.
I checked the endstops by M119, all of the are working.
Any idea what that could be?
Thats the homeall.g file:
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.1 on Sun Jan 10 2021 17:23:39 GMT+0000 (GMT)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-225 Y-225 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-225 Y-225 F360 ; move slowly to X and Y axis endstops once more (second pass)
G1 H1 Z-245 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 -
Can that be related to M122?
When I do diagnostic it says M122 response too long, see the console.
M122 below:
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-6JTD4-3S06M-KV8GSUsed output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 154572
Dynamic ram: 162108 of which 52 recycled
Exception stack ram used: 216
Never used ram: 76268
Tasks: NETWORK(ready,2076) HEAT(blocked,1184) CanReceiv(suspended,3824) CanSender(suspended,1484) CanClock(blocked,1432) TMC(blocked,216) MAIN(running,4444) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 00:07:50 ago, cause: power up
Last software reset at 2021-01-05 17:38, reason: User, spinning module LinuxInterface, available RAM 76036 bytes (slot 3)
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 28.5, current 28.8, max 28.9
Supply voltage: min 24.1, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
Driver 0: standstill, reads 57130, writes 0 timeouts 0, SG min/max not available
Driver 1: standstill, reads 57129, writes 0 timeouts 0, SG min/max not available
Driver 2: standstill, reads 57130, writes 0 timeouts 0, SG min/max not available
Driver 3: standstill, reads 57130, writes 0 timeouts 0, SG min/max not available
Driver 4: standstill, reads 57130, writes 0 timeouts 0, SG min/max not available
Driver 5: standstill, reads 57130, writes 0 timeouts 0, SG min/max not available
Date/time: 2021-01-14 13:11:15
Slowest loop: 3.55ms; fastest: 0.21ms
=== 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 = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = 2 -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 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
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.46ms; 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- Ethernet -
State: disabled
Error counts: 0 0 0 0 0
Socket states: 0 0 0 0 0 0 0 0
=== CAN ===
Messages sent 258, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 1
Last transfer: 17ms ago
RX/TX seq numbers: 17840/17841
SPI underruns 1, overruns 1
Number of disconnects: 0
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.0
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 39.64
Maximum length of RX/TX data transfers: 3140/624
- Ethernet -
-
your homing file has 2 homing passes in.
Are you saying the axis approach and back away more than twice? -
Yes, it is like the homing file was in the loop.
-
I have messed up a few things and I am not sure if is better to erase the board and upload a new firmware.
To perform that I have to put a jumper over erase pins?
-
the firmware doesn't store any config information.
You'd be best off starting with a new config file from the configurator -
@Dan1990 said in Duet 3 - New user - few quires:
Duet 3 MB6HC version 3.01-RC9
Don't erase the board with the jumper. If you still have DWC access it's much easier to just update the firmware there. Wiping the firmware and re-flashing with USB is a last resort.
Just upload this zip file to the system tab in the web interface.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.2/Duet2and3Firmware-3.2.zip
If you get any error messages, or if the firmware doesn't actually apply when you check the version with M115, you can use this method.
@Dan1990 said in Duet 3 - New user - few quires:
M307 H0 R0.000 C140.000:140.000 D5.50 S1.00 V0.0 B0
M307 H1 R0.000 C167.200:140.000 D4.50 S1.00 V24.1 B0
M307 H2 R0.000 C231.100:140.000 D4.60 S1.00 V24.1 B0The tuned values look much better now.
How many times was it bouncing in a loop when homing?
-
So, I have to announce that all the issues are solved now.
The problem with the bouncing was due to old firmware. The one which came with the board was 3.01. Somehow, that was interfering with the settings and doing all these strange things.
At the moment, I am able to do what I wanted. As I said before, the board and RRF are very well made and very complex. I reckon that the adventure with RRF and duet is begun.
-
@Phaedrux said in Duet 3 - New user - few quires:
@Dan1990 said in Duet 3 - New user - few quires:
Btw: Should the Diagnostic LED blink all the time? I have Duet 3.
I have read that is normal but prefer to confirmyes that is normal
We are labelling it STATUS on the next batch of boards instead of DIAG.
