-
; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Orang_" ; set printer name ;M669 K10 Uxx Lxx Rrr Aaa: bb Hxx M669 K10 U170 L319 R55.94 A-45:52 B135 H439.2 X-60,Y60,Z180 M666 X-1.2 Y-0.7 Z1.4 ; Drives M569 P0 S1 ; physical drive 0 goes forwards using default driver timings |D3 stealthChop2 M569 P1 S1 ; physical drive 1 goes forwards using default driver timings M569 P2 S1 ; physical drive 2 goes forwards using default driver timings M569 P3 S0 ; physical drive 3 goes forwards using default driver timings M584 X0 Y1 Z2 E3 ; set drive mapping M350 X64 Y64 Z64 E64 ; configure microstepping with interpolation M92 X1761.5 Y1761.5 Z1761.5 E1488.59 ; set steps per mm M566 X1200.00 Y1200.00 Z1200.00 E1200.00 ; set maximum instantaneous speed changes (mm/min) M203 X18000.00 Y18000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z500.00 E1000.00 ; set accelerations (mm/s^2) M906 X700 Y700 Z700 E600 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 Z-2:270 ; set minimum Z ; Endstops M574 X2 S1 P"!xstopmax" ; configure active-high endstop for low end on X via pin xstop M574 Y2 S1 P"!ystopmax" ; configure active-high endstop for low end on Y via pin ystop M574 Z2 S1 P"!zstopmax" ; configure active-high endstop for low end on Z via pin zstop ; Z-Probe M558 P5 C"^zstop" H5 F120 T2000 X0 Y0 Z1 M557 R80 S20 ; define mesh grid G31 X0 Y0 Z33.385 P25 ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C M563 P2 S"2rr" D0 H1 F0 ; define tool 2 G10 P2 X0 Y0 Z-23.3 ; set tool 2 axis offsets G10 P2 R0 S0 M563 P5 S"TEST" D0 H1 F0 ; define tool 2 G10 P2 X0 Y0 Z-29.3 ; set tool 2 axis offsets G10 P2 R0 S0 ; Custom settings are not defined ; Miscellaneous T2 M575 P1 B57600 S0 -
RepRapFirmware 3.2-RC2 Port for LPC
Have you gone over your printer mechanics? - Yes
"
https://duet3d.dozuki.com/Wiki/Configuring_RepRapFirmware_for_a_Rotary_Deltahttps://duet3d.dozuki.com/Wiki/Calibrating_a_delta_printer
" - yes -
Moved to the LPC port forum since that may be relevant.
Can you also send M98 P"config.g" and post the results?
Also your homedelta.g?
-
; homedelta.g G91 ; relative positioning G1 H1 X265 Y265 Z265 F1800 ; move all towers to the high end stopping at the endstops (first pass) G1 H2 X-5 Y-5 Z-5 F1800 ; go down a few mm G1 H1 X10 Y10 Z10 F360 ; move all towers up once more (second pass) ;G1 Z-5 F1000 ; move down a few mm so that the nozzle can be centred G90 ; absolute positioning -
M98 P "config.g"
Warning: Macro file "config.g" not found -
@Orang_ said in Rotary delta calibration not implemented?:
M98 P "config.g"
Was there a space between the P and " when you sent the command?
-
M98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is disabled -
Thanks. I'm afraid that's the extent of my delta knowledge and I know even less about the LPC port.
A video may help and the results of M122 never hurt.
Is RC2 the latest for the LPC port, or can you update to 3.2 final?
-
-
@Phaedrux said in Rotary delta calibration not implemented?:
RC2 the latest for the LPC port, or can you update to 3.2 final?
yes, i can
-
From your video is seems like it's triggering the probe, but then skipping steps on one arm when it tries to return to the dive height causing it to lurch.
Are you sure there's no slipping grub screw or something like that?
-
M122 === Diagnostics === RepRapFirmware for LPC176x based Boards (biquskr_1.3) version 3.2-beta4.1_1 running on LPC176x at 100Mhz Used output buffers: 3 of 16 (11 max) === RTOS === Static ram: 5044 Dynamic Memory (RTOS Heap 5): 2056 free, 1992 never used Never used RAM 80, free system stack 6 words Tasks: NETWORK(blocked,196) HEAT(blocked,242) MAIN(running,353) IDLE(ready,20) Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:55:21 ago, cause: [software] Last software reset at 2021-01-11 22:25, reason: User, GCodes spinning, available RAM 256, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00428000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN Error status: 0x00 Supply voltage: under voltage events: 0 Driver 0: position 43414, no-driver-detected Driver 1: position 43808, no-driver-detected Driver 2: position 41828, no-driver-detected Driver 3: position 0, no-driver-detected Driver 4: position 0 Driver 5: position 0 Driver 6: position 0 Date/time: 2021-01-11 23:20:45 Slowest loop: 95.26ms; fastest: 0.12ms Step timer: target 2615712365 count 3321023289 delta -705310924 late 0 USBSerial connected 0 ADC not ready 2 ADC error threshold 10 ADC Init 1 Ints: 0; Calls 0; fast: 4294967295uS; slow 0uS adj 0 bad 0 big delta 0 PWM Channels Delta -1446546330 Start -1 End -1 === Storage === Free file entries: 4 SD card 0 detected SD card longest read time 5.7ms, write time 5.3ms, max retries 0 === Move === FreeDm 100 (min 97), maxWait 1181857ms, bed compensation in use: none, comp offset 0.000 === DDARing === Scheduled moves 91, completed moves 91, hiccups 39525, stepErrors 0, LaErrors 0, Underruns [0, 0, 2], CDDA state -1 === Heat === Bed heaters = 0, chamberHeaters = -1 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 Movement lock held by null HTTP 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 322.64ms; fastest: 0.00ms Responder states: HTTP(2) HTTP(0) HTTP sessions: 1 of 2 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.25B0-01L-D WiFi MAC address e0:3f:49:23:39:c4 WiFi Vcc 2.93, reset reason Turned on by main processor WiFi flash size 4194304, free heap 35560 WiFi IP address 192.168.1.97 WiFi signal strength -55dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00181001 Socket states: 0 0 -
There should be no differences between the LPC port and the normal version in terms of kinematics etc that I'm aware of. There are some other restrictions but that's mainly due to memory.
-
You can upgrade to 3.2 final from here https://github.com/gloomyandy/RepRapFirmware/releases/tag/v3.2_1
-
@Phaedrux said in Rotary delta calibration not implemented?:
From your video is seems like it's triggering the probe, but then skipping steps on one arm when it tries to return to the dive height causing it to lurch.
Are you sure there's no slipping grub screw or something like that?
it happens only with delta calibration and mesh compensation, with normal use it is not observed
-
RepRapFirmware 3.2 does not solve the problem(((
-
@Orang_ said in Rotary delta calibration not implemented?:
M350 X64 Y64 Z64 E64 ; configure microstepping with interpolation M92 X1761.5 Y1761.5 Z1761.5 E1488.59 ; set steps per mm
Pardon my ignorance on the LPC port, but perhaps you can try using x16 microstepping to get a baseline?
I notice in your M122 there are a lot of hiccups which can mean skipped steps, so reducing the microstepping could help
hiccups 39525 -
@Phaedrux said in Rotary delta calibration not implemented?:
@Orang_ said in Rotary delta calibration not implemented?:
M350 X64 Y64 Z64 E64 ; configure microstepping with interpolation M92 X1761.5 Y1761.5 Z1761.5 E1488.59 ; set steps per mm
Pardon my ignorance on the LPC port, but perhaps you can try using x16 microstepping to get a baseline?
I notice in your M122 there are a lot of hiccups which can mean skipped steps, so reducing the microstepping could help
hiccups 39525The printer behaves the same way only with delta calibration and mesh compensation, no problems with printing and moving, I do not think the problem is microstepping but I can try
-
@Orang_ yea, I really wouldn't run anything higher than x16 on an LPC
-
@Orang_ said in Rotary delta calibration not implemented?:
only with delta calibration and mesh compensation
Yes, and it's the quick movements to raise Z after probing that it's skipping, and those moves would be generating the most step pulses. The hiccups are indicating an issue caused by too high microstepping values.
If this isn't the problem I'll be surprised.
