One axis will not calibrate
-
@thunderboltcutter said in One axis will not calibrate:
I am getting a spam error when trying to post M122 output to the forum. Is there a work around?
Change the file extension to .g perhaps?
Frederick
-
@fcwilt
I am going break things up into a few posts to see what's getting caught by the filter.~~M98 P"config.g" HTTP is enabled on port 80 FTP is enabled on port 21 TELNET is enabled on port 23~~ -
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS) running on Duet WiFi 1.02 or later Board ID: 08DLM-996RU-N85S4-7JTDL-3SN6R-1S9VR Used output buffers: 1 of 20 (19 max) === RTOS === Static ram: 28380 Dynamic ram: 95820 of which 0 recycled Exception stack ram used: 420 Never used ram: 6452 Task NETWORK ready, free stack 324 Task HEAT blocked, free stack 1256 Task MAIN running, free stack 3624 -
@thunderboltcutter said in One axis will not calibrate:
For some reason my Y axis will not respond to changes in the config.g file. When I print a calibration cube that side always comes out the same.
What exactly does this mean? I'm not sure what you're describing. Photo of the results? What are you expecting to happen? What are you trying to change?
-
I've given you a few upvotes, so hopefully it won't bug you about spam as much. Might also help to take a pause for 10 minutes and try and create a single post again with all the copy and paste. Multiple posts in rapid succession is likely to trigger it.
-
@Phaedrux said in One axis will not calibrate:
I've given you a few upvotes, so hopefully it won't bug you about spam as much. Might also help to take a pause for 10 minutes and try and create a single post again with all the copy and paste. Multiple posts in rapid succession is likely to trigger it.
I learn something new everyday.
Frederick
-
No matter what I do with the y axis variable when printing a calibration cube I get 20.55mm from that side.
Using setting like this yields the same results:
M92 X90.36 Y88.78 Z2151.90
M92 X90.36 Y91.0 Z2151.90M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS) running on Duet WiFi 1.02 or later Board ID: 08DLM-996RU-N85S4-7JTDL-3SN6R-1S9VR Used output buffers: 1 of 20 (19 max) === RTOS === Static ram: 28380 Dynamic ram: 95820 of which 0 recycled Exception stack ram used: 420 Never used ram: 6452 Task NETWORK ready, free stack 324 Task HEAT blocked, free stack 1256 Task MAIN running, free stack 3624 === Platform === Last reset 05:29:33 ago, cause: power up Last software reset at 2021-03-18 20:25, reason: User, spinning module GCodes, available RAM 6588 bytes (slot 3) Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff Error status: 0 Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 0.0ms MCU temperature: min 25.5, current 25.5, max 25.8 Supply voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0, over voltage events: 0 Driver 0: standstill, SG min/max not available Driver 1: standstill, SG min/max not available Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max not available Driver 4: standstill, SG min/max not available Date/time: 2021-03-19 15:06:44 Slowest loop: 7.60ms; fastest: 0.08ms === Move === Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0 Scheduled moves: 0, completed moves: 0 Bed compensation in use: none Bed probe heights: 0.000 0.000 0.000 0.000 0.000 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 Heater 0 is on, I-accum = 0.8 Heater 1 is on, I-accum = 0.4 === GCodes === Segments left: 0 Stack records: 2 allocated, 0 in use 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 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.85ms; fastest: 0.01ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 2 of 8 - WiFi - Network state is running WiFi module is connected to access point Failed messages: pending 3, notready 0, noresp 3 WiFi firmware version 1.25 WiFi MAC address f4:cf:a2:69:48:de WiFi Vcc 3.33, reset reason Turned on by main processor WiFi flash size 4194304, free heap 23104 WiFi IP address 192.168.1.82 WiFi signal strength -56dBm, reconnections 0, sleep mode unknown Socket states: 0 0 0 0 0 0 0 0 === Expansion === -
@thunderboltcutter said in One axis will not calibrate:
No matter what I do with the y axis variable when printing a calibration cube I get 20.55mm from that side.
Using setting like this yields the same results:
M92 X90.36 Y88.78 Z2151.90
M92 X90.36 Y91.0 Z2151.90Where did you get those values? They are a bit unusual.
Perhaps you could restore the X and Y values to the theoretical values and using...
M579 X1.0 Y1.0 Z1.0 ; scaling (values are determined by measuring test object)
to scale the size of the objects printed? Values of 1.0, as shown, produce no scaling.
Frederick
-
@fcwilt said in One axis will not calibrate:
Where did you get those values? They are a bit unusual.
Looks like the solid doodle uses MXL belts and 17 tooth pulleys for an approximate steps per mm of 88.
http://www.soliforum.com/topic/2671/solidoodle-belt-and-pulley-specs-belt-replacement-guide/page/2/
https://tomhorsley.com/hardware/solidoodle/solidoodle-calibration.html
@thunderboltcutter said in One axis will not calibrate:
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS)
Can I get you to update your firmware?
Upload this zip file to the system tab in DWC.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
Don't extract it first.
-
@Phaedrux said in One axis will not calibrate:
Looks like the solid doodle uses MXL belts and 17 tooth pulleys for an approximate steps per mm of 88.
Never heard of MXL belts or 17 tooth pulleys - new facts to stuff into my old brain.
One thing I don't quite understand is why the X and Y steps/mm (whatever they actually should be) would in practice be different.
What is the source of the variation between X and Y?
Thanks.
Frederick
-
@fcwilt said in One axis will not calibrate:
What is the source of the variation between X and Y?
Well Solid Doodle made some funny choices. (MXL, 17 tooth, etc) so who knows what else is funky in there. Product of the times I suppose.
As for why they would be so different here in this case and why the steps per mm isn't having an effect, I wonder if it's something mechanical. Slippage or something. Loose grub screw?
