Topics created by bast

@droftarts said in Accelerometer on toolboard 1.3 : positioning:

I have updated the documentation page using images from the pdf kindly supplied by @Nuramori. Unfortunately I can't upload pdfs to the wiki software, so I have left the original link in.

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_Accelerometer#orientation

Ian

nice documentation update for orientation toolboard !
thanks a lot @droftarts !
little pics of my config on a RR-Vcore 500 on duet 5+mini with toolboard (Ir sensor on toolboard)
337073719_584521030285760_651337798945124974_n.jpg 336799261_753810036251893_6380632004580747668_n.jpg

Perhaps to ensure that everything is now in the right place for the next update, you may wish to upload the 3.4.5 zip file once more to the system tab.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.5/Duet2and3Firmware-3.4.5.zip

@droftarts
it s too small for a photo 🙂

@bast Looking at the external driver datasheet https://www.omc-stepperonline.com/download/CL57T_V4.0.pdf, your M569 timings for the external drivers seem okay. Do you have the enable wires connected? It says it has a 300 millisecond enable time. It could be, if you have the enable connected, that the drives are not having long enough to enable before the steps are sent. The datasheet says:

ENA must be ahead of DIR by at least 200ms [says 300ms on diagram]. Usually, ENA+ and ENA- are NC (not connected).

With ENA+ and ENA- not connected, the drives are enabled all the time, as soon as they have power.

Instantaneous speed (M566 Z30), max speed (M203 Z300), acceleration (M201) seem reasonable for the steps per mm (M92 Z320). What are the motors driving, belts or ballscrews? Is the bed particularly heavy? Are you using a motor brake (I can't see it configured in the config.g)? If it is linked to the enable signal on the external driver, perhaps it is not releasing quickly enough.

Ian

@bast use the trigger value and compare against the P value you specified in G31

I tested all the boards independently
I have toolboard 0 (adress20) which creates a conflict for me in the general can bus
I am reconfiguring a toolboard to replace it
thank you

@Phaedrux and @caviara
it s ok now , i gone try IR sensor
thanks a lot

OK you awsome
My M140 H0 was after M143 so now it would be good

M143 H0
Heater 0 monitor 0 uses sensor 0 to generate a heater fault if the reading exceeds 180.0°C
Heater 0 monitor 1 is disabled
Heater 0 monitor 2 is disabled

thanks a lot guys 😉