SAS Host controller DLL. What do you want to see?

[Forrhouse]

Andy. The atachment here is an official Ticket template for the EZ-pay system.
Thanks,
E

[jay]

To help with the algorithm one would need more than one ticket.

I would suggest two with the same amount and then two more with an alternate amount

[AndyP]

I have heaps of tickets, just dont have any with data on. I have no idea how the machine figures out what dollar value is on the ticket, but there is a ticket amount field in the message that tells you all the info about the inserted ticket.

I might see if I can find some cables to hook a printer to the AVP. I have a nanoptix printer, hopefully that wil fit in somewhere!

[Foster]

The only data that the machine can read by the BV is the bar code and it is the number below the bar code and on the one end of the ticket.

I have stated before that the ticket number is just that a number that is also a primary key to the validation server which holds a ticket/voucher database

That database probably has the following fields:
Ticket/voucher number (primary key) at least it would be a primary key in a database I would design for casino use.
Value
Date
Time
Machine or asset number
Location in the casino (maybe)
Redeemed or Cashed Field.

If the database is to merged into a larger database of a corporation that owns many casino's they may also add a field to ID the casino.

I might be forgetting a field or 2

When the ticket is validated the validation server./host transmits the value back to the machine as either a EFT or AFT transaction I am not sure which.

The value is printed so the patrons and employees know its value.
The cage still scans it to be sure it is a valid ticket and change its status in the database so it cant be used in a machine or cashed again.

[AndyP]

The only data that the machine can read by the BV is the bar code and it is the number below the bar code and on the one end of the ticket.

I have stated before that the ticket number is just that a number that is also a primary key to the validation server which holds a ticket/voucher database

That database probably has the following fields:
Ticket/voucher number (primary key) at least it would be a primary key in a database I would design for casino use.
Value
Date
Time
Machine or asset number
Location in the casino (maybe)
If the database is to merged into a larger database of a corporation that owns many casino's they may also add a field to ID the casino.

I might be forgetting a field or 2

When the ticket is validated the validation server./host transmits the value back to the machine as either a EFT or AFT transaction I am not sure which.

The number on the barcode is what is called the validation ID in SAS protocol. This validation ID is derived from an algorithm that uses ticket amount in credits and time, then a few other funky things are done to the numbers.

When a ticket is inserted into the machine, it generates and exception 67. When this is recieved, you poll the machine for the ticket validation data. The response to this poll includes a field called ticket amount.

Obviously when you tell the EGM to print a ticket, the validation number is issued, and the value is known and this would be stored in your backend to validate the inserted ticket. But how the hell the machine figures out the ticket amount when inserted is beyond me. It might not actually populate that field. I'll do a build tomorrow and post it up on my website, then whoever has valid tickets can insert them and see what happens.

[jay]

Here is a link relative to this.
http://www.patentstorm.us/patents/7118478/fulltext.html

[stayouttadabunker]

Here is a link relative to this.
http://www.patentstorm.us/patents/7118478/fulltext.html

Can that document be summed up simpler for the everyday layman like me? 
Whew! That's complicated stuff! 

[jay]

I am not sure I got a ton of info out of it but here is a brief summary

We have the barcode format which would be important if we were trying to find a device that reads a particular format.

We now know that there are two identical electronic  copies of the number on the ticket plus the people-readable info.
For the machine readable
- theoretically the ticket should be checked against a database but if its not available this is a means to help control counterfitting.
- one is magnetic and the other being the bar code. As a consistancy check the numbers should be the same.
The purpose is that someone with a pen could alter the bar code to change the value to be 940 instead of 94 but as its also double checked via the magnetics you would have to alter both. Most people who are trying to fake a ticket with a pen probably don't have a device capable of reading and then rewriting a magnetic stripe.
- There is a maximum number of outstanding tickets before the numbers repeat

We got that the last two numbers are the unique identifer.
We got references to about 20 different patent numbers that supposedly should lead us to the exact algorithm to to validate the ticket.
I didn't have time last night to start digging through these.

[stayouttadabunker]

               ***NOTICE!!!***
Do not use the S+ motherboard's J9 Pins #1 & #3 !!!!
They will burn out your interface board!

I wanted to eliminate my 12Vdc PS brick and utilize the J9 15-pin header
on the S+ motherboard as a source for power to the Interface board.
When I plugged it in, I noticed the DS 1&2 LEDs light up fairly bright then go out completely.
As I booted up the Test App, I received endless repeating errors and
I know the machine was not communicating with my PC.

I then disconnected the J9 connector and restored the power wires back
to the 12Vdc PS brick and still had no LED lights!  

I then swapped my last known good Interface to the 12Vdc PS brick
and I now have restored communications with an S+ machine to my PC.
For giggles ( I'm NOT really giggling...lol) I swapped Interfaces and verified
that the 1st Interface does not work anymore...
I checked the schematics on the J9 header and saw that it is pushing out 11.8 volts VAC !!!  

Another one bites the dust!    

[poppo]

               ***NOTICE!!!***
Do not use the S+ motherboard's J9 Pins #1 & #3 !!!!
They will burn out your interface board!

I wanted to eliminate my 12Vdc PS brick and utilize the J9 15-pin header
on the S+ motherboard as a source for power to the Interface board.
When I plugged it in, I noticed the DS 1&2 LEDs light up fairly bright then go out completely.
As I booted up the Test App, I received endless repeating errors and
I know the machine was not communicating with my PC.

I then disconnected the J9 connector and restored the power wires back
to the 12Vdc PS brick and still had no LED lights!  

I then swapped my last known good Interface to the 12Vdc PS brick
and I now have restored communications with an S+ machine to my PC.
For giggles ( I'm NOT really giggling...lol) I swapped Interfaces and verified
that the 1st Interface does not work anymore...
I checked the schematics on the J9 header and saw that it is pushing out 11.8 volts VAC !!!  

Another one bites the dust!    

J9 pins 1 &3?   I thought it was pins 1 &2 that should be used. And pin 2 'should' be DC. It is +VB and comes from MPU J2 B26. If there is AC on that line, the MPU diode may be bad. But if it were bad other things would not work. Pin 3 is definitely AC and would measure ~12v AC to ground (since you are not measuring across both hot lines).

Oh, check your e-mail.  

[stayouttadabunker]

Excellent Poppo!
That picture of the connector is horrible...
I thought it was skipping the 2nd Pin location...

For now, I'm going to stay with the 12Vdc PS brick...
at least I'm assured it works...lol

[stayouttadabunker]

                                        ***Update***

I tried moving the J9 Pin#3 to #2 as per Poppo's instructions
and it still doesn't light up.
That board is toast...something fried when I applied 12volts AC to it earlier.

However, I took a chance with my last known good board with the
new J9 connector configuration and it works perfectly!   
Both red & green LEDs are flashing nicely and communications
between the S+ and my PC are fully restored!!!  
Much thanks to our expert in-house board technician Poppo!  

[knagl]

If you haven't already, Mark, label the fried board as bad so you don't try and use it in the future and get confused as to why it's not working.  

[stayouttadabunker]

If you haven't already, Mark, label the fried board as bad so you don't try
and use it in the future and get confused as to why it's not working.  

I've actually just mailed it out    a few minutes ago to get it repaired!  

[poppo]

For now, I'm going to stay with the 12Vdc PS brick...

And yet just 40 minutes later...

However, I took a chance with my last known good board with the new J9 connector configuration and it works perfectly!

Glad it's working    Now just don't touch it. 

[reho33]

Now we can send credits to the machine if we want and play them off instead of inserting bills. And when we get the ticket end of it going, watch out! The opportunities are endless, thanks.

[stayouttadabunker]

For now, I'm going to stay with the 12Vdc PS brick...

And yet just 40 minutes later...

However, I took a chance with my last known good board with the new J9 connector configuration and it works perfectly!

Glad it's working    Now just don't touch it. 

I know...lol
But I knew you could fix it for us! 
You oughta get it in a few days!

[jay]

Regarding the printer out on this board ........ has anyone tried to connect a S+ to a ticket printer yet ???

Would the cash out button trigger the ticket print or would this need to be done as a SAS command ?

[AndyP]

Cash out should be configurable in the machine I assume. I'll have a look at the protocol and see if there is any config stuff in there.

I am just testing a few ticket in functions to make sure the right data is going over the wire as I have a few small bugs, and then I am going to do a build. Should have something up in the next couple of hours.

[AndyP]

Ok. new version is up: http://users.tpg.com.au/adslcmdn/SASEGMTest/V1_0_0_1/SASEGMTestInstall.zip
I have fixed the Legacy Bonus bug and hopefully the installer is a little more user friendly now. It should be installing dot net framework 2 SP1 and should also now ask you to install the C Runtime if it does not already exist.

Does not look much different, but if you check the SASEGMWrapper.cs file in the install directory you will see a lot of new DLL methods. Some have been tested, some haven't. I am aware of several bugs. The C# guru's should be able to start using some of the calls, but if you change SASEGMWrapper.cs please foward me your changes and I will try and integrate them into my version. There is heaps of new polls to retrieve meters. All the messages in the montana spec have been implemented, but not all may work (not tested).

Two new additions to the form are the Ticket Val Data and and Redeem Ticket buttons. When exception code 67 is received, you can retrieve the ticket details using the Ticket Val Data button. When you retrieve the val details, the data is stored into some variables. When redeem ticket is clicked these details are then sent back to the VGM. I doubt it will work, but its worth a try. Please post up any ticket validation data up here. Just realised you cant copy from the list box on the form, but I will fix that in the next version.

Unfortunately I need to do some paying work now, so you wont see many changes over the next few weeks but I will keep watching this forum and I will endeavor to fix any small issues that arise.

[Foster]

Some one want to send me schematic of that interface board?

[poppo]

Some one want to send me schematic of that interface board?

Check your PM for some info.

[stayouttadabunker]

The installer sends us to Microsoft downloads onto the Dot NET Framework 4 Client download.
I had to Google Dot Net Framework2 SP1 to get to the correct download. >>>

http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyId=79BC3B77-E02C-4AD3-AACF-A7633F706BA5&displaylang=en

[AndyP]

Bugger, still got it wrong

Installer has been low down on my list though. Might have to set up a Virtual PC to test it.

[poppo]

The installer sends us to Microsoft downloads onto the Dot NET Framework 4 Client download.
I had to Google Dot Net Framework2 SP1 to get to the correct download. >>>

http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyId=79BC3B77-E02C-4AD3-AACF-A7633F706BA5&displaylang=en

I let it do it's thing and it installed Dot NET Framework 4 Client. I already have Dot Net Framework2 SP2 installed. The program runs (but I don't have anything connected). So does that mean I am good to go?