Advanced Search

You need to be clearer please, loose terminology is confusing things.

You are using "machine" to mean multiple things.

Suggest:
Computer (the hardware linuxcnc runs one)
CNC machines

> as long as you do not need both running at the same time.

Exactly that's what I wanted.

Is there any workaround that could work, too, without having to use two separate machines?

That data suggests a 4.5V minimum input PWM voltage.

Also, if it has an optocoupler input, you can get a 5V signal
out of a 7I92/7I92T by wiring the PWM input to +5V and the PWM
input negative to the PWM output of the 7I92/7I92T.
In this case, you would need to invert the PWM output in
your hal file.
 

OK, that is not what i was thinking/answering, but the replies are still valid, namely most of the pin names would be the same on both instances.
But, having two separate machines/configs with two separate controllers/electronics is for sure possible ... as long as you do not need both running at the same time.

makerhero.com/img/files/download/3PSC3-m...bOy1GiYJwCPiI6EEGEI2

i talk about this thing... and i test now 500hz up to 3khz in 5ü0hz steps.. nothing changed.. i have 3 of them.

i wonder because the arduino brings the converter to 10v.

Maybe the OPTO input circuit requires 5V?

I guess you could test this by simple supplying +3.3VDC
to the input and seeing if you get 10V out

If you need 5V drive, you could put a stiff pullup
on the PWM pin to +5V (say 330 Ohm)

I guess it could also be a scaling issue
 a PWM value >= PWM scale will result in a fullscale
(stuck high) output

i supply 12v... thats the thing.
i dont know the circuit but i think.. the 3.3v are not the reference voltage.
after the optocoupler i meassure a 5v signal of the pwm. is it possible that i need to invert it? or is it the wrong way?
direct on the output of the lm358 i meassure 9.5v at 100% pwm.
then it goes over resistor and cap to the output. down to 9.04v

but.. with the arduino same khz i get 10v....

Again, the jog enables are false so the jog counts are ignored.
The jog enables are false because they are not connected to any
source (no hal "out" pin)

note that halui.axis.x.select and halui.axis.z.select pins are hal "in"
pins so can not enable anything.

What do you do to select an axis for jogging?
This part seems to be missing

That is, these need an additional connection
from whatever selects an axis for jogging:

net axis-select-x halui.axis.x.select
net axis-select-z halui.axis.z.select