Topics created by Agniusm

You should be able to come up with some sort of pattern using M106 and G4 commands. If you're using RRF3 you could even get fancy with some conditional gcode magic and loops.

Photos of your setup? Maybe we can spot something.

@fcwilt
Well, i dont know or have enough electronics knowledge to elaborate. It looks like it works, probe lights up and when metallic piece gets close, led turns off. Then testing with multimeter between ground and signal, beeps continuity as with mechanical switch but when connected to duet, it does nothing, except endstop led on duet dims when metallic object is in close proximity. I tried 5V and 12V and its the same(only LED shines brighter) so it shouldn't be lack of voltage.
P.S. I checked again with the multimeter, diode testing mode and with induction probe it reads 010 when its closed and 678 with metalic piece in close proximity while on mechanical switch it reads 001 closed an 1 open.
Resistance when its closed is 13ohm and when open is over 20Mohm

@Agniusm said in Another damaged board:

left

d'oh, so I clearly can't tell left from right .. somehow thought the all green led one was the defective. my bad!

Actually 6 conductors go to the head: 2 power wires and 2 twisted pairs for CAN. But I'm hoping we will be able to eliminate the second twisted pair in most situations.

@Agniusm said in Induction probe compensation:

After long time i came to the conclusion that my induction probe drifts and its caused by heat from the bed. Is there a way to compensate probe drift?

Yes. In RepRapFirmware 2 you can compensate for probe drift caused by changes in the reading of the bed temperature sensor. In RRF3 you can use any temperature sensor. See the C and S parameters of the G31 command.

Any chance you have the exact script your using or would be willing to walk me through the set up or even a prusasilcer config.ini file would be amazing.

@deckingman Thanks. Yes, i am familiar with what those command do and how they work.
Adding G90 at the begining of the move and G91 after seems to have solved the problem, at least on couple prints i did so far.
Thanks

@dc42 thanks. Good advice. Will report back when done

@agniusm said in Modded Ender 3 Conveyor concept:

is there a temperature tied to that drive? Like the extruder would not move until temp is high enough to extrude and if so could that be altered?

To drive an extruder:

You must select a tool that uses that extruder; If that tool has any associated heaters, you must heat them up to at least the minimum extrusion temperature OR enable cold extrusion.

@agniusm said in Short to ground.:

So i have changed to another motor which is 0.9A and all is working good.
I wast to add a blinking led and my led is connected to fan output. I tried infinite loop for macro:
M106 P2 S1;
G4 P600;
M106 P2 S0;
G4 P600;
M98 P/macros/BlinkLED.g
but it reports stack overflow. How can i get this working(or even make it more high tech and fade in and out) as it is a nice future after print is finished when you have so many printers? Thanks

This is off-topic for this thread. Please start a separate thread for new, unrelated questions.

I did the board this way.

https://www.thingiverse.com/thing:3197999

Nice work

@nophead yes bit the ripples were visible on clear too. Now they are gone.

A clue is that if PanelDue or DWC can't tell you the amount of filament required by the print, the file may be incomplete.

This used to be a particular problem with slic3r, because when writing the file it doesn't keep it open in exclusive mode, making it possible for you to upload it to the Duet before slic3r has finished writing it. I don't know if that has changed since I last used slic3r about 2 or 3 years ago.

All sorted now. Works great