Advanced Search

I would think that could be done with 2 mux2 components
(1 for X and 1 for Z) that select between anglejog outputs
when anglejog is enabled and direct MPG counts when
anglejog is not selected.

I didn't know about g93 you're right that's definitely the way to go

PCW wrote:

Normally the MPG encoder count goes to all Axis jog count pins,
so no routing of the counts is needed.

This is required so that LinuxCNC can track the current MPG count
and only apply changes to the enabled axis.
 
 

The problem is that when using anglejog for emulated compound movement (X+Z), the MPG ticks get processed by anglejog and then analogjog outputs the sin and cos values that are to be fed to; axis.x.jog-counts, and axis.z.jog-counts, however in HAL,  axis.x.jog-counts, and axis.z.jog-counts are already being driven by the raw (non sin and cos values) from the MPG for non compound/anglejog use.

axis.x.jog-counts, and axis.z.jog-counts, can't be driven by both the MPG and anglejog

net encoder-counts  <= hm2_7i96s.0.inm.00.enc1-count
net encoder-counts => axis.x.jog-counts
net encoder-counts => axis.z.jog-counts
net encoder-counts => anglejog.counts-in
net angle_x <= anglejog.coscounts
###net angle_x => axis.x.jog-counts  can't do this!!!
net angle_z <= anglejog.sincounts
###net angle_z => axis.z.jog-counts  can't do this!!!


 

I guess the next step would be to make sure that the analog output path is OK.

A quick check would be to make sure that the analog output voltage of the 7I77
is near 0V when LinuxCNC is not running.

Normally the MPG encoder count goes to all Axis jog count pins,
so no routing of the counts is needed.

This is required so that LinuxCNC can track the current MPG count
and only apply changes to the enabled axis.
 

"mistakenly called an operating system"

I think the card needs to be installed during the installation.

That way, its kernel module will be loaded during boot-up.
 

You're wrong, so very very wrong.