Posts made by Jimmykc

G2/G3 can't run smooth. The issue happens between 42 second to 46 second. What parameter do I fine tune?

I paste video link : https://youtu.be/VPnsPxMx_dk

The issue happens on the line "N295" of NC file.

N295 G18 G02 X87.25 Z13.1 I3.
N300 G01 X88.25 F1000.
N305 G17 G03 X91.25 Y0. J3.
N310 X78.75 I-6.25
N315 X91.25 I6.25
N320 X90.933 Y1.966 I-6.25
N325 X87.141 Y3.87 I-2.848 J-0.944
N330 G01 X86.192 Y3.555
N335 X85.873 Y3.45 Z13.119
N340 X85.558 Y3.345 Z13.175
N345 X85.252 Y3.244 Z13.268
N350 X84.957 Y3.146 Z13.397
N355 X84.677 Y3.053 Z13.56
N360 X84.417 Y2.967 Z13.755
N365 X84.178 Y2.888 Z13.979
N370 X83.966 Y2.818 Z14.23
N375 X83.781 Y2.756 Z14.504
N380 X83.626 Y2.705 Z14.798
N385 X83.504 Y2.665 Z15.109
N390 X83.416 Y2.635 Z15.432
N395 X83.362 Y2.618 Z15.764
N400 X83.344 Y2.612 Z16.1

I upload my NC file below.
3333.txt

@T3P3Tony Thanks, I have run M92 to define step/degree, speed, and acceleration.

So RRF firmware has supported rotational axes, but I have to code firmware to define rotate way myself. Right?

@jumpedwithbothfeet The same result. No rotational axes.

My PCBA are Duet3 MB 6HC and Duet Expansion 3HC. I have 2 axis A and C. I want to configure them as rotational axis. I set M584’s R parameter and M584’s S parameter. It doesn’t work. I provide my config.g.
config.g
I trace the RRF 3.3 source code. I find SetAxisType function only support continuousAxes. There are no different between linearAxes and rotationalAxes.

I want rotational axis. The rotational axis runs between 0 degree and 360 degree, not continuous. How do I do ?

@dc42 You are right. I fix my issue. Thank you so much.

@dc42 Sorry, I write wrong RRF version, but I have to use RRF 3.3+ because RRF3.4 RRF is not available my DWC. I list M122.
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3+ (2022-10-06 15:05:17) running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode)
Board ID: 08DJM-956L2-G43S4-6JKDA-3SN6T-1V6YH
Used output buffers: 3 of 40 (28 max)
=== RTOS ===
Static ram: 150424
Dynamic ram: 97284 of which 332 recycled
Never used RAM 103296, free system stack 171 words
Tasks: NETWORK(ready,26.6%,195) ETHERNET(notifyWait,0.0%,109) HEAT(delaying,0.0%,326) Move(notifyWait,0.0%,256) CanReceiv(notifyWait,0.0%,753) CanSender(notifyWait,0.0%,373) CanClock(delaying,0.0%,340) TMC(notifyWait,8.5%,60) MAIN(running,64.7%,1166) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 01:10:49 ago, cause: software
Last software reset at 2022-10-18 14:09, reason: User, GCodes spinning, available RAM 103296, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00432000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 130
MCU temperature: min 41.4, current 41.9, max 43.8
Supply voltage: min 24.0, 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
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/24/24, gc cycles 0
Driver 0: position 0, standstill, reads 27939, writes 18 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 27939, writes 18 timeouts 0, SG min/max 0/0
Driver 2: position -30, standstill, reads 27934, writes 23 timeouts 0, SG min/max 0/1023
Driver 3: position 0, standstill, reads 27941, writes 16 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 27934, writes 24 timeouts 0, SG min/max 0/1023
Driver 5: position 0, standstill, reads 27944, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2022-10-18 16:17:58
Slowest loop: 14.01ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.4ms, write time 2.7ms, max retries 0
=== Move ===
DMs created 125, maxWait 21975ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 3, completed moves 3, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -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 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
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 38273, received 68084, lost 0, longest wait 1ms for reply type 6042, peak Tx sync delay 477, free buffers 49 (min 48), ts 21247/21246/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 12.85ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8

• Ethernet -
  State: active
  Error counts: 0 0 1 0 0
  Socket states: 5 2 2 2 2 0 0 0

@dc42 said in Can't run 15000 mm per min:

link to the manual for the servo drive
servo driver link :
https://filecenter.deltaww.com/Products/download/06/060201/Manual/DELTA_IA-ASD_ASDA-B3_UM_EN_20210201.pdf

config.g

@droftarts Servo driver is controlled by Duet's step signal. I use servo driver scope to monitor Duet's speed. My 3000 rpm is 15000mm/ min . The RRF 3.4 will stop when the speed close to 1500RPM.

RRF3.1-15000 mm/min

RRF3.4-15000mm/min

@droftarts

My board is Duet3 6HC. The attached photo is my config.g . Z axis can run 15000 mm/min and doesn’t lose step when my RRF version is 3.1.1. Recently I have upgraded the RRF firmware from 3.1.1 to 3.4. My config.g is same. Z axis will stop suddenly and lose step when it run full speed (G0). It looks like over limitation and self- protection. What happen? How do I set my config.g ?

@phaedrux OK, thanks.

@jimmykc I mean I want to download the last firmware of expansion board 3HC. The binary file is Duet3Firmware_EXP3HC.

@jay_s_uk I don't need to build own version. I don't know how to download Duet3Firmware_EXP3HC.bin.

@jay_s_uk I follow the Duet3Expansion's suggestion to build binary file. I download CANlib-master, Duet3Expansion-master, FreeRTOS-master, and RRFLibraries-dev.

I can't build it. Could you tell me how to build it ?

@jay_s_uk I am confused that it is no problem run M584 when my firmware is 3.1.1. Why is the firmware 3.3 compatible to 3.1.1 when I run M584?

My PCBA are Duet3 MB 6HC and Duet Expansion 3HC. My config.g file and diagnose message are showed below:
; Drives
M569 P0.0 S0
M569 P0.1 S0
M569 P0.2 S0
M569 P0.3 S0
M569 P0.4 S0
M569 P0.5 S0
M569 P1.0 S0
M569 P1.1 S0
M569 P1.2 S0
M569 P2.0 S0
M584 X0.0 Y0.1 Z0.2 U0.3 V0.4 W0.5 A1.0 B1.1 C1.2 D1.1

I can’t run M584 to map A axis to drive 1.0. The error is showed below:

I use the duet3 main board 6HC and duet3 Expansion 3HC as CNC’s controller. Now I need to pass the CE certification. I need to provide safety data about PCBA for verification agency. They show the reference’s picture. Could you support me main board 6HC and duet3 Expansion 3HC about PCBA’s age limit for me? Thanks.