I thought it is about end switches https://forum.e3d-online.com/threads/first-print-and-now-strange-homing-issue-need-advice.3362/ but it isn't. But repeatability is not happening. I put an Pin on the bed Homed x y moved had on top noticed values. Drove x and y axis some way and entered G0 X Y to position it didn't work. It seems that my system is every 10mm in x it looses 0,05mm and 10 mm in y it looses 0.1mm and this would also explain my repeatability issue. so even in senseless homing i can home and pick first tool but as soon as some moves happen (heavily tested today) a pick is not possible any more. i was now using an caliper homing x and y go to a good measurable position an measure x set caliper to 0 and go +10 measure go + 10 and so on and back in other direction. i am close at playing around with M92 X100 Y100 Z1600 C100 E417:417:417:417 values So my question are a) does anybody have similar issue ? b) can it be that my duet is broken ? (i have another unused at hand ) c) Do i have to make an holder for an micrometer watch ? d) any hints ? thank you verry much in advance
It sounds very much like lost steps but hard to be sure. I would try to simplify the system as much as possible to try to home in on the issue. You could try create a bare minimum config.g just for X, Y, Z, C motion. Leave everything out not related to that. Start the machine then home each axis manually to check correct function. Hopefully you have the toolhead at the center of the bed. You suspect you are losing steps, so I guess I would create a GCODE file manually of a lot of simple move steps in the middle of the bed. Start with a speed setting: G0 F1000 Set the currents for X and Y M906 X2000 Y2000 Then move through a simple square: G0 X100 Y150 Z5 G0 X200 G0 Y50 G0 X100 G0 Y150 Now repeat these move steps a hundred times and observe whether you see drift. In the start section, with the speed setting, you could alter parameters for XY current for each run. You can also run in M906 through the console at any time to report the active settings. One thing that occurred to me is that the home scripts which used stall detection lowered and raised the motor currents. I wonder if somehow you made changes which resulted in the currents not being returned to 100%. By including specific currents in your manual GCODE, you will at least rule that out.
Thank you spoon i did that dint need to go more than 100mm in x and y went back to the position and was in every try way ba more than an millimeter funny thing it was totally unpredictable (i thought i could rule out one stepper driver and change then the config to a better one. I am now in the process exchanging to an unused original (but 1 year old ) Duet Wifi board to rule out everything then we see thank you for your kind support and help thx thomas
Hi yes it is and M122 says it as well i measured it under load ( heating ) no change Now i have a verry strange situation i changed board , erased sd card started from scratch (as build manual says) ok Switchless home is not reliable so i configured the switches and have some findings 1) when i home x and y and move x+50 and y+50 i get an repeatable point marked by an pin so far so good 2) when i use some scripts to run basically on all positions on the board (like you suggested) and then go to that pin position by G0 x y there is an extreme offset clue 2 ) if you run this script 2 times the offset is wandering towards -y -x around 20 cm each do right now the behavior is for me not explainable any hints ? Ps: I had to rename the g files to code to load them up here thanks in advance Here the small script G1 X150 Y100 F50000 ; G1 X0 Y0 F50000 ; G1 X300 Y200 F50000 ; G1 X300 Y-49 F50000 ; G1 X0 Y200 F50000 ; G1 X150 Y-49 F50000 ; G1 X150 Y-49 F50000 ; park the head and here M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-956GU-DJMSJ-6J9D0-3S86R-KBPMG Used output buffers: 3 of 24 (16 max) === RTOS === Static ram: 25680 Dynamic ram: 95140 of which 0 recycled Exception stack ram used: 628 Never used ram: 9624 Tasks: NETWORK(ready,524) HEAT(blocked,1236) DUEX(suspended,156) MAIN(running,3820) IDLE(ready,160) Owned mutexes: === Platform === Last reset 00:13:01 ago, cause: software Last software reset at 2019-09-22 12:35, reason: User, spinning module GCodes, available RAM 9676 bytes (slot 0) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d Error status: 0 Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 2.7ms, max retries 0 MCU temperature: min 44.2, current 44.6, max 44.8 Supply voltage: min 24.5, current 24.6, max 24.8, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: standstill, SG min/max 7/261 Driver 1: standstill, SG min/max 6/243 Driver 2: standstill, SG min/max 0/235 Driver 3: standstill, SG min/max not available Driver 4: standstill, SG min/max not available Driver 5: standstill, SG min/max not available Driver 6: standstill, SG min/max not available Driver 7: standstill, SG min/max not available Driver 8: standstill, SG min/max not available Driver 9: standstill, SG min/max not available Date/time: 2019-09-22 12:48:58 Cache data hit count 3020222863 Slowest loop: 9.57ms; fastest: 0.08ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Move === Hiccups: 0, FreeDm: 169, MinFreeDm: 165, MaxWait: 77742ms Bed compensation in use: none, comp offset 0.000 === DDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 === GCodes === Segments left: 0 Stack records: 1 allocated, 0 in use 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 serial is idle in state(s) 0 aux is idle in state(s) 0 daemon is idle in state(s) 0 queue is idle in state(s) 0 autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 200.48ms; fastest: 0.08ms Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 - WiFi - Network state is running WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 1 WiFi firmware version 1.22 WiFi MAC address 5c:cf:7f:76:6f:78 WiFi Vcc 3.29, reset reason Turned on by main processor WiFi flash size 4194304, free heap 28320 WiFi IP address 192.168.111.40 WiFi signal strength -62dBm, reconnections 0, sleep mode modem Socket states: 0 2 0 0 0 0 0 0
Finally it was an mechanic error ,.. I don't know why i have overlooked it (maybe because i am fighting a cold an i am not 100% ,.. ) but on one of the X Y steppers there was one of the grub screws gone and the 2nd was not tight. So the axle is not round so in some positions it is driving if directions changes there was the slip ! maybe that should make an entry in the build manual it is verry difficult to see you have to search for it and check it ,.. Sorry for bothering ... and thank you all for the answers i learned a lot now on all the Duet M codes -
Really glad you found it. I guess it's another thing to consider. As we don't build XY, the assumption is that it is perfect as delivered. A missing grub screw would definitely mess things up. Thinking about it now, I kinda hope they all went in with threadlock too.
if you mean that blue or red stuff as threadlock no the grub screws where dry before machine goes to final position i will use loctite 243 to secure all screws. it cost me 3 full days ,..
hi that would be verry helpful and i added an hint at the build material where i would check the screws. Maybe a lot people don't check the ready build motion system but i did but overlooked that skipping effect. So it might help others a lot thx thomas Kamsker
