Welcome to LinuxCNC.org

Sorry I think I mentioned it before. I am able to turn on HAL scope. Then when I try to assign a pin to channel 1, it closes and will not open again. Please see errors below:
halscope: could not set record length: 'MAXCHAN 0'
halscope: too many active channels: 'CHAN 2'
halscope: object not found: 'PIN '
halscope: could not set vertical scale: 'VSCALE 0'
halscope: could not set vertical position: 'VPOS 0.500000'
halscope: could not set vertical offset: 'VOFF 0.000000e+00'
halscope: too many active channels: 'CHAN 1'
halscope: could not set vertical scale: 'VSCALE 0'
halscope: could not set vertical position: 'VPOS 0.501441'
halscope: could not set vertical offset: 'VOFF 0.000000e+00'
halscope: config file 'autosave.halscope' caused 10 warnings

maxvdh wrote:
Try deleting autosave.halscope

That's it. Thank you

PCW wrote:
I wonder about this. If one is using a real MPG the count mode is suitable, that is why PNCconf uses it.
if you use quadrature then you can get counts in between the 'detents'
If you MPG is not perfect you can get inconsistent counts for the same 'detent' position.
By using count mode you get one count for every quadrature sequence on an MPG that would be 100 counts
which divides nicely in everything and if your MPG is one quadrature count off at a detent it still outputs consistently.

Is there another reason this is not suitable?

Chris M

cmorley wrote:Counter-mode only counts up in the case of the software counter.
The Mesa encoder is a little different, as that takes the B channel as a direction, and the way quadrature works means that it still works bidirectionally as long as the quadrature is good and the B-phase is connected.

PNCconf does not use software counters. but it is good info that they work differently.