Dont recognize my SR3 and Univerdsal Hopper

[vilosh]

Hello Dave

I have a problem finally I start my paylink, and updated the firmware
but dont recognize SR3 acceptor and Universal Hopper

My Paylink say:

08:50:53.069 PC: Driver start up
08:50:53.225 USB: Unit 0, ID: 0x0403 0xde50
08:50:53.225 Description: Genoa USB Hub
08:50:53.225 Serial No: AE000001
08:50:53.241 Type: Revison 3 (Original)
08:50:53.241 Latency: 16
08:50:53.272 USB: PC (re)started
08:50:53.303 Config: Paylink Checked OK against file "Standard.cfg"
08:50:53.319 PC: Memory Reset - new protocol
08:50:53.334 USB: PC Link Up
08:50:53.538 DP: Interface memory set up
08:50:53.538

08:50:53.538 PC: *** USB unit major memory reset ***

08:50:53.538
26 May 2013 Firmware: 2.1.12.51 from Mar 26 2013 at 10:20:36 Driver:2.1.12.51
08:50:53.538 Exec: DP App. task took 205 msec
08:51:05.991 00:16
08:51:50.033
08:51:50.033
08:51:50.033 DP: Application active
08:51:50.033 DP: Resending Events
08:51:50.033 DP: Application Watchdog recovered
08:51:50.048 DP: Event 0003
08:51:50.048 DP: Turn off barcodes
08:51:50.720 DP: Event 0001
08:51:50.798 DP: Event 0002
08:51:59.689 DP: Pay request for 200, (200 - 0 (-553056014 - -553056214))
08:52:00.205 DP: Cycle End - DP: Overall status: -6
08:52:00.251 DP: *** DLL has "noticed" pay result!!
08:52:05.345 DP: Application has gone away
08:52:05.345
08:52:05.845 00:17
08:52:19.545


and after this, I run DEMO and say me NO ACEPTORS
even though the led of SR3 is green

what is happening?

[davebush]

The latest version of Paylink requires a configuration file to explain to the firmware which peripherals to look for.

The default file for this configuration is standard.cfg located in the same folder as the Paylink.exe driver program.

As shipped, all the lines in the standard.cfg file are commented out, so Paylink initializes successfully and then doesn't look at anything. You need to modify the file to specify your particular configuration.

There are details on this in the documentation folder.

[vilosh]

Hello Dave,
I configured the file and now the paylink say that:


19:00:34.509 PC: Driver start up
19:00:34.666 USB: Unit 0, ID: 0x0403 0xde50
19:00:34.666 Description: Genoa USB Hub
19:00:34.666 Serial No: AE000001
19:00:34.681 Type: Revison 3 (Original)
19:00:34.681 Latency: 16
19:00:34.712 USB: PC (re)started
19:00:34.759 Config: Paylink Checked OK against file "Standard.cfg"
19:00:34.759 Exec: USB task took 29 msec
19:00:34.775 PC: Memory Reset - new protocol
19:00:34.791 USB: PC Link Up
19:00:34.853 Failed call to delete
19:00:34.853 DP: ccCoin acceptor 2020000 at b90 setup
19:00:34.869 Failed call to delete
19:00:34.869 DP: Hopper S/N 0, Address 5, Value 25 at bc8 setup
19:00:34.900 Failed call to delete
19:00:34.900 DP: Hopper S/N 0, Address 8, Value 5 at c04 setup
19:00:35.056 DP: Interface memory set up
19:00:35.056

19:00:35.056 PC: *** USB unit major memory reset ***

19:00:35.056
28 May 2013 Firmware: 2.1.12.51 from Mar 26 2013 at 10:20:36 Driver:2.1.12.51
19:00:35.056 Exec: DP App. task took 268 msec
19:00:35.556 cctalk: Data Line Frozen
19:00:35.650 cctalk: Data Line Frozen
19:00:35.744 cctalk: Data Line Frozen
19:00:40.791 cctalk: Data Line Frozen
19:00:40.884 cctalk: Data Line Frozen
19:00:40.962 cctalk: Data Line Frozen
19:00:46.009 cctalk: Data Line Frozen
19:00:46.103 cctalk: Data Line Frozen
19:00:46.197 cctalk: Data Line Frozen
19:00:51.244 cctalk: Data Line Frozen
19:00:51.322 cctalk: Data Line Frozen
19:00:51.416 cctalk: Data Line Frozen

[davebush]

"Data Line Frozen" normally means that you've not got 24V power to hoppers.

I detail, the single cctalk data line has multiple drivers and receivers on it, and one of the characteristics is that units can see their outgoing traffic. The drivers selectively connect the data line to earth - the receivers see these transitions.

This diagnostic from Paylink is when the outgoing traffic is not read, and implies that one of the other drivers is permanently connecting the data line to earth, usually because it is not powered.

[vilosh]

Thanks, my last question:

This happens also if I disconnect the hoppers and leave you only connected the SR3?
Then I understand that the solution would be to replace the power of 24v for the cctalk?

Vilosh

[vilosh]

Sorry anything else

What is that?
19:00:34.900 Failed call to delete

Is because the same error (cctalk: Data Line Frozen) ?

[aardvark]

You can ignore 19:00:34.900 Failed call to delete - it's a trivial internal problem.

You should find that with nothing connected the messages go away. It might be a short in cable if it's still there with both the SR3 and Hopper disconnected.

24V to the hopper is merely the most common problem, have you got 12V for the SR3?

[vilosh]

Thanks
When I disconnect the power 24V. SR3 still has on green led, I guess PayLink should recognize it.

[davebush]

Have you solved your problem?

[vilosh]

Hello,

No, dont solve the problem,
to verify that exist current power supply to the connector cctalk 24V, switch power off 12V Paylink,
and checked if there is power in connector 24v cctalk. And yes, there is power.

Do not know what else to do.

[davebush]

So,

With the cctalk leads not connected to the Paylink board you shouldn't see the "cctalk: Data Line Frozen" diagnostic.

• Then, with all the peripherals disconnected from the leads, you plug the leads into the Paylink.
  
  Then you plug the SR3 into the cctalk leads.
  
  Then you unplug the SR3 and plug in the hopper.
  
  Then you plug the SR3 back into the leads.

At which point do the "cctalk: Data Line Frozen" diagnostics start appearing?

[vilosh]

Hello Dave

With the cctalk leads not connected to the Paylink board say:

18:43:13.779 PC: Driver start up
18:43:13.873 USB: Unit 0, ID: 0x0403 0xde50
18:43:13.873 Description: Genoa USB Hub
18:43:13.873 Serial No: AE000001
18:43:13.919 Type: Revison 3 (Original)
18:43:13.919 Latency: 16
18:43:13.951 USB: PC (re)started
18:43:14.013 Config: Paylink Checked OK against file "Standard.cfg"
18:43:14.013 Exec: USB task took 44 msec
18:43:14.029 PC: Memory Reset - new protocol
18:43:14.044 USB: PC Link Up
18:43:14.107 Failed call to delete
18:43:14.107 DP: ccCoin acceptor 2020000 at b90 setup
18:43:14.123 Failed call to delete
18:43:14.123 DP: Hopper S/N 0, Address 7, Value 25 at bc8 setup
18:43:14.154 Failed call to delete
18:43:14.154 DP: Hopper S/N 0, Address 8, Value 5 at c04 setup
18:43:14.310 DP: Interface memory set up
18:43:14.310

18:43:14.310 PC: *** USB unit major memory reset ***

18:43:14.310
18 June 2013 Firmware: 2.1.12.51 from Mar 26 2013 at 10:20:36 Driver:2.1.12.51
18:43:14.310 Exec: DP App. task took 267 msec
18:43:18.576 cctalk: Data Line Frozen
18:43:18.669 cctalk: Data Line Frozen
18:43:18.748 cctalk: Data Line Frozen
18:43:23.794 cctalk: Data Line Frozen
18:43:23.888 cctalk: Data Line Frozen
18:43:23.982 cctalk: Data Line Frozen
18:43:29.029 cctalk: Data Line Frozen

[davebush]

I an afraid that if you're getting this with nothing connected, then you have a physical electrical fault on the cctalk I/O circuit and your Paylink needs repairing / replacing.

[vilosh]

Hello Dave,

In US where I send my Paylink for to repar

thaks
Pablo V.

[davebush]

Can you post your standard.cfg file and itemise the units you have - you don't appear to have successfully configured the peripherals.