Can´t get NPVR - NEWCS - ACAMD to work
|
2011-02-10, 09:33 PM
You really should download the correct driver from AD-Teknik, I beleive it's vital. My card runs with parity EVEN, Stopbits=1, mhz=368 and Reset=normal. You can skip Pincode and you don't need to enable radegastserver. In addition, look in Device Manager and see if your Com6 is set to 9600, Even and 7 databits (port settings should be the same as set in newcs.xml).
"I'd rather have a bottle in front of me than a frontal lobotomy"
2011-02-11, 07:56 AM
If I remember win7 actually installs a driver for the device. It may be sufficient, but I too chose another driver. Actually a much newer driver is available from the chip manufacturer. I do not have the url right now, but looking in the device manager for the device name and googling for it helps.
Second, I am not sure if fiddling with the settings for the COM device actually does anything. I believe that newCS sets the comunication parameters according to its config. One thing though that looked wrong was reset, that should be "normal". Normal = phoenix mode, Inverse = Smartmouse mode. One thing in particular that need to be asked. Andcar, did you put the card in with the chip facing the right way? Tried turning it around? Could it be that simple?
2011-02-11, 08:03 AM
Barsk Wrote:If I remember win7 actually installs a driver for the device. It may be sufficient, but I too chose another driver. Actually a much newer driver is available from the chip manufacturer. I do not have the url right now, but looking in the device manager for the device name and googling for it helps. On my win7 NewCS did not set the parameters to the port itselv, well maybe it was done internally but when I checked it still stood with wrong bitrate and parity. What seeme clear to me is that Andcar has a problem communicating with the smartcard. The card may as well be turned the wrong way :p Edit: The chip manufacturers driver does not nessesarily fit the reader, it depends what AD-Teknik has done around the chip. That may be why thei have their own driver. "I'd rather have a bottle in front of me than a frontal lobotomy"
2011-02-11, 08:41 AM
I will try setting the COM port differently and see if actually has som impact, or if newCS sets the parameters regardless.
The driver is of the same manufacturer and version-scheme. AD-tekniks driver is a bit older than the newer from the manufacturer otherwise they seems identical. I have tried both the AD-teknik and the manufacturer (newer) driver and they behaved identically. The release notes on the newer driver mentions fixing a number of bugs which may or may not help your installation.
2011-02-11, 09:55 AM
barsk Wrote:the release notes on the newer driver mentions fixing a number of bugs which may or may not help your installation. url? "I'd rather have a bottle in front of me than a frontal lobotomy"
2011-02-13, 09:44 AM
The manufacturer is FTDI and the URL to drivers is:
http://www.ftdichip.com/Drivers/VCP.htm
2011-02-13, 11:37 AM
Barsk Wrote:The manufacturer is FTDI and the URL to drivers is: Thanks, I'll give it a go. Any news from Andcar? "I'd rather have a bottle in front of me than a frontal lobotomy"
2011-02-13, 04:22 PM
Barsk Wrote:I will try setting the COM port differently and see if actually has som impact, or if newCS sets the parameters regardless.Tried setting the default values from device manager all wrong and then restarting newCS. No difference, it still worked. So it seems the default setting to the serial port has NO impact on newCS. newCS programs the port with the settings from its config file.
2011-02-13, 05:48 PM
Barsk Wrote:Tried setting the default values from device manager all wrong and then restarting newCS. No difference, it still worked. Is this on W7 or XP? "I'd rather have a bottle in front of me than a frontal lobotomy" |
|
|
