the other option that would really bite but is possible put the chamber heats on a sepeperate outboard controller and call it a day and delete all chamber crap from the configs i feel this is a key part to duet and am shocked this is still a loose end for such a key component i wish i would have know before hand and just built it this way instead perhaps......
but i was pretty sure this would have not been an issue i was wrong! rolling in my hand a T-100 1/2 din TCcontroller wishing i would have not bought the j type daughter board to keep the oem thermocouple then was the clear choice
there is allways more than one way to skin a cat! where to start is again the question...kick this one down the road abit longer or just replace it!
@heisl filamemt winding, eh? Yes, CNC mode is correct. Its really steps per unit. Those units can be whatever you want them to be. It's been a couple years since I used the 4th axis rotary on my mill so i will have to go back and see how i had the FW and gcode set up. I wasnt doing any simultaneous 4th axis, just using it as an indexer. What software, CAM are you using or are you going to piece the gcode together yourself?
@arnold_r_clark well said, even though I'm coming into this thread a few years later. I actually paid someone on Youtube to do some videos about Klipper when it was first coming out. But it was hard for them to make a video back then, and klipper was in it's infancy.
Anyways, if you read this, I appreciate your honesty and intelligence.
This I think is exactly what I am looking for, and it seems the SUPPORT_IOBITS flag is enabled for the Duet2 WIFI (i.e. DuetNG), so it should work out of the box. I'll will try it as soon as I have the opportunity.
@o_lampe i am drawing 6A on the chamber side at 120vac and have 6A remaining @ 120VAC the PS has 21A at 24V and i am using a 80w heater 7 1A fans at 24vdc and 3 nema 23 and one nema 17 ldo HT and 6HC lost of room left eh? yes i am Canadian!
These are incorrect. Only multiple extruder motors require multiple values. If the axis is made up of multiple motors, there only needs to be a single value for the axis, not for each motor. So remove the duplicate Y and Z values. I don't know if this would cause an issue like what you are seeing, but it isn't helping.
You can also send M98 P"config.g" to get a syntax check of your config.g file.
It may also help to see the results of M122 and M122 B# where # is the can address of your expansion boards.
@dc42 TY for your input and posting. Ive been away on business and travel so have just got back into the 3d shop to tinker here in the last week or so.
After spending approx $450 on "stuff" chasing down these gremlins [ toolboards / hotends / filaments / bondtech gears / thermistors / heaters et al ... Its come down to the Voron CW1 extruder IMHO.
I bolted up an LGX Lite and that with a some new heaters and therms - seemed to allow me to print ABS. Still no go with the eSUN ABS+ Im now thinking I got some mislabeled material from them. Atomic abs prints pretty well now.
I did have ot go to square one with this issue and essentially reset all things all over to day 1. It got that crazy. I nthe process I killed a 1LC, 2 thermistors and 1 cheapo heater. The heat actually may have been the impetus for most all mys initial issues from the onset. It wasn the problem but i think it kicked off a chain of events that threw sooo many things out of whack - its complicated.
Im now retuning the machine for the unique things about the new hotends and better heaters and therms as well as the LGX Lite.
That said, I did not write it and am not familiar with G Code other than what I have learned in problem solving/tweaking - so not even familiar with the concepts.
Does what you see in the existing macro explain the erratic behavior? That has been what is most confusing.
Will send this to the person I got it from and see what he has to say, and will try to look at the code, read the definitions for the switches and see if I can make some sense out the differences, then try it out myself. I use these machines for my work and have them both going constantly for the next few days - will try to make time to experiment after that.
Each time this happens can you gather a M122 report and share it here? That would be most helpful in isolating the issue. It would also help to share the config.g file set and sample gcode to help in duplicating it.
The only other thing I can suggest in the meantime is to try updating to 3.4.1 in case a fix in there helps.