Hi
I'm trying to use an NV9 acceptor on my project.
PayLink doesn't seem to recognize it at start-up. The loom is fine, the acceptor and stacker whirr about on power-on as you'd expect...
The acceptor is programmed with ccTalk firmware, and the cctalk encryption key is 123456, and I have used LuminaSerial.exe to set the same key in the PayLink's memory.
I also have a few NV10s kicking around, and they all do not work either, having checked everything I can think of...
Help!!
Many Thanks
note acceptor not recognised
Moderators: aardvark, davebush, Admin
The obvious problem is that the two are not talking the same protocol 
The easiest solution is that although the acceptor is capable of using cctalk it is chosing not to. On the NV* series there are small switches to chose the protocol, cctalk is usually "special" or "other" - so the first thing is to check is that.
The easiest solution is that although the acceptor is capable of using cctalk it is chosing not to. On the NV* series there are small switches to chose the protocol, cctalk is usually "special" or "other" - so the first thing is to check is that.
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.
Hi Dave
Yes, checking everything included the option switches. Been using NVx products for donkey's years now so none of this is unfamiliar territory.
So, both DILs are set to "special" and the acceptor is loaded with ccTalk firmware. I have a DA2 kit so I can chop & change at liberty. The acceptor is fully working under ITLs software.
This morning I upgraded to the latest driver & dll files for the PayLink (from the previous versions) and no differences noted.
Cheers
Ed
Yes, checking everything included the option switches. Been using NVx products for donkey's years now so none of this is unfamiliar territory.
So, both DILs are set to "special" and the acceptor is loaded with ccTalk firmware. I have a DA2 kit so I can chop & change at liberty. The acceptor is fully working under ITLs software.
This morning I upgraded to the latest driver & dll files for the PayLink (from the previous versions) and no differences noted.
Cheers
Ed
Next thing to try is to run the MilanDiag tool. This picks up the "stream of consciousness" diagnostics output by Paylink. (The same data is available in a less convenient form in the driver window.)
If you can’t see anything meaningful / interesting yourself then please copy it here. A good technique is to clear the window and then reset the unit, so that we capture everything at startup.
If you can’t see anything meaningful / interesting yourself then please copy it here. A good technique is to clear the window and then reset the unit, so that we capture everything at startup.
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.
------------------------------------------------------------------
System Information
------------------------------------------------------------------
AES Intelligent Money Handling Equipment Interface
OS Version 5.1
Checking Driver Files:
Found at: C:\WINDOWS\system32\Drivers\FTD2XX.sys
Timestamp : Fri Apr 29 14:33:42 2005
Checking DLL:
Found at: C:\WINDOWS\system32\AesIMHEI.dll
Timestamp : Tue Jun 24 10:03:30 2008
Version 1,4,0,1
Details on AES Genoa USB Interface Unit
AES Intelligent Money Handling Equpiment:
Interface 6, code version 02010a08
Firmware Release Type: Alpha Test
Firmware Code Version: 1.10.8
------------------------------------------------------------------
Peripheral Information
------------------------------------------------------------------
Dispensers on the system are:
Dispenser 0: MCL Serial Compact Hopper
Coin Value 200, Number Paid 20,
Inhibit 0, Address 9
Acceptors on the system are:
Acceptor 0: MCL SR5, Default Path 5,
Event count 0, Currency <GB>, 16 coins:
Coin 0, Value 100, Count 0, Path 3, Coins 0
Coin 1, Value 50, Count 0, Path 5, Coins 0
Coin 2, Value 20, Count 0, Path 5, Coins 1257
Coin 3, Value 10, Count 0, Path 5, Coins 930
Coin 4, Value 0, Count 0, Path 5, Coins 0
Coin 5, Value 200, Count 0, Path 5, Coins 0
Coin 6, Value 5, Count 0, Path 5, Coins 0
Coin 7, Value 0, Count 0, Path 5, Coins 0
Coin 8, Value 100, Count 0, Path 5, Coins 0
Coin 9, Value 50, Count 0, Path 5, Coins 0
Coin 10, Value 20, Count 0, Path 5, Coins 1
Coin 11, Value 10, Count 0, Path 5, Coins 0
Coin 12, Value 0, Count 0, Path 5, Coins 0
Coin 13, Value 200, Count 0, Path 5, Coins 0
Coin 14, Value 5, Count 0, Path 5, Coins 0
Coin 15, Value 0, Count 0, Path 5, Coins 0
------------------------------------------------------------------
Diagnostic Information
------------------------------------------------------------------
15:36:46.194 00:04
******* System Reset ********
15:36:49.759 k
15:36:50.570 PC: Unknown Set sub-code ff1d received
15:36:50.580 PC: Memory Resynch - new protocol
15:36:50.711 PC: Memory Resynch - new protocol
15:36:50.721 USB: PC Link Up
15:36:50.721 USB: PC Link Up
15:36:50.731 DP: Part: -1, Serial: 116428
15:36:50.981 Exec: DP App. task took 262 msec
15:36:50.981 USB: Chip OK
15:36:50.991 PC: Re-sending restart
15:36:51.011 USB: PC (re)started
15:36:51.021 PC: Memory Resynch - new protocol
15:36:51.031 USB: PC Link Up
15:36:51.071 DP: Interface memory set up
15:36:51.071 Exec: DP App. task took 80 msec
15:36:51.081 Idle: SR5/3 found @ 2
15:36:51.251 DP: Interface memory set up
15:36:51.251 PC: Update @0, 12345678=>aa8d4a8c
15:36:51.251 PC: Update @464, b60=>0
15:36:51.251 PC: Update @468, e4c=>0
15:36:51.251 PC: Update @b68, 2020103=>0
15:36:51.251 PC: Update @b6c, 4=>0
15:36:51.251 PC: Update @b70, 10=>0
15:36:51.251 PC: Update @b74, 2=>0
15:36:51.251 PC: Update @b78, 2=>0
15:36:51.251 PC: Update @b7c, 5=>0
15:36:51.251 PC: Update @b84, 4247=>0
15:36:51.251 PC: Update @b88, b8c=>0
15:36:51.251 PC: Update @b8c, bb8=>0
15:36:51.251 PC: Update @b94, 64=>0
15:36:51.251 PC: Update @ba0, 3=>0
15:36:51.251 PC: Update @bb8, be4=>0
15:36:51.251 PC: Update @bc0, 32=>0
15:36:51.251 PC: Update @bcc, 5=>0
15:36:51.251 PC: Update @be4, c10=>0
15:36:51.251 PC: Update @bec, 14=>0
15:36:51.251 PC: Update @bf8, 5=>0
15:36:51.251 PC: Update @bfc, 4e9=>0
15:36:51.251 PC: Update @c10, c3c=>0
15:36:51.251 PC: Update @c18, a=>0
15:36:51.251 PC: Update @c24, 5=>0
15:36:51.251 PC: Update @c28, 3a2=>0
15:36:51.251 PC: Update @c3c, c68=>0
15:36:51.251 PC: Update @c50, 5=>0
15:36:51.251 PC: Update @c68, c94=>0
15:36:51.251 PC: Update @c70, c8=>0
15:36:51.251 PC: Update @c7c, 5=>0
15:36:51.251 PC: Update @c94, cc0=>0
15:36:51.251 PC: Update @c9c, 5=>0
15:36:51.251 PC: Update @ca8, 5=>0
15:36:51.251 PC: Update @cc0, cec=>0
15:36:51.251 PC: Update @cd4, 5=>0
15:36:51.251 PC: Update @cec, d18=>0
15:36:51.251 PC: Update @cf4, 64=>0
15:36:51.251 PC: Update @d00, 5=>0
15:36:51.251 PC: Update @d18, d44=>0
15:36:51.251 PC: Update @d20, 32=>0
15:36:51.251 PC: Update @d2c, 5=>0
15:36:51.251 PC: Update @d44, d70=>0
15:36:51.251 PC: Update @d4c, 14=>0
15:36:51.251 PC: Update @d58, 5=>0
15:36:51.251 PC: Update @d5c, 1=>0
15:36:51.251 PC: Update @d70, d9c=>0
15:36:51.251 PC: Update @d78, a=>0
15:36:51.251 PC: Update @d84, 5=>0
15:36:51.251 PC: Update @d9c, dc8=>0
15:36:51.251 PC: Update @db0, 5=>0
15:36:51.251 PC: Update @dc8, df4=>0
15:36:51.251 PC: Update @dd0, c8=>0
15:36:51.251 PC: Update @ddc, 5=>0
15:36:51.251 PC: Update @df4, e20=>0
15:36:51.251 PC: Update @dfc, 5=>0
15:36:51.251 PC: Update @e08, 5=>0
15:36:51.251 PC: Update @e34, 5=>0
15:36:51.251 PC: Update @e54, 1020101=>0
15:36:51.251 PC: Update @e58, 1=>0
15:36:51.251 PC: Update @e5c, 2=>0
15:36:51.251 PC: Update @e60, 9=>0
15:36:51.251 PC: Update @e64, c8=>0
15:36:51.251 PC: Update @e68, 14=>0
15:36:51.251 PC: Update @e78, 1=>0
15:36:51.251 PC: Transfer Reset
15:36:51.251 PC: USB unit re-synch complete
15:36:51.251 Exec: DP App. task took 170 msec
15:36:51.251 9692 bytes memory free
15:36:51.291 Coin: SR5 Acceptor S/N 55426 found!
15:36:51.351 Coin: Selftest OK
15:36:51.392 Coin: 1 <GB100A>, , value 100
15:36:51.442 Coin: 2 <GB050B>, , value 50
15:36:51.482 Coin: 3 <GB020A>, , value 20
15:36:51.532 Coin: 4 <GB010B>, , value 10
15:36:51.572 Coin: 5 <Token >, , not valid
15:36:51.612 Coin: 6 <GB200A>, , value 200
15:36:51.662 Coin: 7 <GB005B>, , value 5
15:36:51.702 Coin: 8 <......>, , not valid
15:36:51.752 Coin: 9 <GB100A>, , value 100
15:36:51.792 Coin: 10 <GB050B>, , value 50
15:36:51.842 Coin: 11 <GB020A>, , value 20
15:36:51.882 Coin: 12 <GB010B>, , value 10
15:36:51.932 Coin: 13 <Token >, , not valid
15:36:51.972 Coin: 14 <GB200A>, , value 200
15:36:52.012 Coin: 15 <GB005B>, , value 5
15:36:52.062 Coin: 16 <......>, , not valid
15:36:52.103 Coin: 1 path: 3
15:36:52.133 Coin: 2 path: 5
15:36:52.173 Coin: 3 path: 5
15:36:52.213 Coin: 4 path: 5
15:36:52.253 Coin: 5 path: 5
15:36:52.283 Coin: 6 path: 5
15:36:52.323 Coin: 7 path: 5
15:36:52.363 Coin: 8 path: 5
15:36:52.403 Coin: 9 path: 5
15:36:52.443 Coin: 10 path: 5
15:36:52.473 Coin: 11 path: 5
15:36:52.513 Coin: 12 path: 5
15:36:52.553 Coin: 13 path: 5
15:36:52.593 Coin: 14 path: 5
15:36:52.633 Coin: 15 path: 5
15:36:52.673 Coin: 16 path: 5
15:36:52.693 Coin: Cashbox path is 5
15:36:52.854 DP: ccTalk coin acceptor 2020103 at b60 added
15:36:52.854 Exec: cctalk task took 69 msec
15:36:53.515 Idle: Hopper for 200 found @ 9
15:36:53.535 ccHopper: Save slot 1 found for hopper @ 9
15:36:53.535 Exec: cctalk task took 14 msec
15:36:53.595 DP: SCH2-USE_SERNR Hopper S/N 624140, Address 9, Value 200 at e4c added
15:36:53.645 ccHopper: 4 byte dispense!
15:36:53.665 ccHopper: @ 9, Hopper count 20,OK
15:36:53.865 Coin: extracted path overrides 7f
15:36:53.865 Coin: Inhibit all coins
15:36:56.739 9492 bytes memory free
15:36:58.852 ccHopper: @ 9, Selftest OK
------------------------------------------------------------------
System Information
------------------------------------------------------------------
AES Intelligent Money Handling Equipment Interface
OS Version 5.1
Checking Driver Files:
Found at: C:\WINDOWS\system32\Drivers\FTD2XX.sys
Timestamp : Fri Apr 29 14:33:42 2005
Checking DLL:
Found at: C:\WINDOWS\system32\AesIMHEI.dll
Timestamp : Tue Jun 24 10:03:30 2008
Version 1,4,0,1
Details on AES Genoa USB Interface Unit
AES Intelligent Money Handling Equpiment:
Interface 6, code version 02010a08
Firmware Release Type: Alpha Test
Firmware Code Version: 1.10.8
------------------------------------------------------------------
Peripheral Information
------------------------------------------------------------------
Dispensers on the system are:
Dispenser 0: MCL Serial Compact Hopper
Coin Value 200, Number Paid 20,
Inhibit 0, Address 9
Acceptors on the system are:
Acceptor 0: MCL SR5, Default Path 5,
Event count 0, Currency <GB>, 16 coins:
Coin 0, Value 100, Count 0, Path 3, Coins 0
Coin 1, Value 50, Count 0, Path 5, Coins 0
Coin 2, Value 20, Count 0, Path 5, Coins 1257
Coin 3, Value 10, Count 0, Path 5, Coins 930
Coin 4, Value 0, Count 0, Path 5, Coins 0
Coin 5, Value 200, Count 0, Path 5, Coins 0
Coin 6, Value 5, Count 0, Path 5, Coins 0
Coin 7, Value 0, Count 0, Path 5, Coins 0
Coin 8, Value 100, Count 0, Path 5, Coins 0
Coin 9, Value 50, Count 0, Path 5, Coins 0
Coin 10, Value 20, Count 0, Path 5, Coins 1
Coin 11, Value 10, Count 0, Path 5, Coins 0
Coin 12, Value 0, Count 0, Path 5, Coins 0
Coin 13, Value 200, Count 0, Path 5, Coins 0
Coin 14, Value 5, Count 0, Path 5, Coins 0
Coin 15, Value 0, Count 0, Path 5, Coins 0
------------------------------------------------------------------
Diagnostic Information
------------------------------------------------------------------
15:36:46.194 00:04
******* System Reset ********
15:36:49.759 k
15:36:50.570 PC: Unknown Set sub-code ff1d received
15:36:50.580 PC: Memory Resynch - new protocol
15:36:50.711 PC: Memory Resynch - new protocol
15:36:50.721 USB: PC Link Up
15:36:50.721 USB: PC Link Up
15:36:50.731 DP: Part: -1, Serial: 116428
15:36:50.981 Exec: DP App. task took 262 msec
15:36:50.981 USB: Chip OK
15:36:50.991 PC: Re-sending restart
15:36:51.011 USB: PC (re)started
15:36:51.021 PC: Memory Resynch - new protocol
15:36:51.031 USB: PC Link Up
15:36:51.071 DP: Interface memory set up
15:36:51.071 Exec: DP App. task took 80 msec
15:36:51.081 Idle: SR5/3 found @ 2
15:36:51.251 DP: Interface memory set up
15:36:51.251 PC: Update @0, 12345678=>aa8d4a8c
15:36:51.251 PC: Update @464, b60=>0
15:36:51.251 PC: Update @468, e4c=>0
15:36:51.251 PC: Update @b68, 2020103=>0
15:36:51.251 PC: Update @b6c, 4=>0
15:36:51.251 PC: Update @b70, 10=>0
15:36:51.251 PC: Update @b74, 2=>0
15:36:51.251 PC: Update @b78, 2=>0
15:36:51.251 PC: Update @b7c, 5=>0
15:36:51.251 PC: Update @b84, 4247=>0
15:36:51.251 PC: Update @b88, b8c=>0
15:36:51.251 PC: Update @b8c, bb8=>0
15:36:51.251 PC: Update @b94, 64=>0
15:36:51.251 PC: Update @ba0, 3=>0
15:36:51.251 PC: Update @bb8, be4=>0
15:36:51.251 PC: Update @bc0, 32=>0
15:36:51.251 PC: Update @bcc, 5=>0
15:36:51.251 PC: Update @be4, c10=>0
15:36:51.251 PC: Update @bec, 14=>0
15:36:51.251 PC: Update @bf8, 5=>0
15:36:51.251 PC: Update @bfc, 4e9=>0
15:36:51.251 PC: Update @c10, c3c=>0
15:36:51.251 PC: Update @c18, a=>0
15:36:51.251 PC: Update @c24, 5=>0
15:36:51.251 PC: Update @c28, 3a2=>0
15:36:51.251 PC: Update @c3c, c68=>0
15:36:51.251 PC: Update @c50, 5=>0
15:36:51.251 PC: Update @c68, c94=>0
15:36:51.251 PC: Update @c70, c8=>0
15:36:51.251 PC: Update @c7c, 5=>0
15:36:51.251 PC: Update @c94, cc0=>0
15:36:51.251 PC: Update @c9c, 5=>0
15:36:51.251 PC: Update @ca8, 5=>0
15:36:51.251 PC: Update @cc0, cec=>0
15:36:51.251 PC: Update @cd4, 5=>0
15:36:51.251 PC: Update @cec, d18=>0
15:36:51.251 PC: Update @cf4, 64=>0
15:36:51.251 PC: Update @d00, 5=>0
15:36:51.251 PC: Update @d18, d44=>0
15:36:51.251 PC: Update @d20, 32=>0
15:36:51.251 PC: Update @d2c, 5=>0
15:36:51.251 PC: Update @d44, d70=>0
15:36:51.251 PC: Update @d4c, 14=>0
15:36:51.251 PC: Update @d58, 5=>0
15:36:51.251 PC: Update @d5c, 1=>0
15:36:51.251 PC: Update @d70, d9c=>0
15:36:51.251 PC: Update @d78, a=>0
15:36:51.251 PC: Update @d84, 5=>0
15:36:51.251 PC: Update @d9c, dc8=>0
15:36:51.251 PC: Update @db0, 5=>0
15:36:51.251 PC: Update @dc8, df4=>0
15:36:51.251 PC: Update @dd0, c8=>0
15:36:51.251 PC: Update @ddc, 5=>0
15:36:51.251 PC: Update @df4, e20=>0
15:36:51.251 PC: Update @dfc, 5=>0
15:36:51.251 PC: Update @e08, 5=>0
15:36:51.251 PC: Update @e34, 5=>0
15:36:51.251 PC: Update @e54, 1020101=>0
15:36:51.251 PC: Update @e58, 1=>0
15:36:51.251 PC: Update @e5c, 2=>0
15:36:51.251 PC: Update @e60, 9=>0
15:36:51.251 PC: Update @e64, c8=>0
15:36:51.251 PC: Update @e68, 14=>0
15:36:51.251 PC: Update @e78, 1=>0
15:36:51.251 PC: Transfer Reset
15:36:51.251 PC: USB unit re-synch complete
15:36:51.251 Exec: DP App. task took 170 msec
15:36:51.251 9692 bytes memory free
15:36:51.291 Coin: SR5 Acceptor S/N 55426 found!
15:36:51.351 Coin: Selftest OK
15:36:51.392 Coin: 1 <GB100A>, , value 100
15:36:51.442 Coin: 2 <GB050B>, , value 50
15:36:51.482 Coin: 3 <GB020A>, , value 20
15:36:51.532 Coin: 4 <GB010B>, , value 10
15:36:51.572 Coin: 5 <Token >, , not valid
15:36:51.612 Coin: 6 <GB200A>, , value 200
15:36:51.662 Coin: 7 <GB005B>, , value 5
15:36:51.702 Coin: 8 <......>, , not valid
15:36:51.752 Coin: 9 <GB100A>, , value 100
15:36:51.792 Coin: 10 <GB050B>, , value 50
15:36:51.842 Coin: 11 <GB020A>, , value 20
15:36:51.882 Coin: 12 <GB010B>, , value 10
15:36:51.932 Coin: 13 <Token >, , not valid
15:36:51.972 Coin: 14 <GB200A>, , value 200
15:36:52.012 Coin: 15 <GB005B>, , value 5
15:36:52.062 Coin: 16 <......>, , not valid
15:36:52.103 Coin: 1 path: 3
15:36:52.133 Coin: 2 path: 5
15:36:52.173 Coin: 3 path: 5
15:36:52.213 Coin: 4 path: 5
15:36:52.253 Coin: 5 path: 5
15:36:52.283 Coin: 6 path: 5
15:36:52.323 Coin: 7 path: 5
15:36:52.363 Coin: 8 path: 5
15:36:52.403 Coin: 9 path: 5
15:36:52.443 Coin: 10 path: 5
15:36:52.473 Coin: 11 path: 5
15:36:52.513 Coin: 12 path: 5
15:36:52.553 Coin: 13 path: 5
15:36:52.593 Coin: 14 path: 5
15:36:52.633 Coin: 15 path: 5
15:36:52.673 Coin: 16 path: 5
15:36:52.693 Coin: Cashbox path is 5
15:36:52.854 DP: ccTalk coin acceptor 2020103 at b60 added
15:36:52.854 Exec: cctalk task took 69 msec
15:36:53.515 Idle: Hopper for 200 found @ 9
15:36:53.535 ccHopper: Save slot 1 found for hopper @ 9
15:36:53.535 Exec: cctalk task took 14 msec
15:36:53.595 DP: SCH2-USE_SERNR Hopper S/N 624140, Address 9, Value 200 at e4c added
15:36:53.645 ccHopper: 4 byte dispense!
15:36:53.665 ccHopper: @ 9, Hopper count 20,OK
15:36:53.865 Coin: extracted path overrides 7f
15:36:53.865 Coin: Inhibit all coins
15:36:56.739 9492 bytes memory free
15:36:58.852 ccHopper: @ 9, Selftest OK
------------------------------------------------------------------
The "interesting" thing is that the Coin Mech and hoppers work!
If this was on my desk, I'd be concentrating on the key. Are you **positive** that both the Acceptor and Paylink are using 123456?
(If you use LuminaSerial.exe to set it while the diagnostics are being captured, you'll see Paylink message regarding the change.)
If this was on my desk, I'd be concentrating on the key. Are you **positive** that both the Acceptor and Paylink are using 123456?
(If you use LuminaSerial.exe to set it while the diagnostics are being captured, you'll see Paylink message regarding the change.)
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.
Hi Dave
Yup, did that, checked the encryption key on the acceptor is 123456, and used LuminaSerial.exe as you suggested.
I got the lines:
09:44:36.786 Changing BNV s/n to 123456 (BCD)
09:44:36.786 Saving serial number to E2PROM...
09:44:36.786 Reloading...
09:44:36.796 Saved serial number is 123456
09:44:36.806 Exec: DP App. task took 19 msec
09:44:36.936 9264 bytes memory free
So that looks OK to me.
Just to verify, the ITL software reports the ccTalk device address as 40 and that encryption is active.
I also disabled encryption on the acceptor and tried again, and nothing different happened. It's just like it doesn't know anything is there...not even responding to a simple poll?!
I'm at my wits end on this!
Cheers
Yup, did that, checked the encryption key on the acceptor is 123456, and used LuminaSerial.exe as you suggested.
I got the lines:
09:44:36.786 Changing BNV s/n to 123456 (BCD)
09:44:36.786 Saving serial number to E2PROM...
09:44:36.786 Reloading...
09:44:36.796 Saved serial number is 123456
09:44:36.806 Exec: DP App. task took 19 msec
09:44:36.936 9264 bytes memory free
So that looks OK to me.
Just to verify, the ITL software reports the ccTalk device address as 40 and that encryption is active.
I also disabled encryption on the acceptor and tried again, and nothing different happened. It's just like it doesn't know anything is there...not even responding to a simple poll?!
I'm at my wits end on this!
Cheers
I agree - there's not much left.
1/ Paylink supports Encryption+CRC or Normal+Checksum - you may have set up Non-encrypted+CRC which we don't support.
2/ If that doesn't help, I'd suggest check out the LEDs on the NV10 and then try talking to Innovative - support@innovative-technology.co.uk
1/ Paylink supports Encryption+CRC or Normal+Checksum - you may have set up Non-encrypted+CRC which we don't support.
2/ If that doesn't help, I'd suggest check out the LEDs on the NV10 and then try talking to Innovative - support@innovative-technology.co.uk
Aardvark software developer. Please put all communication on the problem through the board for the benefit of others.
Hi Dave
Progress!
For some reason the loom was slightly incorrect, having the RX line one pin off, now corrected.
But no luck with the NV9 still...however the NV10 acceptor is recognized without a problem!
So I have checked the NV9 settings, and they are the same as the NV10 so (in theory at least) it should work. The NV9 works under the Innovative software so I am sure the acceptor hasn't been destroyed by all the fiddling around.
All that is left to do is re-program the NV9 with the firmware (maybe corrupted?!). If that doesn't work......no idea...
Cheers
Progress!
For some reason the loom was slightly incorrect, having the RX line one pin off, now corrected.
But no luck with the NV9 still...however the NV10 acceptor is recognized without a problem!
So I have checked the NV9 settings, and they are the same as the NV10 so (in theory at least) it should work. The NV9 works under the Innovative software so I am sure the acceptor hasn't been destroyed by all the fiddling around.
All that is left to do is re-program the NV9 with the firmware (maybe corrupted?!). If that doesn't work......no idea...
Cheers
