Advanced Search

Argh, @meister thankyou, it works now. Took a bit of googling to figure out how to do that.

For other beginners, what I did in the terminal:
sudo ip addr add 192.168.10.1/24 dev eno1
sudo ip link set eno1 up

I also added the following to the "interfaces" file in /etc/network/
iface eno1 inet static
address 192.168.10.1
netmask 255.255.255.0

Change eno1 to your adaptor name

If you are retaining the hydraulics, the question would be how are the hydraulic valves
that control position controlled and what is the position feedback method.

Sounds like the jogging setup in the hal file is not quite right
can you post your hal file?
 

Honestly, I would just add a  leaded 620 Ohm pulldown
resistor on the back of the breakout card and not make
any further modifications.
 

My guess is that there siginificant coupling of the plasma start transient into the step/dir wires
or perhaps a grounding issue.

If you use single ended connections, the step/dir wiring will be less susceptible to
damage from external RFI/EMI. Another option is to use shielded wiring for step/dir
(with the shield connected to GND only at the 7I96S end) 

Control panel connections :

net matrix_r2c2 matrix_kb.0.key.r2c2 => halui.spindle.0.stop
net matrix_r2c1 matrix_kb.0.key.r2c1 => halui.spindle.0.forward
net matrix_r2c3 matrix_kb.0.key.r2c3 => halui.spindle.0.reverse

Hello zmrdko,

I just found your great work with the easycat card.
I'm starting to play with it, and it works great for digital input and output. With 1 encoder, no problem.

However, with 2 or more encoders, it doesn't work... As soon as I change the "QUADENCS" value to greater than 1, I can no longer connect to the easycat card. I get an error with the "easynavigator" software.
Have you ever had this problem?
Do you have any leads?

regards
Laurent

Hey guys...
I'm using Linux for the first time for a lathe with a turret with eight tools, each in its respective position, sending an individual signal for each position and a turret locked signal.

Working cycle:
"Control system sends signal of tool change -->Motor running with positive rotating -->Toothed disks is disengaged -->tool holder disk rotating-->tool holder disk locating-->Control system receives the signal of tool holder disk locating and sends the signal of delay time of motor reversal rotating Motor running with reversal rotating -->Toothed disks is locked-->Delay time of"

I need to know if there is any component in Linux that supports this cycle, or if someone has already done something similar so that I can use it as a basis to create the tool change cycle.

Amazing! Thank you! 

I don't know the history of the board. Bought it cheap on eBay many years ago. It would be great if I can manage to use it, if not a 7I96S would probably suit my needs better.

Thanks again,

Dan

@Happppppppy

you need to configure your network !

 

7I96 bitfile with 2 PWMGens

Looks like the 74ACT04 (U17) was damaged

Probably. At least I could reproduce it this way.

The issue here is that using 'halui' in parallel to a gui is not really a very good idea at all. Many do it, myself included, to connect panel buttons. Gmoccapy is designed to use button rows aligned with the gui buttons but that is not always practical.

I wonder if it would make sense to have gmoccapy create its own dedicated pins like 'halui' so we would have more control over them.

so a stiff pulldown to fight the pullup of the mesa card for the inputs?

I am using 7c81_5abobx2d firmware with BOB boards on P1 and P2.

Edit:
I did a little bit of digging.
- The relay pin P17 is IO7 of the Mesa ports, which is on the edge of the pull resistor array. I could desolder the array and put it back on shifted by one to remove the resistor of the pin.
- On the BOB there is a 10k pullup array on the relay pin. but the signal comes through a via in the middle of the pullup resistor and the 74HC... I could cut the trace between the via and the resistor to remove the pull up on the BOB
- solder in a pulldown resistor on the BOB (if for whatever reason the flat cable between the Mesa and BOB gets bad).

Great, now the error is gone and LinuxCNC starts normally.
Unfortunately the Encoder handwheel does not move the selected axes. I can see it counting in Halshow, but the axis selected stays where it is.
I read in the documentation that the use of a MPG would reqire homing of the axis- my machine is not homed at the moment- but I thought the line
NO_FORCE_HOMING = 1
would let me use the MPG without homing- probably not, or is there any simple possibility to move the axes via MPG without homing them first?

The other thing I would like to get running is the spindle. I seached quite a bit, but did not really find out how to use the parameters. In diffeerent threads these are described differently.
The spindle is a Fanuc Servo which is capable to make 8000 rpm. Its connected to the correct Fanuc servo drive. The spindle itself only is allowed for 5000rpm. With the old control connected, I found that the max voltage the servo drive gets from the control is 7,6V+ at 5000rpm. So if I scale this to 10V it would give me 6570rpm.
As far as I know only pos voltage is used in the analog signal (0 to 7,6V) and the spindle is reversed by an additional signal to the drive unit. The 2500incr. encoder that I want to connect to the 7I33 is an additional encoder (TTL) driven by the spindle via toothed belt and is originally used with the old control for threadcutting (synch) only- the servo drive gets its info from an encoder inside the motor which I can not access.
So thats what I think currently the spindle params should be I wrote below. Is it correct- I guess not,but how is the calculation in this case done?
And how can I determine the output of min 0V to max 7V and no neg. voltage is used, if not this way.

MAX_OUTPUT = 5000
ENCODER_SCALE = 2500
OUTPUT_SCALE = 6570
OUTPUT_MIN_LIMIT = 0
OUTPUT_MAX_LIMIT = 7

Thanks
Sigi




 

There is no output at all on TB2-2.

Is it possible to move the PWM to one of the other stepgens? eg. TB1-20/21?

Thanks,

Dan