Topics created by likevvii

@likevvii said in Duet3mini driver gets HOT after a few seconds of movement:

Maybe I damaged the driver by having the wire issue.

I'm thinking so, but will check with DC42.

@dc42 said in Induce Control delay and latency?:

@likevvii, adding latency is not currently supported in the firmware. It would be possible to support in principle, which the proviso that for each board in the CAN-connected system, all drivers connected to that board use the same latency.

As @o_lampe says, this will only work well if the added latency for the servo drivers is fixed.

Thank you for the explanation. I do understand the latency is technically not fixed and can vary from maybe 1~5ms. But at the least, I was hoping I could be somewhere at the middle of the standard deviation.

This seems backwards but, Are there some multiplexers out there that take in step/dir signals and then converts it into the things that communicate over ethernet cables to sync everything up? Of course, the drivers will all have to be compatible with the protocol.

"I am guessing 1.3V is still too high for it to be considered as low?"
@likevvii

This is true, I went through a process to hand select a protection diode out of a set for my induction probe to get the off down to 1.1V for a constant responsive low reading (Duet Wifi V1.2)

@Phaedrux

I don't fully recall the exact values, but I did some math when doing a simultaneous (~150mm/s) X and Y move paired with extruder working and mesh bed leveling + sometimes Z hop it would pass 85KHz step rate (I am using duet wifi 2) and would get some stutters.

So I thought getting Z microstepping to as low as possible would be a good idea to help out with the reducing step commands since my mechanical resolution was so good anyways.

I would also love to double my X and Y microstepping rates too. Just not enough commands to keep up sadly!

Thanks for pointing this out.
I am using 5 phase stepper motors. They have a 1000step / rev.

Good catch on the jerk value. I prints better now. But I also noticed I had hiccups after running M122 so I need to reduce my step rate 😞

@likevvii said in Unable to get the Z probe to read correctly. Stuck at "0":

It is possible to reduce motor current during Z probe ONLY when it is going down and normal power when it is moving up?

Not during a G30 currently as far as I know.

Thanks.
Worked right away!

How do I mark this post as solved?

@likevvii said in Duet Wifi 2 - DC air pump / berd air:

what you mean by RRF3

what would version 3.x of the RepRapFirmware, you're currently on 2.04RC1. The last version of 2.x is 2.05.1, then the next step is 3.x.

@likevvii said in Duet Wifi 2 - DC air pump / berd air:

Is it safe for me to just use the second E heater port?

with the addittion of the diode, yes.

As you suggest, NPN types would be more suitable. This PNP switches might work if you connect a load resistor of about 330 ohms between output and ground. If that doesn't work, then a higher value load resistor (e.g. 10K) followed by a 2N7000 mosfet would work.

Many thanks! 🙂

Here are the limited parameters that M500 stores.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M500_Store_parameters

It's only intended to be used for things that are computed or measured by the firmware, not to save arbitrary gcode values.

Just directly edit config.g

@projectR3D said in Too much part cooling? PLA:

Anything above that causes issues that present similar to pressure advance tuning issues or z axis issues.

Can you be more specific?

I will test minimising fan speed. But can't get on that for a few days.