Advanced Search

Good work mate.

For those who like it, I've got an Armbian image ready with Linux 6.17 Cinnamon which is ready to go.
drive.google.com/drive/folders/1_WMbZC0k...ceNNI?usp=drive_link

Last core already isolated
Included sata overlay (which had to be adjusted)
LinuxCNC installed
HDMI audio works
GPU acceleration works
VPU acceleration doesn't work in the web browsers, 1080p on YouTube works fine
IRQ of ethernet automatically pinned to core 5

You rock. Thank you.

For the arc volts, from the torch-, it splits to two wires that go to 2 transformers? and then to the rectifier.
In the attached pic, I circled the torch- wire route in red and the work+ in white.
Should I just attach to one torch- wire at the rectifier or ?

Also, do you mean one 1Mohm/2w on each wire for a total of 2 resistors or two 1Mohm/2w on each wire for a total 4 resistors?

 

Yeah, somehow i managed to miss this.
When in doubt, more C4 !!!
Use relays as you have in the drawing for ARCOK, do not wire anything to Mesa, do a test cut and check if the relay closes while cutting. Do the same thing for TorchON but reversed, meaning contacts go to plasma and coil on the Mesa side but do not wire to Mesa just use whatever can give 15-24V and trigger the relay with it see if the torch fires. After this, you can wire stuff to Mesa, one at a time, test, wire, test....
As for the Arc Voltage, find the big rectifiers, usually with big aluminium heatsinks and find the positive and negative, wire two short wires to each, wire 2 of 1MOhm/2W resistors to each of those wires, on the other side of the resistors wire two thinner wires prefferably shielded and send those to Mesa THCAD, mind the polarity, although nothing will happen if you do mix the polarity but you will have no voltage reading on screen.
Make positively and ultimately sure you have the power cord and plug under your foot while adding this, i do that always to prevent someone somehow getting the idea that it belongs plugged to the wall...while i have both hands inside!

Glad you got that sorted John. Just wanted to mention that I did somewhat similar - wanted to "move the WiFi 10ft away to the top of the HMI box" since that's the highest point of the machine.  Looked at external antennas but none had a cable long enough. So have Rpi --> industrial USB hub --> 10ft USB cable to a tiny  8821CU  dongle with the antenna sticking out of the HMI.  Trap for young players: that particular dongle already has a driver included in the Rpi .iso, but that driver absolutely would not work.  Had to follow the directions at the link to compile a special new driver for it.  After a lot of head-scratching and configuration, have the on-board WiFi disabled and the dongle enabled, and it works a treat.  Cheers.

I decided to remove the phc interface and when I pulled the 37 pin connector, I found that it only has 6 pins. 2 for arc ok, 2 for start, and 2 for hold(which I am not planning on using.) So it looks like I'll need to buy a new 37 pin connector to use the hsd's 24v. 
I am very confused by their example circuits, which are attached to my first post.

Output example 3 has cnc +24v, which appears to be be supplied by the hsd. With a name like cnc +24v, I'd expect it to come from the cnc.
Input example 2 has +24 vdc. Where is this coming from? Would this be my external power supply's +24vdc?
I am also not familiar with the t next to the resistor symbol. Is that a pull down resistor?

Tommy, I appreciate that you're the only one to respond. I assume you haven't followed up since I didn't tell you I have someone to wire up this up. I understand that this plasma has the potential to kill me and you probably don't want to be any part of that.
I am fully capable of killing myself on my own so imagine what I could with a little help.

 

Please look at:
forum.linuxcnc.org/nativecam/53492-nativ...-9-3?start=90#332430

Maybe it solves your problem.

Note that ENCODER_SCALE does nothing as it's not used in the hal file
(same with INPUT_SCALE)

Is there an alternate way to set the scale on the EL5101?

If not, feeding the encoder count through the scale component
(after the S32-->float conversion) would allow scaling/sign change.

 

Hello
I'm loosing my mind on my setup.
Right now, I'm only focused on the X axis so don't pay attention to other axis/joint.

here is my issue:
When jogging, when i press 2 times X+ with 1mm step, the first step moves, the second I have a joint 0 following error.
In HAL show, the first issue I see is the encoder going negative when I press X+.

I tried to setup the output_scale at -1 instead of 1, still the same issue. same for input_scale and encoder_scale.
I tried to put everything negative but my counter always go the same direction.
Do you have any idea please?
If you find something else wrong with my X/joint0 setup do not hesitate. Only the BIAIS works well right now

Thanks a lot

Its part of qtpyvcp www.qtpyvcp.com/showcase/plasma_vcps.html

Update: Got the drive to start moving when the home button is pressed!
We'll see where I go from here 

All stat parameters are false.
opmode = 0
controlword = 0x00000004
statusword = 0x00000000

I realize I commented out the cia402 net commands because they were throwing a "Pin 'lcec.0.3.x' does not exist" error, and if I add SyncManager back in "syncManager is only allowed on generic slaves"

What should I do to configure the pdos, or do I simply have to call them by a default name? If so, where do I find it..?

Sounds good. Sounds like it is in OP.
Then go into halshow and check the cia402.?.stat parameters. ? being your drive number.
Which if all the stat parameters are true, hopefully stat-op-enabled.
And what values ​​do controlword and statusword have?

Can you attach your hal and ethercat-conf file again.

I don't see any errors in syslog or in the LinuxCNC output, but I still get a joint 0 following error when I try to move the drive...

I got this working by using curl in a G-code macro to call a webhook that sends me texts. I signed up with a voip provider that gives me a number capable of receiving and sending SMS through a simple API. That way I don't need a full email setup—just a lightweight script and a network connection. Super handy for longer jobs or when I step away from the machine.