how to get all (error) messages from between B2B banknote and paylink

[flyelephantw]

as the title, please instruct me how to get the detailed log for trouble shooting of B2B banknote validator via Paylink.

For example,
if banknote got jammed in the recycler, B2B can't finish dumping the banknote into cash box,
how could I get the log file from paylink to see the details (error) message to investigate the root cause?

[davebush]

The first thing to do is to check the Paylink log. This is specified in the configuration file, and is often call Paylink.log and in the same folder as the configuration file.

All exceptional / unusual processing will output messages to this log, and, although not directly intended for users, the messages are generally in understandable English.

If you have a problem with a particular section of log, then post it in a reply and I will try to explain what Paylink thinks is happening.

It is possible to request Paylink to output, in hexadecimal, every single message sent to the B2B and the reply - but this generates a lot of log file and is relatively difficult to understand. If you want to try this, i can supply details.

Regards

Dave

[flyelephantw]

hi Dave,

Thank you so much for your support in advance.

I am not sure how we could find the corresponding error message from hexadecimal data.

But, Yes, we would like to try this - to request Paylink to output, in hexadecimal, every single message sent to the B2B and the reply. if possible, please kindly also instruct us how to check the corresponding error messages/info in hexadecimal

I really hope this could help us getting further info from B2B when investigating for some issues.

David

[davebush]

Hi,

This instructions at stage 6 of the instructions here: https://d.pr/f/NcuFML (Obviously you'll need 'd ccn') You can turn then off again by typing 'd off'

Before you do that, it might be a good idea if you post just the normal log output from Paylink while you re-create the problem, and I can tell you what information might be available.

Regards

Dave

[flyelephantw]

hi Dave,

thank you for the document. i will go test to get the log.

However, can paylink allow the log bigger than 1024kb?
since we usually have sufficient storage space( at least 40GB) to save bigger log files for longtime & comprehensive tests…

David

[davebush]

Hi,

There's a line in the Standard.cfg file:
Logfile "Paylink.log" size nnnnn

This gives you full control over the log file - name & location and specifies the size in K (up to 2G - 2000000) at which Paylink switches to a new log.

Dave

[flyelephantw]

hi Dave,

just for double clarification…
i am using v.4.1.12.9 now, can this edition support the log size of 2G capacity?

David

[davebush]

There will be no problem - the file size is in all 4.1.12.x versions

[flyelephantw]

hi Dave,

Since i would like to save as much as detailed log for ccNet protocol between Paylink and B2B, during our SW development and verification test, even, troubleshooting of B2B HW response.

Therefore, my questions is...

1. is it possible to get the detailed logs by running all three program( MilanDiag/ paylink.exe/ our own program) simultaneously?
2. what if the log is reaching to 2GB size? will it automatically overwrite the old info, but keep the latest log info?
or over 2GB, it may cause problems?

David

[davebush]

The log is written by Paylink.exe - the main driver program, which runs all the time.

You only need to run Milan Diag to turn on detailed logs - thereafter you can exit it and the log will continue. The Milan Diag program just provides a convenient way to see the log as it is generated.

The log is written until it reaches the specified size (2GB) at that point Paylink creates a name by replacing the last 3 characters of the log with "old", deletes any existing file with that name, renames the current log file to that name and creates a new, empty log file.

The result is that in a system that's been running a long time there will be between 2GB and 4GB of log file.

Dave

[flyelephantw]

hi Dave,

I am able to get the detailed log of ccNet communication between paylink and B2B when our program is running on machine.

Thus, I am just wondering if all B2B error message/reply, including banknote can be found/retrieved through Paylink SDK?

David

[davebush]

If you post the section of log around the problem, then I can tell you what information is in the messages, and what Paylink will have done with it.

[flyelephantw]

hi Dave,

Thank you for the support.
I typed "d ccn" to generate the clear log for B2B banknote validator and it works.
But, I am wondering if we restart paylink.exe, do we need to re-type "d ccn" to generate log?
If yes, how could I do to generate log instead of manually typing "d ccn" again?
Is it possible to generate log by SW program?

David

[davebush]

Hi,

You need to do the d ccn whenever the external Paylink unit is power cycled (basically if the connected PC is power cycled) - a PC reset will normally not do this.

If you want to be able to programmatically do this after power cycling, I can post the code fragment necessary.

Regards

Dave

[flyelephantw]

hi Dave,

Yes, please.
We would like to be able to programmatically do this after power cycling,

Moreover, could we do "d ccn" by paylink SDK ? or by other way?
Anyway, it would be great if you could share the code fragment related to this, then we could always have the detailed log of all field tests.

Thank you in advance.

David