- Configuring LinuxCNC
- Advanced Configuration
- Spindle Step/Dir servo ramp down before stop on M stop command.
Spindle Step/Dir servo ramp down before stop on M stop command.
It's a Ner-a-Car Model A. bodgesoc.blogspot.com/2014/04/1921-ner-car.htmlWhat Motorcycle is that?
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Anyway, it did its thing!
Joe
My CNC lathe cuts something for the first time...
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
- Posts: 18819
- Thank you received: 6320
Please Log in or Create an account to join the conversation.
That's a good start.
I was going to try to make the changes to configure the C axis, but I spent all day trying to get my 1921 motorcycle running.
Do you need the C axis urgently, or is it on the "nice to have this month" list?
So, how did the motorcycle go?? Read up a bit on what I could find on the internet - a colourful history that motorcycle has!
And, any revelations on my C axis? I am progressing well with the ATC - I think it should end up a neat implementation.
Just a lot of work ahead...
Joe
Please Log in or Create an account to join the conversation.
Unzip the files and drop them all in your existing config file.
You can then choose the new INI file from the LinuxCNC config picker.
Note that the new INI explicitly loads the new HAL. If you get this new config all working and want to go back to plain names then don't forget that you will have to change the HAL file name in the ini [HAL] section when you rename the HAL file.
You will also need to make the M100 and M101 files executable.
chmod +x M100
chmod +x M101
an m100 command should put the machine in C-axis mode, and an m101 should put it back in spindle mode.
Let me know how it goes, I don't expect it to work first time.
Please Log in or Create an account to join the conversation.
May take me a while to figure out what you said...
Thanks
Joe
Please Log in or Create an account to join the conversation.
First was [TRAJ] Cordinates = ZX without the C in the ini - fixed that ( XZC).
Placed the M100 / M101 files in CONFIG directory ( where should they go?) and made then executable ( permissions, etc)
Nexr error is an ini variable not found [JOINT_2]DIRSETUP...not found - see in attached report file.
I did dig in the HAL and ini files to see how that term is used in the other axes, to try understand where it is missing 'from' but did not succeed.
Still not smart enough with this to understand, but I do suspect that maybe the Stepgen allocation is not correct?
X uses Stepgen 00, Z uses Stepgen 01, Spindle uses Stepgen 02, but C_Axis uses Stepgen 01 as well..Should this be Stepgen 03 with the output somehow muxed to the spindle stepgen?
Joe
Please Log in or Create an account to join the conversation.
They should go in the config directory, as the INI is setup ( "[RS274NGC]USER_M_PATH = . " tells it to look there)Placed the M100 / M101 files in CONFIG directory ( where should they go?) and made then executable ( permissions, etc)
You should be able to use M100 and M101 in the MDI window without errors.
Sorry, I left in far too much when I copy-pasted. Delete the entire section "# Step Gen signals/setup" in the AXIS C section.Nexr error is an ini variable not found [JOINT_2]DIRSETUP...not found - see in attached report file.
I did dig in the HAL and ini files to see how that term is used in the other axes, to try understand where it is missing 'from' but did not succeed.
Normally you would be correct, but the config is using stepgen.02 for the spindle in velocity mode for spindle use, and also in velocity mode (controlled by a PID) in position mode.Still not smart enough with this to understand, but I do suspect that maybe the Stepgen allocation is not correct?
X uses Stepgen 00, Z uses Stepgen 01, Spindle uses Stepgen 02, but C_Axis uses Stepgen 01 as well..Should this be Stepgen 03 with the output somehow muxed to the spindle stepgen?
Please Log in or Create an account to join the conversation.
I deleted this entire stepgen section:
# Step Gen signals/setup
setp [HMOT](CARD0).stepgen.01.dirsetup [JOINT_2]DIRSETUP
setp [HMOT](CARD0).stepgen.01.dirhold [JOINT_2]DIRHOLD
setp [HMOT](CARD0).stepgen.01.steplen [JOINT_2]STEPLEN
setp [HMOT](CARD0).stepgen.01.stepspace [JOINT_2]STEPSPACE
setp [HMOT](CARD0).stepgen.01.position-scale [JOINT_2]STEP_SCALE
setp [HMOT](CARD0).stepgen.01.step_type 0
setp [HMOT](CARD0).stepgen.01.control-type 1
setp [HMOT](CARD0).stepgen.01.maxaccel [JOINT_2]STEPGEN_MAXACCEL
setp [HMOT](CARD0).stepgen.01.maxvel [JOINT_2]STEPGEN_MAXVEL
# ---closedloop stepper signals---
net c-pos-cmd <= joint.2.motor-pos-cmd
net c-vel-cmd <= joint.2.vel-cmd
net c-pos-fb <= [HMOT](CARD0).encoder.00.position
net c-pos-fb => joint.1.motor-pos-fb
It came up then with no errors.
C axis is present.
Homing X and Z works.
Homing C moves nothing - but shows C as homed on the AXIS display. I tried this also after executing an M100 in MDI.
Jogging (in AXIS) X and Z works. C does not move ( with or without M100), but returns joint2 following error.
With M101 active, Spindle runs normally ( M03, etc, stops M00/M05)
With M100 active, spindle does not turn with M03 etc.
With M101 active C axis does not move with:
G01 Z10 C45 F100 - just some moves to see what happens - nothing -but get a joint 2 following error.
Joe.
Please Log in or Create an account to join the conversation.
- Configuring LinuxCNC
- Advanced Configuration
- Spindle Step/Dir servo ramp down before stop on M stop command.