Advanced Search

It's not a issue with Intel MACs
If you disable IRQ coalescing
and pin IRQs, You get pretty decent
performance.

For example on this HP8300 I have been running a test on a 7I76EU
with a 3 KHz servo thread for about 3 days while using the PC for general
web browsing, email etc and have not had any issues.
(CPU frequency is 2.9 GHz and times are in CPU clocks)


 

 

First up i am apologizing for the silly thing that i have missed or dont yet understand but i hope i have tried.  

I have my Probe basic (now will be previous stable on 2.9.3) setup mostly working for what i wanted with Pendant etc.. but wanted to customize the physical buttons that i have for start / resume, Step / feed hold and well stop works fine.

(Currently 7i76 with physical buttons mapped through to the following
I started with forum.linuxcnc.org/47-hal-examples/13201...ume-buttons?start=40 and thought that i would like to have it when i press the start button and the system is in a feed hold state to resume.  So first part was to change from the single mapping to using an And to only allow start to happen when idle. (I know that is how the above cycle-start works but i was trying to do it to just prove i could get it working)
#Mapped physical button with no issues to one leg of And
net my-start-resume-button-in1 and2.pause-resume-0.in0 <= hm2_7i76e.0.7i76.0.0.input-07
#Then when trying to map one of the existing pins / signals is where  i get all screwed up.  
net my-start-resume-button-in2 and2.pause-resume-0.in1 <=  halui.program.is-idle

I thought that read as the following Netname = my-start-resume-button-in2, name of signal wire to set and2.pause-resume-0.in1 (the 2nd leg of the And), The trigger signal = halui.program.is-idle 
Instead of that working (Knowing i have no output yet) i get the following error.
custom_postgui.hal:67: Pin 'halui.program.is-idle' was already linked to signal 'prog-running'

So i was well lets change the trigger to be prog.running and see what happens then.
#net my-start-resume-button-in2 and2.pause-resume-0.in1 <=  prog.running
#.../custom_postgui.hal:68: Pin 'prog.running' does not exist (I can see that prog.running is a signal not pin but i am then back to confused about how to do the 2nd part of the and)

Then i was trying to even take the output of the and to trigger 'cycle-start'
net my-start cycle-start <= and2.pause-resume-0.out
#.../custom_postgui.hal:75: Pin 'cycle-start' does not exist

i hope that i am so close but yet so far.  (The reason that i posted this in the Probe basic is my aim is to use qtpvcp.feed-override.reset to remove from feed hold (I hope that is the correct way))
Thank you for reading this far and hoping someone can fix my broken understanding.  Full code block of what i was trying to do below with no extra typing.

Hard to see on the PDF and my glasses, but those look like analog drives, not step/dir so 7i76E would not be the best option.
Can you take a picture of the drives where the pin naming is?

Hello together.

i am Martin form Germany. I have bought a Knuth Mark Super CNC with a fault Controller (GPlus450) and I will not try to fix this old Controller.
The machine has servos with feedback and Maxsine EP100 AC Servo Driver so I think it is not a big deal to change the Controller to LinuxCNC.
I also have the electrical drawings of the machine.


I would use TCP/IP for connection so I think the Mesa 7i76e is fine for me, but this card is not available. So one alternative is the 7i96.
But this card has less in and output and I think I need a lot...

Spindel: CW + CCW + Analog
every Axis 3 switches (end, end, rev)
Lub level
Start/Stop
Drive X, Y, Z on
Cooling Pump
and much more....

So what do you think of this project.
How to start and what hardware I have to use?

Have a nice day
Martin

Yeah if Milton came ashore as a cat5 I am pretty sure it would be quite a while before you all would've been hearing
from me. I am just dumb struck at the mess Helene had become and still is.

my1987toyota wrote:

They're here. They're here. the 7i76EU is now available. Thank you PCW, JT and MESA for making these boards available once again.
Now I just have to scrounge up some money to buy one. LOL. Hurricane prep wasn't cheap. Thanks Helene and Milton.

Great to know you survived. In the end, as far as hurricanes go, Milton's Category 3 was a bit of a Fizzer. Shame about the storm surges and flooding though!

They're here. They're here. the 7i76EU is now available. Thank you PCW, JT and MESA for making these boards available once again.
Now I just have to scrounge up some money to buy one. LOL. Hurricane prep wasn't cheap. Thanks Helene and Milton.
 

it is called Analog servo interface , this card will explain

www.mesanet.com/pdf/motion/7i33man.pdf

Todd wrote:

If you are not already using ClassicLadder, and don't want to bother adding it, it can all be done in hal as well.

I think I'd attack this something like this.

loadrt and2 count=2
loadrt xor2 count=1
loadrt siggen num_chan=1
addf and2.0 servo-thread
addf and2.1 servo-thread
addf xor2.0 servo-thread
addf siggen.0.update servo-thread

setp siggen.0.frequency 2

#Yellow Light
net yellow-in1 <= halui.machine.is-on => and2.0.in0
net yellow-in2 <= halui.program.is-idle => and2.0.in1
net yellow-out <= and2.0.out
net yellow-out => hm2_7i76e.0.7i76.0.0.output-01 #(or what ever your output pin is for the yellow light)

#Green Light
net green-in1 <= halui.program.is-running => xor2.0.in0
net green-in2 <= halui.program.is-paused => and2.1.in1
net flash <= siggen.0.clock => and2.1.in0
net green-flash <= and2.1.out => xor2.0.in1
net green-on <= xor2.0.out => hm2_7i76e.0.7i76.0.0.output-02

#Red Light
net red-on <= halui.estop.is-activated => hm2_7i76e.0.7i76.0.0.output-00 #(or what ever your output pin is for the red light)


(I just have a big red light on each of our machines that turns on when they are not running a program.)
 

 

I have a question which may be version related.  This line:
net yellow-in1 <= halui.machine.is-on => and2.0.in0
gives me the error:
/usr/share/linuxcnc/hallib/qtplasmac_comp.hal:21: Pin 'halui.machine.is-on' was already linked to signal 'yellow-in1'
when I try to run this in version 2.9.3

Could anyone give me some insight into why, and maybe a way to make it work?  I am a total newbie at HAL coding.

I found the error!

After two days of checking, measuring with the oscilloscope, calculating number of pulses by measuring the frequency and pulse duration,  I was questioning my sanity.
I also throughly tested the other axis which are fine, so I compared the axis in all the files and found my error.which should have been set to
I changed the value and had to invert the axis. Everything is running smoothly now.

you need to net the pins with a name, so something like:

hello guys

Today I had a problem, suddenly my computer didn't read the ethernet port and I didn't see any lights on the ethernet port on my computer.
so I conclude, my ethernet port is damaged.

the light on the mesa 7i76e's ethernet port is running. and I tried ping 10.10.10.10 from my LAPTOP and as a result, it worked. Mesa 7i76e is not damaged.

So my suspicions about the Ethernet port on my computer are even more certain.


My question is, can I use a USB to Ethernet adapter on my computer to run LinuxCNC?

Is it reliable? or is it a no no?

Thanks in advance for any help

CB

7i76e_7i76x1_Dpl.bit is the firmware needed for a 7I76E and multiple THCADs

The load resistor for Ohmic sensing determines the sense current
I would not use higher than 25K

Note the if you use a lower value you need to make sure that you do not exceed
the resistors power rating with the open circuit plasma voltage.

Next I want to add ohmic sensing. With a Thad. 

I have downloaded the Firmware files from mesa. There are many files in the hostmot2 folder but have no idea which file I need to flash unto the 7i76E mesa board. What is the file name?

other question is about the serial resistor between positive and Thcad recommended is 390k but in one of the threads 25k is recommended can I freely experiment with resistors? Or does it need a high value to protect the Thcad?

It may be fixable but hard to say without further testing