New to working with NI Daq and im seeing something i dont fully understand

[cron]

I'm working with a USB-6210 and a usb-6421. from the clsaquire class I can run GetCount and get an accurate location from my 6210 from a quad encoder. However when I try this on my 6421, I only get a 1 or 0 back. I have read that this can be because of the hardware encoding and counting features on the 6421 but i cannot find anything which states why this would work the same as the 6210. Can someone point me in the right direction to explain this issue here?  
Thanks Ron

[JB]

To identify the cause of the problem, I suggest starting with a functional check with Measurement And Automation Explorer.

[cron]

This didn't tell me what i was looking for. I am trying to figure out why creating a task programmatically on the USB-6421 isn't working the same was as the USB-6210. Instead of returning the count it only returns 1 and 0. I just don't see why there is a difference in any documentation.

DAQmxCreateCILinEncoderChan(encoderTask, DevName & "/ctr0", "", DAQmx_Val_EncoderType2_X1, False, 0, DAQmx_Val_EncoderZIndexPhase1_AHighBHigh, DAQmx_Val_LengthUnits3_Ticks, 1, resetCount, "") this is what i used before. when i used DAQmxReadCounterF64 on the USB-6210 it returned a count. when i used it on the USB-6421, it only returns 1 or 0.

[Kevin_Price]

I don't know details of your text language API syntax and am reading between the lines quite a bit, but...

I have a suspicion that your Z-index terminal is always in high state.  This *might* be the default state when not wired and driven.  And both the default terminal and its default state might be different across your two devices.

Try X4 encoding mode and see if your values vary from 0-3.  If so, my suspicion is more likely correct.

Here's what'd be going on.  In X1 mode, the internal count increments (or decrements) by one for every full quadrature cycle of 4 states.  (I kinda suspect it might happen on rising edge of A, but can't vouch for that.)  But you also reset the count back to 0 whenever Z-index is high AND both A&B are high.  This happens once per cycle.  So you keep incrementing, resetting, incrementing, resetting and the count value toggles between 0 and 1.

X4 mode would increment (or decrement) for each of the 4 quadrature states, so you might see something like 1,2,3,0,1,2,3,0,1,2...

ACTION: make *sure* the encoder's z-index pulse is wired to the correct terminal and that the encoder's z-index signal is normally low with a single pulse high for 1 quad state once per rev.   Or for troubleshooting, stop enabling the z-index reset behavior of your encoder task.

-Kevin P