Advanced Search

Yes, we have started to periodically remove dormant users. In most cases this is in no way a 'punitive' measure but became necessary because our database had grown to almost 25'000 users with more than half of them dormant or simply spam accounts.
Thank you.

Grotius wrote:

Snowgoeroe,

For my clarity.
You want pathpilot planner running in lcnc?

 

I think it might make the most sense to just port the >3 axis look ahead and blending over to the master LCNC branch.

I am not sure how their TP differs from ours otherwise, but I do know that theirs is pretty well tested and stable at this point.

Hello! I just re-signed up with the same email address and user name as previously. I was just wondering if users are removed periodically (I hadn't logged in for quite some time) or if there was some other reason my user was removed?

I just want to make sure I avoid whatever I did to make it happen so it doesn't happen again!

Thank you!
Evan

The Mesa hardware just doesn’t know about gcode. The computer interprets the gcode into step and direction timings and that is sent to the Mesa hardware. As for encoders, it does the counting and sends this information back to the computer. Any “closing of loops” is done by linuxcnc.

Whilst the Mesa hardware is quite complex (firmware wise) it requires a computer running Linuxcnc to instruct as to what to do.

Scott, thank you very much for pointing me in the right direction. I made changes to the configuration file "ec500-rt1052-DMA.txt" (JSON) according to your guidelines. I modified the parameters: "Step Length": 10, "Step Space": 5, but for now, I’m applying it only to one axis, X - JOINT_0, for testing purposes. I’m glad you helped me. Of course, in the *.ini file, I adjusted the SCALE parameter to match the settings from the HBS86H (microsteps) and to ensure movements are adapted to the lead of the ball screw. For now, everything is set up on the floor at home. In the future, I plan to install the Remora system on my new CNC machine, which I’ve been building for a long time (mainly because it’s very heavy, as it’s supposed to be, and requires a lot of work). I want it to be faster in its movements than my current one, which operates on a parallel port. If I have any questions, I’ll definitely ask you or others on the forum. It’s great that you’re all here and creating such amazing things. Take care for now.   Christopher - tu_koper.

The professors who know me and I think deal with these issues are at DIMEG.

You can go to them saying I was the one who reported them and ask

infodimeg.unical.it/associate_professor/card/152

infodimeg.unical.it/associate_professor/card/148

Change position must be 0 or negative value
XYZ change positions are all in machinecordinates G53:

g53 g0 Z #<_ini[change_position]z>

I am looking to use Axis 2.5.4 to digitize a paper plot or 2D template on a small gantry router.

Is there a simple to implement (my programming skills are weak) solution for writing current machine XY or XYZ position to a file? I am imaging a small pointed probe, aligning it visually, and a keystroke or GUI button to log data.

Thanks!

The 100 RPM plot looks as expected, (It would probably be less jagged if the
interpolated encoder position was used) but the 200 RPM plot is definitely broken.
 I don't understand the slow exponential velocity rise. Plotting the commanded velocity
would discriminate between LinuxCNC motion issues and hardware side issues.
Also , plotting the spindle position might help the diagnosis.


I would try doubling the acceleration to see if that helps (Increasing the acceleration
may _require_ using interpolated spindle position as the large Z position staircase
from having only 10 counts/turn will be less filtered.)

Hi, I am making progress I think. 
the error I have now is that when I try test a file with an M6 command it I get an error 
"Program exceeds machine maximum on axis Z" 
It doesn't matter what code I have in there or where the machine is zeroed 

I have found how to sets the locations of the probe but can't find the source for the probing travels (I think the gcode has a reference to the INI but I don't see anything there) 
perhaps this is an inch vs mm thing,again I think that is correct in the file but it is a bit confusing. 

thank you 

Luke 

Here are the requested outputs

100RPM
   


200RPM
   

try
DISPLAY = qtvcp qtdragon