Advanced Search

Yes, for two cards you need them to be set to different IP addresses (using mesaflash)
You should verify that this is correct by being able to ping 10.10.10.10 and 10.10.10.11

Also for decent performance you need to use read-request so the second card does
not have to wait for the read response of the first card before it's read request is sent:

addf [HMOT](CARD0).read-request servo-thread
addf [HMOT](CARD1).read-request servo-thread
addf [HMOT](CARD0).read servo-thread
addf [HMOT](CARD1).read servo-thread

So I figured it out.
I installed ohmic3 comp.
Put the Hal file into the config folder of my machine and edited the ini file and added the ohmic Hal file.
Linuxcnc starts now without any error messages.

Probe test works.
But if I press ohmic test nothing happens.

Hallo zusammen und erstmal herzlichen Dank für all die Informationen hier!
Auch ich versuche alte Servodrives (Kollmorgen ServoStar 600 Serie) über canbus mit der EL6751 (CANOpen Master) und in weiterer Folge linuxcnc-ethercat kommunizieren zu lassen, leider ohne Erfolg bisher. (linuxcnc-ethercat an sich hab ich am laufen) Nun hab ich hier einen Kommentar von Sviper gelesen, dass eine aktuelle Firmware der Karte notwendig ist -- kann mir jemand die Version 13 (sollte lt. Kompatibilitätsmatrix für meine alte Karte passen) zukommen lassen? Der Beckhoff Support meldet sich auf meine Frage ungünstigerweise nicht.
LG Franz

I don't know what you mean by "connect".

But as per all things networking 2 devices cannot have the same IP address. Are you going through a switch or do you have 2 NICs in your computer.

And why do you need 2 7i92s for a single configuration ?

i think i have a good design starting point for this reduction set up for my Y axis. the X will be easy comparted to the Y axis i think. i think i even avoided losing axis travel and should work well if i can make in come to life i think i will add a cover and rework my belt tension for the X axis into it but i think i have it compressed as much as i can work into this design,

   

Works on my laptop -I'll test a few other systems.
But next time, please start a new thread for a new subject.

Glentek GM4050 (MTR-002) runs about $300 to $800 on ebay.

I have some thoughts/suggestions on a possible retrofit if you're interested.  Little late tonight, but if you're interested let me know.

Hello everyone!I need to connect two 7i92 boards, Pnсconf Wizard does not allow me to complete the configuration and creates an empty hal file, I add the second board manually but still get an error, please tell me what's wrong?

I downloaded the npt_pipe.ngc program this morning and it worked perfectly on my CNC Lathe to cut 1/2"-14 NPT threads. Thank you for sharing this program.

Listed below are a few minor tweaks that I had to make to get the program to run on my setup. I hope this helps others.

1) Double click on the attached file in the forum to open the file in the browser. Then, Select All and Copy. Open NotePad in Windows or Kate in Linux and then Paste in the entire program file. Select, Save As and Title it npt_pipe.ngc.

2) Delete the First Program Line..... o<npt_pipe> sub, OR Comment It Out
using parethesies..... (o<npt_pipe> sub).

3) Delete the Last Program Line...... o<npt_pipe> endsub, OR Comment It
Out using parethesies..... (o<npt_pipe> endsub)

4) About 11 Program Lines down, there is a list of variables = #1, #2, #3 etc. as shown below.

#<_OutsideDiameter> = #1 (Nom or Act Dia, D)
#<_TPI> = #2 (=0 TPI, 0 for auto)
#<_First_Cut_Depth> = #3 (=0.015 First Cut)
#<_Minimum_Cut_Depth> = #4 (=0.003)
#<_X_Clearance> = #5 (=0.075 X clearance)
#<_Z_LeadIn> = #6 (=0.250 Z Leadin)
#<_TipRadius> = #7 (=0.003 Tip Radius)
#<_Spring_Passes> = #8 (=1 Spring Passes)
#<_CompoundSlideAngle> = #9 (=29.5 Angle, 0-30)

Replace the #Numbers with your parameters and save the file. My parameters for a 1/2-14 NPT thread were as follows:

#<_OutsideDiameter> = 0.5 (Nom or Act Dia, D)
#<_TPI> = 0 (=0 TPI, 0 for auto)
#<_First_Cut_Depth> = 0.006 (=0.015 First Cut)
#<_Minimum_Cut_Depth> = 0.002 (=0.003)
#<_X_Clearance> = 0.075 (=0.075 X clearance)
#<_Z_LeadIn> = 0.0625 (=0.250 Z Leadin)
#<_TipRadius> = 0.003 (=0.003 Tip Radius)
#<_Spring_Passes> = 1 (=1 Spring Passes)
#<_CompoundSlideAngle> = 0 (=29.5 Angle, 0-30)

5)  Open the saved .ngc file in Linuxcnc (i.e. Linuxcnc configured for a Lathe.)

Good luck. Barry

Showstopper update:
We are slowly progressing and can operate sometimes, and other times we can not.
Homing issues are now fixed (in the end the homing proximity switches were showing 12.7 volts when not activated and 24v when activated and this was causing intermittant issues. Have since replaced them with a different brand they now show 0 when off and 24v when activated and the homing has been working perfectly).

Still having issues with ohmic sensing. Sometimes it works and sometimes I can't use it. When I first turn the machine on for the day the ohmic sensing can show as high as mid - high 23's and even go to 24v. But here is another problem that I am getting and I wonder if anyone else has experienced this one:
When ohmic probing isn't working normally I just turn it off and when it drives into the sheet the float switch will light up and then it will back off, pierce and cut.
This was working fine but now it isn't. It is driving into the plate the float switch light comes on and it will go until the breakaway is activated and it will give an error.
I unhooked the breakaway switches because I have a strange issue with them where sometimes the breakaway stays on after triggered. When testing with a multi meter it stays on (we are suspecting this is due to faulty proximity switches. New ones are on the way).
When the breakaway sensors are unhooked the torch drives into the plate, the float switch lights up but the motor just keeps driving into the plate and won't stop. So why does qtplasmac not know that it has hit the plate when it knows the float switch has been pushed. And how could this be an issue today when it was working yesterday?
Here is a video if it helps.
photos.app.goo.gl/FyoKbwEHJTWfGdXa9

The LinuxCNC Toggle component replicates a toggling pushbutton functionality. In the case of BJT example. The pyvcp is a push button widget on the screen that used to turn ON and OFF the flood valve.

So, initially the flood is OFF when you press the pyvcp widget the flood will turn ON if you press the same pyvcp widget button the flood will turn OFF and so forth.

In nut shell one push button is used to turn on and off the flood valve.

This is probably the simplest way to turn an output ON/OFF with only one push button (ui or hardwired). If you use hardwired push button add 20 ms debounce.

That's a price for new servo. DC Brushed machine. I like the old fadals cause you can get parts for almost everything. I just don't wanna have to buy this one lol.

I don't know anything about Classic Ladder. But if you want to connect multiple things together in HAL then I can probably help.

You can connect one input to several outputs simply by using the same signal name.

net signal output1 input1 input2 input3 ...

Is one structure. where "output1" is a "writer" pin that supplies a numerical value, and all the input* pins get set to that value.

As long as you use the same signal name, you can split is across lines, and between HAL files. So the example above could equally well be written:

net signal input3
net signal input1
net signal output1 input2

Or any other order/combination as long as all the connections that need to take the same value share the same "signal"

You can give "signal" any name you want. But the inputs and outputs need to be HAL pins that exist at the time that you connect them.

I like resolvers. Both my machines use resolvers, Mesa do a card that can handle them, and drives that can use that feedback to drive the servos (if they are brushless, I suspect your existing ones are probably brushed, though?)

I agree that $1700 for an old (used?) servo might not be a good investment, though there is a counter-argument that in 1993 this was a very expensive machine and the original servos are probably very high quality. (not much comfort having a broken high-quality servo, admittedly)

To be honest the only thing that has me concerned is writing the logic for the tool change.

I know what needs to be done and the steps, but I do not know anything about classic ladder or programming so that will be some learning on its own.