ib_serial |
iButton serial number (16 hex symbols) |
|
ib_alarm_control_mask |
iButton alarm control mask. Define frequency for RTC alarm. 15 - Alarm once per second; 14 - Alarm when seconds match (once per minute); 12 - Alarm when minutes and seconds match (once every hour); 8 - Alarm when hours, minutes, and seconds match (once every day); 0 - Alarm when day, hours, minutes, and seconds match (once every week). (from iButton register page.)
|
|
ib_alarm_time |
time for RTC alarm. RTC alarm will happen every second/minute/day/week (according to ib_alarm_control_mask) (from iButton register page.)
|
HH:MM:SS |
ib_temp_alarm_treshold_low |
Low temperature threshold, the device generates alarm when this temperature is reached. (from iButton register page.)
|
C |
ib_temp_alarm_treshold_high |
High temperature threshold, the device generates alarm when this temperature is reached. (from iButton register page.)
|
C |
ib_sample_rate |
how many seconds the temperature samplings are apart from each other during a mission (from iButton register page.)
|
seconds |
ib_control |
Bit 7: Enable Oscillator (EOSC) Bit 6: Memory Clear Enable (EMCLR) Bit 4: Enable Mission (EM) Bit 3: Rollover Enable/Disable (RO) Bit 2: Temperature Low Alarm Search (TLS) Bit 1: Temperature High Alarm Search (THS) Bit 0: Timer Alarm Search (TAS) (from iButton register page.)
|
bit flag |
ib_rollover |
3rd bit of ib_control. Rollover Enable/Disable. (from iButton register page.)
|
0,1 |
ib_mission_start_delay |
how many minutes the device waits before starting the logging process (from iButton register page.)
|
minutes |
ib_status |
Status Register. Bit 7: Temperature Core Busy (TCB) Bit 6: Memory Cleared (MEMCLR) Bit 5: Mission in Progress (MIP) BIT 4: Sample in Progress (SIP) Bit 2: Temperature Low Flag (TLF) Bit 1: Temperature High Flag (THF) Bit 0: Timer Alarm Flag (TAF) (from iButton register page.)
|
bit flag |
ib_temp |
iButton temperature measurement (from iButton register page.)
|
C |
ib_mission_start |
Time when the mission starts (unix timestamp format). (from iButton register page.)
|
|
ib_mission_samples_counter |
how many temperature measurements have taken place during the current mission in progress (from iButton register page.)
|
|
ib_device_samples_counter |
how many temperature measurements have taken place since the device was assembled at the factory (from iButton register page.)
|
|
ib_alarm_duration |
Alarm duration. (from Alarm Timestamps page.)
|
minutes |
ib_is_alarm_high |
0 : high alarm temperature; 1 : low alarm temperature. (from Alarm Timestamps page.)
|
0,1 |
ib_hist_XXXX |
Temperature histogram value. XXXX is histogram binary address, from 0800 to 087C. 0800 corresponds to -38.5 and lower temperature 0802 corresponds to -38.0 .. -36.5 0804 corresponds to -36.0 .. -34.5 ... 087A corresponds to +82.0 .. +83.5 087C corresponds to +84.0 and higher
(from Alarm Timestamps page.)
|
|
mileage |
Mileage |
km |
hdop |
HDOP
|
|
sat_mode |
Sattelite Mode
indicator
0
– no fix 1
– Autonomous GNSS Fix
2 – Differential GNSS Fix
3 – Estimated/Dead Reckoning Fix
|
|
|
sat_fix |
FS
indicator:
0 – invalid
1 – Fix not available
2 – 2D Fix
3 – 3D Fix
|
|
is_fixnow |
FixNOW
indicator: 0 – Continuous mode; 1 – FixNOW mode
|
|
|
is_pedestrian |
Pedestrian/Automotive
mode indicator: 0 – Automotive; 1 – Pedestrian
|
|
ign |
Ignition |
0,1 |
fake_ign |
“Fake
Ignition” flag. If the device detects movement for at least 15
seconds or detects a point farther than MaxGuardDist, it raises this
flag. If there is no movement for more than 15 seconds the device
clears this flag. |
0,1 |
is_antenna_short_circuit |
Antenna
short circuit: 0 – antenna OK; 1 – antenna short circuit
|
0,1 |
pwr_int |
ADC
reading for the battery voltage. |
|
log_trigger |
Flash write trigger
|
|
core_flag |
Device
status flags and boot up flags
(appear
only once at device start up).
bit
|
Meaning
|
7
|
6
|
5
|
4
|
3
|
2
|
1
|
0
|
|
|
|
|
|
|
|
x
|
Device
reset due to power up occurred.
|
|
|
|
|
|
|
x
|
|
Device
reset due to watchdog reset.
|
|
|
|
|
|
x
|
|
|
Real
Time Clock reset
|
|
|
|
|
x
|
|
|
|
RAM
reset
|
|
|
|
x
|
|
|
|
|
Flash
reset
|
|
|
x
|
|
|
|
|
|
Firmware
update
|
|
x
|
|
|
|
|
|
|
SD/MMC
card present
|
x
|
|
|
|
|
|
|
|
SD/MMC
card error
|
|
|
gpo_flag |
State
of the digital outputs:
bit
|
Meaning
|
7
|
6
|
5
|
4
|
3
|
2
|
1
|
0
|
|
|
|
|
|
|
|
x
|
Ignition
|
|
|
|
|
|
|
x
|
|
Power
supply source; 0 – Internal battery; 1 – External power source
|
|
|
|
|
|
x
|
|
|
Reserved
|
|
|
|
|
x
|
|
|
|
Reserved
|
|
|
|
x
|
|
|
|
|
GPO0
state; 0 – off; 1 – on
|
|
|
x
|
|
|
|
|
|
GPO0
fault; 0 – no fault; 1 – fault (short circuit)
|
|
x
|
|
|
|
|
|
|
GPO1
state; 0 – off; 1 – on
|
x
|
|
|
|
|
|
|
|
GPO1
fault; 0 – no fault; 1 – fault (short circuit)
|
|
|
gsm_activity |
Current GSM activity:
bit
|
Meaning
|
7
|
6
|
5
|
4
|
3
|
2
|
1
|
0
|
|
|
|
|
|
|
|
x
|
GSM
network registration; 0 – not registered; 1 – registered
|
|
|
|
|
|
|
x
|
|
GPRS
attach attempt
|
|
|
|
|
|
x
|
|
|
Registration
within the GPRS network; 0 – not registered; 1 – registered
|
|
|
|
|
x
|
|
|
|
Call
received
|
|
|
|
x
|
|
|
|
|
Attempt
to connect to the ISP using GSM data (CSD)
|
|
|
x
|
|
|
|
|
|
Attempt
to connect to the ISP via GPRS
|
|
x
|
|
|
|
|
|
|
Attempt
to upload a file to the FTP server
|
x
|
|
|
|
|
|
|
|
Attempt
to download a file from the FTP server
|
|
|
gsm_resp |
Indicates
that some of the following messages is received from the GSM:
0
– OK (no error)
1
– ERROR
3
– NO CARRIER
4
– CONNECT
7
– BUSY
8
– NO ANSWER
9
- SHUTDOWN
|
|
gsm_cme_err |
CME error messages:
1025
- Ok_Info_DataBegin
1028
- Ok_Info_WaitingForData
3074
- Ok_Info_SocketClosed
3077
- Ok_Info_Ppp
3086
- Ok_Info_GprsActivation
|
|
driving_reason |
bit
|
15
|
14
|
13
|
12
|
11
|
10
|
9
|
8
|
7
|
6
|
5
|
4
|
3
|
2
|
1
|
0
|
|
|
|
|
|
|
|
|
|
|
x
|
x
|
x
|
x
|
x
|
x
|
Driving
reason:
0 – Work trip
1 – Private trip
|
|
|
|
|
|
|
|
|
|
x
|
|
|
|
|
|
|
0 –
Default driving reason
1- Reason selected by user
|
|
|
|
|
|
|
|
|
x
|
|
|
|
|
|
|
|
N/A
|
|
|
|
|
|
|
|
x
|
|
|
|
|
|
|
|
|
Driving
reason info received from DIM-5000
|
x
|
x
|
x
|
x
|
x
|
x
|
x
|
|
|
|
|
|
|
|
|
|
N/A
|
|
|
mifare_state |
bit
|
|
15
|
14
|
13
|
12
|
11
|
10
|
9
|
8
|
7
|
6
|
5
|
4
|
3
|
2
|
1
|
0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
x
|
0 –
Card unlog/not logged
1 – Card log to the system
|
|
x
|
x
|
x
|
x
|
x
|
x
|
x
|
x
|
x
|
x
|
x
|
x
|
x
|
x
|
|
N/A
|
x
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
0 –
MiFare card info never received from DIM-5000
1 – there is
MiFare card status message from DIM-5000
|
|
|
mifare_id |
MiFare
card number
|
|
f02_GG_NN |
Parameter from configuration frame, GG -
Parameter
Group,
NN - Parameter
Number
|
|
sf02_GG_NN |
Status byte for parameters in reply frames.
bit
|
Value
|
Meaning
|
7
|
6
|
5
|
4
|
3
|
2
|
1
|
0
|
-
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
No Error
|
|
0
|
0
|
0
|
0
|
0
|
0
|
1
|
1
|
Unsupported
parameter group number
|
|
0
|
0
|
0
|
0
|
0
|
1
|
0
|
2
|
Unsupported
parameter number
|
|
0
|
0
|
0
|
0
|
0
|
1
|
1
|
3
|
Value
out of range / try to set a read-only parameter
|
|
0
|
0
|
0
|
0
|
1
|
0
|
0
|
4
|
Value
not set, i.e. the data field value is meaningless
|
|
0
|
0
|
0
|
0
|
1
|
0
|
1
|
5
|
Unfinished
command is present in the frame
|
|
0
|
0
|
0
|
0
|
1
|
1
|
0
|
6
|
An error
occurred while writing the settings into the flash (Command reply
frame).
|
|
0
|
0
|
0
|
0
|
1
|
1
|
1
|
7
|
Command
forbidden in *.dcc file or SMS.
|
|
0
|
0
|
0
|
1
|
0
|
0
|
0
|
8
|
Device
busy (i.e. try to get SD card data start index, while device is
reading or writing data).
|
|
0
|
0
|
0
|
1
|
0
|
0
|
1
|
9
|
Error
accessing a module (i.e. try to get SD card data start index, but
there’s no SD card or SD card is damaged)
|
|
0
|
0
|
0
|
1
|
0
|
1
|
0
|
10
|
This
error is returned by Start Firmware Download command. The device
cannot process the command, because another call is being
processed at the moment.
|
|
0
|
0
|
0
|
1
|
0
|
1
|
1
|
11
|
This
error is returned by Start Firmware Download command. The command
is sent via SMS, but the sender phone number is not authorized to
perform firmware download.
|
x
|
|
|
|
|
|
|
|
|
This
indicates that the last parameter sequence in the frame is
unfinished. i.e. the device expected more data, but the frame had
ended.
|
|
|