RRF3 for Duet 3 uses the same chip, except that if you are using the SAME70XPLD board it may have the A revision of the SAME70 instead of the B revision that we use on Duet 3. So it's probably best to start from the Duet 3 build configuration.
Iep I understand that, and I did it, but because de dashboard buttons don’t indicate units, they just say "Z-5" for example, I made the mistake.
When that button was pressed, the Z axis moved exactly 5 cm which I confirmed as accurate with a tool (not 5mm as it should). But I was so angry and confused that I didn’t notice that the behaviour of the X and Y axis was different. For those the equivalent button only moved 5mm.
sadly no , not here yet. its all on reprap forum threads.
for SKR1.3 LCD, the SPI methods needs to be decided. I think you can run the LCD with software SPI. If not, then you need to jumper some of the EXP1/2 pins to get the right pins on the LCD headers.
Ethernet- P1.0 is not wired on the board anywhere. You need to solder a wire to that pin as well then jumper all the appropriate pins to a LAN8270 module.
if anyone has specific questions, post them here or on the thread in the Experimental firmware section on reprap.
@dc42 Yes I'm aware of the Van de Graff issues with belts - can cause all sorts of problems with model helicopters I believe because the tail rotor is often driven by a continuous belt and the resultant static plays havoc with the receiver. Also anti-static belts are often used in conveyor systems.
But I wonder if it's an issue with printers because generally the belts constantly change direction back and forth rather than always rotate in the same direction. It's an awfully long time since since schoolboy physics but if one reverses the direction of a Van de Graff generator, doesn't that reverse the polarity of the charge?
I don't know why it only occurs on a layer change. The DRV8825 datasheet says it requires 1.9us step pulse with, 1.9us setup pulse interval, and setup and hold times both 650ns. So you should use at least T1.9:1.9:0.65:0.65 in the M569 command. What's surprising is that it works at all if you don't extend the step pulse width.
In practice, the values you specify in the T parameter get rounded up to the nearest multiple of the step pulse clock interval, which on the Arduino/RADDS is 1.52us.
We are not selling the Maestro yet, you can only get it from M3D at present. But we're gradually updating the documentation to cover the Maestro in preparation for when we stock it. Meanwhile, the documentation for the Duet Ethernet is mostly the same as for the Maestro.
Thanks for your answer A little bit disappointed by your solution. I am sure you feel that is not a clean way to work. Please update me once you have developed a better way to stop a motor . I have used Minitronics for years and stopping a motor is clean. Anyway many thanks for the time spent to study my request
I think it's a pretty good idea. It can all be done in a macro.