Posts made by baird1fa

Hello all. I’m working on a step controller using an FPGA to generate the pulses. The issue I’m having is calculating acceleration. The software I’m using makes it easy to use clock cycles of the 40MHz for the timing of the pulse and the frequency of the pulses. I can generate consistent pulses. Where I am struggling is to make controlled movement where the acceleration is consistent over a given number of pulses then stay constant, followed by a controlled deceleration.

If I need say 100 pulses to accelerate over say 0.5 seconds then that would be 2million clock cycles for acceleration. If I shorten the timing between pulses I don’t get smooth acceleration but rather slow acceleration with a sudden quick ramp at the end.

I can’t seem to find anything on google so I thought I would reach out here as I can only assume someone on here has solved this before.

Thanks.

Hello everyone. I’m wondering if any of you know what the wave form looks like for pulses being sent to steppers from the duet. Are the pulses just a fixed width (time) and there is a variable space between them. Or is it a 50% duty cycle and the frequency just varies?

Thank you.

Well I just figured it out, it is because in the CNC mode, the () brackets need to be encased with {} brackets. and that isn't needed in the 3D printer mode.

Hello,

I'm running a duet 2 wifi on a CNC router as well as a 3D printer. I was using the 3D printer to practice some meta commands for an attempt to make a spoil board facing program. I was able to get the program to work the way I want it on my 3D printer and one of the functions I'm using is the "floor" command to do some division for me where I just want the integer value. The floor command is not working when I try it on my CNC router. I'm running the same version of reprap on both units. 3.5.0 rc1. Does anyone else have this same issue?

Hello, I'm just looking through the GCode directory and I'm curious when you would use the M110 command. Can anyone provide an example of when to use that?

Thanks.

I realize this is an old thread but I'm curious if any head way has been made. I was thinking of trying to do something like this with the available touch probes. I have installed this probe on my machine and written a macro to find the XY coordinate of the corner of the work piece shown here: https://youtu.be/sxFnuANYMj0?si=RC7X4tuDhhlL49RF

With the Meta commands is it possible to make reprap generate an output file using the M28 command an the M114 command to store the point cloud data. I think all that would be needed is a set of commands like move so many mm in x then do a probe, on contact save that coordinate, lift up a bit, make another move and probe. Repeat that until there is some user defined stopping point, then move in the Y direction and move back to the X starting position and repeat for as many Y directions as needed.

Is this something that anyone has done, or is there an example of this with meta commmands. I'm very new to meta command and text based programming in general.

I found my issue, I was using a M21 where I should have had G21 to put the macro into mm.

Hello everyone, I've installed a 3D touch probe on my duet run CNC machine and I'm having an issue with the macro that I'm trying to use for probing the X and Y of the workpiece.

Here is the macro that I'm using and when I call it it runs fine, but I get an error that says:

M98 P"0:/macros/Touch Probe/3D Probe corner"
Error: SD card has open file(s)

;This will probe the bottom Left corner of the work piece
;First Probe the Z height
M21                                         ;This macro uses mm moves
M98 P"/macros/Touch Probe/z probe.g"        ;Run Z probe to find surface of material
G91                                         ;Set relative moves
G0 X-25                                     ;Move 25mm away from current position
G0 Z-8                                      ;Move down 8mm, 3mm below surface of work piece
G90                                         ;Set Absolute moves
M98 P"/macros/Touch Probe/X Probe.g"        ;Run X probe macro
G91                                         ;Set Relative moves
G0 Z10                                      ;Lift probe to clear work piece
G0 X20 Y-45                                 ;Move Probe to position for Y probe
G0 z-10                                     ;Move Probe into Z position for Y probe
G90                                         ;Set Absolute moves
M98 P"/macros/Touch Probe/Y Probe.g"        ;Run Y probe macro
G91                                         ;Relative move
G0 Z10                                      ;Lift probe to clear material
G90                                         ;Absolute move
G1 X0 Y0 F500                               ;Move to new soft home

I don't see any thing about this error in my google search or a search of the duet documentation site.

There are no errors is I run the files individually, only if I run the main macro.

@baird1fa I think I found the solution. It looks like the G20 and G21 are only changed temporarily when called inside of a macro and revert back once the macro is completed.

Hello everyone,

I'm looking for some help to extract the machine unit, set by G20 and G21, from the object model to use in macros.

Essentially I want to be able to run my machine in either mm or inches. The issue I have is when my Gcode sets the machine to inches all the macros and such don't work as they were written expecting the machine to be in inches.

I'd like to add a small script at the beginning of any macro that checks if the machine is in machine is in inches and if it is sets it G21 (mm) before proceeding and then sets it back to G20 if needed to continue running the job.

I want to do this because I have macros that will run during a job and they need to be in known unit.

I have found an object model (inputs[].distanceUnit) but I'm not sure how to utilize it.

Thank you.

@T3P3Tony The issue seems to have resolved itself. I connected it via USB and ran the M552 and M587 commands and could see that it was connected. I then powered it up normally and I would stay connected. I think there must have been an issue with too many devices connected to the wifi or an issue with IP address assignments. but it seems to be fine now.

Hello everyone.

I'm having an issue with my duet 2 board. I powered it down last week and when I went to power it up this weekend I cannot connect to it. I can see it connecting to my network then drop, then it connects again and drops. It just keeps cycling like this over and over again.

Does this mean that the board is fried or is there something I can do to fix it.

Thanks.

@droftarts Thank you for pointing me to that document. on a computer I can simply type cncrouter/ and it will find it.

Hello everyone. I'm using a duet 2 for a CNC router control board and I like to use either my phone or a tablet as a pendant control for it. The issue I'm having is finding the DWC interface with my phone or my tablets. I will have to check the network router for the IP it assigned then use that IP address in the browser on my phone or tablet. I don't have a network router that I can configure so I cannot assign the CNC a static IP. Google chrome and other PC web browsers seem to be able to search the local network by name to find the CNC, but I can't seem to get that to work on the phone or table.

@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.