adaencoder and HDD motor

Dear All.

I learn about the adaemcoder library Google Code Archive - Long-term storage for Google Code Project Hosting.

It attract me since it use PinChangeInt, very blessing for 328 based board user.

I want to use my HDD motor as the encoder .... copy cating http://www.instructables.com/id/HDDJ-Turning-an-old-hard-disk-drive-into-a-rotary/

The problem is the fact that HDD motor have 4 pins rather than 3.
Is there any work around that can turn this HDD motor tobe 3 pin encoder

Sincerely
-bino-

The problem is the fact that HDD motor have 4 pins rather than 3.

That's what the article explains. Because from the 3 signals you get 1 is always the negated signal of another pin, 2 are enough for this use case. So you have 3 signals and one ground makes a total of 4. Have you read the whole article or just the first step?

Dear Pylon

Thankyou for your warn ... i'll back to the article.

-bino-

I'm back from the article.

At Step#4 ( I read it before starting this thread) there is 3 Signal from schematic.
adaencoder library only take 2.

Is there any work around ?

-bino-

As you can see in the picture below the schematics two signals are the negated signal of each other. You can eliminate one of them and still have the information you need for a rotary encoder.

I'm sure this one a silly question : What is 'negated signal' ?

From the schematic : Which one is negated by which one ?

Sincerely
-bino-

What is 'negated signal' ?

There are no silly questions if you don't know something. A negated signal is always the opposite of the other one, meaning when signal A is HIGH, the negated signal is LOW and when signal A is LOW, the negated signal is HIGH.

From the schematic : Which one is negated by which one ?

Unfortunately this doesn't get clear from the article. I would just try and attach a scope to two pins. The scope output will show you quickly which are the right ones. Probably this changes from one drive manufacturer to the other, so you have to check anyway.

Dear pylon
I really appreciate your enlightment

pylon:
Unfortunately this doesn't get clear from the article. I would just try and attach a scope to two pins. The scope output will show you quickly which are the right ones. Probably this changes from one drive manufacturer to the other, so you have to check anyway.

Well ... I remember some one give me NanoDSO, but I never learn about it yet.
But internet lead me back to this forum, specialy :
http://arduino.cc/forum/index.php/topic,16497.0.html

I will work from there.

Sincerely
-bino-