Configuration for USB peripherals

[michal.novak]

Hello,
I have question about controlling USB periferials with PayLink.
We have these components for testing:
1) Coin changer NRI currenza c2 with USB (C2-B6U-F-ILS)
2) Bill recycler JCM VEGA-RC with RS232 converter to USB

What are correct settings (in Standard.cfg) for these?
Is it better to use other connections than USB (like MDB) with PayLink?

Thanks
Michal

[davebush]

If you're using MDB, then you must have a traditional "Metal Box" Paylink, as that is the only part of the Paylink system that includes the interface hardware. In that case, the expectation is that your peripherals will connect to the Paylink unit - which has provision for 2 RS232 connections and a cctalk one.

(The USB connectivity provided by Paylink is only intended for those peripherals (from Crane) which only have USB connections.)

If you've got an ID-003 Vega, then you need to connect this to one of the two RS232 connections on the Paylink. The distribution has a folder called "PayLink Looms" - the RS232 cables are in "RS232 - 7 way Molex KK wmh1030" and "RJ45 - 9 Way D wmh937-1"

Standard cfg will have to include:

Code: Select all

Protocol MDB on connector MDB
   Changer at 08h
Protocol ID003 on connector RS232 With Recycler

or

Code: Select all

Protocol MDB on connector MDB
    Changer at 08h
Protocol ID003 on connector RJ45 With Recycler

[michal.novak]

So you advise to remove RS232-USB converter and connect VEGA to PayLink, I will try.
Is it also possible to control device connected to PC with COM port?

What about NRI currenza c2, that has just USB, can you send me config for that?

My second question was about our future order, where we can specify connection (USB or MDB).

[davebush]

I assume that the NRI currenza c2 with USB, still runs some form of the MDB protocol - At present we have no support for that - you should only use MDB peripherals via a direct connection to the Paylink.

There is also no way currently to use Paylink to interface to devices connected to a PC COM port.

As is always the case with software, the fact that there is currently no support doesn't mean that such support could not be provided if there was a way to pay for the development.

[michal.novak]

OK, it means that NRI currenza c2 with USB cannot be controlled with PayLink, for now.

In case of VEGA, that is multi-protocol (DIP switch selectable ID-003, ccTalk or MDB), which one is best for communication with PayLink?

[davebush]

You will probably get best results by using a cctalk configuration, with that done explicit in standard.cfg:

Code: Select all

Protocol cctalk on connector cctalk
  Vega Recycler at 40

The upside in operation is that this will be protected by DES encryption.
The downside in initial testing is that you'll have to get the Vega to exchange DES keys - and I can't remember how that is done. It'll be something like remove the cashbox.

I'm not sure how the unit would behave if you connect it via ID-003.

[michal.novak]

Now, I have semi-working configuration:

NRI currenza c2 connected to (1):

Code: Select all

Protocol MDB on connector MDB 
Changer at 8

Log:

Code: Select all

12:58:22.780 MDB: Manu: NRI, Ser # 10121807-001, Model C2Pv0 3  455, diag. avail, Extended Payout
12:58:22.827 MDB Tube@9: for 100 - reported coins 0=>0
12:58:22.827 MDB Tube@10: for 200 - reported coins 0=>0
12:58:22.827 MDB Tube@11: for 500 - reported coins 0=>0
12:58:22.827 MDB Tube@12: for 1000 - reported coins 0=>0
12:58:22.827 MDB Tube@13: for 2000 - reported coins 0=>0
12:58:22.827 MDB Tube@14: for 5000 - reported coins 0=>0
12:58:22.827 DP: MDB acceptor 2080000 at bd8 and 6 coins updated
12:58:23.062 DP: Level 2 Tube Hopper S/N 10121807, Address 9, Value 100 at d98  added
12:58:23.109 DP: Level 2 Tube Hopper S/N 10121807, Address 10, Value 200 at de4  added
12:58:23.156 DP: Level 2 Tube Hopper S/N 10121807, Address 11, Value 500 at e30  added
12:58:23.203 DP: Level 2 Tube Hopper S/N 10121807, Address 12, Value 1000 at e7c  added
12:58:23.249 DP: Level 2 Tube Hopper S/N 10121807, Address 13, Value 2000 at ec8  added
12:58:23.296 DP: Level 2 Tube Hopper S/N 10121807, Address 14, Value 5000 at f14  added
12:58:23.343 DP: Level 3 Payout System Hopper S/N 10121807, Address 8, Value 100 at f60  added
12:58:23.343 Exec: MDB task took 520 msec
12:58:23.434 Exec: DP App. task took 91 msec
12:58:23.434 MDB: Selftest OK
12:58:23.434 MDB: Inhibit all coins
12:58:23.434 DP: MDB Status to 4

and VEGA-RC connected to (9):

Code: Select all

Protocol ID003 on connector RJ45 With Acceptor

Log:

Code: Select all

13:08:37.657 ID-003: CZE <V(CZE)-100-SH ID003-05 V105-56 27OCT11 5479> found.
13:08:38.204 ID-003: note 0, Value 0
13:08:38.204 ID-003: note 1, Value 0
13:08:38.204 ID-003: note 2, Value 0
13:08:38.204 ID-003: note 3, Value 100
13:08:38.204 ID-003: note 4, Value 200
13:08:38.204 ID-003: note 5, Value 500
13:08:38.204 ID-003: note 6, Value 1000
13:08:38.204 ID-003: note 7, Value 2000
13:08:38.204 ID-003: note 8, Value 5000
13:08:38.223 DP: ID-003 acceptor 12060000 at ba0 and 9 coins updated
13:08:38.426 ID-003: Disable acceptance
13:08:38.426 Exec: ID-003 task took 235 msec
13:08:38.625 DP: ID-003 Status to 65
13:08:38.625 DP: ID-003 Status to 24
13:08:41.037 DP: ID-003 Status to 4

If I tried "With Recycler" it reports:

Code: Select all

12:58:29.142 ID-003: not recycler

Both units now accept bills/coins in Demo.exe, but not return.

I also tried to setup VEGA unit to ccTalk by change DS2 switches and config:

Code: Select all

Protocol CCTALK on connector RJ45
  Vega   Recycler at 40

Than it reports:

Code: Select all

DP: ccNote Pre reg, Addr 40
ccNote: Key slot 0 found
DP: ccNote acceptor 12020000 at ba0 setup

cctalk: Data Line Frozen

[davebush]

You can't use the cctalk protocol on an RS232 connection - it requires transmit and receive to be cross connected, which is impossible on RS232.

To use the Vega in cctalk mode, you have to change the electrical connection to the 5V cctalk mode, and then connect the acceptor to the cctalk connection on Paylink.

JCM should be able to tell you all about this.

Dave

[michal.novak]

OK, I will contact JCM about VEGA connection options.

But VEGA works for me on ID003, but not using recycler, is it possible make it work?
There is also option to use MDB on VEGA, but I don't know if it possible to combine 2 MDB devices on PayLink.

Similar problem I have with currenza coin changer on MDB, it "eats money", but not paying back although hoppers are set as reported in log.

[davebush]

I only know of one ID-003 option for a unit acting as a recycler - and that doesn't appear to work.

No one has ever asked (paid for) us to investigate a Vega recycler on ID-003, or MDB - so they are not yet implemented.

So far as the currenza goes, that should work. Can you pose the Paylink log of the messages around a payout attempt?

[michal.novak]

Currenza starts working both ways after restart, so it is done.

I connect VEGA with recycler through ccTalk cable and set protocol mode to ccTalk (Encrypted) according to manual.
There is also action to init encryption code - set it to VEGA serial number, but this number is 10 digits long and PayLink config accept just 6.
I didn't find any action to resend DES key in VEGA manual.

Result in log:

Code: Select all

16:02:54.764 ccNote: Encyption Information
16:02:54.764       : Protocol: 1, Encryption: 0,
16:02:54.764       : Sizes: 24 / 64 / 64,
16:02:54.764       : No Key available

16:02:57.952 ccNote: Waiting for key, DES Key failed

[davebush]

I've had to go away and check.

The question of Encryption keys is not relevant to DES mode peripherals - the same query that determines the DES mode, also determines the communications mode and keys.

For a cctalk Vega, I use use the setting DS2: 6-ON, 7-OFF, 8-ON. You will probably find 6-ON, 7-ON, 8-OFF works.

You then set DS2-4 to ON before initially powering up and connecting the Vega and Paylink. This will give the Vega permission to give the DES key to Paylink, which will store it. (You should observe the the Green LED on Paylink flashing a double speed while it is waiting for this key.)

Once Paylink has stored the key, you should return DS2-4 to OFF for normal operation.

Edited: As you can tell from the following posts I originally had the wrong switch number!

[michal.novak]

I followed you instructions and message from VEGA is different, but result is same.

Code: Select all

07:37:29.752 ccNote: Encyption Information
07:37:29.752       : Protocol: 0, Encryption: 101,
07:37:29.752       : Sizes: 24 / 64 / 64,
07:37:29.752       : No Key available
07:37:29.814 DP: ccNote Status to 65
07:37:29.814 DP: ccNote Status to 24
07:37:36.665 cctalk: Device @ 40 does not handle message 110
07:37:36.665 ccNote: Waiting for key, DES Key failed
07:37:36.665 DP: ccNote Status to 4
07:37:36.665 DP: ccNote Status to 84

I also tried other combinations of DS2 and PayLink config, but no luck. PayLink flash green LED at double speed all time.

[davebush]

As long as you are seeing "No Key available" on the message block you will not get any further.

At this point, I suggest you contact JCM technical support to find out why the Vega is not performing a key exchange.

[michal.novak]

I received support from JCM, did correct setup (SW4 on DS2) and key is OK!

Vega is accepting notes (4 from 6 types) and paying out.

Thank you for your help.