Getting Transaction Logs Via Sms; Figure 6: Sms Log Samples - (Left) Version Ses6 - (Right) Version G7X Onwards - Select Engineered Systems SG2CL User Programming Manual

Select Engineered Systems - Cellular Select Gate Programming Guide

2.7.4 Getting Transaction Logs via SMS

Once the setup commands have been used to enable and set the correct phone numbers for log reports via SMS,
you can receive log reports of transactions.
To get logs, you have two choices in SMS.
EITHER:
1. Allow the CSG to reach the limit of transactions specified by the 83 command (100 or 500) in the
section 2.7.1, OR,
2. Request current logs entries using the 44 command below.
Transaction Logs Via SMS- Command to Get Transactions Now
All commands define the existing programming password as "PPPP". Wherever "PPPP" occurs,
substitute your own programming password e.g. the examples use factory default "1234".
Command Command Text
Name
*44*PPPP#
44 = Command to Get Log Now
Get Log
Transactions
Example: Set report type to SMS:
Now
Text = *44*1234#
In both cases, all existing log entries will be transmitted to the SMS cell phone number listed to receive log
numbers previously set using command 85 in section 2.7.2.
The number of transactions per SMS message is limited to the message body of 120 characters. A sample is
shown below (date is shown as year/month/date in month).
Figure 6: SMS Log Samples – (Left) Version SES6 – (Right) Version G7x onwards
Meaning:
001@, 002@, 003@,
004@ - sequential event
numbers followed by date
and time (24 hour clock).
Knnnn# or Knnnnnnnn#
are PIN and card numbers
Page 23 of 30
2019_03_D
Text (SMS) Response
Accepted: See Sample
Not Accepted:
Error
response (see Sec. 2.10,
Fig 8)
Meaning:
001@, 002@, 003@, 004@ -
sequential event numbers
followed by date and time (24
hour clock).
KRpppp# or KRcccccccc#
R = Relay Number 1 or 2 for
successful entry (which relay was
opened), or 0 where a relay was
not opened as the PIN/card was
invalid
pppp = PIN
cccccccc = card numbers