Hello all, I just wanted to let any who is interested know that Autodesk has updated their post processor, available to download on their site, to include the G2/G3 commands.

Not related to 3D printers but I regularly heat large metal tubes at work and use many heaters. Up to 40 on a system and each one controlled independently. Each heater does have an effect on the others but usually it is minimal.

It might be a good idea to do that but it may also complicate the slicing setup.

I’m not sure if that was helpful or not.

@Phaedrux well I was able to get the bed cleared off and run my G32 (bed.g) which I added a link to my macro and after the macro I added the M500 P31 in the bed.g and that saved the offsets correctly. So that gets me a work around.

Luckily you are using thermocouples. If you wire them all together the actual voltage signal will average out. So if you just take all the +ve leads and connect together on the same +ve terminal and take the -ve leads to the same -terminal it will average out the three sensor readings. Its a pretty old school trick.

good luck.

I think I just replied to your other post. But you can use the outputs, basically they are a switch so just ware an input and a ground to the alarm terminals on the driver. Then you need to setup a trigger (M581) for those inputs along with the action to take. You can run a macro or a pause or an estop.

@educatingsavvas
I just wired up one of these and it works too.

One thing to note is that using less than 3000hz seems to result in the generation of a 0-10v signal that the VFD sees as oscillating and then it changes frequencies a lot. It ramps up and down 10’s of hertz.

It will likely be in this part of your config.g file.

G31 P25 X-31 Y0 Z0.6                               ; set Z probe trigger value, offset and trigger height
M557 X20:215 Y20:215 S64                           ; define mesh grid

Likely the X-31 is no longer accurate. With the probably area being X20-215 and a -31 offset it could still probe 11mm off the bed (I think). But those are the parameters that you need to adjust to get the probe back on the bed.

what you are looking for is not PWM (pulse width modulation) you want FM (Frequency Modulation). I would suspect that the duet is not setup to use FM as it is not mentioned anywhere in the documentation. As Bearer said you can change the base frequency of the PWM and if you set the PWM to 50% and then changed the base frequency it might work to act like frequency modulation, but i doubt it. Give it a try, it can't hurt.

I do believe you can buy conversion hardware that will take a PWM signal and convert it to an FM signal.

@Phaedrux maybe he has the same issue I had and it is interference with his stepper motors. It possible it was working for testing then he tried to print and now it doesn’t work? We can only guess.

@mrenz999 Try sending an M18 E0 command before you attempt to use the probe.

@bruce

I have managed to fix the G2-G3 issue with this post (or at least is was an issue for me)

there is a piece missing after allowedHelicalMove = true; which should be allowedCircularPlanes = undefined;

Then under // circular output all the i, j, and k variables are forced false that needs to be replaced with
// circular output
false
falsevar iOutput = createReferenceVariable({ prefix: "I"}, xyzFormat);
false
falsevar jOutput = createReferenceVariable({ prefix: "J"}, xyzFormat);
false
falsevar kOutput = createReferenceVariable({ prefix: "K"}, xyzFormat);
false
false

and that should give you G2 and G3 movements. I haven't tested the Gcode yet but at least circular movements are arcs and not thousands of segments.

@droftarts

Thanks. I didn’t see that but I was able to get things working. I rolled it back to reprap 2 as I just don’t have the time to change the names of the pins and stuff to do the upgrade to reprap3. I’ll take a look at that post as maybe that information is there already.

Thanks.

@elmoret I have several legitimate duet boards and choose to support Duet whenever possible. However, when I bought these printers I could tell them to swap out their parts. The software side is still reprap and any issues from the software update I would hope could be resolved here.

It turns out I popped off the wifi antenna cable when I cloned the SD card at some point after I ran the updates. I was able to get things working all on my own which is why I haven’t been back here to respond.

Thank you for your helpful reply.

Hello everyone, I have a printer that is running reprap V2. something and I just tried to update the firmware to version 3.0 as per the documentation before trying to update it to the latest version 3.4. It appears to have updated just fine to version 3.0, but when I did the 3.4 update something didn't work and I can't access the DWC anymore and the panel due give a warning about the driver 9 having a short to ground.

I think the board is a custom clone of the duet 2 wifi, it is a Vivedino Troodon printer. Does anyone have any suggestion to try to roll back the firmware to a V3.0 or even older so I can have a functional printer again?

Thank you.

you may want to find the old post from the ulitmate reprap post that post processor lack the implementation of the G2 and G3 commands.

@mihai-zamfiraz I have a setup similar to what you are describing, I have a duet 2 wifi with the external closed loop drivers. Mine are all mounted in the box and I ran long cables for the encoders and the steppers. What you are suggesting would work fine I would think. The CAN should be suitable for long runs of cables and immune to signal noise. Be sure to use a shielded cable for the spindle power.

@chrishamm I will look into that. Thanks for the tip.

@dc42 it does get faster again when I reboot it. I just thought it was something to do with the duet software (I know nothing about RPI's) as it didn't become an issue until RRF3 ish.

@chrishamm Yeah, I thought that too but I have a dedicated 5V power supplies for both of them. One is using a 5amp and the other is a 12amp buck converter so I would think I have enough power I have also added cooling fans to the raspberry pi's to increase the cooling. They still get very sluggish after a few days of being powered up or after a long print

on this very topic, have you noticed that the RPI gets very sluggish after a few prints or after a few days of being powered up? I have two duet 3 running RPI's and both act the same way. It seems to have started with the RRF3 ish revisions.

Hello Everyone,

Thank you for your replies, based on what was said/suggested I tried a couple of things.

I looked back to the manual of the stepper driver and found that I can run the pulses at 2.5us so I made that change which should allow for upto 507mm/s, based on the math provided by alankilian. it does sound like the machine moves faster now at 300mm/s so maybe there is some issue where the pulses are a limiting factor and the display isn't showing that correctly. Even with that new pulse speed the G0 still maxes out at 300mm/s

Here is the relevant changes in the config.g

; External Drives
M569 P5 S0 R1 T2.5:2.5:5:7.5                     		; external drive 5 goes forwards requires an active high enable, 5us minimum step pulse, 2.5us minimum step interval, 5us DIR setup, and 7.5us hold time
M569 P6 S1 R1 T2.5:2.5:5:7.5                     		; external drive 6 goes forwards requires an active high enable, 5us minimum step pulse, 2.5us minimum step interval, 5us DIR setup, and 7.5us hold time
M569 P7 S1 R1 T2.5:2.5:5:7.5                     		; external drive 7 goes forwards requires an active high enable, 5us minimum step pulse, 2.5us minimum step interval, 5us DIR setup, and 7.5us hold time
M569 P8 S1 R1 T2.5:2.5:5:7.5                     		; external drive 8 goes forwards requires an active high enable, 5us minimum step pulse, 2.5us minimum step interval, 5us DIR setup, and 7.5us hold time
M569 P9 S1 R1 T2.5:2.5:5:7.5                    		; external drive 9 goes forward requires an active high enable, 5us minimum step pulse, 2.5us minimum step interval, 5us DIR setup, and 7.5us hold time

; Disable internal drives
;M569 P1 R-1									   	; disable physical drive
;M569 P2 R-1                                    	; disable physical drive 2
;M569 P3 R-1				                     	; disable physical drive 3
;M569 P4 R-1                                    	; disable physical drive 4
;M569 P5 R-1	                                 	; disable physical drive 5

; Map axis drives
M584 X7 Y5:6 Z8 A9                            		; set drive mapping
;M350 X64 Y64 Z16 E16 I0                        	; configure microstepping with interpolation

; Set drive speeds
M92 X394.09 Y394.09 Z1280.00 A420.00            	; set steps per mm
M566 X300.00 Y300.00 Z300.00 A120.00            	; set maximum instantaneous speed changes (mm/min)
M203 X24000.00 Y24000.00 Z3600.00 A1200.00        	; set maximum speeds (mm/min)
M201 X400.00 Y400.00 Z400.00 A250.00           	 	; set accelerations (mm/s^2)
M906 X800 Y800 Z800 A800 I30                   		; set motor currents (mA) and motor idle factor in per cent
;M84 S30         

I also did try changing the maximum speed to 19800 for x and Y and that also had no effect