Advanced Search

Thank you so much! I will reply back with my experience. Several days, maybe...

github.com/ventoy/Ventoy/releases

Thank you so much! Where do I get the Ventoy download?

In this case the encoder resolution is 10 counts/mm (0.1mm) so I use a deadband = 0.05, This eliminated the oscillations that occurred simply by enabling LCNC.

Hi Tommy, thanks for your quick response. These are my ini and hal files if you'd like to take a look.

Im guessing your talking about axis? I havent found a way to embed the tooltable

but Im starting to remember that I already did this before....
forum.linuxcnc.org/21-axis/38188-solved-...screen-w-usercommand
5.5 years later....looks a little better

you still need a mouse though

This is just a stab in the dark, but try
P=0.2 up to 0.5
D=0.01 up to 0.05
FF1=0
Everything else PID related to 0 except some deadband, like 0.001
-
This is not an assumption, this is the only thing that properly works for my Mazak with Mitsubishi drives
And, yes i did a lot of head scratching, it did not help

1. Install Ventoy to a USB drive.
2. Download the latest LinuxCNC ISO (Chrome downloads files slowly for some reason, use Firefox, curl, wget, JDownloader, etc. for better speed).
3. Download an ISO of Ubuntu 22.04 LTS (more stable, better in certian ways, IMO) or Ubuntu 24.04 LTS (newer) (you can download both and see which you prefer).
4. Copy ISO files onto the USB
5. Install LinuxCNC from the USB, leaving some unpartitioned space (LinuxCNC only needs 100GB max).
6. Install Ubuntu alongside Debian.
7. You can now use both OSes.

Well once again here, ready to continue learning, I have obtained some ethercat modules ek1100, el4032 and el5151, el1008 and el2024, I have a Mecal sw453 machine, I continue with mitre saws haha, until now I had carried out all the tests with (H-Bridge PWM) + (DC Motor with encoder coupled directly to the shaft), for the case in question a servo amplifier is used which I have already talked about here in the forum at another time (Maxifet AF 60 10/20) it takes a control signal +/- 10V and also requires a tachometer the motor power supply is 60V, the motor is coupled to a reducer which could verify the transmission ratio, the encoder is 250 ppr and when connecting it to the 5151 module I was able to make some measurements such as the encoder-scale is 10 since for 2000mm I got 20,000 counts.After this hardware introduction, I can add that I've run tests tuning the control loop, and although I've managed to move the axis, I frequently get tracking errors. Some time ago, I asked here on the forum if it was possible to configure this without the encoder on the motor shaft. Based on some exchanges with Tommylight (thanks a lot for everything), he told me that a control loop with this configuration was viable and that Linuxcnc didn't care where the encoder was. Obviously, everything has its difficulties. I've run some tests, including: I increased the servo-thread frequency to 2 kHz. I tried tuning the PID loop by adding P with I and D set to zero, but the system oscillates with gain P=1. Finally, after much trial and error, I arrived at P=6, I=3, D=:4-6, FF1=1, which produces movement, but at the moment of braking, it begins to oscillate. If anyone can contribute ideas on how to improve the loop response for this configuration they would be very welcome,

Just this:

www.linuxcnc.org/iso/linuxcnc_2.9.4-amd64.hybrid.iso

Oops, missed that you said Ubuntu
 

What downloads do I need to install Ubuntu and Linuxcnc  on a Dell Optiplex 7000 series desktop?

I have the THCAD2 setup for 10V range and 32 divider with the plasma divider set to 20:1 and the arc voltage is displaying correctly after I set the scale and offset. The Thermal Dynamics has a 15V arc voltage before the start is initiated and it is showing correctly along with arc voltage during pierce and cut. For some reason I can't seem to get the Arc OK input to work. I have pin 12 of CPC connected to +24V, pin 14 to Mesa input 15, and -24V connected to Mesa common for the input. If I disconnect the CPC cable from the plasma cutter and short pins 12 and 14 the Mesa input goes high so the cabling should be good.

I have noticed there is a 2 second delay after start is triggered before the pilot arc lights so by setting my pierce time to (2 + pierce delay) and setting "Ignore OK" I have been able to get it to cut and the arc voltage is right around 137 that the cut table shows for the material I'm using.

The service manual for the plasma unit shows that it has an "OK to Move" LED inside the case so I may have to pull the cover and check that as well.

Any other ideas what I could be missing?

EDIT:  I disconnected pins 12 and 14 from the control and checked across them while cutting and there is no continuity so it looks like I will need to pull the case on the plasma unit and check the LED.

FINAL EDIT:  I went through all the resistance and diode checks in the service manual and verified continuity of the relay pins and the "Ok to Move" LED on the inverter board lights but the relay does not close.  So the relay is bad.  I switched to mode 0 in QTPlasmac and that works ok.  Maybe some day I'll pull the inverter board and see if I can just replace the relay but the Mesa/LinuxCNC side is working fine.

step one for me is to figure out how to get my offsets onto a page like MDI and manual jog page instead of opening a whole different window. on linuxcnc I end up G10L10Pxx my tools from mdi because the extra window is annoying to me. It sounds like this is possible but Im having a hard time finding the right search term to get a how-to or starting point. Also is there a way I can add a "common" offset? It looks like "external offset" could be handy here. sometimes its nice to measure in process and adjust a few 0.001" here or there while running.

Hi,

The request:
A few weeks ago i recieved a ethercat servo drive from a forum sponsor. A Delta-asda-b3 drive and motor set.
The sponsor had a request for me. Figur out homing the drive using it with linuxcnc.

The difficulty:
Now the drive has internal home programs. And there comes the problem. How to deal with this using homemod.so?
Where homemod.so is the component responsible for linuxcnc home sequence.

The desired home sequence:
1. Home with search_vel to hard end stop of machine using a lower motor torque and stop on torque home limit value.
2. Move back from hard stop to find the first motor index z pulse, using the servo drive's internal home program.

The motivation to get it work:
1. Using the servo drives internal search for index z pulse program is the most accurate way to home a machine as it is not
depending on a servo cycle, where the servo cycle is not contributing to a ultra high precision.
In theory the index pulse may in between 2 servo cycles. This is what i mean with no ultra high precision.

My workflow:
1. To use the servo drive with ethercat i had to install lcec and cia402.
After installation and editing the ethercat .xml file,  i was able to run  the servo set.

2. The original cia402.so component was written in halcompile language.
The idea was to convert the halcompile component code into a c coded component.
This resulted in a base component, code can be found here.

3. After coding a few day's i was gradually understanding how the servo's work and i could expand the codebase
to include torque control. And i was able to run servo drive internal homing programs.
This resulted in a new component : libcia402

4. After up's and down's and trying different workflows i was able to edit the homemod.so component,
that is used by linuxcnc to do the home sequence.
The new component works exactly as the homemod.so, but it has additional features to enable external homing.
This resulted in a new component:  libhomecia402

Note: The motivation to keep the homemod.so original is that users can now combine external homing on servo's
with steppers and homing works as normal.

Conclusion:
The extern homing on index works as expected.

Variations:
As we use the .ini file to set home configuration. In .hal we can set servo drive home program and more values.
Therefore i did not test other external home variations so far. But we can think of multiple home sequence variations.

Installation on rip systems:
Readme. Section installation.

Sorry for the late reply.

Well, I should have respected the wisdom of the ancients: 'have you tried turning it off and on again?'.

I tried the MDI command and it worked. Then I reloaded the program and it worked, too. Nothing changed, just a reboot between the tries.

Thanks for your support!