Advanced Search

Not that i am aware of, and now we know what you're after we can easily point you in the right direction: Get another PC!
Having two machines controlled by the same PC is not safe as any issue with the PC would stop both machines, together with the materials scraped that may or may not be recoverable.
If space is the issue, most monitors have at least two inputs, some can show both inputs at the same time, some also have KVM so connecting mouse/keyboard to monitor will switch those whenever you switch monitor inputs.
Keep in mind having two PC's on the same monitor without a KVM has the inherit drawback of clicking on keyboard/mouse several times till it dawns it's the wrong PC on. Done this a lot as i have a monitor in the shop with 7 inputs and usually 2-5 PC's connected.
What about using laptops? There are several i tested that work OK for normal "non mission critical" use:
forum.linuxcnc.org/18-computer/54369-use...mesa-ethernet-boards

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

Thank you for the answers.

I think tommylight is understanding it wrong. I don't want anything synchronized. I wanted two machines running on one PC, completely independant from each other. Separate G-Codes and movements. Literally just a second LinuxCNC instance connecting to the other machine.

The most likely cause is that the PWM --> voltage converter is
not using a Rail to Rail output (RRO) OP-AMP. 

The same thing will happen if you use your LM358, it will only
swing up to ~8.5V or 9V with a 10V supply. If you want 10V from
your  converter, you would need to use say a 12V supply. 

These (marked) values will cause a following error if you jog axis:

[AXIS_X]
MIN_LIMIT = 0
MAX_LIMIT = 200
MAX_VELOCITY = 40
MAX_ACCELERATION = 200

[JOINT_0]
AXIS = X
TAB = 0
CARD = 0
MIN_LIMIT = 0
MAX_LIMIT = 200
MAX_VELOCITY = 50
MAX_ACCELERATION = 200
TYPE = LINEAR
SCALE = 320
STEP_INVERT = False
DIR_INVERT = False
STEPGEN_MAX_VEL = 50.00

This is because there is no hardware headroom at 50 mm/s
so if s velocity of 50mm/s is commanded, the hardware may not be
able to keep up. This may be a MesaCT bug, the stepgen maxvel
value need to be about 20% larger than the axis and joint maxvel
values. In this case I would (for all joints) change the joint
maxvel to 40mm/s

Another possible cause of following errors is the close setting of the DPLL
sample time, I would change this from -50 usec to -200 usec

I would also toss all the jog filtering as it's just likely masking a setup issue

github.com/machinekit/mksocfpga Hostmot2 FPGA code for SoC/FPGA Zynq platforms

I’ve been trying to get some stuff working and it’s starting to get there, 

 Added some stuff and mpgs are reading and moving X, Y, Z but it immediately throws an error of positioning error, tired to adjust max acceleration for all axis, and also asked AI to help me make filtering/limiting, worked a little bit, but it went slow and unresponsive,

picture explains more of what happened 

sorry for all comments in the files being Swedish.

@Pipik and @SebastianM
No double posting please.