Encoder Problems after update???

[Lucario231]

I have tried moving it in to begin.vi and had the same problem.

[Mark McLeod]

Where do you Open the DIO's?

Where do you Configure the Timer?

P.S. Take a look at the LabVIEW Encoder Example accessible from the Getting Started window.

[Lucario231]

Ok i am looking at the example and I am still lost.
So I need to do these DIO opens?? and the timer config??

In past versions aka 8.5.1 and before update 2.1, I never needed to do DIO and timer before.

[Mark McLeod]

That Encoder example is from 2009.
It isn't new.

[R2D2DOC]

Hello,

If this is 2009 code in the example, is it still valid for 2010? We have the next version of Labview, 8.6 and update 2.1. We never did anything this elaborate in 2009 to have the encoders operate.

So from the far left through Start Encoder is in BEGIN.
Use the DevRef to go from BEGIN to TELEOP and BEGIN to AUTON.

We'll give it a try. . .

[Mark McLeod]

Originally Posted by R2D2DOC

So from the far left through Start Encoder is in BEGIN.
Use the DevRef to go from BEGIN to TELEOP and BEGIN to AUTON.

We'll give it a try. . .

That's a correct division into the vi's.
I can't comment on what you may have done in the past. Sometimes, system defaults get you through, and sometimes they don't.

We can always try

[Lucario231]

I am still having problems and can't read the encoders. I have the begin code and telop attached. I don't see what I am doing wrong.

Any advice will be helpful

[Mark McLeod]

Nothing else with a conflict for DIO 1-4?
For instance, an old default compressor lying around?

[Lucario231]

There is no other DIO using 1-4.

Is my sequence correct in begin?

I have all of the updates installed. Do you guys have them installed and working?
The updates i put in are up to 2.1 and 1.1 in the DS. Could I be missing anything?

Could anyone display their code with begin and telop and auto that is relevant to encoders?

[Mark McLeod]

Tomorrow I can pull and retest a working example and post the full project as a test if you need it.

The LabVIEW example is also a working test case for you. You can run that to see if it has better luck with your first encoder.

P.S. What model encoder are you using? Did you double-check the pinout?

[Mark McLeod]

I ran the Encode Example as-is, and changed the IP of course, but nothing else.
Hooked up a VEX quad encoder to DIO 1 & 2.

It works fine counting up and down on the front panel display.

cRIO V20, LabVIEW Update 2.1
No Driver Station app. needs to be running for this particular test.

-------------------

If the above doesn't work for you, then I'd try a different encoder you can use just as an unmounted test case, and look closely at the wiring.
Did your electrical team use a scope when they tested the encoders before?
Did they test at the encoder end or at the DIO end of the connecting cable?

Or throw your zipped project up here so we can see what might be hidden and interfering.

[Alan Anderson]

Originally Posted by Lucario231

Is my sequence correct in begin?

It looks right to me. I'm a little confused by the short stubs of wires visible on the error in and out of the Right Encoder's Refnum Get in Teleop, though.

One more thing to check -- look at the DIO status on the Dashboard and see if DIO 1-4 change as you turn the encoders. That will help determine whether they are wired properly. (The Dashboard DIO lights only update twice a second by default, so don't expect them to react quickly.)

[Mark McLeod]

Originally Posted by Alan Anderson

I'm a little confused by the short stubs of wires visible on the error in and out of the Right Encoder's Refnum Get in Teleop, though.

The cursor was resting on that icon when the screen capture was taken, so LabVIEW was highlighting the unattached nubs. Print Screen just doesn't grab the cursor overlay.

[R2D2DOC]

Just to close this thread. . .

As you know we are all busy finishing build and preparing for competitions. We did an audit of the Crio. First we moved all data streams to SLOT 6 and everything worked. Went back and looked at SLOT 4. Turns out that there was a bent pin in the 9pin D connector on the cRIO backplane. After straightening it, no problems.

Thanks for your time and all of your suggestions.

IT AIN'T ALWAYS THE SOFTWARE. . .

[Alan Anderson]

Originally Posted by Lucario231

So I need to do these DIO opens??

Emphatically YES.

Open a DIO input for each of the A and B channels and run each device reference through a DigSrc to the appropriate input of the Encoder Open.

(Tracing through the library code, it looks like the DIOs are closed for you when you do an Encoder Close, so I don't think you will need to close them explicitly.)