Topics created by Eduma

Thanks for testing. It would then appear that it's not a hardware issue at all.

@Eduma said in Duex2 Enstops:

Am I correct that in firmware 2.x you can not remap a home sensor to a different axis?

Kind of, but I don't think it affects their usage as triggers.

Using M584 to map drivers to axes does not affect endstop inputs. In RRF2, endstop inputs XYZ are pre-allocated, after that they are allocated in the order in which axes are created. So if you create just one extra axes (e.g. U), it will use the E0 endstop input. If more than one axis is created in a single M584 command, endstop inputs are allocated to the new axes in axis creation order (see previous item). For example, M584 C5 U6 would allocate endstop input E0 to the U axis and E1 to the C axis.

RRF3 does have more flexibility in how things are mapped, so if you wanted to test, you could create a very basic config using the online configurator for RRF3, update your firmware to 3.0 and then 3.1.1 and test your triggers. If it works, then you could migrate over, if it doesn't work, then you can reflash to 2.05.1 and use your previous config if you wish.

I'll ask DC42 again about the Duex2 endstops being used as triggers.

@T3P3Tony sorry for the delay in getting back to you but i was able to confirm that this issue is filament slip. If my guide to at the entry of the filament monitor is at too much of angle I see slip. If I maintain a straight feed preliminary testing looks like i see accurate readings.

@dc42

P255 should do the trick

I have just measured one:

Threaded bush diameter 6.2mm
Max panel thickness 3.8mm (if you use the nut but leave off the 2 washers), or 5.2mm (if you don't use the nut but screw the bush into a 3D printed part)
Cable length to Duet about 130mm

Thank you all for the response.

No need to feel dumb, there are too many G- and M-Codes to remember them all.

Thank you Danal, the macro approach my work.

Please look at my post linked below to see if this helps you out as well. Thanks

https://forum.duet3d.com/topic/18261/bltouch-v3-1-toolboard-resolution

I'm running version 3. A previous unit I built had no issues, but I'm guessing I got lucky with a BL touch that would work at a lower voltage.

I'll have to add some terminal blocks and run it off the BL touch. Might not be a bad idea to update the BL touch section of the wiki, to warn about expansion IO not supplying 5V if connected to external power supply.

There are lots of equivalent parts for that connector. Here's one: https://uk.farnell.com/multicomp/mc-254-50-00-st-dip/connector-header-50pos-2row-2/dp/2843537. And here's an example of the mating ribbon cable connector: https://uk.farnell.com/3m/d89150-0131hk/connector-rcpt-50pos-2row-2-54mm/dp/2672519.

Firmware 2.01 should be able to access the second SD card. To access it you need to mount it, either explicitly by sending M21 P1 or implicitly by changing to the second SD card in the DWC or PanelDue file list page.

Bad colours on a 7 inch non-integrated PanelDue usually mean that the firmware for a 5" screen or an integrated 7 inch screen has been installed. Recent versions of PanelDue firmware have red, green and blue colour gradients on the Setup page, to help you check that the colours are correct.

I tried that yesterday with no luck

Are you using the Pi to connect to the Duet while its in WAP mode? I've seen a lot of people using the PI zero, but most are connecting to and existing network.

Unfortunately the wyze cam does not allow a static IP. I was looking at some third party firmware for the wyze cam but no luck.

I will look into the Yawcam software.