Posts made by CEsther

Additional Note: I went thru the RepRap Firmware configuration and did not see this option.

I am currently running a Duet Wifi with an Ethernet Board with Firmware 1.18 to 2.02 RTOS (2018 12-24b1), Web Interface is 1.22.5. I was just doing some research on my E3DV6 hot end and it led me to a video by some guy name Thomas Sanladerer showing how to look at and modify the firmware for a new printer. In this video he stated that something very important was the "heater sanity check" which monitors the heaters and temp probes to look at a possible failure and to shut it down in the event that it thinks it has failed. He used the Audrino software, which I downloaded and could not get it to read the Duet Firmware. My question is.......Does the Firmware 2.02 RTOS (2018 12-24b) perform this sanity check? If not, what does it do to prevent a possible overheating/fire condition?

Any help is greatly appreciated.

I am printing a part right now, it will be done by lunch. After that I may try the S2 command without the M564. I'll try to post my results. Again, right now all is working great. Would still like to learn what does what and so forth.

Thanks everyone for your help.

Originally this machine homed x and y first, however, it was always my opinion that Z should be homed first as we have a home switch. Thus it drops the bed down out of the way. With the new firmware, I was excited to see that I could not home anything until Z was homed.

So now my question is......Should I have used an S2 in all of these files instead of the M564 H0? Should I do both? Or don't worry about it since it works? In trouble shooting I have learned to make only one change at a time. It takes a while longer, but at least I know and understand the effects of each action.

homey.g

;
G91
G1 Z0.5 F400
G1 Y-500 F3000 S1
G1 Y4 F600
G1 Y-10 S1
G1 Z-0.5 F400
G90

homex.g

;
G91
G1 Z0.5 F400
G1 X-500 F3000 S1
G1 X4 F600
G1 X-10 S1
G1 Z-0.5 F400
G90

homez.g

;
G91
G1 Z400 F500 S1
G1 Z-4 F200
G1 Z10 S1
G90

Ok, first off. The M564 H0 WORKED!!!!!! However here are the homing files for review.

Here is homeall.g

M561
G91
G1 Z0.5 F400
; home Z first
G1 Z400 F500 S1
G1 Z-4 F200
G1 Z10 S1

; then home Y
G1 Y-500 F3000 S1
G1 Y4 F600
G1 Y-10 S1

; then home X
G1 X-500 F3000 S1
G1 X4 F600
G1 X-10 S1
G90

I'll try that after the print is done. What I don't understand is that my home routine starts with the z axis, then y, then x. This is the order that individual home routines work. I would have thought that if the homeall.g routing contained that same code it would work.

Thanks for your help. I'll post my results.

I actually tried the M667 S1. This is what I started out with. I read the post where it said to look at the update notes, so I did and that is where I got the M669 K1. I thought this was done on a much earlier update. Any way when using the M667 S1 I did the home x, y, and z work as they should individually, however the homeall.g does not function and the G28 in the gcode file still won't work. I am running a print right now that has the g28 command deleted. It is about a 4 hour print. I am going to try the M564 H0 command in the config.g file when I am done with this print.

Ok, I may have solved my own problem. I am posting what the FAQ says so someone doesn't have to go look. This may just fix it.

FAQ States

"Recent firmware versions do not allow axes to be moved before they have been homed. The only movements allows are homing moves (G1 moves with S1 or H1 parameter) and individual motor moves (G1 moves with S2 or H2 parameter). So any Z movements that your homing files make before Z is homed should use the S2 parameter. Alternatively, add M564 H0 to config.g to allow axis movement before homing."

Not sure how I missed the post with this in it.

I get a G0/G1: insufficient axes homed. I just saw another post that says to go to the FAQ on Wiki so I am gonna look there.

Just upgraded from 1.18 to 2.02 RTOS (2018 12-24b1), Web Interface is 1.22.5 and the Homeall.g will not function. All individual home buttons/routines work. I have modified the home routine to home z, then y, then x axis as this is the only way it will home individually. I read the update notes and to my understanding you have to home z first. Further reading of the update notes state that the M667 S1 no longer works and that we are to use the M669 K1 code for a CoreXY machine. I have done this and when I do, the homeall.g routine still doesn't work, and the individual X and Y home buttons now do not home correct. If I remember correctly it swaps end stops and/or moves the gantry in a diagonal motion. Everything else seems to work. When I try to run a print, it will go to the point where the gcode runs a G28 (home all). Then it just stops. I can ignore the G28 or take it out and home it prior to starting and the print seems to run flawless. I have gone thru all of the upgrade notes and cannot find anything else to do. I not be putting in all of the parameters for the M669 and that may be the issue, but all of the instructions are too vague for me. Any help on this issue? Please.

DC42

I am still waiting on a reply from Fusion3. In the meantime I have tried to do another print. Again, I had the same software reset. Through all of this, the only thing that has not been replaced has been the Power Supply. Is it possible to get the error that I am getting "software reset" due to a power supply being undersized. Again, I am just throwing darts trying to see what I might hit.

They are looking into upgrading the firmware.

DC42....Thanks. I have told Fusion exactly what you have stated about the firmware and they state that they can't go to the latest firmware. They have given me some stupid reason for not doing it. So my question is this.......

If they send me their firmware, would it be possible for me to basically make the changes that they need to the latest firmware and then debug myself. I can't very well ignore what they have changed and just update the firmware as I am guessing it would't work.

Thanks again for your help.

Well, it happened again. They sent me a new board. This one is a Duet 2 V 1.04a. This was a different file than before and a much shorter print. Below is the M115 and M122 code info. Does this reveal anything different than before? Either being the same info on a different board or other. Any info or help is greatly appreciated.

7:16:53 AMM115
FIRMWARE_NAME: RepRapFirmware for Duet Ethernet FIRMWARE_VERSION: Fusionware 1.18.1 RC1 ELECTRONICS: Duet Ethernet 1.0 FIRMWARE_DATE: 2017-05-15
7:16:46 AMConnection established!
7:16:41 AMPage Load complete!

6:08:50 AMM122
=== Diagnostics ===
Used output buffers: 2 of 32 (8 max)
=== Platform ===
Static ram used: 25020
Dynamic ram used: 89780
Recycled dynamic ram: 3984
Stack ram used: 1104 current, 3824 maximum
Never used ram: 8464
Last reset 08:36:44 ago, cause: software
Last software reset code 0x5003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0040080f, BFAR 0xe000ed38, SP 0xffffffff
Spinning module during software reset: GCodes, available RAM 4208 bytes (slot 0)
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 32.4, current 35.5, max 39.3
Supply voltage: min 23.5, current 23.6, max 23.7, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: stalled standstill
Driver 3: stalled standstill
Driver 4: standstill
Date/time: 2019-01-23 06:08:50
Slowest main loop (seconds): 0.003906; fastest: 0.000000
=== Move ===
MaxReps: 0, StepErrors: 0, 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
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
=== 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
Code queue is empty.
=== Network ===
State: 4
=== Webserver ===
HTTP sessions: 1 of 8
FTP connections: 0, state 0
Telnet connections: 0, state 0

ronnien59....I am curious if the upgrade solved your problem or if you had to do something else. I am having the same issue and I am running the older firmware 1.18. Please let me know.

DC42,

I need to ask one more question. I have a DuetWifi V1.02 in another printer I have a Duet2 V1.03. Which is the latest version? I am trying to do research to assist in solving this issue. I would like to use the latest board I would think.

DC42,

Where can I get a copy of this new firmware. I am afraid that I am about to go down the same path that I have gone down with them for months. I don't think it is a hardware issue myself. I think it is firmware or some sort of software issue.

DC42,

Thanks! I will pass this on. This has been an ongoing issue for about 10 months. My first printer had a Duet board that did not have the built in ethernet. They upgraded it to one like this. After about 7 months of experimenting, sending new boards, new screens, adding ground wiring, etc. We both decided it was time for a new printer. In November, I got a new printer and at first all worked great. Then about two weeks ago, I had a small print fail. Then over the weekend, I had two large prints fail. The original printer and board gave us a power up reset, even though it never went down. This one gives us a software reset. They are sending me another board with a different firmware, the problem is I don't think they know what is wrong and are just hoping this fixes it. I sent them your text to see what they say.