Advanced Search

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.

i dont do it over a wizard.. only by hand... in the hal and ini.

The issue with the error is being dealt with:
github.com/LinuxCNC/linuxcnc/issues/3510

Andy, did you delete your post?

9V is 90% of 10V, makes me think in the wizard the default values are 10%-90%, but not sure if on StepConf or PncConf.
Check the hal if that is the case, namely if the max PWM value is 90%.

Hi guys.
i am a little bit confused.
I get from amazon a pwm to 0-10v converter.
I try it out first on a arduino which has 5v outputs on the GPIOs. works fine.

then i switched to my 7i92 and 7i92t!
i reach only 9v -9.04v if i screw in the calibration cap.
In the hal i set different pwm base freq. from 1khz up to 30khz. nothing helps.

then i come to the point that the optocoupler on the converter isolate the circuit. this means for me it doesnt matter which voltage is coming from the mesa right?

what are the cause?
i dont search for circuit diagramms..

the idea what i have was to take a lm358 and make it on a breadboard..

but i ask here before waste my time.

thanks

 

No unfortunately a new Config with a MPG already included did not do the trick.
Manual jogging the X and Z axes works, continuos and inkremental but not with the encoder I intend to use as MPG.
I once again ran the suggested command "halcmd show pin | grep jog" - report attached.
Did not imagine it would be this challenging to get a MPG connected...
Sigi