Topics created by Qdeathstar

It is actually that low coming out of the duet.... It’s 4.3v right out the connector.. but i’m using the one that comes from filastruder sold with the panel due... it’s actually sort of dissapointing, i paid extra for it but it’s not keyed like the connectors are, it’s just pin header connections...

Forum search came up with a thread in the wishlist section.

If the rotors are exactly the same diameter and look identical then it might work.

Your resume.g file is out of date, you should add parameters X0 Y0 to both G1 R1 commands.

Yea, the temperature stayed pretty steady but I think the aero extruded just didn’t have enough torque to pull through .4mm of filament at 60mm/s

I tried 40 mm/s and it got 4-5 layers deep before failure so I lowered it again to 30 mm/s and it seems to print fine 8 hours in.

I didn’t hear any clicking from the extruded, so my guess is that the cog was just grinding on the filament slipping in it.

Unfortunately I’m out of white pla due to all the “testing” so I put the printer on pause while I wait for some more.

Thanks.

IMO that would be best implemented in Duet Web Control so that it is optional. So please raise it in the DWC Wishlist section. One thing that the firmware could do to help is to return a "Powered down" status to DWC so that it knows when the Duet doesn't have VIN power.

There was another thread about this, with corexy (with a bed moving in Z rather than an XY gantry moving in Z) you have to use phrases like increase Z or decrease Z rather than up or down, as it obviously moves down for +Z. There was talk of changing the babystepping icons on paneldue/DWC to show two lines with arrows opening them up, or closing them down which would be more intuitive irrespective of which kinematic scheme your printer uses.

I think it becomes even more common to mess it up if one printer is a corexy (with moving Z bed) and the rest are cartesian or delta.

Yes, using the S parameter in the M563 command.

EDIT: Upon reading the reviews it seems like despite being “rated” at 3v the ssr does not actually work at 3.3v.

Thanks for the tip about the diode, i think i will go that route for now as i have diodes on hand…

Not bad for being alone in the dark!

it now reads 3ohms, so i assume that means it’s not shorted (bypassed). With 5v power, i get correct readings from my thermistors.

edit:

I was able to figure out the fault. I am using db25 breakout boards and a db25 cable to route wiring to my hotends/extruders and i mounted the breakout boards to an aluminum tube. Although the breakout board had insulating foam on it, when i screwed the board to the aluminum the compression allowed the pins from the screw terminals to short out against the aluminum tubing. I got the motors moving now but haven’t tried the extenders or heaters yet… hopefully my dumbassery hasn’t messed anything else on the board up.

Thanks for building such a robust board. Short to 12v and she is still kicking 🙂

M558
Z Probe type 1, invert no, dive height 5.0mm, probe speed 120mm/min, travel speed 6000mm/min, recovery time 0.00 sec, used for axes:

9:17:41 PMG31 T1
Threshold 500, trigger height 21.82, offsets X0.0 Y0.0

So. I guess that solves that mystery.. I just checked my config.g file and sure enough 21.82 was set there instead of 1.82.. I didnt change it in between prints though (but maybe several prints before that)….. strange. Barring end-user incompetence, what could it be?!

Thanks, that works perfectly 😄

I don't know how the seemecnc carriages are constructed. On most delta printer designs i have seen, the carriages are screwed on to the sliders or trucks; so if the mounting holes on the carriages are a little oversized then you can rotate the carriages on the sliders or trucks a little before tightening the screws.

Perhaps you should ask for suggestions on the seemecnc forum.

I suggest you set up a macro that sets the bed temperature using M140, waits for it to stabilise using M116, then uses M300 and G4 commands to play a tune.

Thats not the only issue i had, after reading your comment DC42, (and haivng some other issues with prints) I discovered my steps/mm setting was off. I had it as 82.5 steps/mm instead of 80 steps/mm…

Originally, i had to fudge some of the H-values to get the circle to print correctly, now it looks great w/o the fudging! (even better). Ill edit in a picture once its completed.

Just posting this for posterity. Thanks for your help.

Thanks, colons always cause a stink 😄

almost time to print all the things!

Yes, it is working, but it seems in windows10 you need to run the SAM-BA 2.16 in compatability mode for windows 7.

Thank you for your quick response 😄

Thanks. I added the .md extension so that line wrap works, after I write that post. I've corrected the post.