New Life Games LLC

Homebrew Player Tracking and EFT Systems => NLG Homebrew Player Tracking and EFT Systems => Topic started by: peasoup49 on December 11, 2020, 10:21:07 PM

Title: [SOLVED] 0x71 following 0x68
Post by: peasoup49 on December 11, 2020, 10:21:07 PM

For those who track the incoming bytes from the slot machine, has anyone noticed that the slot machine issues another 0x71(integer 113) after the voucher is irretrievably stacked?  This also would be the same Exception code that is sent when the Change Lamp is On.  Is this an indicator to slot managers that someone inserted a ticket with a candle flash? In the info below, 103 is 0x67 received, 104 is 0x68 received, the extra 113 after the audible stacking of the ticket, and then a couple more codes.  These extra bytes vary is length (this one is only 2) and can be as many as 7.  I've tried doing a read byte after the 113, but has no affect to stop these from coming through.  Any hints are appreciated.
Thanks.

Code: [Select]


SASByte(Status Loop) = 103
Code 0x67(Status Loop) - Received
Code 0x70(Status Loop) - Transmitted
Code 0x70(Status Loop) - Received
Code 0x71(Status Loop) - Transmitted
Code 0x71(Status Loop) - Received
SASByte(Status Loop) = 104
Code 0x68(Status Loop) - Received
Code 0x71(Status Loop) - Transmitted
SASByte(Status Loop) = 113
SASByte(Status Loop) = 21
SASByte(Status Loop) = 218


I'm only concerned because it messes with my Status Page.  The attached pic shows that it triggered the Card Cage warning, yet the Card Cage isn't open.

Title: Re: 0x71 following 0x68
Post by: peasoup49 on December 13, 2020, 11:56:52 AM

I think I've been going too hard at this program and need to slow down.  The one thing they teach you in bootcamp is "Pay attention to detail!".  This is what I missed, talk about feeling stupid.  :duh:


What I had:

Code: [Select]

Serial.readBytes(RecvByte, 21);
What is was 'supposed' to be (I was missing the '1' after Serial):

Code: [Select]

Serial1.readBytes(RecvByte, 21);