Unable to home z axis
-
Doing some searching in the E3D Big box forum (https://forum.e3d-online.com/#bigbox-3d-printer.1) I was able to find this, but it's from 2016, which makes it rather old firmware at this point, but it does contain the basics. I also don't know if it matches your BigBox as there were a few different versions and revisions I think... So that complicates matters and makes directly porting a config between machines non-trivial.
; Movement section M569 P0 S1 ; Drive 0 goes forwards (change to S0 to reverse it) M569 P1 S1 ; Drive 1 goes forwards M569 P2 S1 ; Drive 2 goes forwards M569 P3 S1 ; Drive 3 goes forwards M569 P4 S1 ; Drive 4 goes forwards M574 X1 Y1 Z1.2 S1 ; set endstop configuration (X and Y endstops only, at low end, active high) M906 X800 Y600 Z800 E1000 ; Set motor currents (mA) M201 X800 Y800 Z15 E1000 ; Accelerations (mm/s^2) M203 X15000 Y15000 Z100 E3600 ; Maximum speeds (mm/min) M566 X600 Y600 Z30 E20 ; Minimum speeds mm/minute M208 X300 Y200 Z200 ; set axis maxima (adjust to suit your machine) M208 X0 Y0 Z-0.2 S1 ; set axis minimum (adjust to make X=0 and Y=0 the edge of the bed) M92 X160 Y360 Z1600 ; Set axis steps/mm M92 E304:304 ; Set extruder steps per mm G21 ; Work in millimetres G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves M350 X16 Y16 E16 I1 ; Set 16x microstepping with interpolationI found a couple others which all had different values for steps per mm and number of tools etc as each person has customized the machine.
Perhaps this versions list would help identify exactly which one you have? https://wiki.e3d-online.com/BigBox_Version_Overview
At any rate, most of the important parts can be derived from the machine itself during commissioning. Comparing distance requested versus distance moved, etc to get steps per mm.
I think you're quite close though with what you have currently.
-
@Phaedrux
Thanks so much Phaedrux, I'll review the files you've given me.I agree with being close with my current set up but what I'm worrying about is why I can't Z probe or Z home. I have thought before trying to swap Duet for RAMPS or to try the files you've given me is to put a switch on Z lower position plugging it into the normal z socket rather than the Z probe connector, of course doing this just as a trial to prove a point.
I'll keep copies, of course, of all my previous files (I learnt this hard way
) Other points are lifting the floorboards but being 68 and suffering with severe back problems from birth and no children to do the job for me this is the very last option.Can I post a series of all the other relevant files, homeall, homex etc,etc for your perusal just so those are correct. I know you have said previously that they appear good but I think I may have made a small change or two so I'd just like to be sure.
There is one other thing of course, I gather that there are various settings that are different even though they're on the same machine, am I right? If I am right in this assumption could you direct me to which these commands are and I'll attempt to set them to suit.
Keith
-
@Kayjay yes, please post your current files.
For the probe, just to confirm, it triggers when close to the bed, both the LED on the IR probe itself, and goes from 0 to 530ish in DWC,
Also, how exactly are you triggering the home all (or Z)? Using DWC buttons?
Ian
Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard
-
It would appear that I have the Bigbox Pro Hybrid Titan, it's the one with the Titan extruder on the back of the machine rather than above the hotend. The probe changes from 0 to 537 when activated by my finger or a piece of paper etc but the bed never rises to activate the probe, this is the whole problem I am suffering. X and Y home fine at 0 on the left front side of the bed but as you can see from homez and homeall the head moves to the centre of the bed and then just stops whatever height the bed is at, the bed just doesn't move
Here are my current files.
; bed.g M561 ; clear any bed transform G29 ; probe the bed and enable compensation; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Bigbox1" ; set printer name ; Network M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S0 ; physical drive 2 goes backwards M569 P3 S1 ; physical drive 3 goes forwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min) M201 X750.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X300 Y200 Z200 S0 ; set axis maxima ; Endstops M574 X1 Y1 S1 ; set active high endstops M574 Z1 S2 ; set endstops controlled by probe ; Z-Probe M558 P1 H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height M557 X15:215 Y15:195 S20 ; define mesh grid ; Heaters M305 P0 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M305 P1 X200 ; configure PT100 for heater 1 M143 H1 S320 ; set temperature limit for heater 1 to 320C ; Fans M106 P0 S0 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P1 S1 I0 F500 H1 T45 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; 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; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Thu Aug 06 2020 10:36:11 GMT+0100 (British Summer Time) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-305 Y-205 F1800 ; move quickly to X and Y axis endstops and stop there (first pass) G1 H2 X5 Y5 F6000 ; go back a few mm G1 H1 X-305 Y-205 F360 ; move slowly to X and Y axis endstops once more (second pass) G90 ; absolute positioning G1 X150 Y100 F6000 ; go to first bed probe point and home Z G30 ; home Z by probing the bed ; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 Z5 F100 ; lift Z relative to current position ;G90 ; absolute positioning; homex.g G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-305 F1800 ; move quickly to X axis endstop and stop there (first pass) G1 H2 X5 F6000 ; go back a few mm G1 H1 X-305 F360 ; move slowly to X axis endstop once more (second pass) G1 H2 Z-5 F6000 ; lower Z again G90 ; absolute positioning; homey.g G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 Y-205 F1800 ; move quickly to Y axis endstop and stop there (first pass) G1 H2 Y5 F6000 ; go back a few mm G1 H1 Y-205 F360 ; move slowly to Y axis endstop once more (second pass) G1 H2 Z-5 F6000 ; lower Z again G90 ; absolute positioning; homez.g G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G90 ; absolute positioning G1 X150 Y100 F6000 ; go to first probe point G30 ; home Z by probing the bed ; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 Z5 F100 ; lift Z relative to current position ;G90 ; absolute positioning -
@droftarts
Sorry, I forgot to mention how I activate the probe. I've tried Homeall and Homez using the buttons on DWC Machine Control, Head movement.Is there any other method I can use which may help?
-
@Kayjay said in Unable to home z axis:
X and Y home fine at 0 on the left front side of the bed but as you can see from homez and homeall the head moves to the centre of the bed and then just stops whatever height the bed is at, the bed just doesn't move
Your config looks correct and it sounds like it's trying to home correctly. Your probe seems to be registering because the LEDs light up. But your Z axis doesn't seem to be moving.
Does the Z axis ever move?
Can you send these commands to try and test the Z axis movement. Make sure there is enough travel available on the Z axis in either direction just to try and avoid a crash.
G92 Z10
G91
G1 Z5 F60That should let us determine if the Z motor is actually working.
-
@Kayjay said in Unable to home z axis:
M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X750.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per centThis can't be the config.g you're using. All your motor settings are back at the original values. I thought they were now:
M92 X160.00 Y360.00 Z400.00 E304.00 ; set steps per mm
M566 X480.00 Y480.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z360.00 E1500.00 ; set maximum speeds (mm/min)
M201 X750.00 Y750.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
M906 X1300 Y1300 Z1300 E1300 I30 ; set motor currents (mA) and motor idle factor in per centPlease copy the contents of config.g from DWC (as in, what's actually on your SD card) and paste them in your reply. I think you've just copied and pasted old config files from your PC.
Also, I think what @Phaedrux was trying to say is that you need to test the Z motors at low speed, and find the speed that they stall at. So type in each line of the following at the gcode console in DWC, and see what speed the Z axis stops being able to move at:
G92 Z10 ; Set Z axis position G91 ; set to relative positioning G1 Z5 F30 ; move bed down 5mm at F30 G1 Z-5 F30 ; move bed up 5mm at F30 G1 Z5 F60 G1 Z-5 F60 G1 Z5 F90 G1 Z-5 F90 G1 Z5 F120 G1 Z-5 F120 G90 ; set absolute positioningF120 is what your probing move is set to. If the motor can't move at this speed, that'll be why it won't home.
Ian
Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard
-
Thanks for the info. I have gathered several sets of files and it appears I've installed the wrong ones, I do apologise. I'll sort that out in the morning (as you can see I'm awake in the middle of the night) and also delete all the out of date stuff or at least mark it as such so I don't make the same mistake again.
To clarify what I did was copy and paste from system editor in DWC not the card, I must have inadvertently loaded the wrong config files into DWC at some point in the last day or so simply trying different things to test situations but as I say I will rectify this in the morning and ensure I have the correct files installed.
I'll also follow your instructions to test for the stall speed of the Z motors. Just to clarify, Z motors do work at the speed set in homeall, homex, and homey, they move up and down 5mm as per the command settings in the various homing files but wherever the bed is set, at any distance from the head it never moves when it reaches the G30 command.
Your list of commands should help sort out what's happening and possibly where the fault lies.Thanks again
Keith -
droftarts spotted I was using an old set of config files so I'll correct that in the morning.
Regarding your questions, Z does move, in fact it moves whenever commanded to in homeall, homex and homey it just fails in homez, I'm assuming when it reaches G30 as it executes every command before that instruction.
I will though test your instructions in the morning, I will also try out M122 and M98 P"config.g" and post the results, my apologies for not doing this before when you asked.Thanks again
Keith -
Should I make and post a video of what's happening? Would that help? Should I use 'Upload File' to do this? I;m assuming 'Upload Image' is for stills
Keith
-
@Kayjay there’s a limit on the size of file you can upload, and videos are usually too big. Better to upload a video to somewhere like YouTube and post a link to it.
Ian
-
@droftarts
My apologies for one massive error, the files I had installed on my SD were the ones as I explained earlier but I'm afraid those are the only ones I can find. I do have lots of copies -1, -2 etc etc but they appear to be the same so I've made a new set using the config tool and your figures which you noted down for me in your previous post, thank you so much, it was an enormous help. I'll now post the config.g I have on my SD and I would be very grateful if you would cast an eye over it and confirm it's ok. If it is I will then proceed with the next set of test that yourself and Phaedrux has listed for me. Again, I must thank you both for the time you have spent working with my problem, it's only because of that effort that hbas stopped me giving up and buying an Anet 8 Plus which seems good value for money and given that Thomas S has given it the thumbs up I was tempted but I prefer to work with my Bigbox and solve the problem. One main reason is the excellent Duet, there is nothing to touch it on the market ( it's just so darned complicated for novices like me ) Thanks again Ian, I do appreciate everything you've done for me, you really are a star !; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Bigbox1" ; set printer name ; Network M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S0 ; physical drive 2 goes backwards M569 P3 S1 ; physical drive 3 goes forwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X160.00 Y360.00 Z400.00 E304.00 ; set steps per mm M566 X480.00 Y480.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min) M203 X9000.00 Y9000.00 Z360.00 E1500.00 ; set maximum speeds (mm/min) M201 X750.00 Y750.00 Z100.00 E5000.00 ; set accelerations (mm/s^2) M906 X1300 Y1300 Z1300 E800 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X300 Y200 Z200 S0 ; set axis maxima ; Endstops M574 X1 Y1 S1 ; set active high endstops M574 Z1 S2 ; set endstops controlled by probe ; Z-Probe M558 P1 H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds G31 P500 X0 Y25 Z2.5 ; set Z probe trigger value, offset and trigger height M557 X15:215 Y15:195 S20 ; define mesh grid ; Heaters M305 P0 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M305 P1 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 1 M143 H1 S320 ; set temperature limit for heater 1 to 320C ; Fans M106 P0 S0 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P1 S1 I0 F500 H1 T45 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; 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 0CJust a point, I know that there are a few commands that have to be either before or after others. Am I ok regarding this respect, is everything in the right order?
Thanks again
Keith -
@Kayjay looks mostly okay, and in the correct order. You have chosen the default thermistor settings, and a couple of other minor differences. Compare it to the config in your post earlier, here: https://forum.duet3d.com/post/171309
Ian
-
@droftarts
Ah yes, I forgot to set the PT100 didn't I. My Usual dummy self !Here are the M122 results :
10:47:25 AMM122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet Ethernet 1.02 or later Board ID: 08DDM-9FAMU-JW4S4-6JKD4-3SJ6M-92Y7V Used output buffers: 3 of 24 (15 max) === RTOS === Static ram: 25712 Dynamic ram: 92764 of which 0 recycled Exception stack ram used: 272 Never used ram: 12324 Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3736) IDLE(ready,160) Owned mutexes: === Platform === Last reset 00:43:40 ago, cause: software Last software reset at 2020-08-15 10:03, reason: User, spinning module GCodes, available RAM 12324 bytes (slot 1) 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: 0.0ms, max retries 0 MCU temperature: min 44.2, current 44.5, max 44.6 Supply voltage: min 24.5, current 24.6, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes 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: 2020-08-15 10:47:18 Cache data hit count 4294967295 Slowest loop: 1.11ms; fastest: 0.07ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Move === Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms 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: 4.49ms; fastest: 0.06ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 Interface state 5, link 100Mbps full duplex 10:47:17 AMM122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet Ethernet 1.02 or later Board ID: 08DDM-9FAMU-JW4S4-6JKD4-3SJ6M-92Y7V Used output buffers: 3 of 24 (15 max) === RTOS === Static ram: 25712 Dynamic ram: 92764 of which 0 recycled Exception stack ram used: 272 Never used ram: 12324 Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3736) IDLE(ready,160) Owned mutexes: ToolList(NETWORK) === Platform === Last reset 00:43:32 ago, cause: software Last software reset at 2020-08-15 10:03, reason: User, spinning module GCodes, available RAM 12324 bytes (slot 1) 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: 0.0ms, max retries 0 MCU temperature: min 44.2, current 44.4, max 44.6 Supply voltage: min 24.5, current 24.6, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes 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: 2020-08-15 10:47:11 Cache data hit count 4294967295 Slowest loop: 1.11ms; fastest: 0.07ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Move === Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms 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: 4.48ms; fastest: 0.06ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 Interface state 5, link 100Mbps full duplex 10:46:18 AMM122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet Ethernet 1.02 or later Board ID: 08DDM-9FAMU-JW4S4-6JKD4-3SJ6M-92Y7V Used output buffers: 3 of 24 (15 max) === RTOS === Static ram: 25712 Dynamic ram: 92764 of which 0 recycled Exception stack ram used: 272 Never used ram: 12324 Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3736) IDLE(ready,160) Owned mutexes: ToolList(NETWORK) === Platform === Last reset 00:42:33 ago, cause: software Last software reset at 2020-08-15 10:03, reason: User, spinning module GCodes, available RAM 12324 bytes (slot 1) 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: 0.0ms, max retries 0 MCU temperature: min 44.3, current 44.5, max 44.6 Supply voltage: min 24.5, current 24.6, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes 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: 2020-08-15 10:46:12 Cache data hit count 4294967295 Slowest loop: 1.11ms; fastest: 0.07ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Move === Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms 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: 4.47ms; fastest: 0.06ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 Interface state 5, link 100Mbps full duplex 10:46:13 AMM122 10:46:00 AMM122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet Ethernet 1.02 or later Board ID: 08DDM-9FAMU-JW4S4-6JKD4-3SJ6M-92Y7V Used output buffers: 1 of 24 (10 max) === RTOS === Static ram: 25712 Dynamic ram: 92764 of which 0 recycled Exception stack ram used: 272 Never used ram: 12324 Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3736) IDLE(ready,160) Owned mutexes: === Platform === Last reset 00:42:15 ago, cause: software Last software reset at 2020-08-15 10:03, reason: User, spinning module GCodes, available RAM 12324 bytes (slot 1) 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: 0.0ms, max retries 0 MCU temperature: min 42.8, current 44.4, max 44.7 Supply voltage: min 24.5, current 24.6, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes 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: 2020-08-15 10:45:53 Cache data hit count 4294967295 Slowest loop: 3.61ms; fastest: 0.06ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Move === Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms 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: 9.40ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 Interface state 5, link 100Mbps full duplex 10:04:02 AMConnection established! 10:03:55 AMDisconnected. 9:58:19 AMConnection established! 9:58:19 AMPage Load complete! -
These are the results for the M98
11:12:17 AMM98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is disabled -
@Kayjay I’d say have a go with the Z movement tests, once you have your config.g sorted.
You can tell from the M122 response if the Z axis has stalled. Try moving Z, and if it doesn’t, send M122 and look at this line in the response:
Driver 2: standstill, SG min/max not availableThe bit after SG min/max will have numbers. If the max is 1023, the axis has tried to move, but stalled. It could be that the Z axis is binding, particularly as you have two motors on Z.
Ian
-
I sorted the config.g, the PT100 wasn't configured to use the daughterboard, just a slip of the mind .
This is the result of all the drivers from M122. I tried to move z then did the M122
Driver 0: standstill, SG min/max 0/234 Driver 1: standstill, SG min/max 0/295 Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max not available Driver 4: standstill, SG min/max not availableI assume this indicates that Z isn't trying to move. I can't get it to move using any Go or G1 command but it will move in homeall and homez.
I have made a video of Homeall.z which shows x and y homing, then x moving to 150 and y to 100 which is the centre of the bed. After that nothing happens, as though G30 is being ignored completely.
I'm busy trying to upload the video to youtube but at the moment I'm not able to, I do have an account but I have never uploaded anything to my account so it's a matter of another learning curve.
I am getting very close to giving in as nothing seems to works. I'd even send it to Josh at E3D but they no longer handle the Bigbox so I don't think they'll do a repair.To be honest I'd be happy to pay anyone who can make this darned thing work otherwise its the Anet A8 Plus. I am getting very frustrated even with the great help you've all given me. I feel there is an electronic problem rather than software. I'm just at a loss, you guys have been so amazing and helpful, your hints and tips have been amazing too but I just don't know what to do any more. For one I'm a novice so to speak, I don't understand half of the speak, I'd just be happy with a working printer that I can throw a sliced prog in and let it print me a nice result.
-
It sounds like the Z axis isn't stalling, so that's a good sign.\
The reason it won't move the Z axis with G0 or G1 is probably because it hasn't been homed yet, So unless you've sent a G92 Z10 to force the Z axis into a homed position, it won't move.
@Phaedrux said in Unable to home z axis:
I think this may be an issue of Z axis steps per mm being incorrect.
The marlin config for the Bigbox pro hydrid is 1600 steps per mm on Z. You've got it configured as 400.
#define DEFAULT_AXIS_STEPS_PER_UNIT {160,180,1600,417.5} // default steps per unit for Titan BigBoxSo try changing your M92 Z400 to M92 Z1600 and try to homeall again.
-
@Kayjay Have you been able to post the video? Also, I’ve sent you a private message. Click the speech balloon icon at the top of the page to see messages.
Ian
-
@Phaedrux
Well, there is a small improvement, the bed now rises in the steps I have set in homeall, I have to keep homing but by hte time it reaches the top it crashes or rather would if I don't do an emergency stop. I've also tried holding my finger under the probe whilst it is homing , the LED lights but it doesn't stop, neither does it stop as it lights just before I hit emergency stop.; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Sat Aug 15 2020 09:44:17 GMT+0100 (British Summer Time) G91 ; relative positioning G1 H2 Z-25 F6000 ; lift Z relative to current position G1 H1 X-305 Y-205 F1800 ; move quickly to X and Y axis endstops and stop there (first pass) G1 H2 X5 Y5 F6000 ; go back a few mm G1 H1 X-305 Y-205 F360 ; move slowly to X and Y axis endstops once more (second pass) G90 ; absolute positioning G1 X150 Y100 F6000 ; go to first bed probe point and home Z G30 ; home Z by probing the bed ; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 Z5 F100 ; lift Z relative to current position ;G90 ; absolute positioningThe Z-25 setting is temporary to enable a quicker bed rise so I don't have to hit homeall a hundred and umpteen times. Obviously I stop it crashing before it reaches it's limit
