Topics created by wayneosdias

@wayneosdias said in M118 send hex values:

3.6 beta works, 3.5.3 doesn't. M260.2 only works on beta FW?

It says in the Gcode entry “Supported from firmware version 3.6”.

Ian

@wayneosdias try adding these lines to Config/SAMMYC21.h:

#define VARIABLE_NUM_DRIVERS 0 #define TMC22xx_HAS_MUX 0 #define TMC22xx_USE_SLAVEADDR 1

@droftarts I'm not in a position to to check HW versions, but the bootloaders are indeed different, 2.8 vs 2.3. The first LC I got the beginning of the year and the 2nd this past week. Both LC are the same layout, but different versions as I recall the new LC mounting thru holes are enig plated and the older LC mounting thru holes are silk screen. Heres the M122 for both;

M122 B20 Diagnostics for board 20: Duet TOOL1LC rev 1.1 or later firmware version 3.5.3 (2024-09-17 14:35:31) Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1 M122 B21 Diagnostics for board 21: Duet TOOL1LC rev 1.1 or later firmware version 3.5.3 (2024-09-17 14:35:31) Bootloader ID: SAMC21 bootloader version 2.8 (2023-07-25)

@droftarts Understood, thanks again, prevented me from wasting a day chasing my tail 😉

@dc42
Thanks for letting me know I have 4 of these, but cant track one of them down. Of the 3 I have on hand 2/3 are oreinted incorrectly. 03/171 is correct.
2365c426-4a9a-4495-a162-7e99fa925d36-image.png

@wayneosdias I used the 0.9degree motors on my original 1HCL conversion for the toolchanger ad they did work well for my understanding at the time i was testing we subsequently did a lot more testing with a wider range of motors and found that 1.8 degree motors perform better especially with the "standard" 1000CPR encoders used on many motors. The 0.9degree motors i tested have 2500CPR encoders which helps with the positioning accuracy but not with the top speed.

If you're having issues with a reseller, or have had an exceptional experience with one, please feel free to send an email to sales@duet.com.

@wayneosdias

https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Expansion_1HCL#duet3d-magnetic-shaft-encoder

The cable length should not exceed 200mm.

@dc42
Thanks David. I'm rethinking the problem. The issue I was trying to solve was potential 'tool' offsets of different pnp nozzle tips during mid job tip changes. The CP40 tips themselves are all similar length but tip to nozzle mounting depth seems to vary a tip change to tip change. Vacuum threshold was going to be the probe feedback.

I not familiar w tool offsets in Openpnp, but that's not what is bothering me. The inconsistent mount depth of the CP40 is. I'm going back the Juki tips that I am familiar with them and they firmly mount at consistent lengths. Probing for the Juki tips isn't needed.

Thanks for the tip.

@jay_s_uk Thanks! Ill give it try

You can write a macro that will wait for some user action and then call it from the places where you want to stop halt your tested macro.

https://forum.duet3d.com/topic/12897/wait-for-input
https://docs.duet3d.com/User_manual/Reference/Gcodes

@Phaedrux
Yes it reports that without an SD and the old bad SD installed. I now have the machine up and running config wise, but dont have my homing sequences. I'm having issues connecting to dwc via ethernet to the controlling laptop. Otherwise ethernet is fine if connected directly connected to my home router. I have a wifi wifi ethernet bridge on order so I can use dwc with the 6HC in situ, otherwise I have to pull the board ot of the machine.

Once I get the ethernet working in situ I rework my homing processes. For PnP there is an axis interlock sequence for the drag pin feeder to prevent crashes.

In the end my issue was an inexplicable SD card failure. The card is the original that came w the 6HC. Thanks for everyone's help.

@wayneosdias if you already have closed loop motors with drivers that are running well then check out the Duet 3 6XD controller.

If you have existing motors and 1HCLs then a magnetic encoder based board to mount on the back of a Nema17 will be documented and released in around a month.

@dc42 wanted to follow-up on this issue to see if it will make 3.5? I couldn't find the issue on github.. Thanks

@dc42 Thanks again. I rolled back from 3.5 to 3.4.5 because of an issue with CNC mode within DWC; Jogging via DWC throws 'missing u parameter' error. Ill be happy to test 3.5 once that gets resolved

@MintyTrebor @jay_s_uk Thanks guys, FW/DWC v3.4.5 and Btncmd 0.10.15 has everything working in regards to no more DWC jog errors and Fxing btncmd 🙂

@MintyTrebor Perfect, I just exported locally to file, emailed to the device, imported on the device and now just a matter of scaling the controls. So much faster!

Now I have a saved copy for cache clears. Thanks a ton, a wonderful plugin you've got there!

@dc42
Ok got comms sorted. I got this initially
ec6c989e-6c7d-453e-839b-fb3f6f868106-image.png
Looks like the MISO line isnt pulled up locally on the the BTT board. I guess this makes sense as the board is meant to plug into 'step stick port' on a BTT driver board. In all the literature I read from BTT/Biqu makes no mention of pullups or active line jumpering. Any way pulled the MISO line up to 3V via 10k and now I get the following;
24ba278d-01bd-4ecb-87ed-d3a69fce39a0-image.png
DWC is also reporting semi resonable values so now just some tuning and firmer wiring to get the ball rolling. I have a Duet PT100 dtr board coming from filastruda and I dont think ill have it for a week. I also ordered an Adafruit MAX31865 bob that should be here tomorrow so Ill follow up this thread on how that gos.

Huge thanks for this Forum and support, the best 🙂

@dc42 said in Mini 5+ Failure Verification:

@wayneosdias you may also find the resetting the Wifi module (send M552 S-1 from USB or PanelDue) and then attempting to reconnect (M552 S1) restores the connection.

Turns out that the M552 sequence only works 50%. The only sure-fire way to get wifi back after failed reconnect is HW reset via by toggling the mini5 reset btn and toggling serial SW port connection in realterm as above.

I got the HW all sorted so moved up to RRF3.4.5 and the wifi seems to connect faster, more frequently after HW resets. Wifi is (and always was) stable once connected and running...

Thanks for the support

@droftarts said in Read Output pin state:

@wayneosdias Great, thanks.

For sending messages to USB, I guess M118 is going to be the most useful; I actually can't think of any other way to do it. If you wanted to send to DWC or PanelDue (but I don't think you do), use M291 instead.

Ian

You can also use 'echo' commands to retrieve information.