Using a masso optical encoder with 422

[LordVTP]

Hello!

 I'm attempting to connect a masso optical encoder (Sherline lathe setup) so I can enable threading and while the outputs on the encoder board itself are live and appear to function, No input is registered by the board despite being connected to the "A" "B" "C" terminals.   

Using diagnostics readouts, only thing I can see while turning the spindle is I see pin 13 turning on and off, which is very confusing.

[LordVTP]

Ok I can verify that pulses are going to he input terminals, but I get no response on them in the diagnostics read out and my encoder position never leaves zero.

The encoder outputs 10v as high, is that an issue for the boards inputs?

[Steve Stallings]

The A, B, C inputs on a SmartBOB are designed for "TTL" signals in the 0 to 5 volt range. There is protection provided so a 10 volt signal from the Masso encoder will not harm the input, but I am not sure the input will respond.

In order for the A, B, C, input to respond the signal must be capable of producing a valid logic low signal of less than 1.5 volts and the ground reference of the encoder power supply must be connected to the GND terminal of the encoder connector of the SmartBOB. Be careful that there is no conflict in the ground systems.

You can use the Real-Time Input/Output Status panel provided in the SmartBOB plugin configuration tab in Mach4 to verify that the SmartBOB is able to read these signals.

[LordVTP]

Hey Steve! Good to see you are still around!

So I bought a 4 channel opto isolation board rated for 20k hrz that could accept the 10v encoder pulses and relay with 5v (powered from the board, also meeting the ground plane requirement) and had no luck -
So I purchased a new 416 board and the encoder worked first try, very nice!

Got it going this weekend and now I've run into a new issue-

The test lathe programs I was able to run on the 422 board lock up on the 416 board when it reads a G99, very bizarre. 

I'm using the latest mach4 release 4.2.0.5036 hobby licensed and the current pmdx driver, so I'm not sure where to look further.

[LordVTP]

Figured out the issue!

I didn't have the DRO setup right in the custom screen settings, and the system was waiting for the index rpm calculation to set the real feed rate.