Topics created by tfjield

@chickenwoman said in Using Input Shaping. Any suggestions or advice??:

@tfjield this is off topic but what wire did you use on your Modix and what length? I have a Big 60 and have tried several different types of wire and cant get it to work.

The first time I tried I used an old, unshielded network cable and it wouldn't recognize the accelerometer. Then I went with a USB cable.

I followed this guide:
https://forum.duet3d.com/topic/22878/software-package-3-3beta3-released/68?_=1624809172098

I purchased this USB cable from Amazon:
https://smile.amazon.com/dp/B014RWATK2

I left the cable at about 5 feet / 1.5 meters. There are two shields inside wrapped around two different pairs, and a shield around the whole thing. I attached all three shields together, and connected it to one of the ground points on the Duet boards. (I have the DueX5, so I used one of the grounds on one of the 5 endstop connectors.)

I use a PT100 daughterboard, and the daughterboard moves CS3 and CS4 from pins 7 and 9 to pins 3 and 1, respectively. So my CS connects to pin 1 and INT connects to pin 3.

EDIT: Here are some pics of my connection. I didn't have a dual inline plug that took crimp connections for the Duet side so I made one with the connectors that I had.

ee0ab1d7-ee9e-43a5-97dd-b0af4d850763-image.png
633244bf-8312-4683-bf66-d2669ced8806-image.png
7d83f86b-879a-4fdc-9c37-005c4229cd63-image.png

@jay_s_uk Ah, thank you! That makes sense now that I think about it... I never named the hotend fan "Tool Fan." It just seemed like the tool fan! lol

And thanks @fcwilt!

@tfjield

Here is a snippet of code showing how to have two sets of limits

if exists(param.E) ; E for expanded M208 Xmin:max Ymin:max ; values for expanded limits else M208 Xmin:max Ymin:max ; values for normal limits

Put code that into a .G file in the SYS folder and invoke it with M92 P"some_file_name.g" with or without the E parameter as desired.

Frederick

@tfjield I'm glad you got it working.

@tfjield only event messages and only the last one I think.
still a pain in the ....

@fcwilt Yup, I'm with you! It's just triage right now in the little time I have between prints! 😬

@resam Sorry for the late reply! I am no longer using RRF, so I can't test your update. Thank you for keeping me in mind, though!

@comediantf2
This is what I put in filament-error.g so that it would work with both 3.3 and 3.4+:

M25 ; first, pause the print as pre-RRF 3.3 did if {param.D == 0} ; now call the right pre-RRF 3.4 subroutines. M98 P"filament-error0.g" elif {param.D == 1} M98 P"filament-error1.g"

I have 8 machines all running on Duet2Wifi's with Panel Dues and identical settings. Two of them were plagued by this issues for the past year.

I was rebuilding one of them last week and decided to dig in an figure out what the issue was. I didnt think it was my router because all of them have reserved ip address. After hours of screwing with YAT and confirming that all the connections on the board were good, I cleared all the IP reservations and did a software update on my router. (EERO Mesh)

I was shocked to find that after the router firmware update, the issue was totally resolved on both the machines that had the issue. Not sure if it was the actual router firmware update, or the fact that I cleared the ip reservations and did new ones for each machine. Eitherway....the problem is gone.

@diamondback Looks like it! Thanks for making the connection. Yeah, I've never seen it during a real print, either. But yesterday I had booted the machine and I was changing the filament without using any macros and it did it then, too. When I get back home tonight I'll see if I can reproduce it without macros.