7i76e: MPG and Analog inputs with pncconf?

trilobyte wrote: it is working now! tnx guys!


i have this in the custom postui hal:

setp hm2_7i76e.0.7i76.0.0.analogin3-scalemax 460
net halui.maxjoganalog <= hm2_7i76e.0.7i76.0.0.analogin3 => halui.axis.jog-speed

something is a bit strange: if i start linuxcnc i can run a cnc programm without a homeing sequene (the last position is stored) but i can't move the machine with the mpg and the joystick.
with the arrow keys on the keybord it is possible directly after starting the machine.
mpg and the joystick are working after a homeing sequence, or after starting an stopping a ngc file!?


Peter

I think this is a result of the 2.8's Joint-axis separation, you cannot jog axis until homed (only joints)

PCW is on the money. In master, you can't jog until you home all. This is to prevent a gantry from racking by moving a single joint on one side.

rodw wrote: PCW is on the money. In master, you can't jog until you home all. This is to prevent a gantry from racking by moving a single joint on one side.

I did it like this with PCW help. But this is on a simple mill no dual motors.
setp axis.x.jog-enable true
setp joint.0.jog-enable true
## The above line is to be able to jog without homing ##

In master, you can't jog until you home all. This is
to prevent a gantry from racking by moving a single joint on
one side.

In general, the above statement is incorrect.

Joint jogging is allowed prior to homing except for special
cases where joints specify a synchronized final move by
using negative [JOINT_N]HOME_SEQUENCEs. In these cases,
joints that do *not* have a synchronized home sequence may be
jogged prior to homing.

See: linuxcnc.org/docs/master/html/config/ini....html#_home_sequence


The behavior is readily shown using the sim config (no
hardware required):

configs/sim/axis/gantry.ini

In this XYZY config, joints that correspond to the
Y coordinate (1 and 3) are synchronized; joints 0 (X) and
2 (Z) are not synchronized.

github.com/LinuxCNC/linuxcnc/blob/master.../sim/axis/gantry.ini

phillc54 wrote:

trilobyte wrote:
it is working now! tnx guys!
i have this in the custom postui hal:
setp hm2_7i76e.0.7i76.0.0.analogin3-scalemax 460
net halui.maxjoganalog <= hm2_7i76e.0.7i76.0.0.analogin3 => halui.axis.jog-speed

I am a bit confused as I have an up to date version of master and changing the value of halui.axis.jog-speed has no effect on the jog speed slider in Axis.

Cheers, Phill.

Strangely the original developers of the linuxcnc motion controller didn't give it an internal jograte or jog increment memory.
My understanding of this is because in the beginning it was a design requirement to be able to be controlled with multiple user interfaces at the same time - which typically used a switch mechanism to select jograte/increment which of course can't be automatically adjust by another interface..

Consequently, each ui has it's own idea of jograte/increment and there is no easy/universal way to communicate it around.
You would have to hack into AXIS to connect the halui jograte to AXIS's jograte - maybe possible within the .axisrc file.

Chris M

cmorley wrote:
Consequently, each ui has it's own idea of jograte/increment and there is no easy/universal way to communicate it around.
You would have to hack into AXIS to connect the halui jograte to AXIS's jograte - maybe possible within the .axisrc file.

Yes, it can be done with either .axisrc or a user_command_file.
This was asked for in this post so I assumed that a successful result meant that it had been achieved...

Cheers, Phill.