Posts made by rich1351

@phaedrux im not with the machine today but i can send that in the morning.

Ive checked all the homing files for anything that messes with the axes and nothing, ill post those tomorrow aswell. (I wanted to get this issue ironed out before i attempted splitting the x axis to auto square it in the homing routines)

Im sure it is in cnc mode as the G0 will work fine on x axis and i suppose does work to a point on the y axis albeit at a limited rapid of 6000mm/min. A G1 move with f defined yields the same results

I can send m203 in the console and it will return all axes have 20000 mm/min max speeds so nothing seems to be changing the defined max but even if the next command sent is G0 Y1500 the requested and top speed is reported are 6000 mm/min, but the same move in X shows both as 19999 mm/min

@rich1351 ive been using g0 commands to test as g0 should defualt to full speed which it does with x axis but y is maxing out at 6000mm/min.
As for motors all axes are fitted with identical motors so should have plenty torque to achieve what im asking of them. as proof i can swap axes assignments with m584 (make x be y and vice versa) the axis assigned to x will move at 20000mm/min (previously y and limited to 6000mm/min) and the axis assigned y will only do 6000mm/min (previously as x it would do 20000mm/min no problem)
This is why i feel its something in software limiting jus the y axis for some reason or another, ill try a different firmware version tomorrow to see if it makes any difference.
Cheers
Rich

I have been testing further and it appears i can get the full 20000mm/min set on the x axis but not on the y axis, i was mainly testing with the y axis as its a single motor axis whereas x axis is dual motor, i just happened to try moving it with a g0 move instead of the ui jog buttons
i swapped y axis to one of the x axis drives and y is persistently 6000mm/min max and x axis can reach the max 20000mm/min
if i sen m203 in the console it returns

	m203
Max speeds (mm/min): X: 20000.0, Y: 20000.0, Z: 20000.0, E:, min. speed 30.00

it appears nothing is setting the limit to 6000mm/min its just being applied somewhere to the y axis
any ideas
cheers
Rich

@deckingman i was typing it out while testing and doing calculations in various units to try and troubleshoot it they should all be 6000mm/min ive edited it now to show that, my web interface shows as mm/min if it was doing 6000mm/s it would be jumping around the workshop.

; Configure Connection - ENABLE ONLY ONE OF THE BELOW THREE
;M552 S1 ; Enable Wifi Network
;M552 S2 ; Enable Access Point Mode
M552 S1 P192.168.1.137 ; Enable Ethernet - Change IP Address to suit

; Network settings
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Network machine name
M550 P"WorkBee" ; Set machine name

M569 P0 S0 ; Drive 0 goes backwards   0=backwards 1= forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes backwards
M569 P4 S1

M584 X1:3 Y4 Z2 ;U:3 ; Apply drive mapping to axes
M584 P3 ; number of visible axes
M906 X3000 Y3000 Z3000  I100 ; Set motor currents (mA)
M350 X16 Y16 Z16  I1 ; Configure microstepping
M203 X20000 Y20000 Z20000  ; Set maximum speeds (mm/min)
M201 X300 Y300 Z150  ; Set accelerations (mm/s^2)
M566 X300 Y300 Z300  ; Set maximum instantaneous speed changes (mm/min)
M669 K0 X1:0:0:0 Y0:1:0:1 Z0:0:1:0

M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X3365 Y1555 Z94 ; Set axis maxima

M92 X53.33 Y53.33 Z400 ;U53.33 ; Set steps per mm

M574 X1 P"io1.in" S1 ; Set active low X endstop
M574 Y1 P"io3.in" S1 ; Set active low Y endstop
M574 Z1 P"io4.in" S1 ; Set active low Z endstop

M558 K0 P5 C"^!io5.in" H5 F500 T500

M950 R0 C"nil+out9+nil" L12000 ; Spindle 0 uses exp.heater3 as RPM pin and has a max RPM of 12000;define Spindle 0
M563 P0 R0 ;Define Tool 0 assign to Spindle 0

; Other Settings
M453 ; Put the machine into CNC Modes
G90 ; Set absolute coordinates
M140 H-1 ; Disable heated bed
M564 S1 H1 ; Disable jog commands when not homed
M911 S21.0 R23 P"G91 G1 Z3 F1000" ; Configure power loss resume


M558 K1 P8 C"io6.in" H5 F500 T500

the config is in seperate files but i have put the all in one place for ease of reading each file is each "paragraph" and in the order in which they are in the file, since doing this i have found out why i couldnt change the steps per mm and microstepping correctly and have corrected this already in the file. i have just tested it at 1/8 step and the correct steps per mm for that mode and max its still 6000mm/min regardless

@alankilian i havent got any that are internet worthy at the minute, workshop is in a right state, its a cnc router not a printer though. 1600mm x 3600 table with 1550 x 3350 usable area. Bit of a mish mash of an ooznest workbee and custom made bits to make it work at that size. Although i would love a 1500x1500x1500 3d printer, maybe a future project.

@dc42 yes its at full speed for pretty much the entire move of 1500mm the acceleration is set at 300mm/s/s which if i calculated it correctly it should be at full speed after 0.333 seconds and 13mm of travel

Hi
I seem to have hit some form of soft limit on my axis speed on duet 3 mb6hc , I can set m203 to 20000 and when I do a G0 move the Requested and Top Speed show as 6000mm/min, even if F10000 is specified. If I set m203 lower than 6000 it will report that requested and top speed in the interface. my Steps per mm is set at 53.33 and 1/16 microstepping which i have worked out to be 5.33khz step rate at 6000mm/min (if thats correct) which should definitely have headroom for a faster step rate.
I tried reducing the microstepping to 1/8 and as the steps per mm are defined before the microstepping according to the documentation they shouldnt need changing but the axis moves twice the distance and speed when done like this but still hits its 6000mm/min requested and top speed in the interface which is why i feel it is hitting some sort of soft limit i cant seem to find in any of the config files

Cheers
Rich

@phaedrux no error messages, the readouts update as if it has moved. with just the change to driver 4 in config-axes.g and reversing the motor direction in config-drives.g it works flawlessly, ive tested it both ways with the routed wiring, and also made up a single motor wire to eliminate the other wiring and with both it acts exactly the same. I have spoken to ooznest where i purchased the board and they have advised it may be faulty but i need to get comfirmation from this forum to get the warranty claim sorted

Cheers
Rich

@rich1351 bump

After some more testing I've swapped the x axis to driver 4 and all works as should no dropping out whatsoever so I have a feeling this board has a fault on driver 0 unless something in software is messing with driver 0

remaining config files config-user-settings.g config-probe.g config-override.g config-network.g config-laser.g config_default.g

config-spindle.g config-drives.g config-axes-limits.g config-axes-endstops.g config-axes-calibration.g config-axes.g config.g
ill have to upload the rest in another reply as it will only allow so many
The results from M122:
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TJ-6J9F0-3S86L-1V9LT
Used output buffers: 1 of 40 (22 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 91664 of which 0 recycled
Never used RAM 108768, free system stack 206 words
Tasks: NETWORK(ready,31.4%,212) ETHERNET(notifyWait,0.2%,126) HEAT(delaying,0.0%,405) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,333) TMC(notifyWait,7.4%,93) MAIN(running,60.8%,924) IDLE(ready,0.1%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:07:18 ago, cause: power up
Last software reset details not available
Error status: 0x00
Step timer max interval 158
MCU temperature: min 25.1, current 25.7, max 26.0
Supply voltage: min 23.8, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/24/0, gc cycles 0
Driver 0: position 0, standstill, reads 56989, writes 0 timeouts 0, SG min/max not available
Driver 1: position 0, standstill, reads 56989, writes 0 timeouts 0, SG min/max not available
Driver 2: position 0, standstill, reads 56989, writes 0 timeouts 0, SG min/max not available
Driver 3: position 0, standstill, reads 56989, writes 0 timeouts 0, SG min/max not available
Driver 4: position 0, standstill, reads 56989, writes 0 timeouts 0, SG min/max not available
Driver 5: position 0, standstill, reads 56989, writes 0 timeouts 0, SG min/max not available
Date/time: 2022-01-07 10:20:05
Slowest loop: 13.59ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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 = -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 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 521, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 521/0/0
Tx timeouts 0,0,521,0,0,0 last cancelled message type 30 dest 127

=== Network ===
Slowest loop: 13.77ms; 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: 2 of 8

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

The results from M98 P"config.g":
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Tool 49 not found

@theolodian here are the homing fileshomey.g homex.g homeall.g
it wouldnt post if i added them as code kept saying flagged as spam

Ive got an Ooznest Workbee that ive just upgraded to a Duet 3 MB 6HC.
ive updated it to 3.3 and installed Workbee Control. I have changed all the Endstop and relevant definitions in the config files to suit the Duet 3 as workbee control is intended for Duet 2
Im having problems with the X Axis motor (Driver 0) losing all holding/moving power after using HOME ALL.
If i home X on its own from a fresh power up it will home fine and when done will hold its place ang jog about fine. If i home X first then home Y, or do a HOME ALL (does it in same order) once all have homed the X axis has no holding torque and cannot jog about or re-home. If i hold the motor i can feel a slight rumble if i try to jog it, suggesting that the driver hasnt been turned off completely, maybe the current limit has been reduced drastically?
While retreating back to the main pc to sit down and check the homing files etc i came back to the machine and X axis was suddenly working and no matter what order i homed the axes there after it wouldnt repeat the problem. If power cycled it will revert to losing the x axis after HOME ALL or homing X first then Y. If i manually Home Y first then Home X from a fresh power on I can do whatever I like and X will never drop out even if i use HOME ALL or home X then Y.
I haven't tried to use the machine for anything yet as i dont have much faith in not knowing why X is dropping out, and even stranger why it will come back if left for a while.
I'm at a loss, ive double checked all the wiring, im convinced its something software but cant seem to see what could be causing this behaiviour.
Cheers
Rich

@dc42 Thanks, I knew there would be something I had missed, I read through the M558 page that many times it was starting to not make any sense
Ill get that sorted in the morning now, Thanks Again
Cheers
Rich

I have upgraded my duet 2 to a duet 3 after one of trinamic drivers on the duet 2 died.
I have modified the Workbee z probe to use the new duet 3 IO names and that all works fine.
I want to add another Z probe to the machine in a fixed location to simply touch off new tools when changed instead of keep attaching/detaching the ooznest probe each time.
if i add M558 K1 P5 C"io6.in" H5 F500 T500 as a new line in config-probe.g then go into the machine specific tab it shows the 2 probes but both work off the 1st probe input or more specifically the probe input defined as "K0" if i swap them. Im at a bit of a loss and cant find anyone else having the same problem

Cheers
Rich