Advanced Search

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!

Hallo,
in dem Vorschaufenster werden ja die Grenzwerte des G-Codes angezeigt. Das passt auch. Habe ich aber einen Werkzeugwechsel (M6) im G-Code passen die berechneten Grenzwerte überhaupt nicht mehr. (Über- oder Unterscheitung der Z-Grenzwerte) Ich verwende eine dynamische Werkzeugvermessung, ich meine das nennt man so. 
Alle Werkzeuge haben einen Längenverstatz von 0 in der Werkzeugtabelle. Da ich den Längenversatz vom ersten Werkzeug  zum zweiten erst weiß wenn ich das Werkzeug eingespannt und vermessen habe, sollte für die Berechnung der Grenzwerte und alles was in der M6 Routine steht nicht bewertet werden.
Ich meine was ich was gefunden hatte beim googeln, das man beim Aufruf von M6 mit einem Parameter unterbinden kann das der Inhalt von M6 nicht mit verwendet wird bei der Berechnung. Habe aber nie gefunden wie der Parameter heist und wo der eingetragen werden muss. Also hinter dem M6 oder ob das eine globale Einstellung z. B. in der ini ist.
Kurz zusammengefasst: Wie verhindere ich das der Aufruf von M6 die Grenzwertberechnung beeinflusst?

Without Tachometer feedback, the drives are running in torque mode.

There are a couple of options for controlling this:

1. Run as is with different tuning. For single loop torque control tuning is basically:

   A. Increase D term as far as possible until you get buzzing/hf oscillation
   B. Then increase the P term until you get instability and then back off to about 50% of that P value
   C. Increase the I term until you get instability and again back off on the I term about 50%

2. Use a spare analog output channel to simulate a tachometer so the drive itself can run in velocity mode

3. Use a dual PID loop control in LinuxCNC (inner velocity PID loop and outer position PID loop)

There are three hall sensor wires, which have been pre wired as i got the servos and drives as a set. i dont think this is the same as a tachometer?
There is also a 2000PPR encoder which is wired into the Mesa card

I bought e-cam or simplexcam (both the same with other names) a while ago. Now I have a lifetime licence with no subscription trash.

Unfortunately this goes back to work-in-progress state.
The normal arc voltage reader didn't give a reliable output during ohmic sensing.
I'll put in another voltage sensor, right over the 24V-ish supply to the torch and ground.

Klar, musst du nur an einem Digitaleingang an der 7i96 anschliessen.

Heres a quick code thrown together out of Fusion drilling and countersinking a hole. Do some research on G code and how to setup your tool offsets and work offsets. hopefully it gives an idea of the G code structure for you.

Yeah Autodesk sucks. I have 5+ years of programmed parts and custom posts at work. Now they are killing the software. I have fusion so at least I can use my custom posts if needed. they better figure out the ITAR crap for fusion before they totally kill my HSMworks..

I guess banning him is kinda useless 'cause he'll just return as a different user.

Hello everyone
After doing some research, I managed to understand how communication works, and at the moment I have everything communicating as I want it to.
Now my question is why the Spindle tab is not active in the CT table. Is there a bug or am I just an amateur?
thanks