Azkoyen Modular C6 with Paylink (CCTalk)

[Suxen]

Hi,
I use Paylink with an Azkoyen Modular C6 coin mechanism in CCTalk. When I launch the driver here are the Paylink traces. And in Demo.exe the status is equal to 41. Could you tell me what is wrong?
cordially

16:23:21.846 PC: Driver start up
16:23:21.956 USB: Unit 0, ID: 0x0403 0xde50
16:23:21.956 Description: Genoa USB Hub
16:23:21.956 Serial No: AE000001
16:23:21.973 Type: Revision 4 (USB Powered)
16:23:21.974 Latency: 16
16:23:22.021 Config: Start of download
16:23:22.053 Config: Checked, OK
16:23:22.053 Config: Paylink Checked OK against file "Standard.cfg"
16:23:22.054 PC: Memory Reset - new protocol
16:23:22.076 Exec: USB task took 46 msec
16:23:22.076 ccCoin: extracted path overrides 1f
16:23:22.076 ccCoin: Path enables 1f ==> 7f
16:23:22.165 API: ccCoin acceptor 2020103 at ba0 and 8 coins setup
16:23:22.357 API: CCNet acceptor 120b0e01 at df0 and 4 coins setup
16:23:22.466 API: Bill to bill Cassette Hopper S/N 999999, Address 1, Value 1000 at f34 setup
16:23:22.504 API: SCH2-NOENCRYPT Hopper S/N 627804, Address 5, Value 200 at f88 setup
16:23:22.542 API: SCH2-NOENCRYPT Hopper S/N 676893, Address 4, Value 50 at fe0 setup
16:23:22.588 API: SCH2-NOENCRYPT Hopper S/N 672628, Address 3, Value 10 at 1038 setup
16:23:22.762 APIPC: USB unit reset complete
16:23:22.762 : Interface memory set up
16:23:22.762 Exec: API task took 688 msec
16:23:22.781 ccCoin: extracted path overrides 1f
16:23:22.781 ccCoin: Path enables 1f ==> 7f
16:23:22.797 ccCoin: extracted path overrides 1f
16:23:22.814 ccCoin: Path enables 1f ==> 7f
16:23:22.848 ccCoin: extracted path overrides 1f
16:23:22.848 ccCoin: Path enables 1f ==> 7f
16:23:22.883 ccCoin: extracted path overrides 1f
16:23:22.883 ccCoin: Path enables 1f ==> 7f
16:23:22.918 ccCoin: extracted path overrides 1f
16:23:22.918 ccCoin: Path enables 1f ==> 7f
16:23:22.952 ccCoin: extracted path overrides 1f
16:23:22.952 ccCoin: Path enables 1f ==> 7f


My standard.cfg :
driver
run hidden
logfile "Paylink.log" size 10000
system
simultaneous hoppers 4
Protocol cctalk on connector cctalk
Coin Acceptor at 2
Hopper at 3 Value 10
Hopper at 4 Value 50
Hopper at 5 Value 200

Regards

[davebush]

Hi,
The underlying problem seems to be that the coin mechanism is identifying itself as a Crane device, but is then not handling the messages in the same way.

So that I can check, I need to see the character string that identifies the acceptor. I think this is on the Peripherals tab of the diagnostics, I know that it is on the acceptors window on the Demo program.

Dave

[Nathan]

Hi,

In the Description field I can see "~EU ~BRM-F1-V1.00~SR5i"

Does that help?

[davebush]

Hi,

Yes, as I suspected, it has reported to Paylink that is a Crane SR5i, and so Paylink is expecting to responds as though it is an SR5i, but it is not providing an expected response to a particular message.

The easiest thing to do is to probably to change a setting on the coin mechanism so that it actually reports itself as being an Azkoyen C6 (The identity message code is 244) - that way Paylink won't get any other "surprises".

I think there's possibly a quick fix to attempt to notice that the message doesn't work, and changes its operation accordingly.

Let me know if you'd like to try a copy

Dave

[Nathan]

Hi,

So I explain to you, yesterday I tried to understand what you had written to me concerning message 244 and by carrying out many different tests with the software provided with Paylink, at some point Demo.exe managed to read the coin mechanism . I'm not sure how, but now Demo sees the coins gone and the coin mechanism is OK.

The Description is now: "FI33207890-14 ~C6 cctalk V12.1~C6 cctak"

[davebush]

Hi,

The description field is designed to tell you about the connected device. There are a number of "free text" fields that can be retrieved from an acceptor, and they are all reported here with '~' characters separating them.

For a cctalk coin mechanism you get the following: <coin Revision>~<Coin Table>~<Firmware Revision>~<Device Identity>

So, looking at your email for yesterday, Paylink read and reported the <Device Identity> as "SR5i", in today's test it has read it as "C6 cctalk", and as a result has done the correct processing.

If you've not altered the coin mechanism at all, the only way I can see this happening is if you changed the coin mechanism from a real SR5i without actually restarting the Paylink unit (removing the USB cable)?

Anyway, it looks as though you're now good to go with the original Paylink code.

Regards

Dave