Mapping Inputs; Getting The Input State Of Mapped Inputs - Globalstar ST150 User Manual

9150-0125-01 R-4
Example of issuing "AT+INLIST=0" after issuing the GPIOCFGIN commands shown above:
AT+INLIST=0
+INLIST 3,48,0,Accel Motion Event
+INLIST: 3,49,0,Accel Vibration Event
+INLIST: 3,50,1,Accel In-Motion
+INLIST: 3,51,1,Accel Orientation Match
+INLIST: 3,52,0,Accel Orientation Changed Event
+INLIST: 1,2,1,P0.02
+INLIST: 1,3,1,P0.03
+INLIST: 1,4,1,P0.04

7.12.3 Mapping Inputs

To map inputs into the on air messages.
Up to 8 inputs can be mapped.
The input mapping command:
AT+INMAP=<input_source_id>,<input_num>
Where:
<input_source_id> is the Nordic pin number (not the "key") of the input you want to map. There are also
"virtual pins" available with the following pin numbers:
•
48:Accel Motion Event
•
49:Accel Vibration Event
•
50:Accel In-Motion
•
51:Accel Orientation Match
•
52:Accel Orientation Changed Event
Examples:
Map Accel Motion event to input 1 in OTA messages:
AT+INMAP=48,1
Map actual pin 3 to input 2 in OTA messages:
AT+INMAP=3,2
"AT+INMAP?" Returns the mapped inputs. For example, issuing this query after doing the mappings listed
above results in:
AT+INMAP?
+INMAP: 3,2
+INMAP: 48,1
OK

7.12.4 Getting the Input State of Mapped Inputs

The command "AT+GETINSTATE=<input number>" gets the state of the input. The argument is the OTA
message input field that it is mapped to, not the Nordic input number or the key.
For example, in the above examples, virtual input 48, "ACCEL In Motion" is mapped to input 1, so the following
response, shows us that we are not in motion:
AT+GETINSTATE=1
+GETINSTATE: 1,0
OK
ST150M User Manual Confidential & Proprietary Information
50