Giant Delta printer Slow Homing issue.
-
Looking at the data fore the driver that you linked to, the other thing you may need to do is use the alternate connection method to the expansion board:
- Connect PUL+ and DIR+ driver input to the +5V pin on one of the servo headers on the breakout board
- Connect PUL- to STEP- on the breakout board, and DIR- to DIR-.
The data says that you can leave ENA+ and ENA- not connected. This is probably best until you get everything working, however the Duet won't be able to turn the motors off. Therefore, when movement is working correctly, you may wish to connect ENA+ to +5V on the breakout board, and ENA- to ENA-. Use whichever of R0 and R1 works in the M569 commands.
-
Hi,
It finally succeeds, running smooth and correct in calibration, homing perfect, by changing ;- Connect PUL+ and DIR+ driver input to the +5V pin on one of the servo headers on the breakout board
- Keep Remain PUL- to STEP- on the breakout board, and DIR- to DIR-.
- Revert back the P values to "P0, P1, P2, P3" ( Because Correct one Create noise like ball bearings broken and move uncalibrated ). Therefore I cannot control the default direction (S values) ( But however on the drive I managed to change it ).
In a conclusion, even if it is solved, working better with an incorrect parameter. However, a +5V connections make a good job.
I still want to work with the correct parameters as you advise.
Thank you very much.
-
@sozkan said in Giant Delta printer Slow Homing issue.:
Revert back the P values to "P0, P1, P2, P3" ( Because Correct one Create noise like ball bearings broken and move uncalibrated ). Therefore I cannot control the default direction (S values) ( But however on the drive I managed to change it ).
Your external axes will be using default timing. Send
M569 P5and see what it says. It did not run well because of the T parameter settings you used:M569 P5 S1 R1 T3:3:5:0From the product page you linked, there's this, which shows the timing you should be using:
M569 T parameter, where Taa:bb:cc:dd:
aa = Minimum driver step pulse width, in microseconds = t3 in image = not less than 2.5us
bb=step pulse interval, in microseconds = t4 in image = not less than 2.5us
cc=direction setup time, in microseconds = t1/t2/t5 in image = at least 6us
dd=direction hold time, in microseconds = t1/t2/t5 = at least 6us
Enable signal t1 = assume that you have ENA+ an ENA- floating, so constantly enabled. Also, I think t3 and t4 are the wrong way around in the image, but they are the same value.From this, try:
M569 P5 S1 R1 T2.5:2.5:6:6 ; Extruder drive 0 goes Forward M569 P6 S1 R1 T2.5:2.5:6:6 ; X:A drive 1 goes Forward M569 P7 S1 R1 T2.5:2.5:6:6 ; Y:B drive 2 goes Forward M569 P8 S1 R1 T2.5:2.5:6:6 ; Z:C physical drive 3 goes ForwardIan
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
@droftarts said in Giant Delta printer Slow Homing issue.:
@sozkan said in Giant Delta printer Slow Homing issue.:
Revert back the P values to "P0, P1, P2, P3" ( Because Correct one Create noise like ball bearings broken and move uncalibrated ). Therefore I cannot control the default direction (S values) ( But however on the drive I managed to change it ).
Your external axes will be using default timing. Send
M569 P5and see what it says. It did not run well because of the T parameter settings you used:M569 P5 S1 R1 T3:3:5:0From the product page you linked, there's this, which shows the timing you should be using:
M569 T parameter, where Taa:bb:cc:dd:
aa = Minimum driver step pulse width, in microseconds = t3 in image = not less than 2.5us
bb=step pulse interval, in microseconds = t4 in image = not less than 2.5us
cc=direction setup time, in microseconds = t1/t2/t5 in image = at least 6us
dd=direction hold time, in microseconds = t1/t2/t5 = at least 6us
Enable signal t1 = assume that you have ENA+ an ENA- floating, so constantly enabled. Also, I think t3 and t4 are the wrong way around in the image, but they are the same value.From this, try:
M569 P5 S1 R1 T2.5:2.5:6:6 ; Extruder drive 0 goes Forward M569 P6 S1 R1 T2.5:2.5:6:6 ; X:A drive 1 goes Forward M569 P7 S1 R1 T2.5:2.5:6:6 ; Y:B drive 2 goes Forward M569 P8 S1 R1 T2.5:2.5:6:6 ; Z:C physical drive 3 goes ForwardIan
Hello. Thank you for your concern and effort.
I was busy with upgrading mechanical hardware.
I just came to this point once again. The problem is not solved yet. When P values changed to 5,6,7 sounds horrible and inccorrect. But when P values 1,2,3 it is working but not correct right?
Please see the video I make on youtube : Link for video. -
In your video it looks like you're getting an error message when trying to save the config.g and reboot the board. Failed to download config.g.
Are the updates you are making to config.g actually getting saved?
Can you please provide the results of M122 and M98 P"config.g" ?
-
@Phaedrux said in Giant Delta printer Slow Homing issue.:
In your video it looks like you're getting an error message when trying to save the config.g and reboot the board. Failed to download config.g.
Are the updates you are making to config.g actually getting saved?
Can you please provide the results of M122 and M98 P"config.g" ?
Please check the full code:
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Sun Sep 27 2020 20:52:39 GMT+0200 (Central European Summer Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Giant3D" ; set printer name M665 R600 L1200 B575 H1450 ; Set delta radius, diagonal rod length, printable radius and homed height ;M564 H0 ; allow jog without homing M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them ; Network M551 P"xxxxxx" ; set password M587 S"WfiName" P"xxxxxx" I192.168.1.200 M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P5 S0 R0 T3:3:5:0 ; Extruder drive 0 goes Forward M569 P6 S1 R0 T2.5:2.5:6:6 ; X:A drive 1 goes Forward M569 P7 S1 R0 T2.5:2.5:6:6 ; Y:B drive 2 goes Forward M569 P8 S1 R0 T2.5:2.5:6:6 ; Z:C physical drive 3 goes Forward M584 X6 Y7 Z8 E5 ; set drive mapping M350 X0 Y0 Z0 E0 I1 ; configure microstepping without interpolation M92 X114.29 Y114.29 Z114.29 E274.00 ; set steps per mm (400/140) * 40 = 114.2857 ;; 400 step per rev ;; 140 mm one rev pulley ;;1:40 ratio gearbox M566 X1200.00 Y1200.00 Z1200.00 E1200.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z6000.00 E3000.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z500.00 E1000.00 ; set accelerations (mm/s^2) M906 X1000 Y1000 Z1000 E800 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 Z0 S1 ; set minimum Z ; Endstops M574 X2 S1 P"xstop" ; configure active-high endstop for high end on X via pin xstop M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop M574 Z2 S1 P"zstop" ; configure active-high endstop for high end on Z via pin zstop ; Z-Probe M558 P1 C"zprobe.in+zprobe.mod" H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved G31 P500 X0 Y0 Z3.5 ; set Z probe trigger value, offset and trigger height M557 R350 S200 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"e0temp" Y"pt1000" R4700 ; configure sensor 1 as PT1000 on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S0.50 ; disable bang-bang mode for heater and set PWM limit M308 S2 P"e1temp" Y"pt1000" R4700 ; configure sensor 2 as PT1000 on pin e1temp M950 H2 C"e1heat" T2 ; create nozzle heater output on e1heat and map it to sensor 2 M307 H2 B0 S0.50 ; disable bang-bang mode for heater and set PWM limit ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S1 H2:1 T45 ; set fan 0 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1:2 F0 S"Typhoon" ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; set initial tool 1 active and standby temperatures to 0C ; Custom settings are not defined ; Miscellaneous M575 P1 S1 B57600 ; enable support for PanelDue M501 ; load saved parameters from non-volatile memory M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss T0 ; select first tool G91 ; relative positioning ;G1 H2 X-0.1 Y-0.1 Z-0.1 F1000 ; go down a few mm -
Also, in your video it looks like you have the DWC web files in your /system folder. They should not be there. (The CSS, FONTS, JS folders for example, and the html.gz files, etc.) Those files all belong in the /www folder on the SD card.
I think there may have been a few mistakes made during a firmware update.
-
@sozkan said in Giant Delta printer Slow Homing issue.:
Can you please provide the results of M122 and M98 P"config.g" ?
-
@Phaedrux it could be. Thank you for your attention. I am still on the learning curve.
-
You can see an example of the correct file structure here.
https://duet3d.dozuki.com/Wiki/SD_Card#Section_Creating_the_file_structure
Note that your /sys folder will also contain some .bin files for the firmware in addition to the listed .g config files.
It may be easiest to put the SD card into a PC to edit the file structure.
-
@Phaedrux said in Giant Delta printer Slow Homing issue.:
@sozkan said in Giant Delta printer Slow Homing issue.:
Can you please provide the results of M122 and M98 P"config.g" ?
I realize now, you want me to send a command to the machine right? I can do it by tomorrow.
-
Yes, M122 will give us some diagnostic information including verifying what firmware version is installed. And M98 P"config.g" will execute the config.g file as a macro and echo back any error messages which are otherwise missed during power on. This would help eliminate any other syntax errors in config.g.
-
This may not resolve your noisy motors, but it will at least ensure we're working with a correctly functioning setup.
-
M569 P1 P2 P3 are fine if those cause the motors to move those are the correct ones. It's just targeting those driver numbers.
-
@Phaedrux
I will definitely do and share the result by tomorrow.But I am sure there is no imperfection on hardware and wiring. Because motors are accurately working on illegal code, but creating horrible sound and incorrectly working on legal code. That's means I have done something working during the firmware upgrade?
Because it is the latest stable update recently I messed up.
-
And yes, reduce acceleration and jerk. That should help a bit.
The motors are going to be loud. They are large and mounted to metal, but hopefully the adjusted timing and acceleration will make it a bit more bearable.
@sozkan said in Giant Delta printer Slow Homing issue.:
Because motors are accurately working on illegal code, but creating horrible sound and incorrectly working on legal code.
It's not illegal code if it works.
-
@Phaedrux said in Giant Delta printer Slow Homing issue.:
M569 P1 P2 P3 are fine if those cause the motors to move those are the correct ones. It's just targeting those driver numbers.
It`s some how stable on motor step control, but with those settings, I cannot control Enable or disable the motor features as well as the direction due to the illegal numbering. Because event Mr. admin "dc42" suggests for the external motor drives the stepper breakout board legal codes P5,6,7,8. Somehow these legal settings only working enable and direction settings and unstable step signals for the motor.
-
@Phaedrux said in Giant Delta printer Slow Homing issue.:
And yes, reduce acceleration and jerk. That should help a bit.
The motors are going to be loud. They are large and mounted to metal, but hopefully the adjusted timing and acceleration will make it a bit more bearable.
@sozkan said in Giant Delta printer Slow Homing issue.:
Because motors are accurately working on illegal code, but creating horrible sound and incorrectly working on legal code.
It's not illegal code if it works.
Since it is not functioning other variables except stepping, also according to the Firmware developer it is illegal
-
@sozkan said in Giant Delta printer Slow Homing issue.:
@Phaedrux said in Giant Delta printer Slow Homing issue.:
And yes, reduce acceleration and jerk. That should help a bit.
The motors are going to be loud. They are large and mounted to metal, but hopefully the adjusted timing and acceleration will make it a bit more bearable.
@sozkan said in Giant Delta printer Slow Homing issue.:
Because motors are accurately working on illegal code, but creating horrible sound and incorrectly working on legal code.
It's not illegal code if it works.
Since it is not functioning other variables except stepping, also according to the Firmware developer it is illegal
Until I found a stable solution, I will continue with this achieved a motor enable issue by hardware and mechanical brake gearbox and right direction setup on external motor driver. I believe it might run G-codes sufficiently if there is no hidden failure.
-
@Phaedrux said in Giant Delta printer Slow Homing issue.:
M98 P"config.g"
Hi,
I have just done your advise:
result :
10/23/2020, 4:31:32 PM M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2-beta1 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MS8-6JTD4-3S86J-19SHA
Used output buffers: 3 of 24 (21 max)
=== RTOS ===
Static ram: 23916
Dynamic ram: 98532 of which 120 recycled
Exception stack ram used: 544
Never used ram: 7960
Tasks: NETWORK(ready,125) HEAT(blocked,138) MAIN(running,328) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:03:52 ago, cause: power up
Last software reset at 2020-10-22 20:24, reason: User, GCodes spinning, available RAM 8036, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0x028
MCU temperature: min 30.7, current 32.4, max 32.6
Supply voltage: min 24.2, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 276494, standstill, SG min/max not available
Driver 1: position 276494, standstill, SG min/max not available
Driver 2: position 276494, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2020-10-23 16:31:31
Cache data hit count 407671411
Slowest loop: 65.60ms; fastest: 0.15ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 1.0ms, write time 28.7ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 19, completed moves: 19, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 217.22ms; fastest: 0.09ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 2
WiFi firmware version 1.23
WiFi MAC address 80:7d:3a:3f:f6:73
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 22848
WiFi IP address 192.168.43.196
WiFi signal strength -67dBm, reconnections 0, sleep mode modem
Clock register ffffffff
Socket states: 0 0 0 0 0 0 0 0
10/23/2020, 4:30:44 PM Error: Temperature reading fault on heater 1: sensor open circuit
Error: Temperature reading fault on heater 2: sensor open circuit
10/23/2020, 4:30:42 PM M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Driver 6 does not support x0 microstepping with interpolation
Driver 7 does not support x0 microstepping with interpolation
Driver 8 does not support x0 microstepping with interpolation
Driver 5 does not support x0 microstepping with interpolation
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 258C
- WiFi -
