No detect device cctalk

[xagduran]

Hello:
Why does Cctalk not detect the device?
Lines in the standard.cfg file
Protocol cctalk on connector cctalk
ICT Recycler at 40 CRC BNV 123456

The device is an ICT BR2300

Firmware Release Type: Full
Firmware Code Version: 1.12.14


******* System Reset ********

22:38:10.576 k
22:38:11.408 FTDI Chip recovery
22:38:11.408 USB: Genoa Recovery: Reset Device 4/4
22:38:11.692 Genoa Closed
22:38:11.710 No matching USB Device
22:38:12.316 USB: Unit 0, ID: 0x0403 0xde50
22:38:12.316 Description: Genoa
22:38:12.316 Serial No: AE000001
22:38:12.331 Type: Revision 4 (USB Powered)
22:38:12.331 Latency: 16
22:38:12.331 USB: Genoa Recovery: Opened 0/0
22:38:12.331 Recovery: 5087661 Fixed!
22:38:13.634 Configuration
22:38:13.634 cctalk protocol on port 0
22:38:13.666 ICT Recycler at 40
22:38:13.697 API: ccNote Pre reg, Addr 40
22:38:13.744 MDB protocol on port 3
22:38:13.776 Changer at 8
22:38:13.792 API: MDB Pre reg, Addr 8
22:38:13.839 === End ===
22:38:13.917 SEC Meter
22:38:13.917 Port 0 - cctalk protocol
22:38:13.917 Port 1 - unused
22:38:13.917 Port 2 - defaulted to monitor
22:38:13.917 Port 3 - MDB protocol
22:38:13.917 API: Part: -1, Serial: 32303
22:38:14.027 Exec: API task took 125 msec
22:38:14.027 Config: Start of download
22:38:14.059 Config: Checked, OK
22:38:14.059 Config: Paylink Checked OK against file "Standard.cfg"
22:38:14.059 Exec: USB task took 27 msec
22:38:14.059 MDB: Reply < 7 bytes
22:38:14.075 PC: Memory Resynch - new protocol
22:38:14.075 MDB: Level 3, Currency 978
22:38:14.122 MDB: Coin 1, value 5, to tube 1
22:38:14.122 MDB: Coin 2, value 10, to tube 2
22:38:14.122 MDB: Coin 3, value 20, to tube 3
22:38:14.122 MDB: Coin 4, value 50, to tube 4
22:38:14.122 MDB: Coin 5, value 100, to tube 5
22:38:14.122 MDB: Coin 6, value 200, to tube 6
22:38:14.122 Exec: MDB task took 30 msec
22:38:14.279 API: ccNote acceptor 12020000 at ba0 setup
22:38:14.310 API: MDB acceptor 2080000 at bdc setup
22:38:14.593 APIPC: Update @0, 12345678=>0
22:38:14.593 PC: Input Update @468, d9c=>0
22:38:14.593 PC: Input Update @46c, 4=>1
22:38:14.593 PC: Input Update PayValue 800, Old 800
22:38:14.593 PC: Update @be8, 4=>45
22:38:14.593 PC: Update @bec, 6=>0
22:38:14.593 PC: Update @c04, c1c=>0
22:38:14.593 PC: Update @c08, 68b50f4e=>5f5e0ff
22:38:14.593 PC: Update @c1c, c4c=>0
22:38:14.593 PC: Update @c24, 5=>0
22:38:14.593 PC: Update @c30, 1=>0
22:38:14.593 PC: Update @c48, d3c=>0
22:38:14.593 PC: Update @c4c, c7c=>0
22:38:14.593 PC: Update @c54, a=>0
22:38:14.593 PC: Update @c60, 2=>0
22:38:14.593 PC: Update @c78, d4c=>0
22:38:14.593 PC: Update @c7c, cac=>0
22:38:14.593 PC: Update @c84, 14=>0
22:38:14.593 PC: Update @c90, 3=>0
22:38:14.593 PC: Update @ca8, d5c=>0
22:38:14.593 PC: Update @cac, cdc=>0
22:38:14.593 PC: Update @cb4, 32=>0
22:38:14.593 PC: Update @cc0, 4=>0
22:38:14.593 PC: Update @cd8, d6c=>0
22:38:14.593 PC: Update @cdc, d0c=>0
22:38:14.593 PC: Update @ce4, 64=>0
22:38:14.593 PC: Update @cf0, 5=>0
22:38:14.593 PC: Update @d08, d7c=>0
22:38:14.593 PC: Update @d0c, d0c=>0
22:38:14.593 PC: Update @d14, c8=>0
22:38:14.593 PC: Update @d20, 6=>0
22:38:14.593 PC: Update @d38, d8c=>0
22:38:14.593 PC: Update @d3c, 312a35=>0
22:38:14.593 PC: Update @d48, 31000000=>0
22:38:14.593 PC: Update @d4c, 312a3031=>0
22:38:14.593 PC: Update @d58, 32000000=>0
22:38:14.593 PC: Update @d5c, 312a3032=>0
22:38:14.593 PC: Update @d68, 35000000=>0
22:38:14.593 PC: Update @d6c, 312a3035=>0
22:38:14.593 PC: Update @d78, 31000000=>0
22:38:14.593 PC: Update @d7c, 2a303031=>0
22:38:14.593 PC: Update @d80, 31=>0
22:38:14.593 PC: Update @d88, 32000000=>0
22:38:14.593 PC: Update @d8c, 2a303032=>0
22:38:14.593 PC: Update @d90, 31=>0
22:38:14.593 PC: Update @d9c, de8=>0
22:38:14.593 PC: Update @da4, 1090000=>0
22:38:14.593 PC: Update @da8, fffffff9=>0
22:38:14.593 PC: Update @dac, 3=>0
22:38:14.593 PC: Update @db0, 9=>0
22:38:14.593 PC: Update @db4, 5=>0
22:38:14.593 PC: Update @dbc, 1=>0
22:38:14.593 PC: Update @dc8, ffffffff=>0
22:38:14.593 PC: Update @dcc, 68b50f4e=>0
22:38:14.593 PC: Update @dd0, dd8=>0
22:38:14.593 PC: Update @dd8, 6576654c=>0
22:38:14.593 PC: Update @ddc, 2032206c=>0
22:38:14.593 PC: Update @de0, 65627554=>0
22:38:14.593 PC: Update @de8, e34=>0
22:38:14.593 PC: Update @df0, 1090000=>0
22:38:14.593 PC: Update @df4, fffffff9=>0
22:38:14.593 PC: Update @df8, 3=>0
22:38:14.593 PC: Update @dfc, a=>0
22:38:14.593 PC: Update @e00, a=>0
22:38:14.593 PC: Update @e08, 1=>0
22:38:14.593 PC: Update @e14, ffffffff=>0
22:38:14.593 PC: Update @e18, 68b50f4e=>0
22:38:14.593 PC: Update @e1c, e24=>0
22:38:14.593 PC: Update @e24, 6576654c=>0
22:38:14.593 PC: Update @e28, 2032206c=>0
22:38:14.593 PC: Update @e2c, 65627554=>0
22:38:14.593 PC: Update @e34, e80=>0
22:38:14.593 PC: Update @e3c, 1090000=>0
22:38:14.593 PC: Update @e40, fffffff9=>0
22:38:14.593 PC: Update @e44, 3=>0
22:38:14.593 PC: Update @e48, b=>0
22:38:14.593 PC: Update @e4c, 14=>0
22:38:14.593 PC: Update @e54, 1=>0
22:38:14.593 PC: Update @e60, ffffffff=>0
22:38:14.593 PC: Update @e64, 68b50f4e=>0
22:38:14.593 PC: Update @e68, e70=>0
22:38:14.593 PC: Update @e70, 6576654c=>0
22:38:14.593 PC: Update @e74, 2032206c=>0
22:38:14.593 PC: Update @e78, 65627554=>0
22:38:14.593 PC: Update @e80, ecc=>0
22:38:14.593 PC: Update @e88, 1090000=>0
22:38:14.593 PC: Update @e8c, fffffff9=>0
22:38:14.593 PC: Update @e90, 3=>0
22:38:14.593 PC: Update @e94, c=>0
22:38:14.593 PC: Update @e98, 32=>0
22:38:14.593 PC: Update @ea0, 1=>0
22:38:14.593 PC: Update @eac, ffffffff=>0
22:38:14.593 PC: Update @eb0, 68b50f4e=>0
22:38:14.593 PC: Update @eb4, ebc=>0
22:38:14.593 PC: Update @ebc, 6576654c=>0
22:38:14.593 PC: Update @ec0, 2032206c=>0
22:38:14.593 PC: Update @ec4, 65627554=>0
22:38:14.593 PC: Update @ecc, f18=>0
22:38:14.593 PC: Update @ed4, 1090000=>0
22:38:14.593 PC: Update @ed8, fffffff9=>0
22:38:14.593 PC: Update @edc, 3=>0
22:38:14.593 PC: Update @ee0, d=>0
22:38:14.593 PC: Update @ee4, 64=>0
22:38:14.593 PC: Update @eec, 1=>0
22:38:14.593 PC: Update @ef4, 4=>0
22:38:14.593 PC: Update @ef8, ffffffff=>0
22:38:14.593 PC: Update @efc, 68b50f4e=>0
22:38:14.593 PC: Update @f00, f08=>0
22:38:14.593 PC: Update @f08, 6576654c=>0
22:38:14.593 PC: Update @f0c, 2032206c=>0
22:38:14.593 PC: Update @f10, 65627554=>0
22:38:14.593 PC: Update @f18, f64=>0
22:38:14.593 PC: Update @f20, 1090000=>0
22:38:14.593 PC: Update @f24, fffffff9=>0
22:38:14.593 PC: Update @f28, 3=>0
22:38:14.593 PC: Update @f2c, e=>0
22:38:14.593 PC: Update @f30, c8=>0
22:38:14.593 PC: Update @f38, 1=>0
22:38:14.593 PC: Update @f40, 1=>0
22:38:14.593 PC: Update @f44, ffffffff=>0
22:38:14.593 PC: Update @f48, 68b50f4e=>0
22:38:14.593 PC: Update @f4c, f54=>0
22:38:14.593 PC: Update @f54, 6576654c=>0
22:38:14.593 PC: Update @f58, 2032206c=>0
22:38:14.593 PC: Update @f5c, 65627554=>0
22:38:14.593 PC: Update @f6c, 1080000=>0
22:38:14.593 PC: Update @f70, 1=>0
22:38:14.593 PC: Update @f74, 3=>0
22:38:14.593 PC: Update @f78, 8=>0
22:38:14.593 PC: Update @f7c, 1=>0
22:38:14.593 PC: Update @f94, 68b50f4e=>0
22:38:14.593 PC: Update @f98, fa0=>0
22:38:14.593 PC: Update @fa0, 6576654c=>0
22:38:14.593 PC: Update @fa4, 2033206c=>0
22:38:14.593 PC: Update @fa8, 6f796150=>0
22:38:14.593 PC: Update @fac, 53207475=>0
22:38:14.593 PC: Update @fb0, 65747379=>0
22:38:14.593 PC: Update @fb4, 2a2a006d=>0
22:38:14.593 PC: Transfer Reset
22:38:14.593 PC: USB unit re-synch complete
22:38:14.593 : Interface memory set up
22:38:14.593 Exec: API task took 466 msec
22:38:14.593 7496 bytes memory free
22:38:14.593 MDB: Manu: ICT, Ser # 220800028494, Model CCM6-HUF MDB, diag. avail, Ext Pay
22:38:14.655 MDB Tube@9: for 5 - reported coins 0=>0
22:38:14.655 MDB Tube@10: for 10 - reported coins 0=>0
22:38:14.655 MDB Tube@11: for 20 - reported coins 0=>0
22:38:14.655 MDB Tube@12: for 50 - reported coins 0=>0
22:38:14.655 MDB Tube@13: for 100 - reported coins 0=>4
22:38:14.655 MDB Tube@14: for 200 - reported coins 0=>1
22:38:14.655 API: MDB acceptor 2080000 at bdc and 6 coins updated
22:38:14.875 API: Level 2 Tube Hopper S/N 1756696398, Address 9, Value 5 at d9c added
22:38:14.922 API: Level 2 Tube Hopper S/N 1756696398, Address 10, Value 10 at de8 added
22:38:14.969 API: Level 2 Tube Hopper S/N 1756696398, Address 11, Value 20 at e34 added
22:38:15.016 API: Level 2 Tube Hopper S/N 1756696398, Address 12, Value 50 at e80 added
22:38:15.063 API: Level 2 Tube Hopper S/N 1756696398, Address 13, Value 100 at ecc added
22:38:15.110 API: Level 2 Tube Hopper S/N 1756696398, Address 14, Value 200 at f18 added
22:38:15.157 API: Level 3 Payout System Hopper S/N 1756696398, Address 8, Value 1 at f64 added
22:38:15.157 Exec: MDB task took 524 msec
22:38:15.235 Exec: API task took 73 msec
22:38:15.235 MDB: Selftest OK
22:38:15.235 MDB: Inhibit all
22:38:15.251 API: MDB Status to 4
22:38:20.119 7084 bytes memory free
22:39:13.874 00:01

[davebush]

Hi,

The simple answer is because Paylink is not seeing any replies to the "Simple poll" cctalk message.

Reasons for this are: the obvious one of wiring - especially power to the acceptor. Then there's the BNV key value - the CPI default is 123456, I don't remember if that's the one used by ICT. It's also possible the acceptor can be configured for different protocols and it's not configured for cctalk.

I suggest you also try getting ICT support from whoever sold you the acceptor.

Dave

[xagduran]

Hello:
The installation is well done, the pins are well connected, in fact we tested everything with another Paylink in production, and it detects the Br2300 perfectly.
The doubt we have is if they are the Paylink units, we have just received 3 new units, and the same thing happens with the 3rd.
It is the first time that it happens to us.
Hence the doubt.
Can we know in some way the traffic that the Paylink unit is receiving?
We are very surprised that it does not detect anything on the cctalk bus, since everything is correctly connected.
Thanks.
Greetings.
Angel.

[davebush]

If understand correctly, you can set up a working Paylink / ICT recycler and then replace just the Paylink and it fails to see the the recycler.

This sounds like a production problem with the Paylink - although I understand your point about a new unit exhibiting the same fault and it is very rare for Paylink to have a problem with cctalk.

If you have access to an oscilloscope, you can try checking the cctalk data line - it should show "random" changes between 5V and 0V as the serial characters are sent - any other voltage would possibly explain the problem.

Even just checking the cctalk data line for 5V with a multi-meter is worthwhile.

Dave

[xagduran]

Hello:
The data line of the Cctalk Paylink outputs 5v.
We have just checked it with a multimeter.
We are going to install one of these Paylink units in an installation where everything works and we will let you know.
Regards.
Angel.