Not Aardwark flag / No working PCI card found

jlevin · Post by **jlevin** » Wed Apr 15, 2009 1:09 pm

My Milan card is reported by windows as operational but AesTest.exe says that is can't find any working PCI cards:

AES Intelligent Money Handling Equipment Interface
OS Version 5.1
Checking Driver File:
Found at: C:\WINDOWS\System32\Drivers\AesIMHEI.sys
Timestamp : Tue Apr 14 13:39:52 2009

Checking DLL:
Found at: C:\WINDOWS\System32\AesIMHEI.dll
Timestamp : Tue Apr 14 13:39:52 2009
Version 1,4,0,2

Checking Device Access:
Device Aeimhei-0 found in slot 7
770e0000 found - Not Aardvark flag
No working PCI card found

Checking Application access through DLL:
*** Error <31> from DLL Open

End of Tests

I have two cards marked "Milan PCI Interface Revision 1.1" with a sticker labeled "VERSION 1.8.14" and I have tested them in in two different machines and I always get the same error (except 770e0000 is something different for the other card).

My problem is very similar to the one described in this forum post but since I have the exact same problem with two independent cards I doubt that both have a broken firmware and I have double checked that the power supply is working.

What could I be doing wrong? Is there any use trying to manufacture a cable to replace the firmware?

davebush · Post by **davebush** » Thu Apr 16, 2009 11:56 am

It's not clear from your power supply comment that you've understood the power requirements.

The PCI card internals are powered by using one of the 4 wire power connectors inside the PC case, intended for plugging into a hard disc drive, and plugging that connector into the socket on the inside edge of the PCI card.

Assuming that you have done that and the unit isn't working, then constructing a programming cable is probably worthwhile.

jlevin · Post by **jlevin** » Fri Apr 17, 2009 9:49 am

It's not clear from your power supply comment that you've understood the power requirements.

I have attached one of the four-pin power connectors that are used for optical drives and HDDs to the card and I have measured the voltages to be correct as well. (+5V at one edge, +12 at the other edge and Gnd at the two middle pins.)

The reason I didn't believe the firmware was bad was that I had two cards and both have the exact same problem. One of the cards was brand new - I unpacked it from the anti-static bag that it was delivered in just this week.

I am running out of ideas so I guess I will have to try to replace the firmware. If you can think of something else that may be wrong then please let me know.

davebush · Post by **davebush** » Mon Apr 20, 2009 9:53 am

I have attached one of the four-pin power connectors that are used for optical drives and HDDs to the card and I have measured the voltages to be correct as well. (+5V at one edge, +12 at the other edge and Gnd at the two middle pins.)

That's it.

I'm lost as to what's wrong. I'd try using the cable next. Even without the programming connection, Hyperterm etc. should let you talk to the on board diagnostics.

jlevin · Post by **jlevin** » Mon Apr 20, 2009 1:34 pm

Replacing the firmware helped. Weird how both cards had broken firmwares, though. One of them was new out of the box...

Now it works anyways. Thanks.

davebush · Post by **davebush** » Mon Apr 20, 2009 2:08 pm

Glad to hear it.

Please let me know if you get any other problems.