FALCOM MAMBO2-B6/UXFS PFAL Commands

FALCOM MAMBO2-B6/UXFS PFAL Commands
This document is available at
HTTP://WWW.FALCOM.DE/
MAMBO2-B6/UXFS
Command Reference Guide
Firmware revision 2.6.0 and later
(For the firmware revision 2.5.x, use the manual "MAMBO2PFALCommandsReferenceGuide_3.0.1.pdf")
Firmware Version: 3.7.0; Modified: 28.03.2012; This document will be regularly updated
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Version history:
This table provides a summary of the document revisions.
Version
Author
Changes
Modified
3.7.0
F. Beqiri
- Please note that all PFAL commands related to the Bluetooth and IEEE are NOT supported by 28/03/2012
MAMBO2-B6 device. These PFAL commands are available only for MAMBO2-UXFS device.
- The options SD-Card and ANT are no longer available. The related commands are marked grey.
- Starting from the firmware revision 2.8.0 Release Version, the following changes are also made:
- Added new configuration parameter GSM.CALL.SIGNALING
- Added new configuration parameter GSM.SMS.SIGNALING
- Added new configuration parameter GSM.MSG.SIGNALING
- Added new event SYS.Alarmloop.eStop - It will be generated when user cancels a running alarm loop.
- Added new states SYS.Alarmloop.sActive and Sys.Alarmloop.sInactive - True when the alarm loop is
running or not running accordingly.
- Removed configuration parameters GSM.VIBRATION.ENABLE and GSM.RINGER.ENABLE.
- Updated configuration parameters GSM.SPYCALL.SELECTION - A part of a phone number (belonging to a
group of numbers) can also be specified (e.g. "+49633" for all phone numbers starting with "+49633").
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 1 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Version
Author
2.7.0
F. Beqiri
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Changes
Modified
09/09/2011
Starting from the firmware revision 2.7.0 Release Version, the following changes are also made:
- Spy Call: To disable the spy call function, execute the command $PFAL,Cnf.Set,GSM.SPYCALL.SELECTION
then restart the MAMBO2-BXFS
- $PFAL,Display.Button.Swap=enable: Note, it does not swap the buttons functions in PIN Request window.
- Output values of the protocol GP3DP have been changed - see protocol $GP3DP message
- Added new configuration parameter GSM.SPYCALL.EXCEPT="<value>"[,"<value>"]; <value>= disable
(default) or "+4912378745", etc.. up to 5 numbers - see also GSM.SPYCALL.EXCEPT.
- Added new configuration parameter DISP.CALLING=[0,1] to enable/disable calling popup.
- Added new PFAL commands Display.tilt.enable & Display.tilt.disable to enable/disable tilt functionality.
- Added new dynamic entry &(SIMCCID) - reports the Subscriber Identity Module.
2.6.5
F. Beqiri
- Added steps for calibrating the tilt features of the MAMBO2 device.
2.6.4
F. Beqiri
26/10/2010
Starting from the firmware revision 2.6.3 Release Version, the following changes are also made:
- Added/changed/removed commands:
- Extended command Sys.Power.Mode=<mode>[,<ontime>[,<offtime>[,<motion>]]] – Puts device
into power save mode - parameter <motion> added.
- Removed PFAL command $PFAL,Sys.Device.ClearAlarm; Use $PFAL,Cnf.Clear,"AL" instead.
- Removed PFAL command $PFAL,Sys.Device.ClearConfig
- Added PFAL Command Sys.AlarmLoop.Start – Start alarm loop
- Added PFAL Command Sys.AlarmLoop.Stop – Stop alarm loop
- Added/changed/removed configuration
- Increased number of icons on the MAMBO2-B6/UXFS menu DISP.VIEWS - Added index 40..43 as
user menu symbols.
- Added configuration parameter DISP.ALARMLOOP - Specifies settings for alarm loop
- Added/changed/removed Events and States
- Added new event GSM.Voicecall.eIncoming="spy" - occurs when detecting an incoming voice
29/10/2010
call from the GSM.SPYCALL.SELECTION list.
- Added event DISPLAY.User<id> - Occurs when the user select a user menu icon (with id from 40
to 43) from the display.
- Added states GPS.Nav.sDeltaSpeed<comp><value> and GPS.Nav.sDist<comp><value>
- Added neindoor event IEEE.Device.eIndoor="0","nodevice" - generated when MAMBO2 gets out of range
of indoor devices.
2.6.3
F. Beqiri
- Starting from the firmware revision 2.6.3, the following changes are made:
01.07.2010
- Added/changed/removed commands:
- Added new PFAL command Display.Button.Navigation - Disables Left and Right keys and enables the 5way navigation key.
- Added/changed/removed configuration
- Added new index (5) for the MOTION.BEARING - Represents the negation of the one of the Bearings 0 to 4.
- Added DISP.KEYLOCK - locks the keys on the MAMBO2-B6/UXFS after a user specified time period
- Added/changed/removed Events and States
- Added additional reasons for the events and states Sys.Device.eStart - additional parameters can be
specified to determine the start up reasons of the device.
- Added states GSM.VoiceCall.sNotReady and GSM.VoiceCall.sNotInside. True while the GSM is not ready to
dial and not inside a voice call accordingly.
- Added states GPS.Time.sLocalTimespan and GPS.Time.sLocalDatespan - states which are related to the
system date and time and not GPS date and time.
- Added/changed/removed dynamic entries
- Added new dynamic protocol &(Speed.cmps) - reports the current speed in centimeter/second.
- Added new dynamic protocol &(Wpoint) - reports the last reached way point.
- Added/changed/removed protocols
- Added &(TXT_ID:<id>) - reads and reports the text assigned to the specified ID in the text resource.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 2 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Version
Author
F. Beqiri
DOCUMENT VERSION 3.7.0
Changes
-
2.6.2
- FIRMWARE REVISION 2.8.0 -
Modified
Added Language Resources for using the dynamic entry &(TXT_ID:<id>).
Added &(LocalTime) - reports the current local time in the device.
Added &(LocalDate) - reports the current local date in the device.
Added &(Hbeat) - reports the heartbeats measurements from the chest strap transmitter.
Added &(Cadence) - reports the pedaling cadence measurements from the cadence sensor transmitter.
Added &(BikeSpeed) - reports the speed measurements from the speed sensor transmitter.
Added &(BikeDistance) - reports the total distance traveled by the bicycle.
Added &(ANTRaw) - reports the information in raw data supplied by a wireless sensor with ANT+Sport
connectivity that could not be processed by the MAMBO2-B6/UXFS.
Added &(TDistance<id>) - reports the total distance traveled during the trip <id>.
Added &(TDuration<id>) - reports the duration of the trip<id>.
Added &(TSpeed<id>) - reports the maximum speed reached during the trip<id>.
Added &(THeight<id>) - reports the total height during the trip<id>.
Added &(TDate<id>) - reports the start date and time of the trip <id>.
Added &(TDepth<id>) - reports the ascend and descend along the trip<id>.
Added &(PosDist<id>) - reports the total distance to the specified waypoint<id>
Added &(GFName<ID>) - reports the name of the specified Geofence ID.
Added &(GF<ID>) - reports the status of the specified and set up Geofence ID.
Added &(AreaName<ID>) - reports the name of the specified area ID.
Added &(Area<ID>) - reports the current state of the specified and setup area.
- Starting from the firmware revision 2.6.2, the following changes are made:
08.06.2010
- Added/changed/removed commands:
- Added new entry <AID_raw> to the command Sys.RUpdate.Init - Allows uploading of A-GPS data into the
device (chapter 3.2.2.4.1).
- Extended command Display.Message - <icon> parameter replaced by <bgd>. Now it is used for specifying
a background color (chapter 3.2.2.15.3).
-
Removed DIisplay.Show - not supported by this firmware
Extended command Sys.Power.Mode - <PTI> parameter added (chapter3.2.2.11.2).
Adjusted command Display.Alarm - Warning images is only supported (chapter 3.2.2.15.2).
Added new command GSM.SMS.SendRaw - sends data via SMS in raw format (chapter 3.2.6.4.2).
Added new command TCP.SMTP.SendRaw - sends data via eMail in raw format (chapter 3.2.7.3.2).
Added new command MSG.Send.Service - sends needed information to a service server (chapter 3.2.8.1.7).
Commands GPS.NAV.Static, GPS.Nav.SBAS, Sys.GPS.Sleep are only for MAMBO2 devices with SiRF GPS
receiver.
- Removed commands Sys.Security.DisplayLock, Sys.GSM.Powermode, Display.Sliding, Display.PeMenu
- Added/changed/removed configuration
- Updated parameter DEVICE.NAME - If no name specified then the IMEI will be assigned as device name.
- Extended DEVICE.GPS.AUTOCORRECT.
- Added new parameter DEVICE.ANT.CHANNEL - defines different configuration profiles for using different
ANT sensors with the MAMBO2-B6/UXFS.
- Added DEVICE.BIKESPEED.CIRCUM - specifies the circumference of the bicycle wheel to calculate the speed
of the bicycle when using a speed sensor.
- Added new parameter DEVICE.HEARTBEAT.PROFILE - activates an already configured heartbeat profile.
- Added new parameter GSM.SMS.ALWAYSREAD - enables reading of incoming SMS during an active voice
call.
- Added new parameter DISP.MESSAGE.PROT - defines which protocol should be reported when the PFALCommand PFAL,Display.Message is executed as an answer for the server-related M-Box messages.
-
Added new parameter MOTION.TILT- configures the detection of the device position.
Removed DISP.SHOW - not supported by this firmware
Extended DISP.SLIDING - Up to 3 different sliding modes with up to 9 views for each mode can be defined.
Adjusted DISP.VIEWS - supports 25 symbols.
Adjusted DISP.SAVER - the time out is now in milliseconds.
Changed GPS.TRIP.WPOINT<index> - removed<time> and added <mode>
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 3 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Version
Author
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Changes
Modified
- Changed GPS.TRIP.POIMODE - removed entry "follow" and added <trip_category>.
- Added GPS.TRIP.ROUTE<index> - defines which waypoints stored with GPS.TRIP.WPOINT<index> belong
to your route.
- Added GPS.TRACE.DEV<index> - allows to specify the devices to be traced using your MAMBO2-B6/UXFS.
- Added TCP.SERVICE.CONNECT- allows to configure a TCP service connection for running services like
remote control, configuration, remote updates, AGPS data.
- Added TCP.SERVICE.TIMEOUT - allows to specify the timeout for the service server.
- Added/changed/removed Events and States
- Added new type "doze" and new reason "Standing" in the Sys.Device.eStart[=<type>[,<reason>]] - occurs
when the device is in the doze mode and no motion detected with 30 seconds.
- Added a new event "Sys.Motion.e=<state>" and a new state "Sys.Motion.s=<state>" - are available when
the corresponding command Sys.Motion=<state> is executed.
- Added a new event "Sys.Sliding.e=<state>" and a new state "Sys.Sliding.s=<state>" - are available when
the user selects the Sliding item on the MAMBO2-B6/UXFS display.
- Added new event "IO.BTN.e6" for the button on the Bluetooth headset when it is pressed.
- Corrected DISPLAY.DIALOG.e1=<btn> event - btn2 corresponds to the left button on the dialog box while
bnt1 to the right button.
- Added new event IO.Motion.eForce - Occurs when the specified force value is reached or exceeded.
- Added new event IO.Motion.eFalling - Occurs when the device drops from a distance above the earth and
the current values of the motion sensor are within the values specified in the MOTIOM.FALLING parameter.
- Added new event IO.Motion.ePTI - occurs if the device does not detect motion for 30 seconds long.
- Added new state DISPLAY.Tripmode.s=<mode> - True when the specified mode is also selected during a
trip.
- Added new types "Start" and "Success" for the "DISPLAY.Popup.e<id>=<type>" - occur when the popup
dialog appears or OK pressed.
- Added new state "DISPLAY.Phone.s<id>=<state>" - Check the state of a phonebook entry whether it is
empty and the phone number assigned to this entry is valid or not.
- Added new event "DISPLAY.Tilt.e=<state>" - Occurs when the Tilt-function is called, stopped or the
calibration process started, completed, deactivated or failed.
- Added new state "DISPLAY.Tilt.sCounters<comp><value>" - True when the tilt-counter reaches your
specified value.
- Added new event DISPLAY.Follow.eSelect - Occurs when the user start tracing the device with your
specified ID .
- Added new event DISPLAY.Follow.eDest - Occurs when the destination of the device being traced is
reached.
- Added new event ANT.Speed - Occurs when operating with a ANT speed sensor.
- Added new event ANT.Cadence - Occurs when operating with a ANT cadence sensor.
- Removed state IO.BTN.sID - not supported by this firmware.
- Added/changed/removed dynamic entries
- Added new dynamic protocol &(Speed.cmps) - reports the current speed in centimeter/second.
- Added new dynamic protocol &(Wpoint) - reports the last reached way point.
- Added/changed/removed protocols
- Added new protocol FDB with ID 8000 - how to convert the protocols assigned to this ID are given in
chapter FDB.
2.6.0
F. Beqiri
- Initial version of the firmware 2.6.0
02.04.2010
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 4 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Table Of Contents
1 INTRODUCTION......................................................................................................................................... 19
1.1 SCOPE OF THE DOCUMENT................................................................................................................................ 19
1.2 RELATED DOCUMENTS..................................................................................................................................... 20
2 GENERAL................................................................................................................................................... 21
2.1 FEATURES OF THE OPERATING FIRMWARE................................................................................................................ 21
2.2 THE PRINCIPLE OPERATION OF THE FIRMWARE 2.6.XX ................................................................................................. 23
2.3 TCP/IP OVERVIEW...................................................................................................................................... 25
3 SUPPORTED PFAL COMMANDS, CONFIGURATION, STATES AND EVENTS....................................................26
3.1 PFAL COMMAND SYNTAX AND RESPONSE STRUCTURE................................................................................................. 26
3.1.1 PFAL Command syntax ................................................................................................................... 26
3.1.1.1 Command types <c_type>...................................................................................................................28
3.1.1.2 Aliases..................................................................................................................................................28
3.1.2 Using identifiers (optional):............................................................................................................. 28
3.1.3 Response message structure............................................................................................................ 29
3.2 PFAL COMMANDS....................................................................................................................................... 30
3.2.1 "Alarm" command type................................................................................................................... 38
3.2.1.1 "Info" command index.........................................................................................................................38
3.2.1.1.1 Alarm.Info,<index> – Checks alarm conditions..............................................................................38
3.2.1.2 "Clear" command index.......................................................................................................................39
3.2.1.2.1 Alarm.Clear,<index> – Clears settings to an alarm........................................................................39
3.2.2 "Sys"command type........................................................................................................................ 40
3.2.2.1 "Tracking" command index..................................................................................................................40
3.2.2.1.1 Sys.Tracking=<state> Generates events and states .....................................................................40
3.2.2.2 "Geo-fence" command index...............................................................................................................41
3.2.2.2.1 Sys.Geofence=<state> Generates different events and states ....................................................41
3.2.2.3 "Security" command index..................................................................................................................42
3.2.2.3.1 Sys.Security.Lock,<"password"> – Locks system............................................................................42
3.2.2.3.2 Sys.Security.RemoveLock,<"password"> – Removes system lock.................................................42
3.2.2.3.3 Sys.Security.Unlock,<"password"> – Unlocks system ...................................................................43
3.2.2.3.4 Sys.Security.HideAlarm,<"password"> – Protects reading of alarms............................................43
3.2.2.3.5 Sys.Security.UnhideAlarm,<"password"> – Removes alarm protection........................................43
3.2.2.4 "RUpdate" command index.................................................................................................................44
3.2.2.4.1 Sys.RUpdate.Init,<type>,<option>,<size>,<sectors>,<config> – Initializes remote firmware
upgrade........................................................................................................................................44
3.2.2.4.2 Sys.RUpdate.Abort – Aborts remote upgrade................................................................................46
3.2.2.4.3 Sys.RUpdate.DataMode,<msg_input> – Defines the channel and continues upgrading .............46
3.2.2.4.3.1 Binary update commands........................................................................................................47
3.2.2.4.3.2 List of binary commands..........................................................................................................48
3.2.2.4.4 Sys.RUpdate.Finish – Finishes remote upgrade ............................................................................49
3.2.2.5 "Device" command index....................................................................................................................50
3.2.2.5.1 Sys.Device.Reset[,<user_reset>] – Initiates system reset .............................................................50
3.2.2.5.2 Sys.Device.Update – Resets system into update mode/RedBoot (Bluetooth only) .....................50
3.2.2.5.3 Sys.Device.Shutdown – Shuts down system immediately. ...........................................................51
3.2.2.5.4 Sys.Device.FactoryReset – Resets device to factory defaults........................................................51
3.2.2.5.5 Sys.Device.Sleep=<wakeup_condition> – Puts device into sleep mode .......................................52
3.2.2.5.6 Sys.Device.CfgUpdateMode – Sets device into configuration update mode................................53
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 5 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3.2.2.5.7 Sys.Device.RestoreBios – Upgrades or downgrades the on-board BIOS ......................................54
3.2.2.5.8 Sys.Device.Speaker=<mode> – Enables/Disables internal buzzer / loudspeaker..........................54
3.2.2.6 "GSM" command index........................................................................................................................55
3.2.2.6.1 Sys.GSM.Enable – Powers GSM engine on.....................................................................................55
3.2.2.6.2 Sys.GSM.Disable – Powers off the GSM engine.............................................................................55
3.2.2.6.3 Sys.GSM.Reset – Resets the GSM engine.......................................................................................55
3.2.2.7 "GPS" command index.........................................................................................................................56
3.2.2.7.1 Sys.GPS.Enable – Powers on the GPS engine.................................................................................56
3.2.2.7.2 Sys.GPS.Disable – Powers off GPS engine .....................................................................................56
3.2.2.7.3 Sys.GPS.Reset – Initiates a GPS reset ............................................................................................56
3.2.2.7.4 Sys.GPS.Sleep – Puts GPS into sleep mode....................................................................................57
3.2.2.7.5 Sys.GPS.Wakeup – Wakes up GPS from sleep................................................................................57
3.2.2.8 "BT" command index...........................................................................................................................58
3.2.2.8.1 Sys.BT.Enable – Powers on Bluetooth module..............................................................................58
3.2.2.8.2 Sys.BT.Disable – Powers off Bluetooth module ............................................................................58
3.2.2.8.3 Sys.BT.Reset – Resets Bluetooth module.......................................................................................58
3.2.2.9 "CPU" command index.........................................................................................................................59
3.2.2.9.1 Sys.CPU.Reset – Resets CPU...........................................................................................................59
3.2.2.10 "IEEE" command index.......................................................................................................................60
3.2.2.10.1 Sys.IEEE.Enable – Powers on IEEE module ..................................................................................60
3.2.2.10.2 Sys.IEEE.Disable – Powers off IEEE module..................................................................................60
3.2.2.10.3 Sys.IEEE.Reset – Resets IEEE module...........................................................................................60
3.2.2.11 "Power" command index...................................................................................................................61
3.2.2.11.1 Sys.Power.Voltage – Queries input voltage on the USB..............................................................61
3.2.2.11.2 Sys.Power.Mode=<mode>[,<ontime>[,<offtime>[,<motion>]]] – Puts device into power save
mode............................................................................................................................................61
3.2.2.12 "BAT" command index.......................................................................................................................63
3.2.2.12.1 Sys.Bat.Voltage – Queries current battery voltage......................................................................63
3.2.2.12.2 Sys.Bat.ChargeState – Gets current battery state .......................................................................63
3.2.2.13 "Display" command index..................................................................................................................64
3.2.2.13.1 Sys.Display.Enable – Powers on OLED display .............................................................................64
3.2.2.13.2 Sys.Display.Disable – Powers off OLED display ...........................................................................64
3.2.2.14 "SD" command index ........................................................................................................................65
3.2.2.14.1 Sys.SD.Mount – Mounts a mini-SD card.......................................................................................65
3.2.2.14.2 Sys.SD.UnMount – Unmounts a mini-SD card..............................................................................65
3.2.2.14.3 Sys.SD.State – Shows mini-SD card state.....................................................................................66
3.2.2.14.4 Sys.SD.Dir.Show,<"dirname"> – Lists files and directories in mini-SD card.................................66
3.2.2.15 "DISPLAY" command type..................................................................................................................67
3.2.2.15.1 Display.Dialog=<id>,<"title">,<bgd>,<timeout>,<"Ok_left">,<"Cancel_right">,
<"message_text"> – Creates a full-screen dialog box.................................................................67
3.2.2.15.2 Display.Alarm=<image>,<timeout>,<"text"> – Displays a specific alarm image on screen.........68
3.2.2.15.3 Display.Message=<"user">,<id>,<"caption">,<bgd>,<timeout>,<"text">,
[<"answers1">[,<"answer2">,<"answer3">,<"answer4">]]– Displays a specific message (M-Box)
on screen......................................................................................................................................69
3.2.2.15.4 Display.Popup=<id>,<color>,<button>,<icon>,<timeout>,<"text"> – Displays a specific message
(M-Box) on the screen.................................................................................................................70
3.2.2.15.5 Display.POIs.Follow=<lat>,<lon>,<alt>,<radius> – Update a user POI to be followed................71
3.2.2.15.6 Display.Button.Enable – Enables Left and Right keys..................................................................71
3.2.2.15.7 Display.Button.Navigation – Enables Left and Right keys............................................................71
3.2.2.15.8 Display.Button.Disable – Disables Left and Right keys.................................................................72
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 6 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3.2.2.15.9 Display.Button.Swap=<action> – Swaps Left and Right buttons and their press-events............72
3.2.2.15.10 Display.Tilt.Enable – Enables tilt function..................................................................................73
3.2.2.15.11 Display.Tilt.Disable – Disables tilt function................................................................................73
3.2.2.16 "Timer" command index....................................................................................................................74
3.2.2.16.1 Sys.Timer<index>.Configure=<mode>,<timeout> – Configures a timer......................................74
3.2.2.16.2 Sys.Timer<index>.Start=<timer_settings> – Starts a timer.........................................................75
3.2.2.16.3 Sys.Timer<index>.Stop – Stops a running timer..........................................................................76
3.2.2.16.4 Sys.Timer<index>.Pause – Pauses (suspends) a running timer...................................................76
3.2.2.16.5 Sys.Timer<index>.Resume– Restarts execution of a paused timer.............................................76
3.2.2.16.6 Sys.Timer<index>.Arm - Arms an initialized and disarmed timer................................................77
3.2.2.16.7 Sys.Timer<index>.Disarm – Disarms an initialized and armed timer...........................................77
3.2.2.16.8 Sys.Timer<index>.Erase – Erases a timer configuration..............................................................77
3.2.2.16.9 Sys.Timer<index>.Save<slot_id> – Saves a timer state into a storage slot.................................78
3.2.2.16.10 Sys.Timer<index>.Load<slot_id> – Loads a timer state from a storage slot.............................78
3.2.2.16.11 Sys.Timer<index>.State – Reads a timer state...........................................................................78
3.2.2.17 "Trigger" command index..................................................................................................................79
3.2.2.17.1 Sys.Trigger<index>=<state_type> – Sets a trigger to high or low................................................79
3.2.2.17.2 Sys.Trigger<index> – Reads a current trigger state .....................................................................79
3.2.2.17.3 Sys.Trigger<index>.Save<slot-id> – Saves a trigger state to a storage slot.................................80
3.2.2.17.4 Sys.Trigger<index>.Load<storage_slot> – Loads a trigger state with a storage slot...................80
3.2.2.18 "Counter" command index................................................................................................................81
3.2.2.18.1 Sys.Counter<index>.Set=<value> – Assigns initial values to counters.........................................81
3.2.2.18.2 Sys.Counter<index>.Increment=<inc_value> – Increments counters value................................81
3.2.2.18.3 Sys.Counter<index>.Decrement=<dec_value> – Decrements counters value............................81
3.2.2.18.4 Sys. Counter<index>.State – Reads counters state......................................................................82
3.2.2.18.5 Sys.Counter<index>.Save<slot_id> – Saves a counter state to a storage slot.............................82
3.2.2.18.6 Sys.Counter<index>.Load<slot_id> – Loads the content of a storage slot to a counter.............82
3.2.2.18.7 Sys.Counter<index>.Clear – Sets counters to 0............................................................................83
3.2.2.19 "MACRO" command index.................................................................................................................83
3.2.2.19.1 Sys.Macro<index> – Activates configured macros.......................................................................83
3.2.2.20 "UserEvent" command index.............................................................................................................84
3.2.2.20.1 Sys.UserEvent<index> – Creates user-events..............................................................................84
3.2.2.21 "AlarmLoop" command index............................................................................................................85
3.2.2.21.1 Sys.AlarmLoop.Start – Start alarm loop.......................................................................................85
3.2.2.21.2 Sys.AlarmLoop.Stop – Stop alarm loop........................................................................................85
3.2.3 "CNF" command type...................................................................................................................... 86
3.2.3.1 Cnf.Set,<parameter_name=value> - Sets configuration settings........................................................86
3.2.3.2 Cnf.Get,<parameter_name> - Queries configuration settings............................................................90
3.2.3.3 Cnf.Clear,<parameter_name> - Clears parameter settings.................................................................93
3.2.3.4 Cnf.ShowUser - Queries user configuration........................................................................................94
3.2.3.5 Cnf.ShowDefault - Queries default settings........................................................................................94
3.2.3.6 Cnf.Show - Shows used parameters....................................................................................................94
3.2.3.7 Cnf.Search,<parameter> – Searches for parameter names................................................................94
3.2.4 "IO" command type......................................................................................................................... 95
3.2.4.1 IO.LED<index>=<conf_type> – Specifies LED behaviour.....................................................................95
3.2.4.2 IO.Beep<index>=<config_type> – Generates simple tones................................................................96
3.2.4.3 IO.Vibration=<config_type> – Manages device vibrations..................................................................97
3.2.5 "GPS" command type...................................................................................................................... 98
3.2.5.1 "Nav" command index.........................................................................................................................98
3.2.5.1.1 GPS.Nav.Position<buffer_index> – Returns bee-line distance from a stored location.................98
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 7 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3.2.5.1.2 GPS.Nav.Position<buffer_index>=<type> – Saves temporarily or clears a device position..........98
3.2.5.1.3 GPS.Nav.Position<buffer_index>=save<slot_id> – Moves GPS position data from buffer to
storage slots.................................................................................................................................99
3.2.5.1.4 GPS.Nav.Position<buffer_index>=load<slot_id> – Loads data from storage to buffer...............100
3.2.5.1.5 GPS.Nav.Distance – Reads distance counter................................................................................100
3.2.5.1.6 GPS.Nav.Distance.Save – Stores distance....................................................................................101
3.2.5.1.7 GPS.Nav.Distance.Load – Loads distance from memory.............................................................101
3.2.5.1.8 GPS.Nav.Distance=<value> – Sets distance..................................................................................101
3.2.5.1.9 GPS.Nav.SaveLastValid[=<time>,<lat>,<lon>,<alt>] – Saves last valid position...........................102
3.2.5.1.10 GPS.Nav.PowerSave=<mode>,<ontime>,<lptime> – Sets GPS receiver in TricklePower mode 103
3.2.5.1.11 GPS.Nav.SetHeadingTolerance=<value> – Defines heading tolerance......................................104
3.2.5.1.12 GPS.Nav.Static=<value> – Enables/Disables Static Navigation..................................................105
3.2.5.1.13 GPS.Nav.SBAS=<value> – Enables/Disables SBAS operation.....................................................105
3.2.5.1.14 GPS.Nav.TripCalc – Calculates the distance and elevation of a trip manually...........................106
3.2.5.2 "History" command index..................................................................................................................107
3.2.5.2.1 GPS.History.Write,<add_prot_to_memory>,<"text"> – Stores GPS position data in history.....107
3.2.5.2.2 GPS.History.Clear – Clears history ...............................................................................................109
3.2.5.2.3 GPS.History.GetStart – Returns oldest date stored in history ....................................................109
3.2.5.2.4 GPS.History.SetRead[,<s_date>,<s_time>-<e_date><e_time>] – Prepares selected history
records for download.................................................................................................................109
3.2.5.2.5 GPS.History.Read=[<format>] – Downloads history partly .........................................................111
3.2.5.2.5.1 Reading history records in textual format.............................................................................112
3.2.5.2.5.2 Further notes for converting history data with special remark to data logging features.....114
3.2.5.2.6 GPS.History.Push,<msg_output>,[<format>] – Downloads history completely..........................115
3.2.5.3 "Geofence" command index.............................................................................................................116
3.2.5.3.1 GPS.Geofence.Park.Set – Places and activates parking area.......................................................116
3.2.5.3.2 GPS.Geofence.Park.Remove– Disables an activated park area...................................................117
3.2.5.3.3 GPS.Geofence.GeoState,<geo_id>– Returns Geofences state....................................................117
3.2.5.3.4 GPS.Geofence.AreaState,<area_id>– Read areas state...............................................................117
3.2.5.4 "Trip" command index.......................................................................................................................118
3.2.5.4.1 GPS.Trip.Start – Starts a trip.........................................................................................................118
3.2.5.4.2 GPS.Trip.Stop – Stops a started trip.............................................................................................118
3.2.6 "GSM" command type................................................................................................................... 119
3.2.6.1 "GSM" general command indices......................................................................................................119
3.2.6.1.1 GSM.PIN=<"pin"> - Enters PIN number of used SIM card............................................................119
3.2.6.1.2 GSM.PUK=<"puk">,<"pin"> - Enters PUK and PIN numbers .......................................................119
3.2.6.1.3 GSM.IMEI - Gets product serial number......................................................................................119
3.2.6.1.4 GSM.SIMID – Gets ID of SIM Card................................................................................................120
3.2.6.1.5 GSM.OwnNumber– Gets own phone number.............................................................................120
3.2.6.1.6 GSM.Balance – Returns account balance of an used prepaid SIM card......................................120
3.2.6.1.7 GSM.USSD,<"ussd_cmd">,<timeout> – Performs an USSD call and return its answer...............120
3.2.6.1.8 GSM.MCC – Gets mobile country code........................................................................................121
3.2.6.1.9 GSM.Band=<band> – Defines GSM band.....................................................................................121
3.2.6.2 "Voice Call" command index..............................................................................................................122
3.2.6.2.1 GSM.VoiceCall.Dial,<"p_number"> - Makes voice calls...............................................................122
3.2.6.2.2 GSM.VoiceCall.Accept - Accepts an incoming voice call..............................................................122
3.2.6.2.3 GSM.VoiceCall.Hangup – Ends an active voice call......................................................................122
3.2.6.3 "Audio" command index....................................................................................................................123
3.2.6.3.1 GSM.Audio.ActiveProfile=<profile> - Selects and activates audio profiles..................................123
3.2.6.3.2 GSM.Audio.ShowProfile=<profile> - Shows audio profile details................................................124
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 8 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3.2.6.3.3 GSM.Audio.SaveProfileAs=<profile> - Saves audio settings to a profile......................................124
3.2.6.3.4 GSM.Audio.DeleteProfile=<profile> - Deletes stored profiles.....................................................125
3.2.6.3.5 GSM.Audio.EchoCancel=<value> - Activates/deactivates echo cancellation .............................125
3.2.6.3.6 GSM.Audio.SideTone=<value> - Enables/disables side tone output ..........................................126
3.2.6.3.7 GSM.Audio.SpeakerMute=<value> - Mutes/unmutes speaker output.......................................126
3.2.6.3.8 GSM.Audio.SpeakerGain=<value>- Sets speaker gain (volume)..................................................127
3.2.6.3.9 GSM.Audio.MicrophoneMute=<value> - Mutes/unmutes microphone’s signal ........................127
3.2.6.3.10 GSM.Audio.HandsfreeMicroGain=<value> - Sets microphone gain (volume) on hands-free
device ........................................................................................................................................128
3.2.6.3.11 GSM.Audio.HandsetMicroGain=<value> - Sets microphone gain (volume) on the handset
microphone................................................................................................................................128
3.2.6.3.12 GSM.Audio.AudioRingPath=<value>- Chooses path for passing ring signals............................129
3.2.6.3.13 GSM.Audio.RingTone=<value> - Selects incoming call ringtone................................................129
3.2.6.3.14 GSM.Audio.RingGain=<value> - Sets ringtone volume .............................................................130
3.2.6.3.15 GSM.Audio.AudioPath=<value> - Chooses audio path..............................................................130
3.2.6.3.16 GSM.Audio.SoundMode=<value> - Chooses device's global sound mode................................131
3.2.6.4 "SMS" command index......................................................................................................................132
3.2.6.4.1 GSM.SMS.Send,<"p_number">,<protocols>,<"text"> - Sends messages and protocols via SMS 132
3.2.6.4.2 GSM.SMS.SendRaw,<"p_number">,<protocols>,<"text"> - Sends an SMS to the phone number in
raw format.................................................................................................................................133
3.2.6.4.3 GSM.SMS.Inbox.Clear – Clears all stored SMS Messages ...........................................................134
3.2.6.4.4 GSM.SMS.Inbox.State – Returns all inbox SMS Messages ..........................................................134
3.2.6.4.5 GSM.SMS.Outbox.Clear – Clears all outgoing SMS Messages.....................................................134
3.2.6.4.6 GSM.SMS.Outbox.State – Returns all outbox SMS Messages .....................................................134
3.2.6.5 "Data Call" command index...............................................................................................................135
3.2.6.5.1 GSM.DataCall.Send,<protocols>,<"text"> - Sends alarm messages and protocols via an
established data call...................................................................................................................135
3.2.6.5.2 GSM.DataCall.Accept - Accepts incoming Data calls....................................................................135
3.2.6.5.3 GSM.DataCall.Hangup – Hangs up active data calls ....................................................................136
3.2.6.6 "GPRS" command index.....................................................................................................................137
3.2.6.6.1 GSM.GPRS.Connect – Performs GPRS attach...............................................................................137
3.2.6.6.2 GSM.GPRS.Disconnect – Performs GPRS detach.........................................................................137
3.2.6.6.3 GSM.GPRS.State - Returns GPRS state.........................................................................................138
3.2.6.6.4 GSM.GPRS.Traffic[=<complete>,<incoming>,<outgoing>] – Sets GPRS traffic counter..............138
3.2.7 "TCP" command type.................................................................................................................... 139
3.2.7.1 "TCP" command index.......................................................................................................................139
3.2.7.1.1 TCP.Client.Connect - Performs TCP connection to the used server.............................................139
3.2.7.1.2 TCP.Client.Disconnect - Disconnects from the used server.........................................................139
3.2.7.1.3 TCP.Client.State – Returns TCP connection state........................................................................140
3.2.7.1.4 TCP.Client.Send,<protocols>,<"text"> - Sends alarm messages and protocols via TCP to an
internet server...........................................................................................................................140
3.2.7.1.5 TCP.Client.ClearSendBuffer - Clears the internal TCP buffer for outbound packets...................141
3.2.7.2 "STORAGE" command index.............................................................................................................142
3.2.7.2.1 TCP.Storage.Dispatch - Stores information in TCP storage..........................................................142
3.2.7.2.2 TCP.Storage.Clear - Clears TCP storage contents.........................................................................142
3.2.7.2.3 TCP.Storage.AddProtocol,<protocol>,<"text"> - Adds protocols/user-text to TCP storage........143
3.2.7.2.4 TCP.Storage.AddRecord,<protocol>,<"text"> - Appends binary data frame to TCP storage......143
3.2.7.3 "SMTP" command index....................................................................................................................145
3.2.7.3.1 TCP.SMTP.Send,<"email_to">,<protocols>,<"text"> - Sends Emails to remote server...............145
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 9 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3.2.7.3.2 TCP.SMTP.SendRaw,<"email_to">,<protocols>,<"text"> - Sends an Email to the remote SMTP
server in raw format..................................................................................................................146
3.2.8 "MSG" command type................................................................................................................... 148
3.2.8.1 "Send" command index.....................................................................................................................148
3.2.8.1.1 MSG.Send.Serial,<protocols>,<"text"> - Sends protocols over Bluetooth..................................148
3.2.8.1.2 MSG.Send.RawSerial,<protocols>,<"text"> - Sends protocols unformatted over Bluetooth......149
3.2.8.1.3 MSG.Send.USB,<protocols>,<"text"> - Sends protocols to USB port..........................................150
3.2.8.1.4 MSG.Send.RawUSB,<protocols>,<"text"> - Sends protocols unformatted to USB port..............151
3.2.8.1.5 MSG.Send.File,<"filename">,<protocols>,<"text"> - Saves protocols to mini-SD card...............152
3.2.8.1.6 MSG.Send.RawFile,<"filename">,<protocols>,<"text"> - Saves the specified protocols and text
unformatted to mini-SD card ....................................................................................................153
3.2.8.1.7 MSG.Send.Service,<protocols>,<"text"> - Sends the specified protocols and text in a userdefined format to the service server ........................................................................................154
3.2.8.1.8 MSG.Send.CSD,<protocols>,<"text"> - Sends protocols and text in a user-defined format via an
established CSD call...................................................................................................................155
3.2.8.1.9 MSG.Send.TCP,<protocols>,<"text"> - Sends protocols via TCP to the remote server...............156
3.2.8.1.10 MSG.Send.SMTP,<"email_to">,<protocols>,<"text"> - Sends messages to an email address..157
3.2.8.2 "Mode" command index....................................................................................................................158
3.2.8.2.1 MSG.Mode.<interface>=<output_protocol>,<comunication_mode> - Sets communication mode
for receiving data.......................................................................................................................158
3.2.8.3 "Version" command index................................................................................................................160
3.2.8.3.1 MSG.Version.Complete - Gets device information......................................................................160
3.2.8.3.2 MSG.Version.Modules - Gets modules versions..........................................................................160
3.2.8.3.3 MSG.Version.BIOS - Gets BIOS version........................................................................................160
3.2.8.3.4 MSG.Version.HardwareRev - Gets hardware revision.................................................................161
3.2.8.3.5 MSG.Version.Hardware - Gets hardware name...........................................................................161
3.2.8.3.6 MSG.Version.Software - Gets software version...........................................................................161
3.2.8.3.7 MSG.Version.SoftwareID - Gets software ID................................................................................161
3.2.8.4 "Info" command index.......................................................................................................................162
3.2.8.4.1 MSG.Info.ServerLogin – Gets login information data..................................................................162
3.2.8.4.2 MSG.Info.Protocol,<protocols>,<"text"> - Gets data from protocols..........................................162
3.2.8.4.3 MSG.Info.Time – Gets GPS date/time..........................................................................................163
3.2.8.4.4 MSG.Info.Alarm,<alarm_index> - Gets conditions used in the selected alarm...........................163
3.2.8.4.5 MSG.Info.GetInterfaceName – Shows the interface name from which the commands come...163
3.2.9 "IEEE" command type.................................................................................................................... 164
3.2.9.1 "Keyfob" command index..................................................................................................................164
3.2.9.1.1 IEEE.Keyfob<index>.LED<led_index>=<state> - Sets LED state on a Keyfob...............................164
3.2.9.1.2 IEEE.Keyfob<index>.Beep<type>=<state> – Generates beep tones on a Keyfob device............165
3.2.9.1.3 IEEE.Keyfob<index>.Vibration=<state> – Makes Keyfob vibrating .............................................166
3.2.9.1.4 IEEE.Keyfob<index>.bat.level - Gets battery charge state...........................................................167
3.2.9.2 "IOBOX" command index...................................................................................................................168
3.2.9.2.1 IEEE.IOBox<index>.OUT<port>=<state> – Sets output state on an I/O-BOX ..............................168
3.2.9.2.2 IEEE.IOBox<index>.power=<mode> – Changes IO-BOX operation mode....................................169
3.2.9.2.3 IEEE.IOBox<index>.bat.level - Gets battery charge state.............................................................169
3.2.10 "BT" command type.................................................................................................................... 170
3.2.10.1 BT.Audio.Bound - Pairs Bluetooth audio devices............................................................................170
3.2.10.2 BT.Audio.Connect - Places both Bluetooth devices in connection mode ......................................170
3.2.10.3 BT.Audio.Disconnect - Closes a currently open audio connection .................................................170
3.3 DEFINING CONFIGURATION SETTINGS................................................................................................................... 171
3.3.1 DEVICE parameters........................................................................................................................ 172
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 10 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3.3.1.1 DEVICE.NAME....................................................................................................................................172
3.3.1.2 DEVICE.CMD.PFAL.EN........................................................................................................................172
3.3.1.3 DEVICE.COMM.<interface>................................................................................................................173
3.3.1.4 DEVICE.STARTUP.QUIET.....................................................................................................................175
3.3.1.5 DEVICE.IGNTIMEOUT ........................................................................................................................175
3.3.1.6 DEVICE.PROT.BINARY ........................................................................................................................176
3.3.1.7 DEVICE.KEYTONE................................................................................................................................176
3.3.1.8 DEVICE.BEEPTONE.............................................................................................................................177
3.3.1.9 DEVICE.PHONR...................................................................................................................................177
3.3.1.10 DEVICE.GSM.STARTUP.....................................................................................................................177
3.3.1.11 DEVICE.GPS.STARTUP......................................................................................................................178
3.3.1.12 DEVICE.GPS.AUTOCORRECT.............................................................................................................178
3.3.1.13 DEVICE.GPS.CFG...............................................................................................................................181
3.3.1.14 DEVICE.GPS.TIMEOUT......................................................................................................................181
3.3.1.15 DEVICE.GPS.HEADING......................................................................................................................182
3.3.1.16 DEVICE.GPS.NAVSTATIC...................................................................................................................182
3.3.1.17 DEVICE.GPS.NAVSBAS......................................................................................................................183
3.3.1.18 DEVICE.PFAL.SEND.FORMAT............................................................................................................183
3.3.1.19 DEVICE.IEEE.STARTUP......................................................................................................................185
3.3.1.20 DEVICE.BT.STARTUP.........................................................................................................................185
3.3.1.21 DEVICE.BT.LOCALNAME...................................................................................................................185
3.3.1.22 DEVICE.BT.AUDIOGW.......................................................................................................................186
3.3.1.23 DEVICE.ANT.STARTUP......................................................................................................................186
3.3.1.24 DEVICE.ANT.HEARTBEAT..................................................................................................................187
3.3.1.25 DEVICE.ANT.CHANNEL.....................................................................................................................188
3.3.1.26 DEVICE.BIKESPEED.CIRCUM.............................................................................................................189
3.3.1.27 DEVICE.HEARTBEAT.PROFILE...........................................................................................................189
3.3.2 DISP Parameter............................................................................................................................. 190
3.3.2.1 DISP.VIEWS.........................................................................................................................................190
3.3.2.2 DISP.MENU<index>............................................................................................................................192
3.3.2.3 DISP.PHONE<index> ..........................................................................................................................194
3.3.2.4 DISP.MESSAGE.PROT .........................................................................................................................196
3.3.2.5 DISP.ANSWER<index>........................................................................................................................197
3.3.2.6 DISP.ALARMLOOP..............................................................................................................................197
3.3.2.7 DISP.SAVER.........................................................................................................................................198
3.3.2.8 DISP.TZ...............................................................................................................................................199
3.3.2.9 DISP.LANG..........................................................................................................................................200
3.3.2.10 DISP.SLIDING....................................................................................................................................200
3.3.2.11 DISP.KEYLOCK...................................................................................................................................201
3.3.2.12 DISP.SWAPBTN.................................................................................................................................202
3.3.2.13 DISP.CALLING...................................................................................................................................202
3.3.3 IEEE Parameter.............................................................................................................................. 203
3.3.3.1 IEEE.PANID.........................................................................................................................................203
3.3.3.2 IEEE.KEYFOB<index>..........................................................................................................................203
3.3.3.3 IEEE.IOBOX<index>............................................................................................................................204
3.3.3.4 IEEE.INDOOR=<fieldstrength>,<enable>...........................................................................................207
3.3.4 Optional Settings........................................................................................................................... 208
3.3.4.1 STORAGE<id>.....................................................................................................................................208
3.3.4.2 GSM.BANDPREF.................................................................................................................................208
3.3.4.3 GSM.Version......................................................................................................................................208
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 11 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3.3.4.4 GSM.PROFILE.AUDIO<prof_index>....................................................................................................208
3.3.4.5 GSM.PROFILE.CURRENTAUDIO..........................................................................................................211
3.3.4.6 MACRO<index>..................................................................................................................................211
3.3.4.7 DEVICE.LOWPOWER..........................................................................................................................212
3.3.5 REPLACE Parameter....................................................................................................................... 213
3.3.5.1 REPLACE<index>................................................................................................................................213
3.3.6 MOTION parameter....................................................................................................................... 214
3.3.6.1 MOTION.FILTER..................................................................................................................................214
3.3.6.2 MOTION.BEARING..............................................................................................................................215
3.3.6.3 MOTION.TILT......................................................................................................................................217
3.3.6.4 MOTION.FALLING...............................................................................................................................218
3.3.7 ALIAS parameter ........................................................................................................................... 219
3.3.7.1 ALIAS.<type>......................................................................................................................................219
3.3.8 DBG parameter ............................................................................................................................. 220
3.3.8.1 DBG.EN ..............................................................................................................................................220
3.3.9 PROT parameters (protocols supported over Bluetooth and USB port)...........................................221
3.3.9.1 PROT.<message_id> ..........................................................................................................................221
3.3.9.2 PROT.START.BIN ................................................................................................................................222
3.3.10 GPS parameters........................................................................................................................... 223
3.3.10.1 GPS.TRIP.WPOINT<index> ..............................................................................................................223
3.3.10.2 GPS.TRIP.POIMODE .........................................................................................................................224
3.3.10.3 GPS.TRIP.ROUTE<index> .................................................................................................................225
3.3.10.4 GPS.TRACE.DEV<index>...................................................................................................................225
3.3.11 GSM parameters.......................................................................................................................... 228
3.3.11.1 GSM.PIN...........................................................................................................................................228
3.3.11.2 GSM.BALANCE.DIAL.........................................................................................................................228
3.3.11.3 GSM.CALLID.EN ...............................................................................................................................229
3.3.11.4 GSM.OPERATOR.BLACKLIST ............................................................................................................229
3.3.11.5 GSM.OPERATOR.SELECTION ...........................................................................................................230
3.3.11.6 GSM.OPLOST.RESTART ....................................................................................................................232
3.3.11.7 GSM.SMS.RESPONSE........................................................................................................................232
3.3.11.8 GSM.CALL.SIGNALING......................................................................................................................233
3.3.11.9 GSM.SMS.SIGNALING.......................................................................................................................234
3.3.11.10 GSM.MSG.SIGNALING....................................................................................................................234
3.3.11.11 GSM.SMS.RETRIES..........................................................................................................................235
3.3.11.12 GSM.SMS.ALWAYSREAD................................................................................................................235
3.3.11.13 GSM.SPYCALL.SELECTION..............................................................................................................235
3.3.11.14 GSM.SPYCALL.EXCEPT....................................................................................................................236
3.3.12 GPRS parameters......................................................................................................................... 237
3.3.12.1 GPRS.APN ........................................................................................................................................237
3.3.12.2 GPRS.AUTOSTART ...........................................................................................................................237
3.3.12.3 GPRS.DIAL ........................................................................................................................................238
3.3.12.4 GPRS.TIMEOUT ................................................................................................................................238
3.3.12.5 GPRS.QOSMIN .................................................................................................................................239
3.3.12.1 GPRS.QOS.........................................................................................................................................241
3.3.13 PPP parameters........................................................................................................................... 243
3.3.13.1 PPP.USERNAME ...............................................................................................................................243
3.3.13.2 PPP.PASSWORD ...............................................................................................................................243
3.3.13.3 PPP.AUTOPING ................................................................................................................................244
3.3.13.4 PPP.AUTH ........................................................................................................................................244
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 12 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3.3.14 TCP parameters........................................................................................................................... 245
3.3.14.1 TCP.CLIENT.CONNECT......................................................................................................................245
3.3.14.2 TCP.CLIENT.ALTERNATIVE................................................................................................................246
3.3.14.3 TCP.CLIENT.PING .............................................................................................................................247
3.3.14.4 TCP.CLIENT.TIMEOUT ......................................................................................................................247
3.3.14.5 TCP.CLIENT.DNS.TIMEOUT ..............................................................................................................248
3.3.14.6 TCP.CLIENT.LOGIN ...........................................................................................................................248
3.3.14.7 TCP.CLIENT.LOGIN.EXT.....................................................................................................................249
3.3.14.8 TCP.SERVICE.CONNECT....................................................................................................................249
3.3.14.9 TCP.SERVICE.TIMEOUT ....................................................................................................................250
3.3.14.10 TCP.CLIENT.SENDMODE.................................................................................................................250
3.3.14.11 TCP.STORAGE.................................................................................................................................251
3.3.14.12 TCP.SMTP.CONNECT......................................................................................................................251
3.3.14.13 TCP.SMTP.LOGIN............................................................................................................................252
3.3.14.14 TCP.SMTP.FROM............................................................................................................................253
3.3.15 GF parameters (Geofence)........................................................................................................... 254
3.3.15.1 How to setup a GeoFence in the MAMBO2-B6/UXFS ....................................................................254
3.3.15.2 Determine the Zone’s Grid Coordinates..........................................................................................254
3.3.15.3 Setting up Geofences and areas......................................................................................................256
3.3.15.4 GF.CONFIG .......................................................................................................................................257
3.3.15.5 GF.AREA<id> ...................................................................................................................................258
3.3.15.6 GF<id> .............................................................................................................................................259
3.3.16 AL<index> parameter (Alarm configuration)................................................................................264
3.3.16.1 AL<index>= <conditions>:<actions> -Set Alarm Configuration.......................................................264
3.4 SUPPORTED SYSTEM EVENTS AND STATES............................................................................................................. 270
3.4.1 Sys (System states and events)...................................................................................................... 271
3.4.1.1 Sys.Geofence......................................................................................................................................271
3.4.1.2 Sys.Tracking........................................................................................................................................271
3.4.1.3 Sys.Sliding...........................................................................................................................................272
3.4.1.4 Sys.Motion.........................................................................................................................................272
3.4.1.5 Sys.eSerialData ..................................................................................................................................273
3.4.1.6 Sys.UserEvent.....................................................................................................................................273
3.4.1.7 Sys.Device..........................................................................................................................................274
3.4.1.8 Sys.Timer............................................................................................................................................276
3.4.1.9 Sys.Trigger..........................................................................................................................................277
3.4.1.10 Sys.Counter......................................................................................................................................277
3.4.1.11 Sys.Power.........................................................................................................................................278
3.4.1.12 Sys.Bat..............................................................................................................................................279
3.4.1.13 Sys.BT...............................................................................................................................................280
3.4.1.14 Sys.GPS.............................................................................................................................................280
3.4.1.15 Sys.GSM............................................................................................................................................281
3.4.1.16 Sys.SD .............................................................................................................................................281
3.4.1.17 Sys.IEEE............................................................................................................................................281
3.4.1.18 Sys.Alarmloop..................................................................................................................................282
3.4.2 BT (Bluetooth states and events)................................................................................................... 282
3.4.2.1 BT.Audio.............................................................................................................................................282
3.4.3 IO (IO states and events)................................................................................................................ 283
3.4.3.1 IO.Motion...........................................................................................................................................283
3.4.3.2 IO.BTN................................................................................................................................................284
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 13 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3.4.4 DISPLAY (DISPLAY states and events)............................................................................................. 285
3.4.4.1 DISPLAY.Menu....................................................................................................................................285
3.4.4.2 DISPLAY.DIALOG.................................................................................................................................285
3.4.4.3 DISPLAY.Trip.......................................................................................................................................286
3.4.4.4 DISPLAY.Tripmode.............................................................................................................................286
3.4.4.5 DISPLAY.Popup...................................................................................................................................286
3.4.4.6 DISPLAY.Pois.......................................................................................................................................287
3.4.4.7 DISPLAY.Phone...................................................................................................................................287
3.4.4.8 DISPLAY.Tilt........................................................................................................................................287
3.4.4.9 DISPLAY.Follow..................................................................................................................................288
3.4.4.10 DISPLAY.User....................................................................................................................................288
3.4.5 GPS (GPS states and events).......................................................................................................... 289
3.4.5.1 GPS.Nav..............................................................................................................................................289
3.4.5.2 GPS.Time............................................................................................................................................290
3.4.5.3 GPS.History........................................................................................................................................291
3.4.5.4 GPS.Geofence....................................................................................................................................292
3.4.5.5 GPS.Area............................................................................................................................................293
3.4.6 GSM (GSM states and events)........................................................................................................ 294
3.4.6.1 GSM....................................................................................................................................................294
3.4.6.2 GSM.eCell...........................................................................................................................................295
3.4.6.3 GSM.VoiceCall....................................................................................................................................295
3.4.6.4 GSM.SMS............................................................................................................................................296
3.4.6.5 GSM.DataCall.....................................................................................................................................297
3.4.6.6 GSM.GPRS..........................................................................................................................................298
3.4.7 TCP (TCP states and events)........................................................................................................... 299
3.4.7.1 TCP.Client...........................................................................................................................................299
3.4.7.2 TCP.SMTP...........................................................................................................................................300
3.4.8 IEEE (states and events)................................................................................................................. 301
3.4.8.1 INDOOR..............................................................................................................................................301
3.4.8.2 IEEE.IOBOX<index>.State...................................................................................................................301
3.4.8.3 IEEE.IOBOX<index>.IN........................................................................................................................302
3.4.8.4 IEEE.IOBOX<index>.ANA....................................................................................................................302
3.4.9 ANT (ANT states and events) ......................................................................................................... 303
3.4.9.1 ANT.Heartbeat...................................................................................................................................303
3.4.9.2 ANT.Speed..........................................................................................................................................303
3.4.9.3 ANT.Cadence......................................................................................................................................304
4 APPLICATION DEVELOPMENT GUIDE........................................................................................................ 305
4.1 WHAT KIND OF RULES SHOULD BE CONSIDERED TO PREPARE APPLICATION WITH MAMBO2-B6/UXFS......................................305
4.2 TEST YOUR MAMBO2-B6/UXFS BY CREATING A SIMPLE CONFIGURATION.....................................................................306
4.2.1 How to connect a Bluetooth audio headset to a MAMBO2-UXFS ...................................................307
4.3 START A GPRS/TCP CONNECTION................................................................................................................... 308
5 HOW TO SEND SMS MESSAGE TO THE MAMBO2-B6/UXFS DEVICE ...........................................................309
6 NMEA MESSAGES SUPPORTED BY MAMBO2-B6/UXFS DEVICE..................................................................310
6.1 DESCRIPTION OF NMEA OUTPUT MESSAGES ........................................................................................................ 310
6.1.1 $GPGGA message.......................................................................................................................... 311
6.1.2 $GPRMC message.......................................................................................................................... 311
6.1.3 $GPGSV message........................................................................................................................... 312
6.1.4 $GPGSA message........................................................................................................................... 312
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 14 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
6.1.5 $GPVTG message........................................................................................................................... 313
6.1.6 $GPGLL message............................................................................................................................ 313
6.1.7 $GPIOP message............................................................................................................................ 314
6.1.8 $GPGSM message.......................................................................................................................... 314
6.1.9 $GPAREA message......................................................................................................................... 315
6.1.10 $GP3DP message......................................................................................................................... 315
6.1.11 BIN protocol and its format.......................................................................................................... 316
6.1.12 FDB protocol and its format......................................................................................................... 317
7 APPENDIX................................................................................................................................................ 320
7.1 HOW TO UPDATE A NEW FIRMWARE INTO THE MAMBO2-B6/UXFS..........................................................................320
7.2 SUPPORTED DYNAMIC ENTRIES.......................................................................................................................... 320
7.3 LANGUAGE RESOURCES................................................................................................................................. 324
7.4 SUPPORTED PROTOCOLS WHEN SENDING MESSAGES VIA SMS, CSD OR TCP, USB, BLUETOOTH AND SD-CARD ...........................331
7.5 DEFAULT SETTINGS...................................................................................................................................... 332
7.6 SUPPORTED CHARACTER SETS........................................................................................................................... 334
7.6.1 GSM alphabet tables and UCS2 character values............................................................................335
7.7 HOW TO CONVERT THE COORDINATES.................................................................................................................. 338
7.8 EXPLANATION OF THE HISTORY BINARY DATA........................................................................................................ 339
7.8.1 Maximum values & the time the history space will be used up.......................................................339
7.9 MAMBO2-B6/UXFS COMMUNICATION MODES AND THEIR FUNCTIONALITY...................................................................340
7.10 BUTTONS AND LEDS DESIGNATION OF THE KEYFOB CORRESPONDING TO THE FIRMWARE VERSION 2.5.X.......................................341
7.11 I/O-BOX PINOUT................................................................................................................................... 342
7.12 MAMBO2-B6/UXFS CONFIGURATION EXAMPLES............................................................................................ 343
7.12.1 Basic Configuration Examples...................................................................................................... 343
7.12.1.1 Alarm Syntax....................................................................................................................................343
7.12.1.2 History base alarms..........................................................................................................................343
7.12.1.2.1 History entries based on the distance .......................................................................................343
7.12.1.3 Voice calls based alarms..................................................................................................................343
7.12.1.3.1 Accept all or specific incoming voice calls .................................................................................343
7.12.1.3.2 Refuse voice calls after the second ring.....................................................................................343
7.12.1.3.3 Spy calls......................................................................................................................................343
7.12.1.4 CSD (Data calls) based alarms..........................................................................................................344
7.12.1.4.1 Accept incoming data calls.........................................................................................................344
7.12.1.4.2 Refuse data calls after the second ring......................................................................................344
7.12.1.5 SMS based alarms............................................................................................................................344
7.12.1.5.1 SMS responses for self defined commands...............................................................................344
7.12.1.6 Bearing based alarms.......................................................................................................................344
7.12.1.6.1 SMS responses for self defined commands...............................................................................344
7.12.2 Advanced Examples..................................................................................................................... 345
7.12.2.1 Navigation speed based alarms.......................................................................................................345
7.12.2.1.1 Check the over speed of the device each 5 seconds..................................................................345
7.12.2.2 Trigger based alarms........................................................................................................................345
7.12.2.2.1 Save and load important trigger states......................................................................................345
7.12.2.3 Counter based alarms......................................................................................................................345
7.12.2.3.1 Limit the number of automatically sent SMS.............................................................................345
7.12.2.4 Distance based actions....................................................................................................................346
7.12.2.4.1 Report a position each 1000 metres via SMS.............................................................................346
7.12.2.5 History for combined conditions.....................................................................................................346
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 15 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
7.12.2.6 Time based history entries...............................................................................................................346
7.12.2.7 Time and distance based history entries.........................................................................................346
7.12.2.8 TCP storage based actions...............................................................................................................347
7.12.2.8.1 Send special device information to server periodically ............................................................347
7.12.3 Special consideration when using firmware features....................................................................349
7.12.3.1 Using commands inside alarms.......................................................................................................349
7.12.3.2 SMS send..........................................................................................................................................349
7.12.3.3 CSD send..........................................................................................................................................349
7.12.3.4 Storing information to non volatile memory...................................................................................349
7.13 ISP, GPRS CONFIGURATION PARAMETERS OF GERMAN SERVICE PROVIDERS.....................................................................350
7.14 USED ABBREVIATIONS................................................................................................................................. 350
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 16 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Cautions
Information furnished herein by FALCOM is believed to be accurate and reliable. However, no
responsibility is assumed for its use. Please, read carefully the safety precautions.
If you have any technical questions regarding this document or the product described in it, please
contact your vendor.
General information about FALCOM and its range of products are available at the following Internet
address: http://www.falcom.de/
Trademarks
Some mentioned products are registered trademarks of their respective companies.
Copyright
This documentation is copyrighted by FALCOM Wireless Communications GmbH with all rights
reserved. No part of this documentation may be produced in any form without the prior written
permission of FALCOM Wireless Communications GmbH.
FALCOM Wireless Communications GmbH.
No patent liability is assumed with respect to the use of the information contained herein.
Note
Specifications and information given in this document are subject to change by FALCOM without notice.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 17 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
1 INTRODUCTION
This document describes the operation of the firmware version 2.6.0 and later and the supported
configuration commands set to configure your personal tracker MAMBO2-B6/UXFS and adapt it to your
personal needs.
 This document is relating only to the FALCOM product MAMBO2-B6/UXFS.
The firmware running on the MAMBO2-B6/UXFS device has been developed to accommodate a wide
variety of applications and integrate your MAMBO2-B6/UXFS in a stand-alone device.
 Before using the MAMBO2-B6/UXFS device or upgrading it to a new firmware version, please
read the latest product information listed in chapter 1.2 "Related Documents" .
1.1
Scope of the document
This manual is divided into 7 chapters. Each chapter contains different information how to work with
the software running on the MAMBO2-B6/UXFS. To help you find the needed information quickly and
easy, here below there are listed a brief description for each chapter:
➢ Chapter 2 "General" presents the basic benefits of the firmware, lists the key features and
describes the operation principle. This chapter represents figuratively the general system
requirements you can use for accessing the personal tracker MAMBO2-B6/UXFS. It also
provides a brief overview about the TCP/IP protocol.
➢ Chapter 3 „PFAL Commands, " lists all PFAL commands supported by the firmware and shows
the syntax of these commands. It gives you a detailed description about the PFAL commands
and supported settings and shows some examples how to use these command. The firmware
contains also configuration parameters intended to store the settings of some PFAL
commands. These configuration parameter and a description for each setting is given in
chapter 3.3. Chapter 3.3.16 contains a step-by-step guide to show you how to create your
own application, more especially how to define alarms and their configuration possibilities
when using events and states as conditions for executing PFAL commands. Here is also
explained what are Events and States and differences between them. System States and
Events are listed and described in chapter 3.4.
➢ Chapter 4, "Application Development Guide" describes how to transfer input messages from
your PC to your MAMBO2-B6/UXFS, how to test and evaluate your MAMBO2-B6/UXFS
device. How to load a simple configuration into the MAMBO2-B6/UXFS, how to use IEEE
features with the MAMBO2-B6/UXFS, how to set the LEDs light when an event occurs and
how to configure Buttons on the device to release or send out alarms as notification. It also
describes how to communicate remotely with the MAMBO2-B6/UXFS device from a TCPserver.
➢ Chapter 5, "How to send SMS message to the MAMBO2-B6/UXFS device" presents how SMS
messages can be sent from your mobile phone to the MAMBO2-B6/UXFS device. More
precisely, how to configure MAMBO2-B6/UXFS device via SMS.
➢ Chapter 6 „NMEA messages supported by MAMBO2-B6/UXFS device" describes the output
protocols (NMEA messages) supported by the MAMBO2-B6/UXFS device.
➢ Chapter 7 "Appendix" represents how to reprogram the internal FLASH memory of the
MAMBO2-B6/UXFS device with new firmware, the supported protocols, dynamic entries,
firmware default settings and different configuration examples to use your MAMBO2B6/UXFS device.
 This document uses the hypertext links (highlighted in blue) allowing you to navigate the
chapters/sections, tables and text.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 18 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
 Table of Contents (TOC) or PDF bookmarks above will help you you locate the chapter/section
you need. This document can also be easily used for keyword-based search in order to find
specific entries.
1.2
Related documents
Some others PDF documents such as FCC approval, application notes, Certificate of Conformity R&TTE
etc. are available on the Web at: http://www.falcom.de/ in the published download area.
In addition to this document, the following files comprise the full set of MAMBO2-B6/UXFS product
manuals, which are also available on the Web at: http://www.falcom.de/ in the protected download area.
NR
PDF file name
Description
[1]
MAMBO2-B6/UXFSHardwareManual.pdf
Contains information about the hardware features and technical
details.
[2]
MAMBO2-B6/UXFSEvalKitGettingStarted.pdf
Contains an introduction how to get started with MAMBO2B6/UXFS EVALKIT, how do the software and hardware operate,
factory preloaded configuration settings etc.
[3]
AppNoteMAMBO2-B6/UXFSSoftwareUpdate.pdf
Contains information how to upgrade the MAMBO2-B6/UXFS
device to a new firmware version locally via Bluetooth or USB.
[4]
AppNotesRemoteUpdateWithWorkbench.pdf
Contains information how to upgrade the MAMBO2-B6/UXFS
device to a new firmware version remotely via TCP.
[5]
AppNotesMAMBO2AudioHeadSet&HandfreeSet.pdf
Contains information how about voice calls over Bluetooth
headset or hands-free kit.
[6]
AppNotes_Transform_history_data.pdf
Contains information of how to transform/convert history data
that are being transmitted from MAMBO2-B6/UXFS via TCP
connection to the server.
[7]
AppNote_Remote_update.pdf
Contains information of how to upgrade the MAMBO2-B6/UXFS
device to a new firmware revision remotely via TCP.
[8]
AppNoteMAMBO2SerialConnectionOnLINUX.pdf
Contains information how to perform a serial connection with
MAMBO2-B6/UXFS on LINUX operating system.
[9]
AppNoteGettingStartedWithKeyfob&IOBOX.pdf
Contains information about Keyfob and I/O-Box as well as how to
get stated with them.
These PDF files are viewable and printable from Adobe Reader. If you do not have the Adobe Reader installed,
you can download it from http://www.adobe.com
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 19 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
2 GENERAL
The MAMBO2-B6/UXFS device offers a speedy development of system solutions within the fields of:
➢ Personal security and recovery/emergency services
➢ Fleet tracking management
➢ Real-time positioning
➢ Theft protection
➢ Territory monitoring
➢ GPS Data Collection
➢ Distance calculations
➢ Point-to-Point navigation
➢ Outdoor sports and activities
➢ Trip management and many others
2.1
Features of the operating firmware
MAMBO2-B6/UXFS is an advanced personal tracker and personal tracking system that uses a quad-band
GSM/GPRS technology for two way communication and the latest GPS technology for positioning.
MAMBO2-B6/UXFS is an all-in-one handheld product equipped with a sophisticated software that
allows system integrators and developers the possibility to develop their own cost efficient and flexible
applications in both SMS and TCP communication modes. This gives MAMBO2-B6/UXFS the ability to
transmit its position not only to your cell phone by SMS, but also to an internet server by GPRS. The
operating firmware is ideally suited for personal security for independent workers, fleet management
tracking, safety locator devices for police officers and fire/rescue personnel, and so much more.
The operating firmware offers the following main features:
✔
Device behaviour can be fully adapted to user application requirements,
✔
Possibility to gather and exchange information by device and/or server,
✔
Advanced control of different communication modes (Local, GSM and GPRS/TCP
communications).
✔
Automatically switching between GSM and GPRS working modes.
✔
Different power saving modes,
✔
Automatically/manually connecting/disconnecting to/from the GPRS/TCP services.
✔
Allows access to an internet server over GPRS. Advantages in terms of cost and speed, with low
costs option for Web- based client-server applications (always on-line - pay for the data you
send or receive, rather than the time spent on-line).
✔
Create your own protocol how the device will transmit its data via SMS or TCP (generally for
server application).
✔
Uses different types of dynamic protocols that can be sent through different data channels
(USB, Bluetooth, SMS, Data Call, TCP).
✔
Offers remote configuration and communication over GSM and TCP, more specifically; SMS
message, TCP packet generation and voice calls as well as handling of incoming SMS, voice calls
and TCP packets.
✔
Allows configuration of simple and complex behaviour depending to its current situation,
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 20 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
✔
Different types of tracking applications such vehicle tracking, kid tracking and assets tracking.
Their location can be sent via GPRS/TCP to a remote server, via SMS or data call to a GSM
modem, or via Email to an email address/server.
✔
Fully compatible with Trace4You service provided by FALCOM. Offers location and tracking of
objects (people, tracks, boats, vehicle etc.) on-line from Internet.
✔
MAMBO2-B6/UXFS offers firmware upgrade remotely via TCP.
✔
Download all or a part of the history stored data remotely or locally
✔
Clear all history stored records.
✔
Supports flexible power saving features (sleep modes). Various wakeup events be used (even in
combination) to wake up the system.
✔
Buffering GPS positions* in case of GPRS/TCP connection drops
✔
Offers GPRS cell selection and re-selection processes.
✔
Commands and messages can be routed from one communication interface to another,
✔
Tracking down the initialization/execution of firmware, monitoring runtime errors from
different communication interfaces (Locally, GSM and TCP),
✔
Supports user generated events to report device changes and perform alarms.
✔
Allows flexible configuration which allows to adapt its behaviour to almost any environment or
situation,
✔
Up to 20 TIMERs available - TIMERs properties and their configuration methods affect the
functionality to activate events handler and execute actions at regular interval,
✔
Up to 20 TRIGGERs implemented to execute and start various actions to a particular time,
✔
Up to 20 COUNTERs implemented to limit the number of actions executed automatically,
✔
History function (stores the waypoints of a vehicles path on-board FLASH memory. The
waypoints are downloaded remotely by Internet or after the vehicle is back home by a PC),
✔
Following waypoints (a route) forward or backward,
✔
Geo-fencing functionality (incl. park-area functionality, send report when park-area leaved). Up
to 100 Geofencing zones included within up to 32 areas (with inside/outside features. Sending
reports when device enters in a pre-defined zone, deviates off a pre-defined route or it detects
that a vehicle leaves a pre-defined country and many others),
*)
The firmware contains a TCP buffer. Thus the GPS position data can be internally stored in case
the connection to the services will be dropped (e.g. bad GSM coverage). Once the connection will
be re-established, the stored data will be sent directly to the used remote server. Following a
short overview, how many packets (data) can internally be buffered:
binary RMC :
approx. 1800 (packets)
RMC+GPIO :
approx. 400 (packets)
GGA,GSA,GSV,RMC,GLL,VTG,GPIO,GSM :
approx. 80 (packets)
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 21 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
2.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
The principle operation of the firmware 2.6.xx
To integrate the MAMBO2-B6/UXFS device operating with firmware version 2.6.xx in the field
mentioned in chapter 2.1, page 21 requires the following elements:
1. A MAMBO2-B6/UXFS device,
2. A SIM card for Voice and/or DATA,
3. A remote Server (the setup Server in your network – e.g. trace4you server from FALCOM),
4. TCP settings (to connect to the remote server),
5. GPRS settings (provided by your provider),
6. User -PC (Personal Computer for using services provided by the remote server).
The illustration below represents interfaces used by the MAMBO2-B6/UXFS to access the Remote
Server via GPRS Network.
Figure 1:
Interfaces used by the firmware to access the remote server via GPRS Network
The principle operation of system is very simple. Each object/person is equipped with a MAMBO2B6/UXFS device, which consists of:
• an integrated GPS receiver with internal active antenna for reception of signals from GPS
satellite system,
• a GSM/GPRS modem with internal antenna for transmission of this GPS data by radio,
• a Mini USB to USB cable to enable data connectivity to a PC and making the device
configuration locally.
The GPS receiver inside the MAMBO2-B6/UXFS device uses the satellites data signals to calculate its
exact position. The GSM/GPRS modem allows transferring of the calculated GPS data through the GPRS
network (IP-based) to a remote server for internet-based application. A user web developed program
can be installed on the remote server to help you to represent the data being sent from the MAMBO2B6/UXFS devices on the integrated map. All MAMBO2-B6/UXFS devices shipped in the EVALKIT are
factory pre-configured allowing these devices to connect automatically to the trace4you server when
turned on.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 22 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
After turning the MAMBO2-B6/UXFS on, it attaches to the GPRS network using the GPRS configuration
settings, and temporary gets a dynamic IP-address allocated from this network. With the help of this IPaddress that constantly changes, the device is able to perform a TCP connection using the TCP settings
in the configuration. Now a client-server communication process between MAMBO2-B6/UXFS and
remote server takes place. The MAMBO2-B6/UXFS initiates a TCP communication session, while the
server waits for requests from the device. Upon server request the MAMBO2-B6/UXFS sends
automatically its logging data which are available in the contents of the command
$PFAL,MSG.Info.ServerLogin. By means of the IMEI number contained in this command all MAMBO2B6/UXFS device can be selected and separately configured from the remote server. The IMEI is an
unique number on each device and can be used as object identifier for such applications.
If you are going to use your own server, you have to modify the TCP settings using the FALCOM
Workbench software. (This program is developed by FALCOM and helps you to configure and evaluate
all FALCOM devices.) After the TCP configuration settings in the device are correctly set and
$PFAL,Cnf.Set,GSM.GPRS.AUTOSTART=1 is executed then, the MAMBO2-B6/UXFS will try to register
itself into the GSM network, attach to the GPRS services and by means of the modified TCP settings (see
chapter 3.3.14) tries to establish a TCP connection to your remote server.
The firmware in the MAMBO2-B6/UXFS device allows you to control all device operations by using PFAL
commands starting with “$PFAL”. PFAL-Commands are used to execute particular actions, read and set
particular configuration settings. These commands are used for all kinds of operation, including: SMS,
CSD, TCP and SMTP. For example, you may send current GPS position of the device to a phone number
or SMS server by simply using the command: $PFAL,GSM.SMS.Send,"+491234567",8,"Current Position:
" or to a remote server via TCP: $PFAL,TCP.Client.Send,8,"Current Position: ".
MAMBO2-B6/UXFS offers Geo-fence features for territory management, route verification, prohibited
locations, parking area and more, for reporting a wide variety of events, such as arrivals, departures,
deliveries, pick-ups, illegal entries, unauthorized movement, etc.. MAMBO2-B6/UXFS contains a datalogger function (History) that enables you to archive unique GPS positions in sequence for several days
long and analyse them later.
An action is a PFAL command (see example below in green color) that is executed in response to an
event (see example below in red color), for example, IF GPS position goes valid THEN execute a PFALCommand (e.g. transmit device position to a remote server).
Example: $PFAL,Cnf.Set,AL1=GPS.Nav.eFix=valid:TCP.Client.Send,8,"POS"
The firmware offers a rich of events, states and PFAL commands that allows you to create highperformance solutions with MAMBO2-B6/UXFS device.
Depending on your configuration settings inside the MAMBO2-B6/UXFS device, you can setup up to
three different solutions:
GSM
GPRS/Internet
The MAMBO2-B6/UXFS device can send and receive SMS messages, make and
receive Voice and Data calls. Thus, you are able to use such communication
services that do not require GPRS and TCP configurations and develop
applications in a short time. The execution of the PFAL commands takes place
via SMS from which you can access the information that your MAMBO2B6/UXFS device provides.
The MAMBO2-B6/UXFS device has its own TCP/IP stack thus it allows you to
develop internet-based application. Since the Internet is just a medium for
computers to "talk" to each other, it enables you to track, message or monitor
the MAMBO2-B6/UXFS devices at almost any PC in any location around the
world. The presence of a remote server is an essential prerequisite, which is
needed to log in the MAMBO2-B6/UXFS device and to enable access to the
information that your MAMBO2-B6/UXFS device provides. Such internet
applications require both GSM, GPRS, and TCP configuration settings.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 23 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
2.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
TCP/IP Overview
MAMBO2-B6/UXFS represents over TCP/IP stack a kind of serial communication. TCP (Transmission
Control Protocol) is the most widely used transport protocol for non-real-time Internet applications like
www, e-mail. It provides a connection-oriented end-to-end service ensuring the reliable transfer of
data, thus this service is mostly used for GPS application and the GPS information provided by your
MAMBO2-B6/UXFS device can also be represented on a map software for live tracking.
As with all other communication protocols, TCP/IP is composed of following layers:
IP
is responsible for moving packet of data from node to node. IP forwards each
packet based on a four-byte destination address (the IP number). IP operates
on gateway machines that move data from department to organization to
region and then around the world.
TCP
is responsible for verifying the correct delivery of data from client to server.
Data can be lost in the intermediate network. TCP adds support to detect
errors or lost data and to trigger retransmission until the data is correctly and
completely received.
PORT
is a name given to the package of subroutines that provide access to TCP/IP
on most system.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 24 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3 SUPPORTED PFAL COMMANDS, CONFIGURATION, STATES AND
EVENTS
All PFAL-Commands given in this document can be sent to MAMBO2-B6/UXFS either locally via USB or
Bluetooth with the help of FALCOM Workbench software, or remotely via SMS, TCP.
 When sending a series of PFAL commands on separate lines to the MAMBO2-B6/UXFS device,
you must leave a pause between the prior and the next PFAL command until the response (for
example SUCCESS, ERROR and so on - see possible responses in chapter 3.1.3) appears. This
avoids sending too many PFAL commands at a time without waiting for a response for each
PFAL command and avoids communication errors or syntax errors that may occur when the
command buffer is fulled up.
3.1
3.1.1
PFAL Command syntax and response structure
PFAL Command syntax
Each PFAL command is given as an alone caption. Within a chapter you will find a table containing the
following information.
➢ The first row of table represents the syntax of the PFAL-Command. Within the Command syntax
there are invalid characters such as "<", ">" and assigned name, which are used only to show
the Command syntax. You can not send such a syntax to the MAMBO2-B6/UXFS device.
➢ The second row of table gives one or more examples of how this command can be sent to the
MAMBO2-B6/UXFS device.
All PFAL-Commands in the firmware 2.6.0 and above support the following formats, and in one of these
formats the commands can be sent to the MAMBO2-B6/UXFS:
Format
1
2
3
4
Header
$PFAL
$PFAL
PFAL
PFAL
Command
<cmd>
<cmd>
<cmd>
<cmd>
Table 1:
[$]PFAL
<cmd>
Parameter
<parameter>
<parameter>
<parameter>
<parameter>
Checksum
<*CKSUM>
none
<*CKSUM>
none
End Sequence
<CR><LF>
<CR><LF>
<CR><LF>
<CR><LF>
PFAL-Command syntaxes.
This is the command header. Do not use the [$] sign when sending PFAL-Commands via
SMS as the [$] sign may be misinterpreted by the GSM and the command you sent via
SMS could not be executed.
Determines the type of the command to be executed. The [$]PFAL and <cmd> are
comma-separated. To specify a <cmd> command, throughout the document are used
<c_type> (the type of the command), <c_index> (the index of the command type) and
<c_subindex> (the sub-index following the command index). Other to say, a command
type is sorted by an index, and the command index closes the <cmd> with a sub-index if
the index supports any sub-index. An index changes according to the user-specified
command type and the sub-index changes according to the user-specified command
type and index. The command type, index and subindex are separated by a dot ["."
character]. A PFAL-Command may include one or more parameters. According to this
explanation, a <cmd> can be represented as follow:
<c_type>.<c_index>.<c_subindex> or
<c_type>.<c_index>=<value or
<c_type>.<c_index>.<c_subindex>=<value>
Combining <cmd> on the same PFAL-Command line is also allowed. If more than one
<cmd> is set on the same command line, they should be separated by semi-colon ";"
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 25 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
without double quotes. Note that, the maximal length of a PFAL-Command is limited to
1500 characters. In this case the common syntax my be represented as follow:
<cmd_1>;<cmd_2>;<cmd_3>….<cmd_n>
<parameter>
May contain different settings. Some parameters do not require any value, so left them
empty. According to this explanation, the syntax of the <parameter> is:
<parameter>=<value>
[<*CKSUM>]* Optional. If <*CKSUM> is used, it consists of an asterisk "*" character (without double
quotes), followed by two hexadecimal values. Only PFAL commands with valid
checksum can be accepted and executed.
In order to calculate the Checksum of the command to be sent to the target device, use
your own application. Below a small source code written in Visual Basic:
//*****************************************
Public Sub CheckSum(field As String)
If field = "" then CS = "*"
CS = 0
For i = 1 to Len(field)
CS = CS Xor Asc(Mid$(field, i, 1))
Next
CS = Hex(CS)
If Len(CS) =1 then CS = "0" & CS
CS = "*" & CS
END SUB
//*****************************************
Therefore, the string over which the checksum will be calculated is:
field = PFAL,<cmd>,<parameter>
excluding "$" character. The "CS" variable in the CheckSum procedure above must be
declared as a global variable.
[<CRLF>]
Optional. Carriage Return and Line Feed (ASCII CODE #13#10 (without any spaces) hexadecimal: 0x0D 0x0A)
According to the above explanation, the improved format to specify a PFAL command is:
$PFAL,<c_type>.<c_index>.<c_subindex>,<parameter>=<value><*CKSUM><CR><LF>
or
$PFAL,<c_type>.<c_index>.<c_subindex>,<parameter>=<value><CR><LF>
For example:
PFAL-Command
1
$PFAL,SYS.Device.Reset*31<CR><LF>
No parameter required
2
$PFAL,Sys.Trigger5=high<CR><LF>
No sub-index required
3
$PFAL,IO.LED1=hpulse,2000<CR><LF>
No sub-index required
4
$PFAL,Sys.Timer0.Start=single,5000<CR><LF>
All are required
5
$PFAL,Cnf.Set,DEVICE.NAME="myMAMBO2-B6/UXFS"<CR><LF>
Configuration command
6
$PFAL,Cnf.Set,AL0=IO.BTN.e0=long:IO.LED1=cyclic,2000,500<CR><LF>
Alarm configuration command
Example 5 above sets device name to "myMAMBO2-B6/UXFS".
Example 6 above sets LED1 flashing, when a long event on the left button is detected.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 26 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
 Warning: It is suggested always to use a checksum inside the PFAL commands. Therefore, if
the checksum <*CKSUM> will not be used, please prevent using of ANY asterisk "*" character
inside the value of PFAL commands (especially 3 characters before the <CR><LF>).
3.1.1.1
Command types <c_type>
The command types <c_type> is used to separate the huge amount of commands to different types. The
following command types are currently available.
<c_type>
Definition
Accomplishes a predefined set of system tasks such as:
- System management tasks, including; Reset, Shutdown/power management etc.
Sys
- Initialization/interruption of system processes, including: Timers, Counters etc.
Cnf
- The operating firmware provides configuration parameters that can be set/changed or read. Based on
the parameter-settings some events will be occurred.
IO
- Accomplishes a predefined set of system peripheral commands allowing access to the buttons and LEDs
on MAMBO2-B6/UXFS and Keyfob.
GPS
- Accomplishes a predefined set of GPS commands including navigation, history logging and geo-fencing
data.
GSM
- Accomplishes a predefined set of GSM commands including SMS, voice calls, GPRS services etc.
TCP
- Accomplishes a predefined set of TCP connection commands including connecting, disconnecting and
sending of TCP packets to the predefined address of remote server etc.
MSG
- Accomplishes a predefined set of output messages (GPS protocols) allowing information to be
transmitted across the serial interface, CSD network or Internet (TCP).
Table 2:
3.1.1.2
Supported command types <c_type>.
Aliases
This PFAL-Command allows you to specify alias names for all available <c_type>, <c_index>,
<c_subindex>
By default, the following alias names are available:
Sys
is the alias name of
System
Cnf
is the alias name of
Config
If an alias name has been specified, it can freely be used instead of the original word (or number). To
specify alias names, please refer to chapter 3.3.7.1 page 220.
Notes
• To avoid misinterpretation, please assure that no equal or very similar aliases are used
inside the same command type/index. Also avoid starting aliases with numbers as they
might be misinterpreted as original index numbers.
3.1.2
Using identifiers (optional):
Syntax1
- $PFAL:id<idtxt>,<commands>*<CS><CRLF>
Syntax2
- $PFAL:id<idtxt>,<commands><CS><CRLF>
Syntax3
- PFAL:id<idtxt>,<commands>*<CS><CRLF>
Syntax4
- PFAL:id<idtxt>,<commands><CS><CRLF>
Table 3:
<idtxt>
Identifier syntaxes
Specifies an optional text, which do not contain any comma (,). The case sensitive text will be
returned within the response to that PFAL command.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 27 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
<commands>
Comprises one or more PFAL commands.
<CS>
NMEA Checksum (see description of the checksum in chapter 3.1.1)
<CRLF>
Carriage Return Line Feed - ASCII CODE 13 10 (without any spaces) - hexadecimal: 0x0D 0x0A)
3.1.3
Response message structure
PFAL-Command Configuration reports are outputted in the text format as shown in the table below.
Types of response command:
Respond message type if a single PFAL command line includes no
more then one command
Structure
Example
$PFAL,Cnf.Set,DEVICE.NAME=myMAMBO2-B6/UXFS<CRLF>
From read commands/configuration
$<cmd><CR><LF>
$report of executed parameter<CR><LF>
$SUCCESS or $ERROR<CR><LF>
$<end>
Example 1
$<Cnf.Get>
$NAME=unnamed MAMBO2-B6/UXFS
$SUCCESS
$<end>
From execution command/configuration
$<cmd><CR><LF>
$ report of executed parameter<CR><LF>
$SUCCESS or $ERROR<CR><LF>
$<end>
Example 2
$<Cnf.Set>
$NAME written to flash
$SUCCESS
$<end>
Respond message type if several commands are added in a single PFAL
command line
Structure
Example
$PFAL,Sys.Trigger0;Sys.Trigger5<CRLF>
From read commands/configuration
$<Sys.Trigger0><CR><LF>
$Trigger0=high<CR><LF>
$<Sys.Trigger5><CR><LF>
$Trigger5=low<CR><LF>
$SUCCESS<CR><LF>
$<end><CR><LF>
Respond message type if identifiers are used
Structure
Example
PFAL:id001,Sys.Trigger0<CRLF>
From read commands/configuration
$<Sys.Trigger0><CR><LF>
$Trigger0=high<CR><LF>
$SUCCESS<CR><LF>
$<end:001><CR><LF>
Table 4:
Response messages structure.
Note
• If the first command fails (i.e. wrong syntax or it can not be executed correctly), the system
will stop the execution of this command.
• If identifiers are submitted within PFAL commands, they will be returned inside PFAL
responses.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 28 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
PFAL Commands
The following table provides a complete list of PFAL commands used to manage/administrate different
parts of an application setup with MAMBO2-B6/UXFS. All commands listed in the table below should
start with $PFAL, when you send them to the MAMBO2-B6/UXFS device. However, when sending these
commands to the MAMBO2-B6/UXFS via SMS do not use the $-sign before, as it may be misinterpreted
by the GSM network.
 Please note that all PFAL commands listed in the table below could not be sent to the target
device in that form. Information about each command can be found within the respective
reference chapter. Use the hypertext links (shown in blue text) to navigate the chapter/sections
and to read the tasks the command performs when received.
Please note that, only regular quotation marks (" ") should be used in the PFAL commands,
configuration parameters, etc. As this documentation has been created using OpenOffice, some
quotation marks might have been transformed to the 'starting' and 'ending' quotation marks,
which won't be accepted by the device.
PFAL COMMANDS
DESCRIPTION
Chapter
Alarm commands
Alarm.Info,<index>
Displays all conditions related to the selected alarm. Index ranges
3.2.1.1.1
from 0 to 99
Alarm.Clear,<index>
Clears the specified alarm. Index ranges from 0 to 99.
3.2.1.2.1
Sys.Tracking=<state>
Generates the corresponding Tracking events for general purpose
3.2.2.1.1
Sys.Geofence=<state>
Generates the corresponding Geofence events for general purpose
3.2.2.2.1
Sys.Security.Lock,"password"
Locks the system
3.2.2.3.1
Sys.Security.Unlock,"password"
Unlocks the system
3.2.2.3.3
Sys.Security.RemoveLock,"password"
Removes the system lock
3.2.2.3.2
Sys.Security.HideAlarm,"pasword"
Hides alarm configurations from being read out using a pasword
3.2.2.3.4
Sys.Security.UnhideAlarm,"pasword"
Removes the read protection of alarms using a pasword
3.2.2.3.5
Sys.RUpdate.Init,<type>,<option>,<size>,<sectors>,<confi
g>
Initialize remote firmware update
3.2.2.4.1
Sys.RUpdate.DataMode,<msg_input>
Define firmware upgrade channel & continue upgrading (including
binary update command and lists all binary commands)
3.2.2.4.3
Sys.RUpdate.Finish
Finish a started remote update and writes the new firmware into
the FLASH
3.2.2.4.4
Sys.Device.Reset
Resets the system
3.2.2.5.1
Sys.Device.Update
Sets the system into the update mode
3.2.2.5.2
Sys.Device.Shutdown
Shuts down the system immediately
3.2.2.5.3
Sys.Device.FactoryReset
Resets the user-configuration to factory default
3.2.2.5.4
Sys.Device.Sleep=<wakeup_conditions>
Sets the system into the sleep mode until the specified wakeup
condition is detected
3.2.2.5.5
Sys.Device.CfgUpdateMode
Saves the reconfigured alarm settings
3.2.2.5.6
System commands
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 29 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
PFAL COMMANDS
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DESCRIPTION
Chapter
Sys.Device.RestoreBios
Upgrades the on-board BIOS
3.2.2.5.7
Sys.Device.Speaker=<mode>
Enables/disable internal buzzer/laudspeaker
3.2.2.5.8
Sys.GSM.Enable
Powers on the GSM engine
3.2.2.6.1
Sys.GSM.Disable
Powers off the GSM engine
3.2.2.6.2
Sys.GSM.Reset
Resets GSM engine
3.2.2.6.3
Sys.GPS.Enable
Powers on GPS engine
3.2.2.7.1
Sys.GPS.Disable
Powers off GPS engine
3.2.2.7.2
Sys.GPS.Reset
Resets GSM engine
3.2.2.7.3
Sys.GPS.Sleep
Puts GPS into sleep mode
3.2.2.7.4
Sys.GPS.WakeUp
Wakes up GPS from sleep mode
3.2.2.7.5
Sys.BT.Enable
Powers on Bluetooth module
3.2.2.8.1
Sys.BT.Disable
Powers off Bluetooth module
3.2.2.8.2
Sys.BT.Reset
Resets Bluetooth module
3.2.2.8.3
Sys.CPU.Reset
Resets main controller and set system into the firmware update
mode.
3.2.2.9.1
Sys.IEEE.Enable
Powers on IEEE module
3.2.2.10.1
Sys.IEEE.Disable
Powers off IEEE module
3.2.2.10.2
Sys.IEEE.Reset
Resets IEEE module.
3.2.2.10.3
Sys.Power.Voltage
Queries the operating voltage
3.2.2.11.1
Sys.Power.Mode
Sets device into power saving mode
3.2.2.11.2
Sys.Bat.Voltage
Queries the current battery voltage
3.2.2.12.1
Sys.Bat.ChargeState
Gets the current battery state
3.2.2.12.2
Sys.Display.Enable
Powers on the OLED display
3.2.2.13.1
Sys.Display.Disable
Powers off the OLED display
3.2.2.13.2
Sys.SD.Mount
Mounts a mini-SD card. SD option is no longer available
3.2.2.14.1
Sys.SD.UnMount
Unmounts a mini-SD card. SD option is no longer available
3.2.2.14.2
Sys.SD.State
Queries the state of mini-SD card. SD option is no longer available
3.2.2.14.3
Sys.SD.Dir.Show
Shows the directory of mini-SD card. SD option is no longer
available
3.2.2.14.4
Display.Dialog=<id>,<"caption">,<icon>,<timeout>,<"OK"
>,<"Cancel">,<"text">
Creates and displays a dialog box on the screen.
3.2.2.15.1
Display.Alarm=<image>,<timeout>,<"text">
Displays a specific alarm icon on the screen
3.2.2.15.2
Display.Message=<"user">,<id>,<"caption">,<bgd>,<time
out>,<"text">[,<"answer1">...[,<"answer4">]]
Displays a specific message on the screen
3.2.2.15.3
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 30 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
PFAL COMMANDS
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DESCRIPTION
Chapter
Display.Popup=<id>,<color>,<button>,<icon>,<timeout>,
<"text">
Displays a specific popup on the screen
3.2.2.15.4
Display.Pois.Follow=<lat>,<lon>,<alt>,<radius>
Sets/updates the user POI to be followed
3.2.2.15.5
Display.Button.Enable
Enable Left and Right buttons on MAMBO2-B6/UXFS
3.2.2.15.6
Display.Button.Navigation
Disables Left and Right buttons on MAMBO2-B6/UXFS and enables
just the 5-way navigation key.
3.2.2.15.7
Display.Button.Disable
Disable Left and Right buttons on MAMBO2-B6/UXFS
3.2.2.15.8
Display.Button.Swap=<action>
Swaps buttons on MAMBO2-B6/UXFS
3.2.2.15.9
Sys.Timer<index>.Configure=<mode>,<timeout>
Configures a system timer
3.2.2.16.1
Sys.Timer<index>.Start=<timer_settings>
Starts/restarts a system timer
3.2.2.16.2
Sys.Timer<index>.Stop
Stops a running timer
3.2.2.16.3
Sys.Timer<index>.Pause
Pauses (suspends) a running timer
3.2.2.16.4
Sys.Timer<index>.Resume
Restarts the execution of a paused timer
3.2.2.16.5
Sys.Timer<index>.Arm
Arms an initialized and disarmed timer
3.2.2.16.6
Sys.Timer<index>.Disarm
Disarms an initialized and armed timer
3.2.2.16.7
Sys.Timer<index>.Erase
Erases the configuration of a timer
3.2.2.16.8
Sys.Timer<index>.Save<storage_index>
Saves a timer state to a storage index
3.2.2.16.9
Sys.Timer<index>.Load<storage_index>
Loads the saved timer state from a storage index
3.2.2.16.10
Sys.Timer<index>.State
Queries the state of a used timer
3.2.2.16.11
Sys.Trigger<index>=<state_type>
Activates/deactivates a system trigger
3.2.2.17.1
Sys.Trigger<index>
Queries current trigger state
3.2.2.17.2
Sys.Trigger<index>.Save<storage_index>
Saves the state of trigger to a storage index
3.2.2.17.3
Sys.Trigger<index>.Load<storage_index>
Loads a saved trigger from a storage index
3.2.2.17.4
Sys.Counter<index>.Set=<value>
Sets the value of a counter
3.2.2.18.1
Sys.Counter<index>.Increment=<inc_value>
Increments the existing value of a counter
3.2.2.18.2
Sys.Counter<index>.Decrement=<dec_value>
Subtracts the existing value of a counter
3.2.2.18.3
Sys. Counter<index>.State
Queries the state of a used counter
3.2.2.18.4
Sys.Counter<index>.Save<storage_index>
Saves the state of the counter to a storage index
3.2.2.18.5
Sys.Counter<index>.Load<storage_index>
Loads a saved counter from a storage index
3.2.2.18.6
Sys. Counter<index>.Clear
Sets a specified counter to 0
3.2.2.18.7
Sys.Macro<index>
Activates a configured macro
3.2.2.19.1
Sys.UserEvent<index>
Creates a user-event for specific application requirements
3.2.2.20.1
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 31 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
PFAL COMMANDS
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DESCRIPTION
Chapter
Cnf.Set,<parameter_name=value>
Enables to set up or change the device configuration settings
3.2.3.1
Cnf.Get,<parameter_name>
Enables to read out the device configuration settings
3.2.3.2
Cnf.Clear,<parameter_name>
Clears the available configuration settings of the set parameter
name
3.2.3.3
Cnf.ShowUser
Queries the configuration settings set by the user.
3.2.3.4
Cnf.ShowDefault
Queries the factory default settings
3.2.3.5
Cnf.Show
Queries the settings of all used parameters
3.2.3.6
Cnf.Search,<parameter_name>
Searches for a parameter name
3.2.3.7
IO.LED<index>=<config_type>
Configures the LED indicators
3.2.4.1
IO.Beep<index>=<config_type>
Generates beep tones
3.2.4.2
IO.Vibration=<config_type>
Manages device vibrations
3.2.4.3
GPS.Nav.Position<buffer_index>
Returns bee-line distance of the device from a stored location
3.2.5.1.1
GPS.Nav.Position<buffer_index>=<type>
Saves temporarily a device location or clears the data that exists in
the buffer index
3.2.5.1.2
GPS.Nav.Position<buffer_index>=Save<storage_index>
Moves the GPS data from the buffer and stores it to a storage
index
3.2.5.1.3
GPS.Nav.Position<buffer_index>=load<storage_index>
Loads the GPS data from storage to buffer index for temporarily
use
3.2.5.1.4
GPS.Nav.Distance
Queries the covered distance from a start point
3.2.5.1.5
GPS.Nav.Distance.Save
Stores the distance into the memory
3.2.5.1.6
GPS.Nav.Distance.Load
Loads the saved distance from the memory
3.2.5.1.7
GPS.Nav.Distance=<value>
Sets/resets the distance to a user defined value
3.2.5.1.8
GPS.Nav.SaveLastValid
Saves last valid position, if no GPS-fix valid.
3.2.5.1.9
GPS.Nav.SetHeadingTolerance=<value>
Sets GPS heading tolerance
3.2.5.1.11
GPS.Nav.Static=<value>
Enables static navigation (MAMBO2 with SiRF receiver only)
3.2.5.1.12
GPS.Nav.SBAS=<value>
Enables SBAS (MAMBO2 with SiRF receiver only)
3.2.5.1.13
GPS.Nav.TripCalc
Calculates the distance and elevation of a trip manually
3.2.5.1.14
GPS.History.Write,<add_prot_to_memory>,<"text">
Records a GPS position data into the history memory
3.2.5.2.1
GPS.History.Clear
Clears the history memory.
3.2.5.2.2
GPS.History.GetStart
Queries the oldest date stored in the history memory.
3.2.5.2.3
GPS.History.SetRead,<s_date>,<s_time><e_date>,<e_time>
Selects the number of records from the history memory to be
downloaded.
3.2.5.2.4
Configuration commands
I/O commands
GPS commands
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 32 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
PFAL COMMANDS
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DESCRIPTION
Chapter
GPS.History.Read
Downloads the selected records from the history memory.
3.2.5.2.5
GPS.History.Push
Downloads all selected history at once.
3.2.5.2.6
GPS.Geofence.Park.Set
Places/activates a virtual circular fence around vehicle (Park area).
3.2.5.3.1
GPS.Geofence.Park.Remove
Disables an activated park area.
3.2.5.3.2
GPS.Geo-fence.GeoState,<geo_id>
Queries the state of a defined geo-fence.
3.2.5.3.3
GPS.Geo-fence.AreaState,<area_id>
Queries the state of a defined area.
3.2.5.3.4
GPS.Trip.Start
Starts a Trip
3.2.5.4.1
GPS.Trip.Stop
Stops a started Trip
3.2.5.4.2
GSM.PIN=<"pin">
Enters the PIN number of the used SIM card.
3.2.6.1.1
GSM.PUK=<"puk">,<"pin">
Enters the PUK and PIN numbers.
3.2.6.1.2
GSM.IMEI
Queries the serial identification number of the product.
3.2.6.1.3
GSM.SIMID
Queries the ID of SIM Card.
3.2.6.1.4
GSM.OwnNumber
Queries the caller's phone number.
3.2.6.1.5
GSM.Balance
Queries the account information of the used SIM card.
3.2.6.1.6
GSM.USSD,<"ussd_cmd">,<timeout>
Performs an USSD call and return its answer
3.2.6.1.7
GSM.MCC
Queries the current mobile country code information of the
operator the device is registered to.
3.2.6.1.8
GSM.Band=<band>
Specifies the GSM band used by the device.
3.2.6.1.9
GSM.VoiceCall.Dial,< "p_number">
Performs a GSM Voice call.
3.2.6.2.1
GSM.VoiceCall.Accept
Accepts an incoming voice call.
3.2.6.2.2
GSM.VoiceCall.Hangup
Hangs-up an active voice call.
3.2.6.2.3
GSM.Audio.ActiveProfile
Selects and activates an audio profile
3.2.6.3.1
GSM.Audio.ShowProfile
Shows all details of the specified audio profile.
3.2.6.3.2
GSM.Audio.SaveProfileAs
Stores the currently used audio settings to a profile
3.2.6.3.3
GSM.Audio.DeleteProfile
Erases a stored profile
3.2.6.3.4
GSM.Audio.EchoCancel
Activates or deactivates echo cancellation for a handsfree
speaker/microphone
3.2.6.3.5
GSM.Audio.SideTone
Activates or deactivates handset side tone
3.2.6.3.6
GSM.Audio.SpeakerMute
Activates or deactivates speaker output
3.2.6.3.7
GSM.Audio.SpeakerGain
Sets speaker gain (loudness)
3.2.6.3.8
GSM.Audio.MicrophoneMute
Activates or deactivates microphone
3.2.6.3.9
GSM.Audio.HandsfreeMicroGain
Sets microphone gain (loudness) for handsfree microphone
3.2.6.3.10
GSM commands
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 33 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
PFAL COMMANDS
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DESCRIPTION
Chapter
GSM.Audio.HandsetMicroGain
Sets microphone gain (loudness) for handset microphone
3.2.6.3.11
GSM.Audio.AudioRingPath
Selects the path to which ring signals signals (i.e. voice
input/output) are directed
3.2.6.3.12
GSM.Audio.RingTone
Selects the used ring tone for incoming calls
3.2.6.3.13
GSM.Audio.RingGain
Sets the gain (loudness) for ring tones
3.2.6.3.14
GSM.Audio.AudioPath
Selects the path for regular audio signals (i.e. voice )
3.2.6.3.15
GSM.Audio.SoundMode
Selects a global sound mode for the device
3.2.6.3.16
GSM.SMS.Send,<"p_number">,<protocols>,<"text">
Sends an SMS to the defined phone number.
3.2.6.4.1
GSM.SMS.SendRaw,<"p_number">,<protocols>,<"text">
Sends an SMS in raw data format.
3.2.7.3.2
GSM.SMS.Inbox.Clear
Clears all inbox SMS messages (SMS memory for incoming
messages).
3.2.6.4.3
GSM.SMS.Inbox.State
Queries all inbox SMS messages.
3.2.6.4.4
GSM.SMS.Outbox.Clear
Clears all outbox SMS messages (SMS memory for outgoing
messages).
3.2.6.4.5
GSM.SMS.Outbox.State
Queries all outbox SMS messages.
3.2.6.4.6
GSM.DataCall.Send,<protocols>,<"text">
Sends messages to a GSM modem via an established data call.
3.2.6.5.1
GSM.DataCall.Accept
Accepts an incoming Data call.
3.2.6.5.2
GSM.DataCall.Hangup
Hangs-up an active voice call.
3.2.6.5.3
GSM.GPRS.Connect
Connects device to GPRS network.
3.2.6.6.1
GSM.GPRS.Disconnect
Disconnects device from GPRS network.
3.2.6.6.2
GSM.GPRS.State
Returns the GPRS state.
3.2.6.6.3
GSM.GPRS.Traffic=<complete>,<incoming>,<outgoing>
Sets or reads the GPRS traffic counter.
3.2.6.6.4
TCP.Client.Connect
Performs a TCP connection to the remote server.
3.2.7.1.1
TCP.Client.Disconnect
Performs a TCP Disconnection from the connected server.
3.2.7.1.2
TCP.Client.State
Reads the TCP connection state.
3.2.7.1.3
TCP.Client.Send,<protocols>,<"text">
Sends a TCP packet to the connected remote server.
3.2.7.1.4
TCP.Client.ClearSendBuffer
Clears the internal TCP buffer for outbound packets
3.2.7.1.5
TCP.Storage.Dispatch
Moves the currently stored information inside the TCP storage to
the outgoing TCP buffer.
3.2.7.2.1
TCP.Storage.Clear
Clears the contents of the created TCP storage.
3.2.7.2.2
TCP.Storage.AddProtocol,<protocol>,<"text">
Writes the specified protocols and/or user text to the TCP storage.
3.2.7.2.3
TCP.Storage.AddRecord,<protocol>,<"text">
Appends a binary dataframe to TCP storage.
3.2.7.2.4
TCP.SMTP.Send,<"email_to">,<protocols>,<"text">
Sends out an email in user predefined format
3.2.7.3.1
TCP commands
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 34 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
PFAL COMMANDS
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DESCRIPTION
Chapter
Sends out an email in raw data format
3.2.7.3.2
MSG.Send.Serial,<protocols>,<"text">
Sends protocols to Bluetooth in user predefined format.
3.2.8.1
MSG.Send.RawSerial,<protocols>,<"text">
Sends protocols to Bluetooth in raw data format.
3.2.8.1.2
MSG.Send.USB,<protocols>,<"text">
Sends protocols to USB in user predefined format.
3.2.8.1.3
MSG.Send.RawUSB,<protocols>,<"text">
Sends protocols to USB in raw data format.
3.2.8.1.4
MSG.Send.File,<"filename">,<protocols>,<"text">
Saves protocols into a file to the mini-SD card in user predefined
format.. SD option is no longer available
3.2.8.1.5
MSG.Send.RawFile,<"filename">,<protocols>,<"text">
Saves protocols into a file to the mini-SD card in raw data format.
SD option is no longer available
3.2.8.1.6
MSG.Send.CSD,<protocols>,<"text">
Sends protocols to a GSM modem via an established data call.
3.2.8.1.8
MSG.Send.Service,<protocols>,<"text">
Sends protocols to a connected service server via TCP.
3.2.8.1.7
MSG.Send.TCP,<protocols>,<"text">
Sends protocols to a connected server via TCP.
3.2.8.1.9
MSG.Send.SMTP,<"email_to">,<protocols>,<"text">
Sends protocols to an email address.
3.2.8.1.10
MSG.Mode.<interface>=<out_protocol>,<comm_mode>
Sets communication mode for receiving data and data channel for
forwarding.
3.2.8.2.1
MSG.Version.Complete
Queries the complete versions of components in the device.
3.2.8.3.1
MSG.Version.Modules
Queries the version of all modules.
3.2.8.3.2
MSG.Version.BIOS
Queries the firmware version of microcontroller
3.2.8.3.3
MSG.Version.HardwareRev
Queries the hardware revision of PCB.
3.2.8.3.4
MSG.Version.Hardware
Queries the hardware version of target device.
3.2.8.3.5
MSG.Version.Software
Queries the software version running on device.
3.2.8.3.6
MSG.Version.SoftwareID
Queries the software ID.
3.2.8.3.7
MSG.Info.ServerLogin
Identifies the device to the FALCOM’s Server.
3.2.8.4.1
MSG.Info.Protocol,<protocols>,<"text">
Transmits the selected protocols to the sender.
3.2.8.4.2
MSG.Info.Time
Displays the current system time.
3.2.8.4.3
MSG.Info.Alarm,<alarm_index>
Transmits the selected alarm to the sender.
3.2.8.4.4
MSG.Info.GetInterfaceName
Queries the current communication interface.
3.2.8.4.5
IEEE.Keyfob<index>.LED<led_index>=<state>
Sets and controls LED blinking to a Keyfob
3.2.9.1.1
IEEE.Keyfob<index>.Beep=<state>
Sets and controls the Beep tones to be generated on a Keyfob.
3.2.9.1.2
IEEE.Keyfob<index>.Vibration=<state>
Sets the type of vibration alert on a Keyfob
3.2.9.1.3
IEEE.Keyfob<index>.bat.level
Queries the battery voltage level of the keyfob.
3.2.9.1.4
IEEE.IOBox<index>.OUT<port>=<state>
Configures the outputs on an I/O-BOX
3.2.9.2.1
IEEE.IOBox<index>.power=<mode>
Set the operation mode on an I/O-BOX
3.2.9.2.2
TCP.SMTP.SendRaw,<"email_to">,<protocols>,<"text">
Communication/ Messaging commands
IEEE commands
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 35 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Communication/ Messaging commands
IEEE.IOBox<index>.bat.level
Gets battery charge state
3.2.9.2.3
BT.Audio.Bound
Pairs Bluetooth audio devices
3.2.10.1
BT.Audio.Connect
Places both Bluetooth devices in the connection mod
3.2.10.2
BT.Audio.Disconnect
Closes a currently open audio connection
3.2.10.3
Bluetooth Audio commands
Table 5:
Complete list of PFAL commands
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 36 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Alarm" command type
3.2.1.1
3.2.1.1.1
"Info" command index
Alarm.Info,<index> – Checks alarm conditions
Command syntax
$PFAL,Alarm.Info,<index>
Examples
$PFAL,Alarm.Info,1
If the alarm <index> does not exist the response looks like this:
$conditions of alarm 20:
$CND0: unused
$CND1: unused
$CND2: unused
$CND3: unused
$CND4: unused
$Action0: unused
$Action1: unused
$Action2: unused
$Action3: unused
$Action4: unused
$SUCCESS
Responses
If the alarm <index> exists the response looks like this:
$conditions of alarm 1:
$CND0: true (SYS.Trigger.s0=low)
$CND1: false (SYS.Bat.sVoltage<=38.000000)
$CND2: unused
$CND3: unused
$CND4: unused
$Action0: SYS.Trigger0=high
$Action1: DISPLAY.Dialog
$Action2: unused
$Action3: unused
$Action4: unused
$SUCCESS
Message description
This command is used to check the current state of conditions setup in the selected alarm
<index>.
Parameter description
<index>
Determine what alarm index should be called. The index ranges from 0 to 99, without leading
"0".
Note:
• This command can be used to check even most complex alarm configurations step by step
to validate its behaviour.
• Events are always shown as „true" (even if there are several events inside an alarm - in
practice such an alarm will never be executed).
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 37 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.1.2
3.2.1.2.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Clear" command index
Alarm.Clear,<index> – Clears settings to an alarm
Command syntax
$PFAL,Alarm.Clear,<index>
Examples
$PFAL,Alarm.Clear,1
$alarm 1 deactivated
Responses
$alarm 1 cleared
$SUCCESS
Message description
This command is used to stop and clear the settings of the alarm having the specified index. The
device responds an error if the specified index is not found in the configuration.
Parameter description
<index>
Determine what alarm should be cleared. It specifies a number ranging from 0 to 99, without
leading "0" (e.g. 1).
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 38 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Sys"command type
3.2.2.1
3.2.2.1.1
Command syntax
"Tracking" command index
Sys.Tracking=<state> Generates events and states
$PFAL,Sys.Tracking=<state>
$PFAL,Sys.Tracking=high
Examples
$PFAL,Sys.Tracking=low
$Alarm = low
$SUCCESS
Response
Message description
This command can be used to trigger the corresponding event or to change the corresponding
state. You can execute this command to generate an event and start or stop something from the
user menu on the MAMBO2-B6/UXFS.
Parameter description
<state>
Specifies which of the following events should be occurred when executing this command.
The following parameters are available for use in this command:
Value
Meaning
high
Generates the event Sys.Tracking.e=high and sets the state of this
command to Sys.Tracking.s=high.
low
Generates the event Sys.Tracking.e=low and sets the state of this
command to Sys.Tracking.s=low.
load
Generates the event Sys.Tracking.e=load and loads the command with the
parameter found in the slot 9. A parameter should be saved before
loading.
save
Generates the event Sys.Tracking.e=save and stores the parameter the
command currently has into the slot 9.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 39 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.2
3.2.2.2.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Geo-fence" command index
Sys.Geofence=<state> Generates different events and states
Command syntax
$PFAL,Sys.Geofence=<state>
Examples
$PFAL,Sys.Geofence=high
$PFAL,Sys.Geofence=low
Message description
This command can be used to trigger the corresponding event or to change the corresponding
state. You can execute this command to generate an event and start or stop something from the
user menu on the MAMBO2-B6/UXFS.
Parameter description
<state>
Specifies which of the following events should be occurred when executing this command.
The following parameters are available for use in this command:
Value
Meaning
high
Generates the event Sys.Geofence.e=high and sets the sets the state of
this command to Sys.Geofence.s=high.
low
Generates the event Sys.Geofence.e=low and sets the sets the state of this
command to Sys.Geofence.s=low.
load
Generates the event Sys.Geofence.e=load and loads the command with
the parameter found in the slot 9. A parameter should be saved before
loading.
save
Generates the event Sys.Geofence.e=save and stores the parameter the
command currently has into the slot 9.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 40 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Security" command index
The software has a built-in locking feature, which prevents the unauthorized users from accessing the
system. The system remains locked until executing the UnLock command with correct password. An
application may use this mechanism for the following purposes:
 to ensure that system does not complete any user request while the system is locked.
 to prevent unauthorized users attempting to change the system configuration.
To remove permanently the password, first UnLock it and then execute the command
$PFAL,Sys.Security.RemoveLock,"used_password".
3.2.2.3.1
Sys.Security.Lock,<"password"> – Locks system
Command syntax
$PFAL,Sys.Security.Lock,<"password">
Examples
$PFAL,Sys.Security.Lock,"12345"
$security lock installed
Responses
$SUCCESS
Message description
This command is used to lock the device with a password and prevent it from the unauthorized
accesses on all communication interfaces (regardless of the input PFAL-Commands via TCP, SMS,
CSD, USB or Bluetooth). To unlock the system just for the time the device is running, use the
command (Sys.Security.Unlock,"password"). However, the system remains locked after rebooting.
If you try to reconfigure a locked device the following message is shown:
$A security lock is currently installed
$To execute PFAL commands, first unlock the system with PFAL,SYS.Security.Unlock,<password>
Parameter description
<"password">
Specify the password to lock the device. It consists of a string with a length up to 50
characters.
3.2.2.3.2
Command syntax
Examples
Responses
Sys.Security.RemoveLock,<"password"> – Removes system lock
$PFAL,Sys.Security.RemoveLock, <"password">
$PFAL,Sys.Security.RemoveLock,"12345"
$security lock removed
$SUCCESS
Message description
This command is used to remove a previously applied lock permanently. To remove it, first unlock
the device, then execute the command RemoveLock. This command can also be used whenever
you want to change the password.
Parameter description
<"password">
Specify the password to remove locking of alarms. It consists of a string with a length up to 50
characters. To remove the system lock, the last locking password must be used.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 41 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.3.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.Security.Unlock,<"password"> – Unlocks system
Command syntax
$PFAL,Sys.Security.Unlock, <"password">
Examples
$PFAL,Sys.Security.Unlock,"12345"
$security unlocked until next restart
Responses
$SUCCESS
Message description
This command is used to unlock a previously applied lock on a device just for the time the device is
running. Device remains locked again whenever restarted. To remove the lock permanently, use
the command $PFAL,Sys.Security.RemoveLock,<"password">. The password given must
correspond with the existing password specified for that device when the system has been locked.
Unlocking the system enables the user to read/write the configuration and to execute PFAL
-Commands again.
Parameter description
<"password">
Specify the same password you have used for locking the device. The password specified here
is used to unlock the device. The password must be a string with a length up to 50 characters.
It is assumed that the password has already been set when sending this command.
3.2.2.3.4
Sys.Security.HideAlarm,<"password"> – Protects reading of alarms
Command syntax
$PFAL,Sys.Security.HideAlarm, <"password">
Examples
$PFAL,Sys.Security.HideAlarm,"12345"
Message description
This command is used to protect the stored alarms (AL) in the device from reading. Unless the
specified password is known and entered within the following UnhideAlarm command, no alarms
can be read out by PFAL-Commands.
Parameter description
<"password">
Specify the password to protect the alarms from reading. The password must be a string with
a length up to 50 characters.
3.2.2.3.5
Sys.Security.UnhideAlarm,<"password"> – Removes alarm protection
Command syntax
$PFAL,Sys.Security.UnhideAlarm, <"password">
Examples
$PFAL,Sys.Security.UnhideAlarm,"12345"
Message description
This command is used to remove the protection of alarms (AL). Alarms (AL) can then be read after
this command completes.
Parameter description
<"password">
Specify the password to remove the protection of alarms from being read. The password must
be a string with a length up to 50 characters. To remove the protection, use the same
password used with the Sys.Security.HideAlarm,"password" command.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 42 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"RUpdate" command index
There are two ways to upgrade the MAMBO2-B6/UXFS device to a new firmware. The simple way is to
upgrade it locally with the help of Workbench software and the other one is to upgrade the device
remotely via TCP connection with the help of a TCP server.
Using the Workbench and upgrading the device locally via Bluetooth or USB is the most common way
for customer and the instructions for the upgrade procedure tare available in the manual "MAMBO2B6/UXFSSoftwareUpdate.pdf". With the new feature implemented in the Workbench software you can
also update your MAMBO2-B6/UXFS remotely with the help of a DSL-Router, refer to the application
note "AppNotesRemoteUpdateWithWorkbench.pdf" for instructions on the update procedure.
The second way to upgrade the device is the most difficult one and it can be implemented only by
system integrators. For more information of how to implement such an application in your server and
all commands needed for the remote upgrade are available in the Application Note "AppNote_Remote_update.pdf".
 Except the information found in this document and in the application note for remote update,
FALCOM will not provide additional technical support for developing/implementing such webbased solutions on your server.
All commands within this chapter will be used for upgrading your MAMBO2-B6/UXFS device to a new
firmware version remotely over the air.
 It is strongly recommended to use the PFAL-Commands for the remote upgrade with special
care.
3.2.2.4.1
Sys.RUpdate.Init,<type>,<option>,<size>,<sectors>,<config>
firmware upgrade
–
Command syntax
$PFAL,Sys.RUpdate.Init,<type>,<option>,<size>,<sectors>,<config>
Examples
$PFAL,Sys.RUpdate.Init,FW_raw,new,890812,14,raw_cfg
Initializes
remote
Message description
This command is used to start a new upgrade or resume a previous upgrade process (also possible
after a system restart). It returns the number of sectors required for the upgrade process. After
initializing the upgrade procedure, to start transferring of the firmware to the MAMBO2-B6/UXFS
device you have to define the channel from where the new firmware or recourse data will be
received on the MAMBO2-B6/UXFS device by using the PFAL-Command in chapter 3.2.2.4.3,
"$PFAL,Sys.RUpdate.DataMode,<channel>".
Parameter description
<type>
Specifies what kind of data (compressed or uncompressed) contains the firmware file that you
are going to transfer to the remote device:
Value
Meaning
FW_raw
The firmware file contains an uncompressed binary data.
FW_cpr
The firmware file contains a compressed gzip data. The size of the
compressed firmware is limited to 786 KB (maximal 12 sectors). A
configuration can be stored within the compressed file, which later will be
unpacked.
AID_raw
Performs a remote update for Assisted GPS data, also known as A-GPS or
AGPS. To use this feature, you should first download the satellite almanac
from the internet and then perform a remote update for uploading this
data into the target device. Only MAMBO2-B6/UXFS devices with a u-blox
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 43 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPS receiver inside support A-GPS. The device does not perform a system
reset.
RC_raw
The firmware file contains an uncompressed resource data in binary
format (still not tested).
RC_cpr
The firmware file contains a compressed resource data in gzip format
(still not tested).
<option>
Specify what kind of upgrade process you are going to start.
Value
Meaning
new
Starts a new upgrade process. It erases previously transmitted data and
also erases e.g. possible history data stored in this region.
resume
Continues an aborted upgrade process. The previously transmitted device
configuration will be erased and retransmitted again. However, the
previously stored firmware data will be kept.
<size>
Specify the exact length of the remote update firmware data. For FW_raw, this number
specifies the length, in bytes, of the binary firmware file. Note that the length of a binary is
maximal 65536 * 14 -1 bytes. For FW_cpr, this number specifies the length, in bytes, of the
compressed firmware file.
<sectors>
Specify how many sectors are needed to be written for the firmware (the number of sectors
the firmware file needs in uncompressed format). One sector is 64 KByte. For example: a
firmware uses 14 sectors, so the <sectors> should be set to 14.
<config>
Specify how to handle the configuration in the device during upgrade process. See also
related documents chapter 1.2, page 20 points [4] and [8]. It can be set to one of the following
strings:
Value
raw_cfg
Meaning
Erases the device configuration during the update process. A new
(uncompressed) configuration can be transmitted via remote update (see
select sector for more details). <config> can still be used until the remote
update is finished; after finishing, the old configuration will be cleared.
compressed_cfg A new configuration is stored in the compressed firmware. No separate
<config> will be needed. It is not allowed to write uncompressed
configuration data to the configuration sector if compressed_cfg is used.
current_cfg
The available configuration in the device will be kept and used after the
upgrade process has completed and the device restarted. No separate
configuration needs to be transmitted. An existing compressed
configuration would be overwritten.
Note:
• A resource file contain a collection of icons, pictures, and strings tables that can be
uploaded to the MAMBO2-B6/UXFS device.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 44 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.4.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.RUpdate.Abort – Aborts remote upgrade
Command syntax
$PFAL,Sys.RUpdate.Abort
Examples
$PFAL,Sys.RUpdate.Abort
Message description
This command is used to abort an initiated remote update and allow the history to be written
again. The selected user interface turns back to the command mode once this command is
executed.
Parameter description
None
3.2.2.4.3
Sys.RUpdate.DataMode,<msg_input> – Defines the channel and continues
upgrading
Command syntax
$PFAL,Sys.RUpdate.DataMode,<msg_input>
Examples
$PFAL,Sys.RUpdate.DataMode,TCP.Client
Message description
This command is used to enter the device into the data mode, which allows only entering of
binary update commands. Inside this mode, no further PFAL commands can be locally or remotely
executed.
Once this PFAL-Command has been received by the MAMBO2-B6/UXFS device, you can send other
binary update commands given in the next sub-chapter.
Parameter description
<msg_input>
Set up the channel to which the firmware-based packets will be received from the MAMBO2B6/UXFS.
Value
Meaning
Serial
Received via serial port (Bluetooth).
TCP.Client
Received via TCP connection.
CSD
Received via CSD call (GSM data call).
USB
Received via USB port.
Note:
• This command can be executed anytime after a remote update has been initiated with the
command $PFAL,Rupdate.Init.
• After this command has been received by the device, the binary Update commands can be
sent (see next sub-section, 3.2.2.4.3.1 ).
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 45 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3.2.2.4.3.1 Binary update commands
Command syntax
<sta><length><cmd_id><answer_id><datalength><data><sto>
Binary Command
Format
Size
<sta>
Description
Responses*
Syntax
Example**
1 Byte
0xFC
<length>
1-n Byte
MSB bit (0x80) signalizes that another length byte follows.
The length itself may range from '0x00 to 0x7F' for each
byte (to a maximal length of 4096 - the current size of the
internal buffer)
Shows the number of bytes after <length> until <sto>
(<sto> is included)
<cmd_id>
1-n Byte
MSB bit (0x80) signalizes that another cmd byte follows.
Specifies the command being sent. In the next sub-section
are listed all commands and their values correspondingly.
$<<txt_cmd>>
$<03>
Here can be specified any value - the headline of the $answer lines
$C06F
corresponding response will contain this value in order to $SUCCESS
OR
$SUCCESS
identify the response. (Therefore, different values should be ERROR
used for different commands)
$<end:01>
$<end:<txt_id>>
Specifies the amount of following bytes inside <data> its
value depends on the specified <cmd_id> (see next subsection).
MSB bit (0x80) signalizes that another length byte follows.
The length itself may range from '0x00 … 0x7F' for each
byte (to a maximal length of 4096 - the current size of the
internal buffer).
<answer_id>
1 Byte
<datalength>
1-2 Bytes
<data>
0-n Byte
(Specified with <datalength>)
Contains formatted data which depends on the specified
<cmd_id> (see next sub-section, 3.2.2.4.3.2).
<sto>
1 Byte
0xEC
* Although update commands are sent in binary, their answers are text messages, which match the PFAL answer format.
** A response for a checksum command (it is ID=0x01)
<txt_id>
<txt_cmd>
- the textual decimal value of <id> ( i.e. <id>=255 )
- the textual hexadecimal value of <cmd>
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 46 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3.2.2.4.3.2 List of binary commands
Syntax
Exit
Data
Mode
Select Sector
Write Data to Sector
Read Sector Checksum
Clear Sector
<cmd_id>
0x00
0x01
0x02
0x03
0x04
2
0
<datalength>
0x00
0x01
4 + number of bytes to
be written.
<data>
-
Number of sector or 99 to
select configuration sector.
-
-
-
<pos>
-
-
2 Bytes (position inside
sector 0x00-0xFFFF)
2 Bytes (position inside
sector 0x00-0xFFFF)
-
<data_to_write>
-
-
data for this position
-
-
<cksum>
-
-
2 Byte (16 bit checksum
of
<pos>
and
<data_to_write>)
-
-
Writes data to the
specified position inside
a currently selected
sector.
Computes a 16 Bit
Cksum of the currently
selected sector from
the first byte until
<pos> (the byte at the
specified position is
included). This Cksum
has to match with the
expected value (i.e. of
the new firmware
sector).
If this Cksum differs
from expected results,
data is corrupted,
which can result in an
unreachable device.
in case a wrong cksum
was reported, the
whole sector has to be
erased
(see
next
command).
Note:
If just a part
of a sector needs to be
written, the specified
position should be the
last byte written. If the
maximum
value
(0xFFFF) is specified,
trailing 0xFF’s inside
this sector would be
also
used
for
calculation.
Do not specify 0xFFFF
for the very last sector
containing
a
configuration – the
maximum value for
this sector is 0x7FF.
Erases a currently
selected
sector.
(i.e. if corrupted
data was inside)
Selects one of the sectors (0
... number returned from
the command RUpdate.Init).
If 'cfg' is selected, only a
half sector can be accessed.
the
new
device
configuration can be stored
Switches back there if desired.
to
normal This selected sector is used
for all further commands
Command
mode (PFAL data can be written only to
commands)
the
currently
selected
sector
The checksum command
works only for the currently
selected sector.
Erasing a sector can be
performed only on the
currently selected one.
- To be omitted
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 47 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.4.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.RUpdate.Finish – Finishes remote upgrade
Command syntax
$PFAL,Sys.RUpdate.Finish
Examples
$PFAL,Sys.RUpdate.Finish
Message description
This command is used to finish the update process, deletes the available firmware from the
FLASH, writes the new one into the FLASH and reset the upgraded device. Device boots up with
new firmware. The boot up process takes approx. 30-40 seconds, however it depends on the size
of the firmware you have updated to the device.
Parameter description
None.
Note:
• All the data required for the firmware upgrade has to be specified and verified using the
checksum commands before executing.
• For "FW_raw" <type>:
 Note that if the upgrade finish command fails, and you resume the firmware
upgrade later, a previously transmitted configuration will always be erased. This
doesn't matter if the old firmware configuration is used with the option "keep_cnf",
however if it was transferred with the option "clear_cnf", you MUST transfer it
again before finishing the upgrade, otherwise the device will be unreachable
because it starts up with the default settings.
• If you resume a firmware upgrade, note that a previously transmitted configuration will
always be erased. This doesn't matter in case the old device configuration is used, but in
case it was transferred, it MUST be transferred again before finishing the update
procedure. Otherwise the device will be unreachable (because it will start with default
settings)
• This command doesn't respond if it is successfully executed, but only if it fails.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 48 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Device" command index
The commands related to this index allow resetting of the device, setting the device into a sleep mode
or shutdown the device. Each PFAL-Command listed in this chapter responses by an event when
executed. For example, the event Sys.Device.eStart raises when the device (re)starts (after each
initialization), and the shutdown event raises when the device turns off or goes to sleep. You can then
handle such events to execute PFAL-Commands and keep track of the device behaviours. All these
events that are supported by the firmware can be found in chapter 3.4.1.7.
3.2.2.5.1
Sys.Device.Reset[,<user_reset>] – Initiates system reset
Command syntax
$PFAL,Sys.Device.Reset[,<user_reason>]
Examples
$PFAL,Sys.Device.Reset
$PFAL,Sys.Device.Reset,2
//the event Sys.Device.eStart=Reset,User0 occurs
//the event Sys.Device.eStart=Reset,User2 occurs
Message description
This command is used to reset the device.
Parameter description
[<user_reason>]
Optional setting. Determine what type of optional reset the device should execute and what
type of reset event you are going to use when the device restarts. The following values are
supported:
Value
Meaning
0
USER Reset 0 (default)
1
USER Reset 1
2
USER Reset 2
Notes
• This command does not respond due to it restarts immediately.
• 5 different reset types can be specified, which are displayed within eWakeupReason event
on the next startup.
3.2.2.5.2
Sys.Device.Update – Resets system into update mode/RedBoot (Bluetooth only)
Command syntax
$PFAL,Sys.Device.Update
Examples
$PFAL,Sys.Device.Update
Message description
This command is used to reset the MAMBO2-B6/UXFS device into the update mode. The firmware
update can take place only via Bluetooth interface (and NOT via USB or TCP). To aboard this mode
and restart the device, use the hardware shutdown button (see figure below).
Parameter description
None.
Notes
• No responses will be delivered.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 49 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.5.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.Device.Shutdown – Shuts down system immediately.
Command syntax
$PFAL,Sys.Device.Shutdown
Examples
$PFAL,Sys.Device.Shutdown
Message description
This command is used to shutdown the MAMBO2-B6/UXFS by occurring the event
„Sys.eShutdown". When the device receives this command, it stops all operations and enters into
a specific sleep mode. To wake up your MAMBO2-B6/UXFS from this sleep mode, you must press
the right button on the MAMBO2-B6/UXFS device. The running firmware does not check any
system states when receiving this command.
➢ Pending SMS, Emails and TCP packets will be lost.
➢ For applications where safety against losing messages/data is required, this command
should not be used, use Sys.Device.Sleep=<wakeup_condition> instead.
Parameter description
None.
3.2.2.5.4
Sys.Device.FactoryReset – Resets device to factory defaults
Command syntax
$PFAL,Sys.Device.FactoryReset
Examples
$PFAL,Sys.Device.FactoryReset
Message description
This command is used to reset the device to its factory-default state. Once this command is
executed, all settings done by the user will be erased. The device will start up and run with factory
default settings listed in chapter 7.7, page 339. This command does not return any answers.
Parameter description
None.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 50 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.5.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.Device.Sleep=<wakeup_condition> – Puts device into sleep mode
Command syntax
$PFAL,Sys.Device.Sleep=<wakeup_conditions>
Examples
$PFAL,Sys.Device.Sleep=Ign
$PFAL,Sys.Device.Sleep=Ign+Ring+Timer=1:20:00
$PFAL,Sys.Device.Sleep=Ign+Motion
Message description
This command is used to enter the device into a sleep mode, however not before the following
conditions in the device returns true:
✔
The event „Sys.eShutdown" occurs,
✔
The sleep timer countdown pre-defined (by default 60000ms) with DEVICE.IGNTIMEOUT,
✔
No other events will occur when executing this command,
✔
Active alarms/commands will try to be executed,
✔
Existing TCP and GPRS connections will be closed however not beforer the pending TCP
messages are transmitted.
and when the countdown timer reaches zero or no more alarms are to be executed, then your
device enters the specified sleep mode.
Parameter description
<wakeup_conditions>
Specifies the sleep mode to be entered and defines the wakeup condition. At least one
<wakeup_condition> has to be specified. Several <wakeup_condition> can be added by using a
"+" character between wakeup condition names. Following values can be set:
Value
Meaning
Ign
Puts the MAMBO2-B6/UXFS into IGN-SLEEP mode until the right key
(BTN1) on MAMBO2-B6/UXFS is pressed. This SLEEP mode permanently
blocks the serial interface (Bluetooth) and USB port, closes the available
TCP line, detaches the MAMBO2-B6/UXFS from the GPRS and de-registers
it form GSM network. To wake up your MAMBO2-B6/UXFS from this sleep
mode press the right button on MAMBO2-B6/UXFS. Note: This mode
allows lowest power consumption when the device is sleeping.
Ring
Puts the MAMBO2-B6/UXFS into RING-SLEPP mode until an incoming
voice call or SMS is detected. This SLEEP mode permanently blocks the
serial interface (Bluetooth), USB, closes the available TCP line and
detaches the MAMBO2-B6/UXFS from the GPRS services. Only GSM engine
will stay on and remain registered into the GSM network for detecting
voice calls or SMS. Once the first ring of an incoming call is received, the
MAMBO2-B6/UXFS hangs up that call, wakes up and re-initializing the
GSM engine during startup. When waken up by SMS, the MAMBO2B6/UXFS will also execute the PFAL command(s) sent with SMS. This sleep
mode could not be entered, while MAMBO2-B6/UXFS is not registered to
the GSM network. Note: This mode requires most power because the
GSM engine remains powered on while the device is sleeping. The device
goes into the RING-SLEPP mode only if the device is registered into the
GSM network.
Hint: The wake up signal (dialling or sending SMS to the MAMBO2B6/UXFS phone number) should be used only when the internal battery
has enough power, otherwise no alarms will be triggered after the system
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 51 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
wakes up, and the GSM engine will not be detected by the internal
software until external power applied.
Note: Do not use the Ring wakeup parameter alone. It is recommended
to combine it with the IGN-SLEEP parameter.
Motion
Puts the MAMBO2-B6/UXFS into MOTION-SLEEP mode until motion is
detected (attempts to move it in any direction, either up or down, or left
or right). This SLEEP mode permanently blocks the serial interface
(Bluetooth), USB, closes the available TCP line and detaches the MAMBO2B6/UXFS from the GPRS services. This mode allows an average power
consumption (more than Timer, less than Ring). Note: Do not use the
Motion wakeup parameter alone. It is recommended to combine it with
the IGN-SLEEP parameter.
Timer=<timeout>Puts the system into TIMER-SLEEP mode until the timer expires with an
accuracy of 10 minutes. Note: this mode allows low power consumption,
but higher than IGN mode. Do not use the TIMER-SLEEP parameter
alone. It is recommended to combine it with the IGN-SLEEP parameter.
<timeout>
Sleep time specified as <hh>:<mm>:<ss>.
<hh>
<mm>
<ss>
Number from 0 – 200. It will be set to 200, if the max.
value is exceeded.
Number from 0 – 59. It will be set to 59 if the max.
value is exceeded.
Number from 0 – 50. It will be set to 50 if the max.
value is exceeded. Its accuracy is 10 seconds. The
specified value will be rounded to 10,20,30,40 or 50.
Note
• Wakeup conditions are not case-sensitive.
• The order of several specified wakeup conditions doesn’t matter.
• These sleep modes always should be used in combination with IGN-Sleep parameter.
3.2.2.5.6
Sys.Device.CfgUpdateMode – Sets device into configuration update mode
Command syntax
$PFAL,Sys.Device.CfgUpdateMode[,<timeout>]
Examples
$PFAL,Sys.Device.CfgUpdateMode,120
Message description
This command is used to enter the device into a special configuration update mode that is
recommended when making changes in the alarm configuration. This mode is used to prevent
interferences between the old and new alarms.
When being inside this mode:
-
all available alarms become inactive,
-
Macros can be executed directly via PFAL commands.
Parameter description
<timeout>
Optional parameter which defines how many seconds the device will stay in this mode before
it resets and leaves this mode.
Notes
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 52 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
• If the timeout is still not expired and you want to leave the configuration update then just
reset the device.
• This mode can also be used to test the alarm conditions and simulate step-by-step the
behaviour of usual alarms:
 Events will be displayed,
 Alarm states can be checked with the command MSG.Info.Alarm,
 Alarm actions will be simulated using the PFAL commands (because no actions are
being executed - i.e. the user has to start timers, increment counters or change the
trigger’s states etc.).
• However, it is not possible to easily change other system states such as, the device speed,
connection states etc.
3.2.2.5.7
Sys.Device.RestoreBios – Upgrades or downgrades the on-board BIOS
Command syntax
$PFAL,Sys.Device.RestoreBios
Examples
$PFAL,Sys.Device.RestoreBios
Message description
This command is used to upgrade the on-board BIOS firmware to a new version and keep the
internal BIOS up to date. The new BIOS firmware is always included in each firmware file. This
command works only with the BIOS firmware version 5 and higher.
 IMPORTANT: After executing this command, assure that the device keeps powered until
the BIOS firmware upgrade completes which approx. takes 5-10 seconds. Otherwise the
device may be damaged and it will be no longer functional if this process is interrupted.
Parameter description
None.
3.2.2.5.8
Sys.Device.Speaker=<mode> – Enables/Disables internal buzzer / loudspeaker
Command syntax
$PFAL,Sys.Device.Speaker=<mode>
Examples
$PFAL,Sys.Device.Speaker=enable
Message description
This command is used to activate or deactivate the internal buzzer of the MAMBO2-B6/UXFS
device or the built-in hands-free speaker in MAMBO2-B6/UXFS. The MAMBO2-B6/UXFS has a
built-in loudspeaker for using hands-free operations, for instance, during voice calls.
To activate the speaker in your MAMBO2-B6/UXFS either:
✔
press the left -key "Speaker on" on the MAMBO2-B6/UXFS when you are inside a voice call,
✔
or execute $PFAL,Sys.Device.Speaker=enable when a voice call comes in.
The speaker is automatically turned off when the call party hangs up that call, or when you select
the left key "Speaker off" on the MAMBO2-B6/UXFS screen. To deactivate the speaker in the
MAMBO2-B6/UXFS either:
✔
press the left key "Speaker off" on the MAMBO2-B6/UXFS screen,
✔
or execute $PFAL,Sys.Device.Speaker=disable when you want to end/terminate that call.
Parameter description
<mode>
Define the operating mode of the buzzer or built-in speaker. It can be set to:
disable
(Default) Disables the buzzer or speaker in the device.
enable
Enables the i the buzzer or speaker in the device.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 53 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.6
3.2.2.6.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"GSM" command index
Sys.GSM.Enable – Powers GSM engine on
Command syntax
$PFAL,Sys.GSM.Enable
Examples
$PFAL,Sys.GSM.Enable
Message description
This command is used to power on the built-in GSM engine, if it is powered off.
Parameter description
None.
Notes
• When starting of the GSM engine be sure that the battery voltage is above 2.2V.
• Do not use this command to reset the GSM engine, use Sys.GSM.Reset instead. Resetting
of the GSM engine isn't required, but if it is desired, you should perform a complete system
reset and not only reset the GSM engine.
3.2.2.6.2
Sys.GSM.Disable – Powers off the GSM engine
Command syntax
$PFAL,Sys.GSM.Disable
Examples
$PFAL,Sys.GSM.Disable
Message description
This command is used to power off the GSM engine, if it is currently running. The purpose of this
command is to power off the GSM engine, when the use of GSM/GPRS services is not required for
a long period of time. To reset the GSM/GPRS engine (generally not required) the only possibility is
to perform a full system reset, using Sys.Device.Reset.
Parameter description
none.
Notes
• It is not recommended to use this command, when the device is attached to GPRS network.
3.2.2.6.3
Sys.GSM.Reset – Resets the GSM engine
Command syntax
$PFAL,Sys.GSM.Reset
Examples
$PFAL,Sys.GSM.Reset
Responses
E.g. $SUCCESS
Command description
This command is used to reset the GSM engine, if it is currently powered on. The event
SYS.GSM.eEnable occurs when the GSM engine restarts.
Parameter description
None.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 54 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.7
3.2.2.7.1
DOCUMENT VERSION 3.7.0
"GPS" command index
Sys.GPS.Enable – Powers on the GPS engine
Command syntax
$PFAL,Sys.GPS.Enable
Examples
$PFAL,Sys.GPS.Enable
Responses
- FIRMWARE REVISION 2.8.0 -
$GPS started
$SUCCESS
Command description
This command is used to power on the GPS engine if it is switched off. The event SYS.GPS.eEnable
occurs when executing this command, and when the GPS gets a valid fix the event
GPS.Nav.eFix=valid occurs. By default, the GPS engine is enabled when the device starts up.
Parameter description
None.
3.2.2.7.2
Command syntax
Sys.GPS.Disable – Powers off GPS engine
$PFAL,Sys.GPS.Disable
$PFAL,Sys.GPS.Disable
Examples
Responses
$GPS shut down
$SUCCESS
Command description
This command is used to power off the GPS engine if it is currently running. The event
SYS.GPS.eDisable occurs when this command is executed.
Parameter description
None.
3.2.2.7.3
Command syntax
Sys.GPS.Reset – Initiates a GPS reset
$PFAL,Sys.GPS.Rest
$PFAL,Sys.GPS.Reset
Examples
Responses
$reset performed
$SUCCESS
Message description
This command is used to reset the GPS engine. The event GPS.Nav.eFix=invalid occurs after
executing this command. The event SYS.GPS.eEnable also will be occurred after the GPS engine is
restarted. This command does not response any answer when executed.
Parameter description
None.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 55 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.7.4
Command syntax
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.GPS.Sleep – Puts GPS into sleep mode
$PFAL,Sys.GPS.Sleep
$PFAL,Sys.GPS.Sleep
Examples
$SUCCESS
or
Responses
$error, device is already sleeping or disable
$Error to execute command type SYS
$ERROR
Command description
Two kinds of power saving modes are offered by MAMBO2-B6/UXFS regarding the GPS operation
to meet applications that have different requirements in position report interval and power
consumption.
This command is used to set the GPS receiver into sleep mode. It is designed for the application
that requires infrequent position reporting. The GPS receiver stays in a low-power mode (so called
Hibernate mode), and on demand it wakes up to refresh position, time, ephemeris data and RTC
calibration. When your application needs a position report, execute the command
Sys.GPS.Wakeup to wake the receiver up, which is then able to supply a position within the hotstart time. The receiver remains then in full power until the command Sys.GPS.Sleep is executed
again.
Parameter description
none
3.2.2.7.5
Sys.GPS.Wakeup – Wakes up GPS from sleep
Command syntax
$PFAL,Sys.GPS.Wakeup
Examples
$PFAL,Sys.GPS.Wakeup
Responses
E.g. $SUCCESS
Command description
This command is used to wake up the GPS receiver from the sleep mode. After waking up, the
receiver will stay on full power until the command Sys.GPS.Sleep is executed again.
Parameter description
none
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 56 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.8
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"BT" command index
(BT option is only available for the MAMBO2-UXFS)
The Bluetooth is a hardware option for the MAMBO2-UXFS device. Therefore, all PFAL-Commands given
below should be executed only if the MAMBO2-UXFS has the Bluetooth option. These PFAL-Commands
may response SUCCESS when executed even if the Bluetooth option is not available in the device.
3.2.2.8.1
Sys.BT.Enable – Powers on Bluetooth module
Command syntax
$PFAL,Sys.BT.Enable
Examples
$PFAL,Sys.BT.Enable
Command description
This command is used to power on the Bluetooth module, if it is switched off. The event
SYS.BT.eEnable occurs when this command is executed. By default, the Bluetooth is powered on
during startup. The Bluetooth module can also be enabled or disabled via "Settings" symbol on
the MAMBO2-UXFS display.
Parameter description
None.
3.2.2.8.2
Sys.BT.Disable – Powers off Bluetooth module
Command syntax
$PFAL,Sys.BT.Disable
Examples
$PFAL,Sys.BT.Disable
Command description
This command is used to power off the Bluetooth module if it is currently running. The event
SYS.BT.eDisable occurs when this command is executed. The Bluetooth module can also be
enabled or disabled via "Settings" symbol on the MAMBO2-UXFS display.
Parameter description
None.
3.2.2.8.3
Sys.BT.Reset – Resets Bluetooth module
Command syntax
$PFAL,Sys.BT.Reset
Examples
$PFAL,Sys.BT.Reset
Responses
E.g. $SUCCESS
Command description
This command is used to reset the Bluetooth module. The event SYS.BT.eEnable occurs after the
Bluetooth restarts.
Parameter description
None.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 57 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.9
3.2.2.9.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"CPU" command index
Sys.CPU.Reset – Resets CPU.
Command syntax
$PFAL,Sys.CPU.Reset
Examples
$PFAL,Sys.CPU.Reset
Responses
-
Command description
This command is used to rest the device's CPU. After executing this command the device sets itself
into the RedBoot mode - on the serial channel (Bluetooth connected) the following text is shown:
RedBoot> go 0x60000000.
Parameter description
None.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 58 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.10
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"IEEE" command index
(IEEE option is only available for the MAMBO2-UXFS)
The IEEE is a hardware option for the MAMBO2-UXFS device. Therefore, the PFAL-Commands given
below are available only if the MAMBO2-UXFS has the IEEE option. These PFAL-Commands may
response SUCCESS when executed even if the IEEE option is not available in the device.
3.2.2.10.1
Sys.IEEE.Enable – Powers on IEEE module
Command syntax
$PFAL,Sys.IEEE.Enable
Examples
$PFAL,Sys.IEEE.Enable
Responses
E.g. $SUCCESS
Command description
This command is used to power on the IEEE engine, if it is switched off. The event
SYS.IEEE.eEnable occurs when this command is executed. IEEE can also be enabled or disabled via
"Settings" symbol on the MAMBO2-UXFS display.
Parameter description
None.
3.2.2.10.2
Sys.IEEE.Disable – Powers off IEEE module
Command syntax
$PFAL,Sys.IEEE.Disable
Examples
$PFAL,Sys.IEEE.Disable
Command description
This command is used to power off the IEEE module if it is currently running. The event
SYS.IEEE.eDisable occurs when this command is executed. IEEE can also be enabled or disabled via
"Settings" symbol on the MAMBO2-UXFS display.
Parameter description
None.
3.2.2.10.3
Sys.IEEE.Reset – Resets IEEE module
Command syntax
$PFAL,Sys.IEEE.Reset
Examples
$PFAL,Sys.IEEE.Reset
Command description
This command is used to reset the IEEE module. The event SYS.IEEE.eEnable occurs when the IEEE
restarts. It can be executed, for example, when the IEEE hardware reports error during the
runtime.
Parameter description
None.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 59 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.11
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Power" command index
3.2.2.11.1
Sys.Power.Voltage – Queries input voltage on the USB
Message syntax
$PFAL,Sys.Power.Voltage
Examples
$PFAL,Sys.Power.Voltage
Responses
$Power voltage: 4.453 V
$Power voltage: 0.000 V
//When external power connected
//When external power disconnected
Command description
This command is used to read out the amount of input voltage on the device's mini-USB port. The
returned value is in Volt (V). Execute this command when the device is connected to a USB port
and it applies power at request time, otherwise the device responses 0.000 V.
Parameter description
none.
3.2.2.11.2
Sys.Power.Mode=<mode>[,<ontime>[,<offtime>[,<motion>]]] – Puts device into
power save mode
Message syntax
$PFAL,Sys.Power.Mode=<mode>[,<ontime>[,<offtime>[,<motion>]]]
Examples
$PFAL,Sys.Power.mode=auto,30
$PFAL,Sys.Power.mode=doze,120,600
$PFAL,Sys.Power.mode=doze,120,600,PTI
$PFAL,Sys.Power.mode=doze,120,600,Motion
$PFAL,Sys.Power.mode=disable
Command description
This command is used to put the device periodically into the power save mode. This command
stores its values in the configuration DEVICE.LOWPOWER.
Parameter description
<mode>
Define what mode should be set on the device. It can be set to the following values:
Value
Meaning
disable
Device remains always in full power operation.
auto
Device switches on power save mode periodically every user-specified time
if no event occurs within this time.
doze
System enters doze mode if the USB port is disconnected and whenever
the defined on-time expires. This mode means: display goes off, processor
goes to sleep, GSM keeps running in stand-by state and GPS enters
hibernate state. During in doze mode only a key-presses, an SMS, a GSM
call or a TCP event can wake up the device. It is NOT recommended to use
GSM power save mode when the system is in doze mode. The display will
stay turned off if the device is woken up from the doze mode. The display
can be turned on by using the following alarm:
$PFAL,CNF.Set,AL60=Sys.Device.eStart=doze:Sys.Display.Enable
The configuration parameter
(DISPLAY.SAVER≠2).
DISPLAY.SAVER
must
not
be
2
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 60 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
<ontime>
This entry should only be used for the "auto and doze" mode. Define the amount of time, in
seconds, that elapses before the system enters power save or doze mode, if there are no
event received within this time, such as button-press, incoming SMS etc. The default value is
30 seconds.
When the device enters the sleep mode with Auto parameter, it only stays in that mode a
short time, in normal operation 5 seconds at the maximum, then it wakes up. However, if the
device is too busy processing other requests (for example, a burst of alarms occurs when too
many alarms are available in the configuration) and processor load is too high, then it goes
very infrequent into this power save.
[<offtime>]
Optional entry should only be used for the "doze" mode. Define the number of seconds
before the system wakes up from "doze mode". Normally the system wakes up either by key
pressing or GSM event occurring e.g. when activity on the GSM modem is detected such as
incoming SMS, Voice call, TCP.
[<motion>]
Optional entry. Specify whether the device should wake up and generate the event
"Sys.Device.eStart=doze,Standing" when no moves are detected from the built-in 3D
acceleration sensor within 30 seconds or the device should wake up when moves are detected
and generate the the event "Sys.Device.eStart=doze,Motion". It can be set to:
Value
Meaning
PTI
When no moves are detected within 30 seconds, the device wakes up
from
the
doze
mode
and
generates
the
event
"Sys.Device.eStart=doze,Standing". Should only be used for the "doze"
mode.
Motion
Wake up only when motion is detected. The device generates the event
"Sys.Device.eStart=doze,Motion". Should only be used for the "doze"
mode.
Notes
• The Doze mode is not recommended to be used in combination with GSM power save
mode.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 61 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.12
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"BAT" command index
3.2.2.12.1
Sys.Bat.Voltage – Queries current battery voltage
Command syntax
$PFAL,Sys.Bat.Voltage
Examples
$PFAL,Sys.Bat.Voltage
Responses
E.g. $battery voltage: 3.8 V
Command description
This command is used to read out the amount of voltage of the internal battery. The returned
value is in Volt (V). If battery is being charged at the request time, this command reports incorrect
voltage. Therefore, to get the correct battery voltage execute this command when battery is not
charging (disconnected from external power source).
Parameter description
none.
3.2.2.12.2
Sys.Bat.ChargeState – Gets current battery state
Command syntax
$PFAL,Sys.Bat.ChargeState
Examples
$PFAL,Sys.Bat.ChargeState
Responses
E.g. $ charging
Command description
This command is used to read out the state of charge of the internal battery. Returns a text that
indicates the battery state as follow:
charging
battery is charging.
not charging
battery is not charging (no external power is available)
full
battery is full charged.
Parameter description
None.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 62 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.13
3.2.2.13.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Display" command index
Sys.Display.Enable – Powers on OLED display
Message syntax
$PFAL,Sys.Display.Enable
Examples
$PFAL,Sys.Display.Enable
Command description
This command is used to power on the OLED display of the MAMBO2-B6/UXFS.
Parameter description
none.
Notes
• The command does not work if $PFAL,Cnf.Set,DISP.SAVER=2.
3.2.2.13.2
Sys.Display.Disable – Powers off OLED display
Message syntax
$PFAL,Sys.Display.Disable
Examples
$PFAL,Sys.Display.Disable
Command description
This command is used to power off the OLED display of the MAMBO2-B6/UXFS.
Parameter description
none.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 63 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.14
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"SD" command index
(SD option is no longer available)
Your MAMBO2-UXFS device has upon request a mini SD Card reader which supports up to 1 GB mini-SD
cards for external data storage. When you are going to use the mini-SD card on the MAMBO2-UXFS
device you have to mount it. To mount a mini-SD card into your MAMBO2-UXFS, follow the steps given
below:
Insert the card into the card reader,
when inserting the card the event SD.eInserted occurs,
when you see that event, execute the command $PFAL,Sys.SD.Mount ,
thereafter, execute the command $PFAL,Sys.SD.State to get the home directory of the
inserted mini-SD card,
Execute $PFAL,Sys.SD.Dir.Show,"/homedirectory" (where "/homedirectory" is the
directory responded from the $PFAL,Sys.SD.Statet command) to list the subdirectories
and files in the mini-SD card just
To
save
GPS
positions
into
the
mini-SD
card,
execute
$PFAL.MSG.Send.File,"Trip.log",8,"Trip started" via alarm configuration when a trip
starts and stops,
Finally, when you want to remove the card, first execute Sys.SD.UnMount then remove
the card.
➢
➢
➢
➢
➢
➢
➢
3.2.2.14.1
Sys.SD.Mount – Mounts a mini-SD card
Message syntax
$PFAL,Sys.SD.Mount
Examples
$PFAL,Sys.SD.Mount
Command description
(SD option is no longer available)
This command is used to mount a mini-SD card into the device. Execute this command after
inserting the mini-SD card into the device's card reader and event SD.eInserted is occurred,
otherwise no card can be attached. This mount command makes a mini-SD card accessible by
attaching it to the device.
Parameter description
none.
3.2.2.14.2
Sys.SD.UnMount – Unmounts a mini-SD card
Message syntax
$PFAL,Sys.SD.UnMount
Examples
$PFAL,Sys.SD.UnMount
Command description
(SD option is no longer available)
This command is used to un-mount a mounted mini-SD card from device, before removing it from
the mini-SD card reader. This command makes the card inaccessible by detaching it form the
device. The card should manually be removed after executing this command.
Parameter description
none
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 64 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.14.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.SD.State – Shows mini-SD card state
Message syntax
$PFAL,Sys.SD.State
Examples
$PFAL,Sys.SD.State
Responses
$<SYS.SD.State>
$mounted /dev/sd/1 on /sd as fatfs 127139840 bytes SPI: 10000
kHz S/N:107008 SD:00
$SUCCESS
Command description
(SD option is no longer available)
This command is used to show the state of the mini SD interface whether it is mounted or
unmounted. If it is mounted, this command responses the root directory of the mini SD card (for
example, "/sd") otherwise the mini SD card is not mounted.
Parameter description
none.
3.2.2.14.4
Sys.SD.Dir.Show,<"dirname"> – Lists files and directories in mini-SD card
Message syntax
$PFAL,Sys.SD.Dir.Show,<"dirname">
Examples
$PFAL,Sys.SD.Dir.Show,"/sd/DGB"
Command description
(SD option is no longer available)
This command is used to display the list of files and subdirectories in the given directory. Main
directory name always starts with "/sd", e.g. "/sd/DGB".
Parameter description
<"dirname">
Specify the directory to list.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 65 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.15
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"DISPLAY" command type
This chapter contains all commands related to the DISPLAY command type.
 Do not combine the configuration commands and display commands in one alarm. Only one
display command should be used per alarm and this command should always be set at the end
of the alarm so that no other commands follows any display command in an alarm (see AL3
below).
$PFAL,Cnf.Set,AL3=Sys.Bat.eLow:IO.LED1=cyclic,500,500&Display.Alarm=WARNING,5,"Battery low"
//not allowed
$PFAL,Cnf.Set,AL3=Sys.Bat.eLow:Display.Alarm=WARNING,5,"Battery low"&IO.LED1=cyclic,500,500
Display.Dialog=<id>,<"title">,<bgd>,<timeout>,<"Ok_left">,<"Cancel_right">,
<"message_text"> – Creates a full-screen dialog box
3.2.2.15.1
Command syntax
$PFAL,Display.Dialog=<id>,<"title">,<bgd>,<timeout>,<"Ok_left">,<"Cancel_right">,<"message_text">
Examples
$PFAL,Display.Dialog=1,"Message",0,10,"OK","Cancel","Hello World"
Responses
E.g. $SUCCESS
Command description
This command is used to create and display a dialog box with information on the MAMBO2B6/UXFS's screen. MAMBO2-B6/UXFS contains a dialog box, which displays a message to the user
with a confirmation and cancellation of an action. The dialog box provides two option buttons that
are accessible through the left and right keys. Each option on this dialog box provides an event
when it is pressed. These events can be used to execute different actions. These buttons can also
be ignored when you want to display a timeout-based dialog box that do not require occurring of
any events.
Parameter description
<id>
Determine the ID number of the dialog box to be displayed. Up to 100 dialog boxes in range
from 0 to 99 are provided by the firmware.
<"title">
Specify a text string that identifies the type of the message to the user. It will be shown on the
top of the dialog box.
<bgd>
Specify the background color of the dialog box when it appears. Following values are
available:
Value
Meaning
0
Blue background
1
Green background
2
Red background
3
Black background
<timeout>
Specify the time how long, in seconds, the dialog will stay open on the MAMBO's screen.
When the timeout expires, then the dialog will be hidden and the event
display.dialog.e1=inactive occurs.
<"Ok_left">
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 66 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Specify "OK" the OK () icon. When this button is pressed, the event display.dialog.e1=btn2
occurs and the dialog will be hidden. If it is left empty no button is shown.
<"Cancel_right">
Specify "Cancle" for the Cancel () icon. When this button is pressed, the event
display.dialog.e1=btn1 occurs and the dialog will be hidden. If it is left empty no button is
shown.
<"message_text">
Specify the text containing the message to be displayed on the dialog. If you want to display
also any dynamic entry the syntax of the <"text"> can be expanded to:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Each dynamic entry is separated by ampersand "&" and without spaces it is enclosed in
parentheses "( )".
The command for requesting such system states might look like this:
For example:
$PFAL,Display.Dialog=10,"Speed Message",3,10,"OK","Cancel","Moving with a velocity of &(Speed) m/s"
Dynamic entries are listed in chapter 7.2 page 321.
3.2.2.15.2
Display.Alarm=<image>,<timeout>,<"text"> – Displays a specific alarm image on
screen
Command syntax
$PFAL,Display.Alarm=<image>,<timeout>,<"text">
Examples
$PFAL,Display.Alarm=WARNING,5,"Battery low"
Responses
E.g. $SUCCESS
Command description
This command is used to display a specific alarm image on the screen letting the user know that
something has happened (e.g., a specific event occurs, receiving call, leaving/entering a Geo-fence
area etc.).
Parameter description
<image>
Specify the image to be appeared on the MAMBO2-B6/UXFS's screen. The following symbol
can be set:
Value
WARNING
Meaning
Displays a warning image (e.g. when the battery becomes low)
<timeout>
Specify the time how long, in seconds, the image/alarm will stay appeared on the screen.
<"text">
Specify the text containing the message that will be displayed on the screen together with the
specified image.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 67 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.15.3
Command syntax
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Display.Message=<"user">,<id>,<"caption">,<bgd>,<timeout>,<"text">,
[<"answers1">[,<"answer2">,<"answer3">,<"answer4">]]– Displays a
message (M-Box) on screen
specific
$PFAL,Display.Message=<"user">,<id>,<"caption">,<bgd>,<timeout>,<"text">,
[<"answers1">[,<"answer2">,<"answer3">,<"answer4">]]
$PFAL,Display.Message="John",1,"Info",0,5,"Come home !"
Examples
$PFAL,Display.Message="John",1,"Info",0,5,"I can not come............."
$PFAL,Display.Message="John",1,"Info",0,5,"Hello World "
Responses
E.g. $SUCCESS
Command description
This command is used to display a specific message on the MAMBO2-B6/UXFS display, letting the
user know that something has happened (e.g., a specific event occurs, a message from the remote
server received, leaving/entering a Geo-fence area etc.). This command can also be used for
server-related messages.
Parameter description
<"user">
Specify a text, as a string, to identify the sender of the message. For example, for server
related messages the username can be used.
<id>
Define the ID of the message to be created. Up to 100 message boxes in range from 0 to 99
are available.
<"caption">
Specify a text, as a string, to identify the type of the message to be shown. It will be shown on
the top of the dialog box.
<bgd>
This parameter is retained solely for backward compatibility. Starting from the firmware
version 2.6.0 and above the following values do not have any effect. Specify the icon to be
appeared on the right side of caption on the dialog box. Following values can be set.
Value
Meaning
0
Blue background,
1
Green background,
2
Red background,
3
Black background.
<timeout>
Specify the time how long, in seconds, the dialog box will stay open on the screen.
<"text">
Specify the text, as a string max. 1500 characters, containing the message to be displayed on
the MAMBO2-B6/UXFS screen.
[<"answers1">[,<"answer2">,<"answer3">,<"answer4">]]
Specify the possible answers to the message you want to send to. You can specify up to 4
answers separated by commas and enclosed in quotation marks. If no answers is specified
here, then the default one (see chapter 3.3.2.5) will be used.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 68 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.15.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Display.Popup=<id>,<color>,<button>,<icon>,<timeout>,<"text">
specific message (M-Box) on the screen
–
Command syntax
$PFAL,Display.Popup=<id>,<color>,<button>,<icon>,<timeout>,<"text">
Examples
$PFAL,Display.Popup=2,blue,OK,WARNING,10,"Hello World wird ausgeloest"
Responses
E.g. $SUCCESS
Displays
a
Command description
This command is used to display a popup box with a specific information on the MAMBO2B6/UXFS screen, letting the user know that something has happened (e.g., e.g., a specific event
occurs, a message from the remote server received, leaving/entering a Geo-fence area etc.). This
command can be used for server related messages.
Parameter description
<id>
Define the ID of the popup to be created. Up to 100 popup in the range 0 through 99 are
available.
<color>
Define the background color of the popup. It can be set to: blue, green, red, or black.
<button>
Specify the type of button that will be shown on the bottom of the popup screen when it
appears. It can be set to OK or CANCEL.
<icon>
Depending on the provided resources, specify the icon that appears on the right side of
caption in the dialog box when it is displayed. It can be set to a value in range 0 to 3.
Value
Meaning
WARNING
Displays a warning image (e.g. when the battery becomes low).
CALL
Displays a call image (e.g. when receiving a GSM call).
NEWSMS
Displays an SMS image (e.g. when receiving an SMS).
MAIL
Displays a mail image (e.g. when receiving a mail).
KEYFOB
Displays a keyfob image (e.g. when connected to a keyfob).
GEOFENCE
Displays a Geo-fence image (e.g. when leaving/entering a Geo-fence or
Area).
CONNECT
Displays a connect image (e.g. when connecting to a service).
POI
Displays a POI image.
<timeout>
Specify the time how long, in seconds, the popup box will stay open on the MAMBO2B6/UXFS screen.
<"text">
Specify the text, as a string, containing the message to be displayed on the screen.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 69 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.15.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Display.POIs.Follow=<lat>,<lon>,<alt>,<radius> – Update a user POI to be followed
Command syntax
$PFAL,Display.POIs.Follow=<lat>,<lon>,<alt>,<radius>
Examples
$PFAL,Display.POIs.Follow=50.2889,10.3647,450,30
Responses
E.g. $SUCCESS
Command description
This command is used to set and update a user POI (point of interest). This command works only if
the configuration is set to GPS.TRIP.POIMODE=follow and the trip is already started . The values
that will be sent with this command are stored into the RAM. Once this command is sent to the
MAMBO2-B6/UXFS device, the on-screen compass will show the direction to that location. When
this POI is reached, the next POI to be followed can be sent to the MAMBO2-B6/UXFS via SMS or
TCP. In other words, the user will follow the first POI and continue following the next POI until the
destination reached. Each time this command is sent to the MAMBO2-B6/UXFS device the existing
POI values are overwritten and the on-screen compass will show the direction to that POI.
Parameter description
<lat>
Specify the latitude, in decimal format, of the location.
<lon>
Specify the longitude, in decimal format, of the location.
<alt>
Specify the altitude, in meter, of the location.
<radius>
Specify the radius, in meter, of the location. When the radius of the location is reached the
devices will generate the event "Display.poi.e1".
3.2.2.15.6
Display.Button.Enable – Enables Left and Right keys
Command syntax
$PFAL,Display.Button.Enable
Examples
$PFAL,Display.Button.Enable
Responses
E.g. $SUCCESS
Command description
This command allows to enable the Left and Right and 5-way navigation buttons for navigating
and using the menus on the MAMBO2-B6/UXFS screen. This setting is stored into the
configuration.
Parameter description
none.
3.2.2.15.7
Display.Button.Navigation – Enables Left and Right keys
Command syntax
$PFAL,Display.Button.Enable
Examples
$PFAL,Display.Button.Enable
Responses
E.g. $SUCCESS
Command description
This command disables the Left and Right buttons and enables 5-way navigation button for
navigating thrugh the menus on the MAMBO2-B6/UXFS screen. This setting is stored into the
configuration.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 70 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Parameter description
none.
3.2.2.15.8
Display.Button.Disable – Disables Left and Right keys
Command syntax
$PFAL,Display.Button.Disable
Examples
$PFAL,Display.Button.Disable
Responses
E.g. $SUCCESS
Command description
This command allows to disable the Left and Right and 5-way navigation buttons. The key press
events will still be generated after deactivating the buttons. This setting is stored into the
configuration.
Notice, the Left and Right and 5-way navigation buttons are used to navigate through the menus
in the MAMBO2-B6/UXFS. The button press events will be occurred even when these buttons are
deactivated. To turn off a MAMBO2-B6/UXFS device with buttons deactivated, you must configure
an alarm that shuts down the device when pressing a button:
$PFAL,Cnf.Set,AL99=IO.BTN.e1=long:Sys.Device.Shutdown
Parameter description
none.
3.2.2.15.9
Display.Button.Swap=<action> – Swaps Left and Right buttons and their pressevents
Command syntax
$PFAL,Display.Button.Swap=<action>
Examples
$PFAL,Display.Button.Swap=enable
Responses
E.g. $SUCCESS
Command description
This command allows to swap the Left and Right buttons on the MAMBO2-B6/UXFS screen and
their button press events. To detect whether buttons are swapped use the configuration
parameter $PFAL,Cnf.Get,DISP.SWAPBTN which return either 0 = unswapped or 1 = swapped.
Parameter description
<action>
Specifies whether to swap the right and left buttons on the MAMBO2-B6/UXFS device.
Value
Meaning
enable
Swaps the buttons, button press events and the icons OK and Cancel on
the dialog box.
disable
Unswaps the buttons (default).
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 71 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3.2.2.15.10 Display.Tilt.Enable – Enables tilt function
Command syntax
$PFAL,Display.Tilt.Enable
Examples
$PFAL,Display.Tilt.Enable
Responses
E.g. $SUCCESS
Command description
This command allows to enable the tilt functionality.
Parameter description
none.
3.2.2.15.11 Display.Tilt.Disable – Disables tilt function
Command syntax
$PFAL,Display.Tilt.Disable
Examples
$PFAL,Display.Tilt.Disable
Responses
E.g. $SUCCESS
Command description
This command allows to disable the tilt functionality.
Parameter description
none.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 72 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.16
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Timer" command index
Timers are used for alarm configuration only. Their purpose is to launch periodical or delayed actions.
 Remarks: Only the armed timers raise events when they expire (by default, all times
are armed when the device starts up).
 Warning: Timers can not be started more frequently than in 5-seconds intervals.
3.2.2.16.1
Sys.Timer<index>.Configure=<mode>,<timeout> – Configures a timer
Command syntax
$PFAL,Sys.Timer<index>.Configure=<mode>,<timeout>
Examples
$PFAL,Sys.Timer0.Configure=cyclic,5000
$PFAL,Sys.Timer1.Configure=single,10000
……
$PFAL,Sys.Timer19.Configure=……………………
Message description
This command is used to (re)configure and stop a timer. To start a specific timer use the command
Sys.Timer<index>.Start.
Parameter description
<index>
Determine the index of the timer to be configured. MAMBO2-B6/UXFS supports 20 Timers
ranging from 0 to 19.
<mode>
Define the configuration how to trigger the timer event, either one time or repeatedly, when
this timer is started and after the specified time passes.
Value
Meaning
single
Triggers the timer event only one time, when the specified timeout passes,
allowing to execute alarms just one time.
cyclic
Triggers the timer event repeatedly, each time the specified timeout
passes, allowing to execute alarms periodically.
<timeout>
Determine how frequently should the timer event occur. Each time the specified interval
passes, the timer event will occur. It is a 32-bit integer value ranging from 5000 to
4294967295 in 5000 milliseconds interval (i.e. 5000, 10000, 15000 and so on). The minimum
specified timeout is 5000 msec.
Notes
• Take caution when using cyclic timers with a very small timeout value. Always keep an eye
on the execution time of alarms which are executed upon this timer event (i.e. periodical
SMS cannot be sent faster than each 10 seconds. So, timers with very short time intervals
will only slow down the system performances).
• This command stops a timer <index> if it is currently running. To start a timer use the
command "SYS.Timer0.Start".
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 73 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.16.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.Timer<index>.Start=<timer_settings> – Starts a timer
Command syntax
$PFAL,Sys.Timer<index>.Start=[<timer_settings>]
Examples
$PFAL,Sys.Timer0.Start
$PFAL,Sys.Timer0.Start=cyclic,5000
$PFAL,Sys.Timer0.Start=single,10000
Message description
This command is used to start a configured timer. The timer is set to its initial timeout whenever
this command is executed. Resetting or reconfiguring a timer is possible this way. A timer can also
be configured and started with the same command ($PFAL,Sys.Timer0.Configure) if it is not
currently running.
Parameter description
<index>
Determine the index of the timer to be started. MAMBO2-B6/UXFS supports 20 Timers
ranging from 0 to 19.
[<timer_settings>]
Optional. Used to start an unconfigured timer or to overwrite the existing settings. It consists
of the <mode> and <timeout> parameters with the same settings as parameters in
Sys.Timer<index>.Configure. When used, the syntax of this command looks like this:
Command syntax
$PFAL,Sys.Timer<index>.Start=<mode>,<timeout>
<mode>
Define the configuration how to trigger this timer event, either one time or repeatedly, after
the specified time elapses. It can be set to:
Value
Meaning
single
Triggers the timer event only one time, when the specified timeout passes,
allowing to execute alarms just one time.
cyclic
Triggers the timer event repeatedly, each time the specified timeout
passes, allowing to execute alarms periodically.
<timeout>
Determine how frequently the timer event occurs. Each time the specified interval passes, the
timer event occurs. It is a 32-bit integer value ranging from 5000 to 4294967295 in 5000
milliseconds interval (i.e. 5000, 10000, 15000 and so on).
Notes
• Periodical SMS cannot be sent faster than every 10 seconds.
• The "$PFAL,Sys.Timer<index>.Start" command without value can be used only by
configured timers.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 74 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.16.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.Timer<index>.Stop – Stops a running timer
Command syntax
$PFAL,Sys.Timer<index>.Stop
Examples
$PFAL,Sys.Timer0.Stop
Message description
This command is used to discontinue a timed event. It stops a configured and running timer
immediately. Once stopped to restart it use the command Sys.Timer<index>.Start. Note that, a
stopped timer cannot be resumed anymore.
Parameter description
<index>
Determine the index of the timer to be stopped. MAMBO2-B6/UXFS supports 20 Timers
ranging from 0 to 19.
3.2.2.16.4
Sys.Timer<index>.Pause – Pauses (suspends) a running timer
Command syntax
$PFAL,Sys.Timer<index>.Pause
Examples
$PFAL,Sys.Timer0.Pause
Message description
This command is used to pause a running timer. While paused, the remaining time until expiration
is memorized. To continue the timer, use the resume function. Also a start command can be used
to force a restart of this timer.
Parameter description
<index>
Determine the index of the timer to be paused. MAMBO2-B6/UXFS supports 20 Timers
ranging from 0 to 19.
3.2.2.16.5
Sys.Timer<index>.Resume– Restarts execution of a paused timer
Command syntax
$PFAL,Sys.Timer<index>.Resume
Examples
$PFAL,Sys.Timer0.Resume
Message description
This command is used to continue execution of a paused timer. Note that ,the timer has to be
paused first before resuming execution.
Parameter description
<index>
Determine the index of the timer to be resumed. MAMBO2-B6/UXFS supports 20 Timers
ranging from 0 to 19. Please, specify a paused timer.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 75 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.16.6
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.Timer<index>.Arm - Arms an initialized and disarmed timer
Command syntax
$PFAL,Sys.Timer<index>.Arm
Examples
$PFAL,Sys.Timer0.Arm
Message description
This command is used to arm an initialized, disarmed timer. Only armed timer will generate events
when they expire. Each Timer is armed per default when configured. The start command however
doesn’t change the armed/disarmed state, allowing to restart disarmed timers too. Note that the
timers should be disarmed before arming.
Parameter description
<index>
Determine the index of the timer to be armed. MAMBO2-B6/UXFS supports 20 Timers ranging
from 0 to 19. Please, specify the index of a disarmed system timer.
3.2.2.16.7
Sys.Timer<index>.Disarm – Disarms an initialized and armed timer
Command syntax
$PFAL,Sys.Timer<index>.Disarm
Examples
$PFAL,Sys.Timer0.Disarm
Message description
This command is used to disarm an initialized, armed timer. Disarmed timers will not generate any
events when they expire. Each Timer is armed per default when configured (using the configure
command). Note that the timers should be armed before disarming.
Parameter description
<index>
Determine the index of the timer to be disarmed. MAMBO2-B6/UXFS supports 20 Timers
ranging from 0 to 19.
3.2.2.16.8
Sys.Timer<index>.Erase – Erases a timer configuration
Command syntax
$PFAL,Sys.Timer<index>.Erase
Examples
$PFAL,Sys.Timer0.Erase
Message description
This command is used to erase the configuration of a timer. If a timer was running, it stops
immediately. To restart this timer, it should be configured first (you may use the start command
plus initialisation parameters).
Parameter description
<index>
Determine the index of the timer to be erased. MAMBO2-B6/UXFS supports 20 Timers ranging
from 0 to 19.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 76 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.16.9
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.Timer<index>.Save<slot_id> – Saves a timer state into a storage slot
Command syntax
$PFAL,Sys.Timer<index>.Save<slot_id>
Examples
$PFAL,Sys.Timer0.Save0
Message description
This command is used to save a timer state into the specified storage slot.
Parameter description
<index>
Determine the index of the timer to be saved. MAMBO2-B6/UXFS supports 20 Timers ranging
from 0 to 19.
<slot_id>
Saves the current timer state to a storage slot. The ID of the slot is used to store the current
state of the timer. There are totally 5 storage slots supported by the MAMBO2-B6/UXFS
device ranging from 0 to 4.
3.2.2.16.10 Sys.Timer<index>.Load<slot_id> – Loads a timer state from a storage slot
Command syntax
$PFAL,Sys.Timer<index>.Load<slot_id>
Examples
$PFAL,Sys.Timer0.Load0
Message description
This command is used to load a timer with a saved timer state from the specified storage slot.
Parameter description
<index>
Determine the index of the timer to be loaded with the contents stored in the <slot_id>.
MAMBO2-B6/UXFS supports 20 Timers ranging from 0 to 19.
<slot_id>
Specify the ID of the slot containing a timer state that has been saved in this slot with the
command Sys.Timer<index>.Save<slot_id>. There are totally 5 storage slots supported by the
MAMBO2-B6/UXFS device ranging from 0 to 4. Please, specify a <slot_id> with timer contents,
otherwise the device returns error "$error loading Timer <index>".
3.2.2.16.11 Sys.Timer<index>.State – Reads a timer state
Command syntax
$PFAL,Sys.Timer<index>.State
Examples
$PFAL,Sys.Timer0.State
Message description
This command is used to read out a timer state. All returned states are comma-separated:
Example1:
state of timer 17: erased, inactive, armed.
Example2:
state of timer 18: initialized, active, running, armed
Example3:
state of timer 19: initialized, active, paused, disarmed
Parameter description
<index>
Determine the index of the timer to be read out. MAMBO2-B6/UXFS supports 20 Timers
ranging from 0 to 19.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 77 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.17
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Trigger" command index
Triggers are used for alarm configuration only. Their purpose is to act as additional conditions (so
actions can be launched depending on the value of a Trigger).
Any Trigger value can be either high or low. Triggers don’t create events. Only their state can be used
inside alarm conditions.
3.2.2.17.1
Sys.Trigger<index>=<state_type> – Sets a trigger to high or low
Command syntax
$PFAL,Sys.Trigger<index>=<state_type>
Examples
$PFAL,Sys.Trigger0=high
Message description
This command is used to change a trigger state and set it or a trigger to high or low.
Parameter description
<index>
Determine the index of the trigger to be set. MAMBO2-B6/UXFS supports 20 Triggers ranging
from 0 to 19.
<state_type>
Define the state of the trigger. Following states are available:
Value
Meaning
High
Sets Trigger<index> to high level (active)
Low
Sets Trigger<index> to low level (inactive)
Notes
• Triggers do not generate events, when they change their states. This command can be
used as an action.
3.2.2.17.2
Sys.Trigger<index> – Reads a current trigger state
Command syntax
$PFAL,Sys.Trigger<index>
Examples
$PFAL,Sys.Trigger0
Responses
$<SYS.Trigger0>
$state of trigger 0: high
$SUCCESS
Message description
This command is used to read out the current state of the specified trigger.
Parameter description
<index>
Determine the index of the trigger to be read. MAMBO2-B6/UXFS supports 20 Triggers
ranging from 0 to 19.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 78 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.17.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.Trigger<index>.Save<slot-id> – Saves a trigger state to a storage slot
Command syntax
$PFAL,Sys.Trigger<index>.Save<slot_id>
Examples
$PFAL,Sys.Trigger0.Save0
Message description
This command is used to save the state of a trigger into the specified storage slot.
Parameter description
<index>
Determine the index of the trigger to be saved. MAMBO2-B6/UXFS supports 20 Triggers
ranging from 0 to 19.
<slot_id>
Saves the current trigger state to a storage slot. The ID of the slot which is used to store the
state. There are totally 5 storage slots supported by the MAMBO2-B6/UXFS device ranging
from 0 to 4..
Notes
• Alias
names
can
be
defined
for
ALIAS.STORAGE<storage_index>=<alias_name>.
3.2.2.17.4
all
storage
indices
by
using
Sys.Trigger<index>.Load<storage_slot> – Loads a trigger state with a storage slot
Command syntax
$PFAL,Sys.Trigger<index>.Load<slot_id>
Examples
$PFAL,Sys.Trigger0.Load0
Message description
This command is used to load a trigger with the state of a storage slot.
Parameter description
<index>
Determine the index of the trigger to be loaded with the contents of the <slot_id>. MAMBO2B6/UXFS supports 20 Triggers ranging from 0 to 19.
<slot_id>
The ID of the slot where a trigger state has previously been saved with the command
Sys.Trigger<index>.Save<slot_id>. There are totally 5 storage slots supported by the
MAMBO2-B6/UXFS device ranging from 0 to 4. Please, specify a <slot_id> with trigger
contents, otherwise the device returns error "$error loading Trigger <index>"..
Notes
• Alias
names
can
be
defined
for
ALIAS.STORAGE<storage_index>=<alias_name>.
all
storage
index
by
using
• This operation is successful only if a Trigger state is saved inside the chosen storage slot.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 79 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.18
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Counter" command index
Counters are used for alarm configuration only. The purpose of the counters is to count certain events
or combinations of various states. Depending on the counter value other actions can be executed. Once
a counter reaches 0 (while decrementing or if set to 0), an event can be launched. If a counter remains
at 0, no events will be generated. Beside the event also the current value of a counter can be used
inside alarms, for example, send an SMS when the counter value reach 10.
3.2.2.18.1
Sys.Counter<index>.Set=<value> – Assigns initial values to counters
Command syntax
$PFAL,Sys.Counter<index>.Set=<value>
$PFAL,Sys.Counter0.Set=55
Examples
Message description
This command is used to assign an initial value to a counter.
Parameter description
<index>
Define the index of the counter to be configured. The index must be in the range 0 through
19.
<value>
Specify a value, 32-bit integer, ranging from 0 to 2147483647, for the Counter<index>.
3.2.2.18.2
Sys.Counter<index>.Increment=<inc_value> – Increments counters value
Command syntax
$PFAL,Sys.Counter<index>.Increment=<inc_value>
Examples
$PFAL,Sys.Counter0.Increment=11
Message description
This command is used to increment the value of a counter by a specified value. Once the counter
reaches the maximum value, further increments have no effect.
Parameter description
<index>
Define the index of the counter to be incremented. The index must be in the range 0 through
19.
<inc_value>
Specify a value, 32-bit integer value from 0 to 2147483647, to increment a counter.
3.2.2.18.3
Sys.Counter<index>.Decrement=<dec_value> – Decrements counters value
Command syntax
$PFAL,Sys.Counter<index>.Decrement=<dec_value>
Examples
$PFAL,Sys.Counter0.Decrement=11
Message description
This command is used to decrement the value of a counter. Once a counter reaches the minimum
value (0), further decrements have no effect
Parameter description
<index>
Determine the index of the counter to be subtracted. The index must be in the range 0
through 19.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 80 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
<dec_value>
Specify a value, 32-bit integer from 0 to 2147483647, to decrement a counter.
3.2.2.18.4
Sys. Counter<index>.State – Reads counters state
Command syntax
$PFAL,Sys.Counter<index>.State
Examples
$PFAL,Sys.Counter0.State
Message description
This command is used to read out the current state of a counter.
Parameter description
<index>
Determine the index of the counter to be read. The index must be in the range 0 through 19.
3.2.2.18.5
Sys.Counter<index>.Save<slot_id> – Saves a counter state to a storage slot
Command syntax
$PFAL,Sys.Counter<index>.Save<slot_id>
Examples
$PFAL,Sys.Counter0.Save0
Message description
Saves the current counter state to a storage slot. This operation is successful only if a counter
state is saved inside the chosen storage slot.
Parameter description
<index>
Determine the index of the counter to be saved. The index must be in the range 0 through 19.
<slot_id>
The ID of the slot which is used to store the state. There are totally 5 storage slots supported
by the MAMBO2-B6/UXFS device ranging from 0 to 4.
Notes
• Alias
names
can
be
defined
for
ALIAS.STORAGE<storage_index>=<alias_name>.
3.2.2.18.6
all
storage
indices
by
using
Sys.Counter<index>.Load<slot_id> – Loads the content of a storage slot to a counter
Command syntax
$PFAL,Sys.Counter<index>.Load<slot_id>
Examples
$PFAL,Sys.Counter0.Load0
Message description
This command is used to load the current counter with the previously saved counter state of a
storage slot.
Parameter description
<index>
Determine the index of the counter to be loaded. The index must be in the range 0 through
19.
<slot_id>
The ID of the slot which is used to load the state. There are totally 5 storage slots supported
by the MAMBO2-B6/UXFS device ranging from 0 to 4.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 81 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Notes
• Alias
names
can
be
defined
for
ALIAS.STORAGE<storage_index>=<alias_name>.
3.2.2.18.7
all
storage
indices
by
using
Sys.Counter<index>.Clear – Sets counters to 0
Command syntax
$PFAL,Sys.Counter<index>.Clear
Examples
$PFAL,Sys.Counter0.Clear
Message description
This command is used to set a counter to the value "0". This might cause a counter event if not set
to 0 before.
Parameter description
<index>
Determine the index of the counter to be cleared. The index must be in the range 0 through
19.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 82 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.19
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"MACRO" command index
3.2.2.19.1
Sys.Macro<index> – Activates configured macros
Command syntax
$PFAL,Sys.Macro<index>
Examples
$PFAL,Sys.Macro0
Message description
This command is used to activate a configured macro. To configure a macro, please refer to the
corresponding specification of the parameter (MACRO<index>).
Parameter description
<index>
Determine the index of the counter to be activated. The index must be in the range 0 through
19.
Notes
• This command does not directly execute several times a macro, even if the macro is
activated e.g. by an event, it will execute the Marco just once.
• Of course, a macro can be executed several times, but the time between 2 activations
depends on how much time the macro needs to execute all set commands within it before
it will be reactivated again.
• if the time-span between 2 activations is too short, then only a part of set commands
within a macro might be executed twice.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 83 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.20
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"UserEvent" command index
3.2.2.20.1
Sys.UserEvent<index> – Creates user-events
Command syntax
$PFAL,Sys.UserEvent<index>
Examples
$PFAL,Sys.UserEvent0
Message description
This command is used to create a user-event for executing specific alarms.
Parameter description
<index>
Determine what UserEvent index should be created. Up to 10 UserEvents are available. For
details see the event Sys.UserEvent.e<index>. It can be set to a value from 0 to 9.
Notes
• This event can be used to combine several alarms (i.e. for optimizing larger configuration
or simply if more than 5 conditions are needed).
Warning !
 It is not recommended to use the UserEvent as it may produce „endless loops" that can slow
down the system performances or may affect the stability of other functions.
 Use the UserEvents at own risk. However, when using the UserEvents, think about all
consequences of (maybe recursively) launching alarms, especially in combination with various
states, which may influence itself by actions. System behaviour can be very unpredictable and
complex.
 Therefore, no support will be provided for configurations that contain UserEvents.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 84 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.2.21
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"AlarmLoop" command index
3.2.2.21.1
Sys.AlarmLoop.Start – Start alarm loop
Command syntax
$PFAL,Sys.AlarmLoop.Start[=<counter>,<delay>,<timeout>[,<text>]]
Examples
$PFAL,Sys.AlarmLoop.Start // Alarm loop will be started. the parameters will be loaded from
the corresponding cobfiguration
Message description
This command is used to create an alarm loop for emergency calling routine. The emergency
calling routine consists of different phases. In the 1st phase, the device appears a popup dialog
box with a countdown counter on the display, which is accompanied by beep tones. In this phase
the user has the possibility to manually cancel the emergency, otherwise the the device starts the
2nd phase. In the 2nd phase, the device sends an SMS message to the pre-configured phone
number and then starts making an emergency call by selecting the phone numbers in the phone
book entries with ID from 102 to 106 one by one until a phone number from the list is reached. If
the emergency call is successfully completed, then the calling loop will be stopped otherwise the
device will ask using a popup dialog box whether the emergency loop should be started one more
time. If the user does not reacts within 30 seconds, the device will restart a new emergency calling
loop.
Parameter description
[<counter>]
Determine the number of beep tones that will be heard during the alarm loop, which
decreases itself for each delay cycles.
[<delay>]
Determine the delay time in milliseconds between two beep tones. The minimum time is 2000
ms.
[<timeout>]
Determine the timeout in milliseconds for the outgoing calls. The minimum timeout is 2000
ms.
[<text>]
Optional user text, up to 18 characters, to be shown on the MAMBO2 display.
Notes
• If this command is executed without any parameters, then the parameters of the
configuration DISP.ALARMLOOP will be used.
3.2.2.21.2
Sys.AlarmLoop.Stop – Stop alarm loop
Command syntax
$PFAL,Sys.AlarmLoop.Stop
Examples
$PFAL,Sys.AlarmLoop.Stop
Message description
This command is used to stop the alarm loop as long as the device is in the 1st phase (see
Sys.AlarmLoop.Start)
Parameter description
none
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 85 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"CNF" command type
The CNF command type is used to set and read all device configuration settings. Device configuration
settings are stored in the non-volatile system memory, so they remain active after booting up the
device. Each parameter can be set, modified, cleared and read out at any time. However notice that
some changes might not get active immediately, for example, when changing TCP/GPRS connection
settings while the device is connected to GPRS and TCP services. A few configuration settings also
require a device reset to get active. If a configuration setting is cleared, and it has a default value then
this value is loaded again.
3.2.3.1
Cnf.Set,<parameter_name=value> - Sets configuration settings
Command syntax
$PFAL,Cnf.Set,<parameter_name=value>
Examples
$PFAL,Cnf.Set,GSM.PIN=1234
$PFAL,Cnf.Set,DEVICE.NAME=myMAMBO2-B6/UXFS
$PFAL,Cnf.Set,AL0=Sys.BT.eConnected:IO.LED1=cyclic,500,1000
$PFAL,Cnf.Set,AL1=Sys.BT.eDisconnected:IO.LED1=low
….
Command description
This command is used to set the device configuration settings.
Parameter description
<parameter_name=value>
This entry defines the parameter name and the corresponding value(s) that has to be set ot
changed. Note that <parameter_name> has to be specified in CAPITAL letters always. If small
letters are inside - or the spelling is not exactly the same, this configuration setting would also
be stored, but would never become active as it differs from the configuration. Specifying a
<parameter_name> which is unknown for the system allows to store user information
permanently, which might be desired for some applications.
ê Warning: The configuration memory is restricted to approx. 32KB – this means it is not
possible to enter more than approx. 32700 characters for the configuration.
The value contains the settings of the specified parameter. Usually this information is case
insensitive, but special care should be taken to match the required syntax for the
corresponding parameter name otherwise the settings might not be stored or lead to
unexpected system behaviour.
The following table shows the configuration parameters that are used in the MAMBO2B6/UXFS firmware grouped by major category. Use the hypertext links (shown in blue text) to
navigate the parameter description, which explains how to configure that parameter.
Parameter names
Setting Device Configuration
Brief description
Chapter
DEVICE.NAME
Defines or changes the device name.
3.3.1.1
DEVICE.CMD.PFAL.EN
Defines communication channels to be available on the device.
3.3.1.2
DEVICE.COMM.<interface>
Determines the communication mode on the allowed interfaces. This
parameter doesn't have to be configured with CNF.SET. The PFAL 3.3.1.3
command "MSG.Mode" can be used instead.
DEVICE.STARTUP.QUIET
Sets device into the quiet mode during boot and shutdown
3.3.1.4
DEVICE.IGNTIMEOUT
Determines the amount of timeout the system waits until it shutdown.
3.3.1.5
DEVICE.PROT.BINARY
Defines which protocols should be reported when the PFAL-Command
3.3.1.6
$PFAL,MSG.Send.<channel>,8000,"test" is received by the device.
DEVICE.KEYTONE
Activates/deactivates key tones
3.3.1.7
DEVICE.BEEPTONE
Activates or deactivates the beep tones
3.3.1.8
DEVICE.PHONR
Enters either the MAMBO2-B6/UXFS phone number or any desired text or
3.3.1.9
number.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 86 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Parameter names
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Brief description
Chapter
DEVICE.GSM.STARTUP
Controls the operation of the GSM engine
3.3.1.10
DEVICE.GPS.STARTUP
Controls the operation of the GPS engine
3.3.1.11
DEVICE.GPS.AUTOCORRECT
DEVICE.GPS.CFG
DEVICE.GPS.TIMEOUT
DEVICE.GPS.HEADING
Implements an internal GPS position check routine, to filter out the
incorrect or improbable GPS positions. Its main purpose is to filter out the 3.3.1.12
„GPS Jumps" in areas with very poor GPS signal quality.
Specifies the number of satellites to consider a GPS Fix as "valid".
3.3.1.13
Enables and specifies the period of time the GPS will search for satellites 3.3.1.14
before performing a GPS reset.
Configures the GPS heading feature
3.3.1.15
DEVICE.PFAL.SEND.FORMAT
Enables or disables the static navigation mode (for MAMBO2 devices with 3.3.1.16
SiRF receiver only)
Enables or disables the SBAS mode (for MAMBO2 devices with SiRF 3.3.1.17
receiver only)
Generates a specific format for all MSG.Send commands.
3.3.1.18
DEVICE.IEEE.STARTUP
Controls the operation of the IEEE module
3.3.1.19
DEVICE.BT.STARTUP
Controls the operation of the Bluetooth module
3.3.1.20
DEVICE.BT.LOCALNAME
Defines a name for your MAMBO2-B6/UXFS Bluetooth device
3.3.1.21
DEVICE.BT.AUDIOGW
Specifies the MAC address and passkey for the Bluetooth headset
3.3.1.22
DEVICE.GPS.NAVSTATIC
DEVICE.GPS.NAVSBAS
DEVICE.ANT.STARTUP
DEVICE.ANT.HEARTBEAT
DEVICE.ANT.CHANNEL
DEVICE.BIKESPEED.CIRCUM
DEVICE.HEARTBEAT.PROFILE
Controls the operation of the ANT module. ANT option is no longer 3.3.1.23
available.
Monitors the heartbeats. ANT option is no longer available.
3.3.1.24
Defines different configuration profiles for using different ANT sensors 3.3.1.25
with the MAMBO2-B6/UXFS. ANT option is no longer available.
Specifies the circumference of the bicycle wheel to calculate the speed of 3.3.1.26
the bicycle. ANT option is no longer available.
Activates an already configured heartbeat profile. ANT option is no longer 3.3.1.27
available.
Setting DISP configuration
DISP.VIEWS
DISP.MENU
DISP.PHONE
Defines the views that will be used on the MAMBO2-B6/UXFS display
3.3.2.1
Adds items directly into a menu or submenu and allows to control your 3.3.2.2
device per key press.
Saves phone numbers in the phonebook
3.3.2.3
DISP.ANSWER
Defines which protocol should be reported when the PFAL-Command 3.3.2.4
PFAL,Display.Message is executed as an answer for the server-related M-Box
messages.
Defines the text that will be used as an answer for the received SMS
3.3.2.5
DISP.ALARMLOOP
Defines the settings for the alarm loop.
3.3.2.6
DISP.SAVER
Defines how to start the screen saver
3.3.2.7
DISP.TZ
Converts the time-zone to local time
3.3.2.8
DISP.LANG
Specifies the language on the device
3.3.2.9
DISP.MESSAGE.PROT
DISPLAY.SLIDING
DISP.KEYLOCK
Displays alternately every 2 or 3 seconds specific views until a key press is 3.3.2.10
detected
Locks the keys on the MAMBO2-B6/UXFS after a time period you specified 3.3.2.11
and protect them from being pressed accidentally
Setting IEEE configuration
IEEE.PANID
Specifies the PAN (Personal Area Network) identifier.
3.3.3.1
IEEE.KEYFOB
Connects a Keyfob to the MAMBO2-B6/UXFS
3.3.3.2
IEEE.IOBOX
Connects an IO-BOX to the MAMBO2-B6/UXFS
3.3.3.3
IEEE.INDOOR
Defines when the INDOOR event should be occurs.
3.3.3.4
Designed for executing a large numbers of commands within a single line.
3.3.4.6
Optional Settings
MACRO<index>
Setting REPLACE Configuration
REPLACE<index>
Allows you to replace a specified number of strings (such as phone
numbers, user text etc.) with a specified replacement string. It helps you 3.3.5.1
change the text just one time instead each Alarm text (AL) separately.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 87 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Parameter names
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Brief description
Chapter
GSM.PROFILE.AUDIO<prof_index>
Adjusts the profile for loudspeaker volume level and microphone side tone. 3.3.4.4
GSM.PROFILE.CURRENT
Loads a configured audio profile.
3.3.4.5
MOTION.FILTER
Filters out the values of motion to generate its events.
3.3.6.1
MOTION.BEARING
Defines the configuration settings to filter bearings of device motions
3.3.6.2
Configures the detection of the device position and generates the tilt event
when the device detects a change of orientation more then the 3.3.6.3
predefined range from the calibrated position.
Defines the limit values for all three axes of the 3D-sensor for detecting
3.3.6.4
falling event.
Setting MOTION Configuration
MOTION.TILT
MOTION.FALLING
Setting ALIAS Configuration
ALIAS.<type>
Defines alias names for each command type.
3.3.7.1
Enables or disables debug information to be output on the serial interface.
3.3.8.1
Setting Debugger Configuration
DBG.EN
Setting Protocol Configuration (for serial communication, only)
PROT.<message_id>
PROT.START.BIN
Not only allows certain messages to be enabled or disabled but also
3.3.9.1
specifies the rate at which they are sent to the serial interface.
Creates your own BIN protocol. Consists of 18 Bytes and used as a device
3.3.9.2
identifier for example.
Setting GPS configuration
GPS.TRIP.WPOINT<index>
Stores different waypoints in the list.
3.3.10.1
GPS.TRIP.POIMODE
Defines how the existing waypoints in the list should be followed.
3.3.10.2
GPS.TRIP.ROUTE<index>
Stores the location of up to 20 waypoints that are of interest to the user.
3.3.10.3
GPS.TRACE.DEV<index>
Specifies the name of other MAMBO2-B6/UXFS devices that you want to
covertly follow/track when the situation requires.
3.3.10.4
Setting GSM configuration
GSM.PIN
GSM.CALLID.EN
Sets the PIN of used SIM card (only locally possible).
3.3.11.1
Dials a specific GSM number to get the remaining credit for your used pre3.3.11.2
paid card
Controls the caller identification.
3.3.11.3
GSM.RINGER.ENABLE
Controls the Call Progress Tones generated when a call sets up
Fehler:
Referenz
nicht
gefunden
GSM.OPERATOR.BLACKLIST
Creates a customized blacklist consisting of GSM operator names.
3.3.11.4
GSM.OPERATOR.SELECTION
Configures the GSM operator selection.
3.3.11.5
GSM.BALANCE.DIAL
GSM.OPLOST.RESTART
GSM.SMS.RESPONSE
Determines whether the system should reinitialize the GSM engine when
3.3.11.6
the GSM operator becomes lost.
Enables/disables responses from the MAMBO2-B6/UXFS when SMS
3.3.11.7
communication is applied.
GSM.SMS.RETRIES
Enables the device to re-send failed SMS messages
3.3.11.11
GSM.CALL.SIGNALING
Enables/Disables Call Progress Tones
3.3.11.8
GSM.SMS.SIGNALING
Enables/Disables signalling when receiving an SMS.
3.3.11.9
GSM.MSG.SIGNALING
Enables/Disables signalling when receiving TCP messages.
3.3.11.10
GSM.SMS.ALWAYSREAD
Enables reading of incoming SMS during an active voice call
3.3.11.12
GSM.SPYCALL.SELECTION
Defines a list of spy calls
3.3.11.13
GSM.SPYCALL.EXCEPT
The list of phone numbers to be excepted from the spy call list.
3.3.11.14
GPRS.APN
Specifies the APN (Access Point Name) context for GPRS connection.
3.3.12.1
GPRS.AUTOSTART
Enables/disables the GPRS auto start. It performs automatically a GPRS
3.3.12.2
attachment even if it fails unexpectedly.
Setting GPRS configuration
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 88 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Parameter names
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Brief description
Chapter
GPRS.DIAL
Specifies the dial text used for GPRS connection.
3.3.12.3
GPRS.TIMEOUT
Specifies the time out in which the GPRS connection will be automatically
3.3.12.4
shutdown if there is no TCP communication currently available.
GPRS.QOSMIN
Specifies the minimum acceptable profile for identified context.
3.3.12.5
GPRS.QOS
Specifies the acceptable profile for identified context.
3.3.12.1
PPP.USERNAME
Specifies the user name to connect to the GPRS network.
3.3.13.1
PPP.PASSWORD
Specifies the password to connect to the GPRS network operator.
3.3.13.2
PPP.AUTOPING
Enables/disables the maximal idle time until the a ping will be sent to the
3.3.13.3
GPRS network to keep the GPRS connection alive.
PPP.AUTH
Defines the authentication method to be used over PPP.
3.3.13.4
TCP.CLIENT.CONNECT
Specifies the IP address and port number of the remote server.
3.3.14.1
TCP.CLIENT.ALTERNATIVE
Defines an alternative server in case the primary server fails
3.3.14.2
TCP.CLIENT.PING
Enables/disables the sending of pings to the remote server to keep that
connection alive.
3.3.14.3
Specifies the length of time the MAMBO2-B6/UXFS waits between
attempts to establish a TCP connection connection.
3.3.14.4
Setting TCP Configuration
TCP.CLIENT.TIMEOUT
TCP.CLIENT.DNS.TIMEOUT
Specifies the DNS cache timeout.
3.3.14.5
TCP.CLIENT.LOGIN
Specifies the login data to log the device into the used remote server.
3.3.14.5
Defines the login extension data to be additionally sent to the remote
3.3.14.7
server
Configures a TCP service connection, which allows to run services like
remote control, configuration, remote updates, AGPS etc.. without the 3.3.14.8
need to reconfigure a currently used TCP client connection.
Defines the period of time the device will wait for a response and between
two connection attempts when the connection to the TCP service server 3.3.14.9
fails.
TCP.CLIENT.LOGIN.EXT
TCP.SERVICE.CONNECT
TCP.SERVICE.TIMEOUT
TCP.CLIENT.SENDMODE
Selects the type of TCP transmissions between fast and safe.
3.3.14.10
TCP.STORAGE
Specifies the size of TCP storage and the operation mode.
3.3.14.11
TCP.SMTP.CONNECT
Configures the sending of E-Mail via an Internet mail server.
3.3.14.12
TCP.SMTP.LOGIN
Identities the authentication for the SMTP session when sending E-Mail to
3.3.14.13
an Internet mail server.
TCP.SMTP.FROM
Configure the E-Mail address of the sender of the message.
3.3.14.14
GF.CONFIG
Sets the global configuration of the Geo-fence functionalities.
3.3.15.4
GF.AREA
Allows setting up 32 areas in a range of 0 to 31.
3.3.15.5
GF<id>
Sets up the shape of the Geo-fence zone. The MAMBO2-B6/UXFS device
3.3.15.6
can hold up to 100 Geo-fence zones.
Setting SMTP Configuration
Setting Geo-fence Configuration
Setting Alarm Configuration
Allows to specify a powerful multi-configuration and reporting messages as
well as to create a maximum monitoring of system events and states which 3.3.16
can be occurred during the operation of the MAMBO2-B6/UXFS device.
AL<index>
Table 6:
Configuration parameters supported by the device and grouped by major category.
Notes
• Configuration parameters must be written in capital letters, otherwise no configuration is
stored.
• If a configuration parameter is transmitted to the device without settings, its current
configuration will be reset to its default and it remains active all the time until overwritten.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 89 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.3.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Cnf.Get,<parameter_name> - Queries configuration settings
Command syntax
$PFAL,Cnf.Get,<parameter_name>
Examples
$PFAL,Cnf.Get,GSM.PIN
$PFAL,Cnf.Get,DEVICE.NAME
$PFAL,Cnf.Get,TCP.CLIENT.CONNECT
….
Message description
This command is used to read the device configuration settings.
Parameter description
<parameter_name>
The following table shows the configuration parameters that are available in the MAMBO2B6/UXFS firmware grouped by major category. Use the hypertext links (shown in blue text) to
navigate the parameter description, which explains you, what does the received configuration
mean.
Parameter names
Setting Device Configuration
DEVICE.NAME
Brief description
Chapter
DEVICE.COMM.<interface>
Queries device name.
3.3.1.1
Queries the configuration of communication channels on the
3.3.1.2
device.
Queries the communication mode on different interfaces.
3.3.1.3
DEVICE.STARTUP.QUIET
Queries whether the quiet mode is enabled or disabled
DEVICE.CMD.PFAL.EN
DEVICE.IGNTIMEOUT
DEVICE.PROT.BINARY
3.3.1.4
Queries the amount of timeout the system waits before going to
3.3.1.5
sleep
Returns an integer indicating the protocol that will be reported
when the PFAL-Command $PFAL,MSG.Send.<channel>,8000,"test" 3.3.1.6
is received by the device.
DEVICE.KEYTONE
Queries whether the key tone is activated or deactivated
3.3.1.7
DEVICE.BEEPTONE
Returns an integer indicating if the beep tones have been activated.
3.3.1.8
DEVICE.PHONR
Returns the phone number of the MAMBO2-B6/UXFS or any other
3.3.1.9
string if it has been specified.
DEVICE.GSM.STARTUP
Queries whether the GSM engine is powered on or off
3.3.1.10
DEVICE.GPS.STARTUP
Queries whether the GPS engine is powered on or off
3.3.1.11
DEVICE.GPS.AUTOCORRECT
Queries the settings for GPS auto correction
3.3.1.12
Queries the number of satellites considered for a valid GPS Fix.
3.3.1.13
DEVICE.GPS.CFG
DEVICE.GPS.TIMEOUT
DEVICE.GPS.HEADING
Queries the period of time the GPS will search for satellites before 3.3.1.14
performing a GPS reset.
Queries the settings for GPS heading.
3.3.1.15
DEVICE.PFAL.SEND.FORMAT
Returns an integer indicating if the static navigation mode has been 3.3.1.16
enabled (for MAMBO2 devices with SiRF receiver only)
Returns an integer indicating if the SBAS mode has been enabled 3.3.1.17
(for MAMBO2 devices with SiRF receiver only)
Queries the format syntax for all MSG.Sendcommands.
3.3.1.18
DEVICE.IEEE.STARTUP
Queries whether the IEEE module is powered on or off.
3.3.1.19
DEVICE.BT.STARTUP
Queries whether the Bluetooth module is powered on or off.
3.3.1.20
DEVICE.BT.LOCALNAME
Queries the name used for Bluetooth.
3.3.1.21
DEVICE.GPS.NAVSTATIC
DEVICE.GPS.NAVSBAS
DEVICE.ANT.STARTUP
Queries the MAC address and passkey of the last connected 3.3.1.22
Bluetooth headset.
Queries whether the ANT module is powered on or off.
3.3.1.23
DEVICE.ANT.HEARTBEAT
Queries the min. and max. for heartbeats.
DEVICE.BT.AUDIOGW
DEVICE.ANT.CHANNEL
DEVICE.BIKESPEED.CIRCUM
DEVICE.HEARTBEAT.PROFILE
3.3.1.24
Returns the configuration profiles that the device is using for 3.3.1.25
connecting different ANT sensors with the MAMBO2-B6/UXFS.
Returns the circumference of the bicycle wheel that the device is 3.3.1.26
using to calculate the speed of the bicycle.
Returns an integer indicating the heartbeat profile being active.
3.3.1.27
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 90 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Parameter names
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Brief description
Chapter
Setting DISP configuration
DISP.VIEWS
Queries which views are shown on the screen.
3.3.2.1
DISP.MENU
Queries which items are available to a menu or submenu
3.3.2.2
DISP.PHONE
Queries which phone numbers are available in the phonebook
3.3.2.3
DISP.ANSWER
Returns an integer indicating the protocol to be reported when the 3.3.2.4
PFAL-Command PFAL,Display.Message is executed.
Queries the available answers that can be uses for the received SMS 3.3.2.5
DISP.ALARMLOOP
Queries settings for the alarm loop.
3.3.2.6
DISP.SAVER
Queries the settings for the screen saver
3.3.2.7
DISP.TZ
Queries the local time
3.3.2.8
DISP.LANG
Queries the language currently available on the device
3.3.2.9
DISPLAY.SLIDING
Queries the mode and time out in seconds of sliding.
3.3.2.10
DISP.MESSAGE.PROT
DISP.KEYLOCK
DISP.SWAPBTN
Returns an integer indicating the time period after which the 3.3.2.11
MAMBO2-B6/UXFS will lock the keys in case of inactivity.
Returns an integer indicating if the functionality of the left and right 3.3.2.12
mouse buttons has been swapped.
Setting IEEE configuration
IEEE.PANID
Queries the PAN (Personal Area Network) identifier.
3.3.3.1
IEEE.KEYFOB
Queries which Keyfobs are connected to the MAMBO2-B6/UXFS
3.3.3.2
IEEE.IOBOX
Queries which IO-BOX are connected to the MAMBO2-B6/UXFS
3.3.3.3
IEEE.INDOOR
Queries when the INDOOR field strength
3.3.3.4
STORAGE<id>
-
3.3.4.1
GSM.BANDPREF
-
3.3.4.2
GSM.VERSION
-
3.3.4.3
GSM.PROFILE.AUDIO<prof_index>
-
3.3.4.4
GSM.PROFILE.CURRENT
-
3.3.4.5
GSM.PROFILE.CURRENT
-
3.3.4.5
MACRO<index>
-
3.3.4.6
Queries the REPLACE settings
3.3.5.1
Queries motion filters settings.
3.3.6.1
MOTION.BEARING
Queries bearing settings
3.3.6.2
MOTION.TILT
Queries Tilt settings
3.3.6.3
Returns the limit values for all three axes that the MAMBO2-B6/UXFS
3.3.6.4
will use detecting falling event.
Optional Settings
Setting REPLACE Configuration
REPLACE<index>
Setting MOTION Configuration
MOTION.FILTER
MOTION.FALLING
Setting ALIAS Configuration
ALIAS.<type>
Queries alias names
3.3.7.1
Queries whether the debug is enabled or disabled
3.3.8.1
Setting Debugger Configuration
DBG.EN
Setting Protocol Configuration (for serial communication, only)
PROT.<message_id>
Queries whether specific protocol is switched on or off
3.3.9.1
PROT.START.BIN
Queries BIN protocol syntax
3.3.9.2
Queries waypoint settings of specified index.
3.3.10.1
Setting GPS configuration
GPS.TRIP.WPOINT<index>
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 91 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Parameter names
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Brief description
Chapter
GPS.TRIP.POIMODE
Queries the mode of how the existing waypoints in the list are
selected.
GPS.TRIP.ROUTE<index>
Depending on the specified index, it returns the location of a
waypoint.
3.3.10.3
GPS.TRACE.DEV<index>
Depending on the specified index, it returns the specified name of
other MAMBO2-B6/UXFS devices that you want to covertly
follow/track when the situation requires.
3.3.10.4
3.3.10.2
Setting GSM configuration
GSM.PIN
GSM.BALANCE.DIAL
GSM.CALLID.EN
Queries the PIN of used SIM card (only locally possible).
3.3.11.1
Queries what number will be dialled to get the remaining credit for
3.3.11.2
your used pre-paid card.
Queries whether the caller identification is enabled or disabled.
3.3.11.3
Fehler: Referenz nicht gefunden
Fehler:
Queries whether or not the Call Progress Tones will be generated Referenz
when a call sets up.
nicht
gefunden
GSM.OPERATOR.BLACKLIST
Queries blacklist for GSM operator names.
3.3.11.4
GSM.OPERATOR.SELECTION
Queries the GSM operator selection.
3.3.11.5
GSM.OPLOST.RESTART
Queries GSM behaviours when it looses an GSM operator.
3.3.11.6
GSM.SMS.RESPONSE
Queries the number of SMS responses
3.3.11.7
GSM.SMS.RETRIES
Returns the retries for sending failed SMS messages
3.3.11.11
GSM.SMS.ALWAYSREAD
Returns an integer indicating if the device will read the incoming
3.3.11.12
SMS during an active voice call.
GSM.SPYCALL.SELECTION
Returns a list of spy calls.
3.3.11.13
GPRS.APN
Queries the APN (Access Point Name) context for GPRS connection.
3.3.12.1
GPRS.AUTOSTART
Queries GPRS auto start.
3.3.12.2
GPRS.DIAL
Queries dial text used for GPRS connection.
3.3.12.3
GPRS.TIMEOUT
Queries GPRS connection timeout.
3.3.12.4
GPRS.QOSMIN
Queries minimum acceptable profile for a context.
3.3.12.5
GPRS.QOS
Queries acceptable profile for a context.
3.3.12.1
PPP.USERNAME
Queries logging name used for GPRS dialup.
3.3.13.1
PPP.PASSWORD
Queries logging password used for GPRS dialup.
3.3.13.2
PPP.AUTOPING
Queries time of auto pings for GPRS network
3.3.13.3
PPP.AUTH
Queries authentication method used for PPP.
3.3.13.4
Setting GPRS configuration
Setting TCP Configuration
TCP.CLIENT.CONNECT
Queries IP address and port number for TCP connection
3.3.14.1
TCP.CLIENT.ALTERNATIVE
Returns the IP address and port number of the alternative TCP
server.
3.3.14.2
TCP.CLIENT.PING
Returns the time of pings for TCP connection.
3.3.14.3
TCP.CLIENT.TIMEOUT
Returns the TCP connection timeout.
3.3.14.4
TCP.CLIENT.DNS.TIMEOUT
Returns the DNS cache timeout.
3.3.14.5
TCP.CLIENT.LOGIN
Returns the device login data used for remote server.
3.3.14.6
TCP.CLIENT.LOGIN.EXT
Returns the the login extension data that will additionally be sent to
3.3.14.7
the remote server.
TCP.SERVICE.CONNECT
Returns the TCP service server settings
3.3.14.8
TCP.SERVICE.TIMEOUT
Returns the TCP service server connection time out
3.3.14.9
TCP.CLIENT.SENDMODE
Queries the defined type of TCP transmissions.
3.3.14.10
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 92 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Parameter names
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Brief description
TCP.STORAGE
Chapter
Queries TCP storage size
3.3.14.11
TCP.SMTP.CONNECT
Queries SMTP mail server settings
3.3.14.12
TCP.SMTP.LOGIN
Queries SMTP mail server authentication settings.
3.3.14.13
TCP.SMTP.FROM
Queries E-Mail address of message sender
3.3.14.14
GF.CONFIG
Queries Geo-fence settings.
3.3.15.4
GF.AREA
Queries Area settings
3.3.15.5
GF<id>
Queries Geo-fence type
3.3.15.6
Queries settings for a specific alarm
3.3.16
Setting SMTP Configuration
Setting Geo-fence Configuration
Setting Alarm Configuration
AL<index>
Table 7:
3.2.3.3
Configuration parameters supported by the device and grouped by major category
Cnf.Clear,<parameter_name> - Clears parameter settings
Command syntax
$PFAL,Cnf.Clear,"<parameter_name>"
Examples
$PFAL,Cnf.Clear,"AL"
Message description
This command is used to clear a single or a groups of configuration parameters. Each configuration
parameter will be reset to its default value when cleared. If the specified name matches to several
parameters (i.e. AL3, AL4, AL10), then all these parameters will be cleared. The device responds an
error if the specified parameter name is not found.
Parameter description
"<parameter_name>"
Specify, in capital letters, the name of the the parameter for erasing its present settings. Set
one of the parameters listed in the chapter 3.3, page 172.
Notes
• The name of the parameter (or the start characters) must be written in capital letters. Do
not use semicolon inside the specified parameter name.
• After executing this command, a list of the deleted parameters is displayed.
• The factory default settings cannot be erased.
• This command might take several seconds to complete the process depending on the
amount of the configuration settings to be erased.
3.2.3.4
Cnf.ShowUser - Queries user configuration
Command syntax
$PFAL,Cnf.ShowUser
Examples
$PFAL,Cnf.ShowUser
Message description
This command is used to show your custom settings. MAMBO2-B6/UXFS device will deliver all
parameter settings, except default configuration.
Parameter description
None.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 93 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.3.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Cnf.ShowDefault - Queries default settings
Command syntax
$PFAL,Cnf.ShowDefault
Examples
$PFAL,Cnf.ShowDefault
Message description
This command is used to show only the default settings. Default settings are listed in chapter 7.5.
Parameter description
None.
3.2.3.6
Cnf.Show - Shows used parameters
Command syntax
$PFAL,Cnf.Show
Examples
$PFAL,Cnf.Show
Message description
This command is used to show the used parameter stored in the internal FLASH memory of the
MAMBO2-B6/UXFS device. Default parameter settings will be displayed, if not modified by the
user. For example, if the user changes the device name from default "unnamed MAMBO2B6/UXFS" to "myMAMBO2-B6/UXFS", then this parameter is not delivered.
Parameter description
None.
3.2.3.7
Cnf.Search,<parameter> – Searches for parameter names
Command syntax
$PFAL,Cnf.Search,<parameter>
Examples
$PFAL,Cnf.Search,"DEVICE"
$PFAL,Cnf.Search,"TCP"
Message description
This command is used to search for the parameter names available in the configuration inside
MAMBO2-B6/UXFS starting with the specified name. If any parameters are found they are
displayed together with their current settings.
Parameter description
<parameter>
Enter a parameter name, in capital letters, that you want to search. The specified search text
must be wrapped in double quotation marks (""). The text can be one of the parameter names
listed in chapter 3.3, page 172. If no parameter is found the device will output only:
$<CNF.Search>
$SUCCESS
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 94 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"IO" command type
3.2.4.1
IO.LED<index>=<conf_type> – Specifies LED behaviour
Command syntax
$PFAL,IO.LED<index>=<config_type>
Examples
$PFAL,IO.LED1=high
$PFAL,IO.LED1=low
Message description
This command is used to specify the behaviours of LED1.
Parameter description
<index>
Specify the index of the LED to be configured. Following values are available:
Value
Meaning
1
MAMBO2-B6/UXFS has only one LED indicator and this is LED1. This LED is
free configurable as long as the firmware is running. During the MAMBO2B6/UXFS is sleeping or charging, this LED indicates the battery charging
status - it lights red when the battery is charging.
2
MAMBO2-B6/UXFS (hardware revisions 5E) has also 2 LED indicators and
these are LED1 (Red) and LED2 (Blue). Both LEDs are free configurable.
<config_type>
Specify the configuration type on the LED1. The LED1 on MAMBO2-B6/UXFS can be set to one
of following values:
Value
Meaning
high
Sets IO<index> to the High level.
low
Sets IO<index> to the Low level.
hpulse,<high_time>
Performs a single high pulse for the specified time. The output
immediately switches to high level, waits <high_time> ms and then
switches back to low level.
lpulse,<low_time>
Performs a single low pulse for the specified time. The output
immediately switches to low level, waits <high_time> ms and then
switches back to high level.
cyclic,<high_time>,<low_time>
Changes level periodically for the specified times. The
output immediately switches to high level, waits <high_time> ms, then
switches to low level for <low_time> ms. This procedure is repeated until
another functionality is specified.
<high_time>
Time* in ms at which the port is set to high level.
<low_time>
Time* in ms at which the LED is set to low level.
* minimum: currently 125 ms. smaller values will be accepted but won't show
a different behaviour. Maximum: (nothing to care about: 2 exp 32 –1 ms).
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 95 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.4.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
IO.Beep<index>=<config_type> – Generates simple tones
Command syntax
$PFAL,IO.Beep<volume>=<config_type>
Examples
$PFAL,IO.Beep0=cyclic,500,1000
$PFAL,IO.Beep1=high
$PFAL,IO.Beep2=low
$PFAL,IO.Beep3=hpulse,5000
……
$PFAL,IO.Beep27=…..
E.g. $SUCCESS
Responses
Command description
This command is used to generate a simple tone with specific volume level on the MAMBO2B6/UXFS device, for example, a simple tone can be generated when the device receives or sends
an SMS, GPS-fix, TCP packet etc.. Muting and the volume control of the speaker have no effect on
Beep; you will still hear the tone. The calculation of the 3D motion values is deactivated during the
device is beeping.
Parameter description
<volume>
Selects the volume level of the sound. It must be in the range 0 (low) through 27 (high).
 MAMBO2-B6/UXFS (hands-free) can produce a very loud sound when this value is too
high.
<config_type>
Configure the settings related to generate simple tones on the device. It can be set to:
Value
Meaning
high
Generates continuous tone.
low
Disables continuous or cyclic tones.
hpulse,<on-time>
Generates a single tone for the <on-time> period.
lpulse,<off-time>
Disables a continuous tone for the <off-time> period.
cyclic,<on-time>,<off-time>
Generates cyclic tones for the <on-time> period and no
tones for the <off-time> period.
<on-time>
Determines the amount of "on-time", in milliseconds, during one cycle.
<off-time>
Determines the amount of "off-time", in milliseconds, during one cycle.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 96 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.4.3
Command syntax
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
IO.Vibration=<config_type> – Manages device vibrations
$PFAL,IO.Vibration=<config_type>
$PFAL,IO.Vibration=hpulse,5000
Examples
$PFAL,IO.Vibration=cyclic,500,1000
E.g. $SUCCESS
Responses
Command description
This command can be used to make the device vibrate, for example, when receiving a GSM call,
SMS, TCP packet etc. The calculation of the 3D motion values is deactivated while the device is
beeping.
Parameter description
<config_type>
Configure the settings of how to generate a vibration on the device. It can be set to:
Value
Meaning
high
Enables continuous vibration.
low
Disables a continuous vibration.
hpulse,<on-time>
Vibrates for the <on-time> period.
cyclic,<on-time>,<off-time>
Vibrates for the <on-time> period and no vibrations for
the <off-time> period.
<pn-time>
Determines the amount of "on-time", in milliseconds, during one cycle.
<off-time>
Determines the amount of "off-time", in milliseconds, during one cycle.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 97 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"GPS" command type
3.2.5.1
"Nav" command index
The following PFAL-Commands can be used to save the last valid GPS positions, retrieve the distances
and assign, load or store specific positions.
The distance between different positions and the device can be used inside alarms.

Positions are used for alarm configuration only. Their purpose is temporarily storing of
GPS positions. Alarm actions may be launched depending on the distance to a defined
position.

The distance counter can be used to calculate the number of metres covered by the
device. The counter can be retrieved at any time e.g. even during a trip.

Saving a last valid position is used to ‚always‘ assure a valid position. Usually directly
after system startup (before GPS gets a valid fix for the first time) there is no available
last valid position. If a position has been saved in the past (before device shuts down),
this position can be used as "last valid position" until GPS gets a new valid fix.
3.2.5.1.1
GPS.Nav.Position<buffer_index> – Returns bee-line distance from a stored location
Command syntax
$PFAL,GPS.Nav.Position<buffer_index>
Examples
$PFAL,GPS.Nav.Position0
Message description
This command retrieves the number of metres (bee-line distance) between the device and
specified position which has to be assigned first.
Parameter Description
<buffer_index>
Specify the memory buffer index, in the range from 0 to 4, to be read. Each memory buffer
index is a piece of SRAM memory that is used to temporarily store/read the data. The content
of each buffer index is available as long as the internal software is running. Should the device
be reset, switched off, or goes into sleep mode, each index loses its contents forever. Each
memory buffer index has a fixed size and each of them can be updated with new data or the
available data on them can be erased.
3.2.5.1.2
GPS.Nav.Position<buffer_index>=<type> – Saves temporarily or clears a device
position
Command syntax
$PFAL,GPS.Nav.Position<buffer_index>=<type>
Examples
$PFAL,GPS.Nav.Position1=current
$PFAL,GPS.Nav.Position2=none
$PFAL,GPS.Nav.Position2=pos50.683317,10.980760,490.0
Command description
This command is used to store temporarily one of the supported values into the specified
<buffer_index>. After a position is stored into the <buffer_index>, the alarm conditions can be
defined to launch certain action based on the distance calculated from a saved position to the
current device position. The calculated distance is in meter.
Parameter Description
<buffer_index>
Specify the memory buffer index, in the range from 0 to 4, to save information for possible
further use. Each memory buffer index is a piece of SRAM memory that is used to temporarily
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 98 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
store the data. The content of each buffer index is available as long as the internal software is
running. Should the device be reset, switched off, or goes into sleep mode, each index loses
its contents forever. Each memory buffer index has a fixed size and each of them can be
updated with new data or the available data on them can be erased.
<type>
Determine what type of data should be saved in the specified buffer index. This entry can be
set to one of the following values:
Value
Meaning
none
Clears the contents of the selected <buffer_index>. If the specified
contents is empty, the MAMBO2-B6/UXFS response " Error to execute
command type GPS".
current
Stores the current GPS position of the device into the selected
<buffer_index>. Position is stored only when the device has a valid GPS-fix.
pos<lat>,<lon>,<alt>
Stores temporarily the latitude, longitude and altitude of a
location. This location enables to execute certain distance-based actions.
As
reference,
see
description
of
the
"GPS.Nav.Position.s<buffer_index><comp><value>" state.
The <lat>,<lon> and <alt> should be entered in decimal format. The <alt>
determines the altitude, in meters, above the sea level. If you do not know
exactly the altitude of that location then specify an approx. value as an
integer without decimal dot ".".
Notes
• The functionality of this command enables periodically sending of messages that are based
on distance covered by the device.
• The current GPS position will be stored into the specified <buffer_index>, if <buffer_index>
contents results valid.
3.2.5.1.3
GPS.Nav.Position<buffer_index>=save<slot_id> – Moves GPS position data from
buffer to storage slots
Command syntax
$PFAL,GPS.Nav.Position<buffer_index>=save<slot_id>
Examples
$PFAL,GPS.Nav.Position3=save0
Command description
This command is used to memorize the contents of the position slot to a storage slot even if the
device resets or shuts down.
Parameter description
<buffer_index>
Specify the buffer index, in the range from 0 to 4, to restore its contents into the FLASH.
<slot_id>
The ID of the slot to store the contents. There are totally 5 storage slots, from 0 to 4,
supported by the MAMBO2-B6/UXFS device. Please, specify a <slot_id> that is empty,
otherwise you will overwrite that contents.
Notes
• An Alias name can be defined for
ALIAS.STORAGE<storage_index>=<alias_name>.
each
storage
index
by
using
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 99 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.5.1.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPS.Nav.Position<buffer_index>=load<slot_id> – Loads data from storage to buffer
Command syntax
$PFAL,GPS.Nav.Position<buffer_index>=load<slot_id>
Examples
$PFAL,GPS.Nav.Position3=load0
Command description
This command is used to load temporarily the contents of the selected <slot_id> into the selected
<buffer_index>. The selected buffer index will be automatically refreshed with new data while the
data into the <slot_id> remains unchanged. The data selected from the storage index must be
validated (means, the <slot_id> must contain only GPS position data and no other data like Timer
or Trigger states) before making any attempt to access the new data loaded in the selected
<buffer_index>.
Parameter description
<buffer_index>
Specify the buffer index, in the range from 0 to 4, for loading with new data.
<slot_id>
The ID of the slot to load the contents. There are totally 5 storage slots, from 0 to 4,
supported by the MAMBO2-B6/UXFS device. Please, specify a <slot_id> containing GPS data
(stored with GPS.Nav.Position<buffer_index>=save<slot_id>), otherwise the device returns
error.
Notes
• An Alias name can be defined for
ALIAS.STORAGE<storage_index>=<alias_name>.
3.2.5.1.5
each
storage
index
by
using
GPS.Nav.Distance – Reads distance counter
Command syntax
$PFAL,GPS.Nav.Distance
Examples
$PFAL,GPS.Nav.Distance
Command description
This command is used to read out the distance, in metres, from the current distance counter.
Parameter description
None
Notes
• To get the distance the device has done (e.g. during a trip), first reset the distance to zero
(GPS.Nav.Distance=0, see the next section) and then simply read out (GPS.Nav.Distance)
the distance when the destination point of the trip is reached.
• To get the distance between 2 specific positions, use the command SetDistance to reset
the counter on the first position (e.g. when a trip starts). To get the number of meters
covered by the device (e.g. during this trip), simply read out the distance when the end
position of this trip is reached.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 100 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.5.1.6
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPS.Nav.Distance.Save – Stores distance
Command syntax
$PFAL,GPS.Nav.Distance.Save
Examples
$PFAL,GPS.Nav.Distance.Save
Command description
This command stores the current distance counter to non-volatile memory. The stored value will be
automatically loaded during startup, so no further commands are required.
Parameter description
None
3.2.5.1.7
GPS.Nav.Distance.Load – Loads distance from memory
Command syntax
$PFAL,GPS.Nav.Distance.Load
Examples
$PFAL,GPS.Nav.Distance.Load
Command description
This command loads the current distance counter from non-volatile memory. The stored value will
be automatically loaded during startup, so no further commands are required at system start.
Parameter description
None
3.2.5.1.8
GPS.Nav.Distance=<value> – Sets distance
Command syntax
$PFAL,GPS.Nav.Distance=<value>
Examples
$PFAL,GPS.Nav.Distance=0
$PFAL,GPS.Nav.Distance=10
Message description
This command is used to set the distance counter to a fixed value. It can be used either to reset
the distance counter (set it to 0) or to use an offset distance from which the counter starts.
Parameter description
<value>
Integer type value in the range of 0 to 4294967295.
Notes
• The distance covered by the device (since startup or last "counter reset") is permanently
added to the distance counter if GPS has a valid position and if DOP values are sufficient
for Geo-fence usage (see configuration reference – Geo-fence setting to get details of the
defined maximal DOP value.
• To get the distance covered by the device after a certain position, simply reset the counter
when the device is at the desired position. (e.g. when a trip starts). To get the number of
meters covered by the device (e.g. during or after a trip), simply read out the distance.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 101 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.5.1.9
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPS.Nav.SaveLastValid[=<time>,<lat>,<lon>,<alt>] – Saves last valid position
Command syntax
$PFAL,GPS.Nav.SaveLastValid[=<time>,<lat>,<lon>,<alt>]
Examples
$PFAL,GPS.Nav.SaveLastValid
$PFAL,GPS.Nav.SaveLastValid=133726569,502536,103567,450
$last valid position updated with customized position/time
Responses
$last valid position saved to configuration
Message description
This command is used to save the last valid position even if the device has an invalid GPS-fix. If
MAMBO2-B6/UXFS is receiving invalid GPS position when this command is executed, then an
empty RMC message (a RMC protocol containing only zero values) will be internally stored. To
prevent MAMBO2-B6/UXFS form storing invalid GPS positions, set this command in an alarm (e.g.
AL2) for saving valid GPS position into non-volatile memory before the device shuts down
($PFAL,Cnf.Set,AL2=Sys.Device.eShutdown:GPS.Nav.SaveLastValid). This stored data is needed for
the next power up scenario. So, if there is no valid GPS fix during the next startup, then the last
valid position already stored in the device will automatically be added to the command
"MSG.Info.Serverlogin" and sent to the remote server as well as an invalid RMC protocol will be
updated with the last stored valid position. In this way you will always receive valid GPS position
instead of an invalid RMC protocol that contains only zero values.
Additionally, as long as the device has an invalid GPS time during the startup, it always uses either
the time from the last valid position (the latest known time, if available) or the time starting from
"06.01.1980 00:00:00". This time can be used until the device gets a valid GPS fix again, which
allows to show a valid position even when the device has no GPS fix after startup. Once a few GPS
satellites are in view the estimated GPS time information can be shown. If this time is older than
the last valid position stored in the device, it will be discarded.
Parameter description
All these parameters listed below are optional.
[<time>]
The UTC time to be saved, in decimal format (e.g. 133726569).
[<lat>]
Specify the latitude to be saved, in decimal format (e.g. 502536).
[<lon>]
Specify the longitude to be saved, in decimal format (e.g. 103567).
[<alt>]
Specify the altitude to be saved, in meter (e.g. 450).
Notes
• Because the non-volatile memory is limited to several 100'000 write operations, it is
strongly recommended to prevent periodically saving of the last valid position in a short
period of time.
• The saved last valid position will always be displayed, during the system startup, when the
system exists in an area without GPS coverage and whenever a valid GPS fix becomes
invalid.
• This command may need up to 30 seconds to complete. To reduce the time to first fix
(TTFF) process, the MAMBO2-B6/UXFSwill automatically load the last stored valid position
during each startup.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 102 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
• This time can be used to write history records and perform data logging. In order to read
out the history by time/date span, be sure that the stored time in these records is always
up to date!!
 Following the hints to assure correct processing:
✔ To assure consistent history times, always store the last valid position before
shutting down the device and write history entries after the device starts up. Do
not write any history entries between saving and device shutdown process.
✔ It may never happen that the time of a record to be stored in the history is
smaller than the time of the prior record already logged in history. The time/date
of each new record you write must always be greater than the prior stored
record.
3.2.5.1.10
GPS.Nav.PowerSave=<mode>,<ontime>,<lptime>
TricklePower mode
Command syntax
GPS.Nav.PowerSave=<Mode>,<OnTimeMs>,<LPInterval>
Examples
$PFAL,GPS.Nav.PowerSave=enable,300,1000
$PFAL,GPS.Nav.PowerSave=enable,400,2000
$PFAL,GPS.Nav.PowerSave=disable,0,0
–
Sets
GPS
receiver
in
Command description
 This command applies to MAMBO2 devices with SiRF GPS receiver only.
This command is used to set the GPS receiver into the TrickePower mode. By default the GPS
receiver runs in continuous mode (full power). TricklePower is a power-saving mode characterized
by frequent, short power-on times and continuous GPS fixes. When this mode is activated and the
signal levels drop, the receiver returns to full power so that message output rates remain constant
even in difficult environments. This results in variable power savings but much more reliable
performance for a fixed output rate. Applications using this mode should give performance very
similar to full power, but with significant power savings in strong-signal conditions.
Parameter Description
<Mode>
Define the mode to be performed. It can be set to:
disable
Sets the GPS receiver back to full power mode.
enable
Sets the GPS receiver into the TricklePower (TP) mode.
<OnTimeMs>
Define the OnTime period in milliseconds the GPS receiver will stay in full power state until a
position solution is made and estimated to be reliable. Please note that, in harsh tracking
environments the receiver automatically switches to full power state to improve navigation
performance even if the defined OnTime has been expired. When the satellites are sorted
according to their signal strength, the fourth satellite determines if the transition to Standby
mode/hibernate state will occur or not. It can be set to a value between:
200 ... 900
OnTime period in milliseconds.
<LPInterval>
Define the complete interval of time in milliseconds the receiver will stay in full power and
Standby mode/hibernate state. The greater this value, the more power is saved.
It can be set to a value between:
1000 ... 10000
Interval of time in milliseconds intended for TricklePower (TP)
mode.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 103 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Notes
• It is recommended to use either 300 ms, 1000 ms or 400 ms, 2000 ms for optimum GPS
performance.
3.2.5.1.11
GPS.Nav.SetHeadingTolerance=<value> – Defines heading tolerance
Command syntax
$PFAL,GPS.Nav.SetHeadingTolerance=<value>
Examples
$PFAL,GPS.Nav.SetHeadingTolerance=22
Message description
This command can be used to define the tolerance for heading feature in degree. The tolerance is
stored into the non-volatile memory, and will automatically be used after the device boots up.
Each time the specified angle is exceeded, the event GPS.Nav.eChangeHeading occurs, and the
driving direction resets to zero. This state is checked each second and only when the actual vehicle
speed exceeds 3.6 km/h.
Figure below (Powered by Google Maps™) represents graphically the way points (marked by x) in
which a GPS.Nav.eChangeHeading event occurs whenever the device deviates the direction for
more then 22 degrees.
Parameter description
<value>
Define the angle in degrees to occur the corresponding event. It ranges from 0 ... 359.
Value
Meaning
0
Disables heading and its event.
1 ... 359
Enables heading and its event (see notes for more details about the
suggested value range).
Notes
• It is NOT RECOMMENDED to use values below 10 or above 320 degrees. The lower the
value, the more often the event occurs. Values above 180 degrees doesn't make much
sense, the suggested value is 45° (default).
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 104 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.5.1.12
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPS.Nav.Static=<value> – Enables/Disables Static Navigation
Command syntax
$PFAL,GPS.Nav.Static=<value>
Examples
$PFAL,GPS.Nav.Static=enable
Message description
 This command applies to MAMBO2 devices with SiRF GPS receiver only.
This command can be used to enable or disable the static navigation mode in a MAMBO2 with Sirf
GPS receiver. The steady state detection allows the navigating algorithms to decrease the noise in
the position output when the acceleration is below the threshold. This improves position accuracy
especially in stationary applications. By default, the "Static navigation" is turned off. When this
command is executed it updates automatically the settings of the DEVICE.GPS.NAVSTATIC
parameter.
Parameter description
<value>
Define whether to enable or not the static navigation mode on the MAMBO2 device. It can be
set to:
Value
Meaning
enable
Enables static navigation mode. Holds the current position as fixed when
the user is in a stationary mode.
disable
(Default) Disables static navigation mode.
3.2.5.1.13
GPS.Nav.SBAS=<value> – Enables/Disables SBAS operation
Command syntax
$PFAL,GPS.Nav.SBAS=<value>
Examples
$PFAL,GPS.Nav.SBAS=enable
Message description
 This command applies to MAMBO2 devices with SiRF GPS receiver only.
This command can be used to enable or disable the SBAS (Satellite Based Augmentation System)
operation in a MAMBO2 with Sirf GPS receiver. By default, the "SBAS operation" is turned on. A
GPS receiver with SBAS enabled will offer more accurate position. The reception of SBAS messages
requires that the device locks one of the GEO satellites with SateliteID ranging from 33 to 51.
These IDs (if available) are shown in the $GPGSV NMEA protocol. When this command is executed
it updates automatically the settings of the DEVICE.GPS.NAVSBAS parameter.
Parameter description
<value>
Define whether or not to enable the SBAS operation on the MAMBO2 device. It can be set to:
Value
Meaning
enable
Enables the SBAS operation.
disable
(Default) Disables the SBAS operation.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 105 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.5.1.14
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPS.Nav.TripCalc – Calculates the distance and elevation of a trip manually
Command syntax
$PFAL,GPS.Nav.TripCalc
Examples
$PFAL,GPS.Nav.TripCalc
Message description
This command is used to calculate manually the distance and elevation for your trip . The distance
and elevation are calculated from the trip-start location to the trip-stop destination. These values
are then stored in the dynamic entries (Tdistance) and (Theight) and can be sent out by Email,
TCP, SMS or through Serial port. In the prior versions, this calculation has been done automatically
by the system, but now starting from the firmware version 2.6.1 it must be done manually by the
user, for example using the alarms below:
$PFAL,Cnf.Set,AL98=Sys.Device.eStart:Sys.Timer1.Start=cyclic,20000
$PFAL,Cnf.Set,AL99=SYS.TIMER.e1&GPS.Nav.sSpeed>0:GPS.Nav.TripCalc
This is just an example to show how to calculate the distance and elevation for your trip manually.
Based on the alarms above, the calculation is performed using a timer and the navigation speed of
the device. The distance and elevation values are stored in the corresponding dynamic entries
(Tdistance) and (Theight) every 20 seconds if the device is moving.
Parameter description
None
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 106 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.5.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"History" command index
History data can be stored at non volatile memory inside the device. This data can be read out later to
retrieve GPS positions, speeds and additional information during the specified timespan.
Special data logging possibilities have been added to the basic „position/speed" history. These
functionalities allow to write history records even when there is no GPS fix valid.
As a general remark: writing GPS data into the history without a valid GPS fix should be avoided if each
history position needs to have a completely reliable time-stamp.
In areas with bad GPS signal strength or for data logging purposes, you might have to write history
records. Any records you write without a valid GPS fix are marked inside the history as „no fix". This
eases the identification of „totally reliable" data and those who aren’t. Please, find further notes to this
topic at the commands History.Read, History.Write, History.Setread and GPS.SaveLastValid.
Additional details to the history and especially to the binary history format can be found in an separate
application note "AppNotes_Transform_history_data.pdf".
Important Note:
3.2.5.2.1
-
Storing of data in the history is disabled as long as the remote update is in progress.
-
History will be enabled again, once the remote update has finished OR a serial update
(with option "erase whole flash") has been performed.
GPS.History.Write,<add_prot_to_memory>,<"text"> – Stores GPS position data in
history
Command syntax
$PFAL,GPS.History.Write,<add_prot_to_memory>,<"text">
Examples
$PFAL,GPS.History.Write,20,"enter_the_text_to_be stored"
$PFAL,GPS.History.Write,1,""
$PFAL,GPS.History.Write,0,""
$PFAL,GPS.History.Write,0,"Date: &(Date) Time: &(Time) Speed:&(Speed)"
Message description
This command is used to record a new entry (incl.: current position, speed, number of satellites and
time) in the history (currently there are only 3 MByte memory reserved for storing history data).
Dynamic entries can also be stored into the history.
 Warning: when writing data into the device history, please note that the MAMBO2B6/UXFS device can not write data in the history more frequently than one write per 5
seconds.
Parameter Description
<add_prot_to_memory>
Specify a hexadecimal number defining what information should be saved into the history.
This entry can be set to one or a combination of the following hex numbers:
Value
Meaning
0x00
Writes in the history the current GPS position of the device.
0x01
Not supported by MAMBO2-B6/UXFS.
0x02
Writes in the history the current state of the GSM (field strength, cell id,
area code, of incoming/outgoing SMS etc.).
0x04
Writes in the history the current operating mode of the system, GPRS, PPP,
TCP, system lifetime.
0x08
Reserved.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 107 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
0x10
Reserved.
0x20
Writes in the history the specified text from the <"text"> field (up to 99
characters available).
0x40
Writes the current state of the Geo-fence areas (inside or outside of a
marked area)
0x80
reserved
<"text">
Wrapped in quotation marks, specify a string, up to 255 characters, containing additional
information to the stored data. If no additional information to the record are needed, then
leave this field left empty "".
If it is required to write also system information (dynamic entry) at certain times the following
syntax of the <"text"> is also possible:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Each dynamic entry is separated by ampersand "&" without spaces and enclosed in
parentheses "( )".
For example:
$PFAL,TCP.Client.Send,8,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
Dynamic entries are listed in chapter 7.2 page 321.
 Warning: Note that this would extremely increase the size of history entries, which
means that the history gets filled much faster and therefore needs to be read out more
frequently.
Notes
• Entries can be written without having a valid GPS fix. In such a case the entries may store
the user messages or other additional information.
• If there is no GPS-fix currently available and the device stores a record in the history, then
this will be „invalid". However, each entry can store:
➢ The internal last valid position (if available)
➢ Or the last stored valid position (if available)
➢ Or an empty data "ECEF:0,0,0"
• When there is no GPS-fix currently available, the most recent available timestamp is used:
➢ From Last valid position if it is the newest timestamp of the system
➢ Or from locally shown RMC if this is the most recent time
➢ Else internal time is used that means the date can start from 06.01.1980.
-> Only records written with a valid GPS fix show an absolutely reliable timestamp
when being read out later.
• A combination of protocols can be stored in the history at once by specifying the sum of
the hex value for each protocol accordingly, for example:
−
The hex value 42 means: GSM + Geofence states will be stored together with current
location of the device at once.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 108 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.5.2.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPS.History.Clear – Clears history
Command syntax
$PFAL,GPS.History.Clear
Examples
$PFAL,GPS.History.Clear
Message description
This command is used to clear completely the history. The command $PFAL,GPS.History.Write will
not be executed, while the history is being cleared. When the clear history completes the device
will output:
$<GPS.History.Clear>
$history cleared (duration: 13,996 seconds)
$SUCCESS
Parameter Description
None
3.2.5.2.3
GPS.History.GetStart – Returns oldest date stored in history
Command syntax
$PFAL,GPS.History.GetStart
Examples
$PFAL,GPS.History.GetStart
Message description
This command is used to read out the oldest date and time stored in history data. The retrieved
time is in UTC Time. If the history is empty the device will output:
$<GPS.History.GetStart>
$history is empty (no valid history entry found)
$Error to execute command type GPS
$ERROR
Parameter Description
None
3.2.5.2.4
Command syntax
GPS.History.SetRead[,<s_date>,<s_time>-<e_date><e_time>] – Prepares selected
history records for download
$PFAL,GPS.History.SetRead,all
$PFAL,GPS.History.SetRead,<s_date>,<s_time>-<e_date>,<e_time>
$PFAL,GPS.History.SetRead,all //Selects all history records stored in the history
Examples
$PFAL,GPS.History.SetRead,14.6.2008,10:05:20-14.6.2008,12:06:16
//Selects the history records
that have be recorded on 14.6.2008 from 10:05:20 to 12:06:16
Message description
This command is used to select the history entries for download either completely or partly by
specifying a start and end date for the next use of the GPS.History.Read command. Only history
records being within the specified timespan will be read out. Please, read „Notes" below for more
details.
Parameter Description
<s_date>
Specify the start date in format: DD.MM.YYYY
Format
Meaning/Value
DD
Represents the day as a number (1 - 31)
MM
Represents the month as a number (1 - 12).
YYYY
Represents the year as a four-digit number (1900 - 9999).
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 109 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
<s_time>
Specify the start time in format: HH:MM:SS
Format
Meaning/Value
HH
Represents the hour (0 - 23).
MM
Represents the minute (0 - 59).
SS
Represents the second (0 - 59).
<e_date>
Specify the end date in format: DD.MM.YYYY
Format
Meaning/Value
DD
Represents the day as a number (1 - 31)
MM
Represents the month as a number (1 - 12).
YYYY
Represents the year as a four-digit number (1900 - 9999).
<e_time>
Specify the end time in format: HH:MM:SS
Format
Meaning/Value
HH
Represents the hour (0 - 23).
MM
Represents the minute (0 - 59).
SS
Represents the second (0 - 59).
Notes
• This command returns the estimated space used for the history. This number shouldn’t be
used to specify or define the amount of bytes read out by History.Read. The available
amount of bytes being read out is returned by History.Read itself.
• The start and stop times should be specified in UTC time rather than local time, as the
stored records in the history are always stored in UTC time.
• In order to read out history by date/timespan, be sure that the time is always up to date
when storing the history records !!
i.e. assure the following:
- You have always stored the last valid position right before shutting down the device,
and not write history entries between saving and shutting down to assure consistent
history times.
- Each new record you store has a future time/date compared to the the previous
written record (i.e. it may never happen that a history record contains a time which
is in the past compared to a record written before).
if one condition of the above is not fulfilled, a History.SetRead by date/timespan might
not select all data you want to read.
This happen if you do the following:
1. Store a last valid position,
2. Restart the device,
3. Write a record before having a valid GPS fix,
4. Restart the device again (which means internal time is set to the old „last
valid position" time - from the fist step),
5. Write a record before having a GPS fix.
Doing so, 2 history entries are written which have exactly the same time and date.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 110 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
You can still read out such history files – but JUST with History.SetRead,all, as a date/timespan
based search might return not all or just a part of the desired records if they exist multiple
times inside history.
3.2.5.2.5
GPS.History.Read=[<format>] – Downloads history partly
Command syntax
$PFAL,GPS.History.Read,fmt=[<format>]
Examples
$PFAL,GPS.History.Read
$PFAL,GPS.History.Read,fmt=txt
Message description
This command is used to read out the stored history contents. By default, the format of the data
being received is binary. Binary data has a length indicator that shows how many bytes have been
read out. Currently there is a maximum of 512 Bytes which can be read out each time the read
command is sent to the MAMBO2-B6/UXFS device.
If the part of the history you are going to read contains more than 512 Bytes of data, then you
should send this command several times to the device until the total history read completes. Each
command will return 512 Byte packet of history data. The last received packet will return the text
"readout completed" instead of "SUCCESS". For detailed information, please refer to the
document „AppNotes_Transform_history_data.pdf".
Parameter Description
[<format>]
Optional setting. Define in what format do you prefer to download the history entries that are
stored in the device. If this parameter is omitted then the history data will be downloaded in
binary format. It can be defined to:
Value
Meaning
bin
Download the history entries in binary format (default) .
txt
Download the history entries in a special textual format. A brief
description of this format can be found in the next sub-chapter.
rmc
Generates an RMC protocol for each history entry .
Notes
• Note, the maximum number of bytes that can be downloaded at once is predefined to 512
bytes.
• When downloading a part of the history data, please specify the start and end date/time
in UTC Time, otherwise you will download other entries from the history.
• Advantage: Depending on the amount of the history data available in the device, the
readout of the complete history may take much time. Within this timespan no PFAL
commands could be executed. Splitting history data to several packets allows the server to
execute PFAL commands even when a history readout has been started. Reading history
packets can be continued whenever desired (until the device is shut down or performed a
reset).
• A new executed command „History.SetRead" will reset the current process of reading out
a history – so it is recommended to gain a user who reads out history exclusive access to
the device.
• Keep in mind, that binary history data first starts with a length info (the first 2 bytes),
indicating how many bytes of history data follow. The first 2 bytes are not included in the
length of data !
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 111 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3.2.5.2.5.1 Reading history records in textual format
Each history entry is reported within a single line with a format given below:
Syntax
$<history_entry_standard>,<history_entry_extension><CRLF>
Example
$113.10.2006,13:26.56,1,03,50.673325,10.980685,600.9,100,0:10010110.10011110
Format
Example
Description
$
$
Start of records
dd.mm.yyyy
13.10.2006
Date: dd day, mm month, yyyy year separated by dots.
hh:mm:ss
13:26.56
Time: hh hours, mm minutes, ss seconds separated by colons.
x
1
xx
03
GPS position validity:
0: GPS fix invalid
1: GPS fix valid
Number of satellites in view (0 to 15)
dd.mmmmmm
50.673325
Latitude, a double value in decimal degrees format.
dd.mmmmmm
10.980685
Longitude, a double value in decimal degrees format.
dd.m
600.9
xxx
100
Altitude, an approximate height value (0 … 8000) above sea level in meter
format.
Speed, an integer (0 … 225) representing the speed value over the ground in
meter/second format
<history_entry_standard>
<date>,<time>,<fix>,<minsats>,<lat>,<lon>,<alt>,<speed>
<history_entry_extention>
<ext_id>:<data>
<ext1>,<ext2>, ….,<extn>
0:10010110.10011110
<CR><LF>
It is an optional parameter and is added only if extensions exist.
Extensions are sorted before output, so it is assured that e.g. extension
containing IN and OUT state will come first, before all other extensions.
A complete set of extensions, separated by commas, is shown in the table
8.1 below (sorted: the upper entry comes first).
End of message termination
Table 8:
Reading history records in textual format.
<ext_id>:<data>
<ext>
<ext_id>
<data>
Example
Description
0
<IN>.<OUT>
1
<fieldstrength>.<area_code
>.<cell_id>.<SMS_in>.<SMS 120.5518.4caa.10.9
_out>
2
<GPRS>.<PPP>.<TCP>.<Mai
n>.<Lifetime>
2:1.2.3.4.20000
3
-
-
Separated by dots, it shows the IN and OUT states (not for
MAMBO2-B6/UXFS).
IN
e.g. 00000000
OUT
e.g. 00000000
Separated by dots, it shows the current GSM state:
<fieldstrength>
GSM field strength (0 to 31;
99=unknown)
<area code>
area/country code of GSM operator
<cell_id>
GSM cell ID
<SMS_IN> Incoming SMS number
<SMS_out>
Outgoing SMS number
Separated by dots, it shows the current system state:
<GPRS>
current GPRS state
<PPP>
current PPP state
<TCP>
current TCP state
<Main>
current main state
<lifetime>
current time since the device started (in
milliseconds)
States mentioned above are not further documented. They should
be used for debugging purposes only (i.e. to report when a system
state changes or how the system state was at a specific time). This
information might be useful and should be sent within support
requests.
Alarm event (not yet implemented)
4
-
-
Reserved
0:10010110.10011110
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 112 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
"<user_specified_text>"
5
6
<areas_h>.<areas_l>
- FIRMWARE REVISION 2.8.0 -
5:"your entered text"
6:2000.00FC
7
DOCUMENT VERSION 3.7.0
Wrapped in quotation marks, it shows the user message.
<user specified text> It can be either a simply text
or outputs of the dynamic
protocols.
Separated by dot, it shows the area states (being inside or outside
of an area)
<areas_h>
Hexadecimal value of area 16..31
(area16 is the least significant bit)
<areas_l>
Hexadecimal value of area 0..15 (area0
is the least significant bit)
It is almost the same syntax as in the GPAREA protocol.
reserved
<CRLF>
Table 8.1:
A complete set of extensions.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 113 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3.2.5.2.5.2 Further notes for converting history data with special remark to data logging features
If a stored history record has „no GPS fix", its position should be ignored for any navigation (this
position is invalid, and if it is a differential record, its relative position will be 0 for dx, dy, dz) .
Furthermore, the time in this record is invalid GPS time.
This time is usually reliable in the following case:
The device has had a GPS fix after startup and lost it due to bad GPS coverage. The internal
time for the stored record is quite accurate (± a few seconds for a long time span).
This time is not reliable in the following case:
The device has had no GPS fix after startup. Only the stored LastValid position (and its time)
could be used to initialize the internal clock.
MAMBO2-B6/UXFS uses this time (LastValid) and increments it as long as the device has no
valid GPS time. However, the internal time can be in the past (depending on how long the
device has been switched off after saving the LastValidPosition for the last time).
History records created with „last valid" times are ordered correctly – so you can assume
which record happened before/after another one in the past (allows event /data logging).
Furthermore, time differences between single records are also correctly shown for a session:
In order to distinguish which records belong to a „session" in the past (device started, wrote
history records and was sent to sleep later), you can do the following two things:
1. Write a record containing special user data right before saving the last valid position and
sending the device to sleep. Whenever, you read out this user data later you know when
the device was sent to sleep (your session ended).
2. As a general hint, whenever a new „full record" is written in the history, the device
probably performs a restart.
- if there is a time gap between the last differential record and the new full record,
the device has been sleeping (this time gap shows how long the device has been
sleeping/shut off)
- if there is no time gap in between, the device was not sleeping, which means that
the time differences between all records of this session are absolutely reliable.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 114 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.5.2.6
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPS.History.Push,<msg_output>,[<format>] – Downloads history completely
Command syntax
$PFAL,GPS.History.Push,<msg_output>,[<format>]
Examples
$PFAL,GPS.History.Push,Serial
$PFAL,GPS.History.Push,TCP,fmt=txt
Message description
This command is used to download the selected history records at once. Push creates
automatically several packets of data. Just one command has to be executed in order to read the
history completely (or a part of it). A regular answer is created for this Push command. After this,
the command History.Read will be called periodically until the readout finishes. During the Pushprocess, no PFAL commands or low priority alarm actions will be executed.
Parameter Description
<msg_output>
Optional setting. Define the channel in which you want to start the download. It can be set to:
Value
Meaning
Serial
Sends history data to the serial port (Bluetooth).
USB
Sends history data to the USB port.
CSD
Sends history data to an established CSD data call.
TCP.Client
Sends history data to a TCP server (the device should be connected to a
server when calling this command).
TCP
Sends history data to a TCP port (the device should be connected to a
server when calling this command) – for backward compatibility.
[<format>]
Optional setting. If this parameter is omitted, then the history data is retrieved in binary
format. Define in which format the history data should be downloaded. It can be set to:
Value
Meaning
fmt=bin
Downloads history data in binary format (default) .
fmt=txt
Downloads history data in a special textual format. A brief description of
this format is available in Table 8 and Table 8.1.
fmt=rmc
Generates an RMC protocol for each history entry. NMEA checksum for
each RMC protocol can be enabled by enabling the checksums within the
DEVICE.PFAL.SEND.FORMAT parameter.
Notes
• Advantage: No multiple Read commands have to be sent.
• Disadvantage: During the history readout process, no PFAL commands or low priority
alarm actions will be executed. It is also not possible to e.g. accept a voice call or
send/receive SMS.
• The answers of this command are 100% compatible to answers generated from
History.Read.
• Please, see also History.Read command notes for more information.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 115 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.5.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Geofence" command index
What are geofences and what are they used for, refer to the chapter 3.3.14.11, page 252.
Geofencing are used to monitor the entries and exits of a tracking device from geographic boundary
and to alert a message when the boundary violations are detected. Additionally a park area can be
specified which might launch certain alarm actions if the device moves outside the defined range (i.e.
thief alarm).
 Note: If you are going to use the park feature, please do NOT use the GF.0/area0
regular geofence as it is intended for parking feature. If commands
Park.Set/Park.Remove are not used for park feature, then you can use the GF0/area0
as a regular Geofence/area.
3.2.5.3.1
GPS.Geofence.Park.Set – Places and activates parking area
Command syntax
$PFAL,GPS.Geofence.Park.Set
Examples
$PFAL,GPS.Geofence.Park.Set
Message description
This command is used to activate a parking area (GF.0). It places the MAMBO2-B6/UXFS device
into a circular park area, where the current position (including Latitude and Longitude) of the
MAMBO2-B6/UXFS is the center of circle and the user specified <park_radius> value (see
GF.CONFIG parameter) is the radius, in meter, of the circular area. This Geofence is automatically
attached to area0.
Parameter Description
None
Notes
• The events GF.e0=inside and AREA.e0=inside are usually occurred from the
$PFAL,GPS.Geofence.Park.Set.. Both events (GPS.GF.e0=inside and GPS.AREA.e0=inside)
can be used to confirm the proper activation of the park area.
• Usually Park.Set will cause the event eGF.0=inside and eAREA.0=inside. Both events can
be used to confirm the proper activation of the park Geofence.
• This command works also if the device has an invalid GPS position. In this case the last
valid position will be used. Please not that this might lead to an immediate alarm in case
the device gets a valid GPS-fix. This happens if the device was moving without a fix and the
park area is set.
• If the MAMBO2-B6/UXFS device has got a GPS-fix and it is valid, the GPS.GF.e0=inside and
GPS.AREA.e0=inside will occur, which indicates that this park area is properly set up.
• To deactivate the park condition (without occurring the event GPS.AREA.e0=outside), use
the command $PFAL,GPS.Geofence.Park.Remove.
• The Geofence settings will be also written in the Flash memory, so even when the device
performs a reset the park area will remain active until manually deactivated. When a
system restart occurs, and the park area remains activated, the events GPS.GF.e0=inside
and GPS.AREA.e0=inside are occurred again as soon as the MAMBO2-B6/UXFS receives a
valid GPS fix.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 116 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.5.3.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPS.Geofence.Park.Remove– Disables an activated park area
Command syntax
$PFAL,GPS.Geofence.Park.Remove
Examples
$PFAL,GPS.Geofence.Park.Remove
Message description
This command is used to deactivate an activated park area (GF.0).
Parameter Description
None
Notes
• The event GPS.GF.e0=inside and GPS.AREA.e0=inside are no longer available.
3.2.5.3.3
GPS.Geofence.GeoState,<geo_id>– Returns Geofences state
Command syntax
$PFAL,GPS.Geofence.GeoState,<geo_ID>
Examples
$PFAL,GPS.Geofence.GeoState,0
Message description
This command is used to read out whether the device is inside or outside of the specified Geofence
(). If it is configured, the name of the Geofence will also be shown. Currently 100 Geofences are
supported by the MAMBO2-B6/UXFS device.
Parameter Description
<geo_ID>
Specify a number for the geofence from 0 to 99 to get its state.
3.2.5.3.4
GPS.Geofence.AreaState,<area_id>– Read areas state
Command syntax
$PFAL,GPS.Geofence.AreaState,<area_id>
Examples
$PFAL,GPS.Geofence.AreaState,0
Message description
This command is used to read out the state (whether the device is inside or outside) of the specified
area. If configured, the name of the area will be also shown. Up to 32 areas can be defined (index 0
– 31).
Parameter Description
<area_id>
Number from 0 to 31 which specifies the areas to be read out.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 117 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.5.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Trip" command index
Both commands below can be used to start and stop a trip. You can also start a trip by selecting the
item "Trip Start/Stop" on the Trip-view on the Standard GUI (as reference use figure added in the
chapter "DISP.VIEWS"
3.2.5.4.1
GPS.Trip.Start – Starts a trip
Command syntax
$PFAL,GPS.Trip.Start
Examples
$PFAL,GPS.Trip.Start
Message description
This command is used to start a trip. When this command is executed, the event Disp.Trip.e=Start
occurs and the item "Trip Started" on Trip-view of the MAMBO2-B6/UXFS change to "TRIP STOP".
Parameter Description
None
3.2.5.4.2
GPS.Trip.Stop – Stops a started trip
Command syntax
$PFAL,GPS.Trip.Stop
Examples
$PFAL,GPS.Trip.Stop
Message description
This command is used to stop a started trip. When this command is executed, the event
Disp.Trip.e=stop occurs and the item "Trip Started" on Trip-view of the MAMBO2-B6/UXFS change
to "TRIP START".
Parameter Description
None
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 118 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"GSM" command type
3.2.6.1
3.2.6.1.1
"GSM" general command indices
GSM.PIN=<"pin"> - Enters PIN number of used SIM card
Command syntax
$PFAL,GSM.PIN=<"pin">
Examples
$PFAL,GSM.PIN="1111"
Message description
This command is used to enter the PIN code of the used SIM card in the MAMBO2-B6/UXFS
device. If SIM PIN has already been entered and the target device is already registered into the
GSM network, no further entry needed and the device returns error. See also the description in
chapter 3.3.11.1, page 229 for more details.
Parameter Description
<"pin">
Wrapped in quotation marks, specify the PIN number of the used SIM card.
3.2.6.1.2
Command syntax
Examples
GSM.PUK=<"puk">,<"pin"> - Enters PUK and PIN numbers
$PFAL,GSM.PUK=<"puk">,<"pin">
$PFAL,GSM.PUK="22222222","1111"
Message description
This command is used to unblock the SIM card by entering the associated PUK code.
Parameter Description
<"puk">
Entering incorrect PIN three times, the SIM card will be blocked. To unblock it, you have to
enter the PUK code of the used SIM card, wrapped in quotation marks (" "). After ten failed
attempts to enter the PUK, the SIM card will be invalidated and no longer operable. In such a
case, the card needs to be replaced. PIN consists of 4 to 8 digits; PUK is an 8-digit code only.
<"pin">
Wrapped in quotation marks (" ") specify the PUK of the used SIM card.
3.2.6.1.3
Command syntax
Examples
GSM.IMEI - Gets product serial number
$PFAL,GSM.IMEI
$PFAL,GSM.IMEI
Message description
This command is used to get the product serial identification number.
Parameter Description
None
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 119 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.1.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.SIMID – Gets ID of SIM Card
Command syntax
$PFAL,GSM.SIMID
Examples
$PFAL,GSM.SIMID
Message description
This command is used to get the ID of the used SIM card.
Parameter Description
None
3.2.6.1.5
GSM.OwnNumber– Gets own phone number
Command syntax
$PFAL,GSM.OwnNumber
Examples
$PFAL,GSM.OwnNumber
Message description
This command is used to get your own phone number.
Parameter Description
None
3.2.6.1.6
GSM.Balance – Returns account balance of an used prepaid SIM card
Command syntax
$PFAL,GSM.Balance
Examples
$PFAL,GSM.Balance
Message description
This command is used to request the amount of money and the validity period of your account
balance only for prepaid SIM cards (if provider of your SIM Card supports this function).
Parameter Description
None
Notes
• When the user sends this command to the device, the number "ATD*100#" will
automatically be dialled. This number is only for the E-plus German network operator
available. Other countries may have other dial numbers for checking the account balance.
3.2.6.1.7
GSM.USSD,<"ussd_cmd">,<timeout> – Performs an USSD call and return its answer
Command syntax
$PFAL,GSM.USSD,<"ussd_cmd">,<timeout>
Examples
$PFAL,GSM.USSD," *100#",10
Message description
This command is used to perform an USSD call and get its answer.
Parameter Description
None
<"ussd_cmd">
Specify the USSD call command (i.e. *100# to query a SIM account balance)
<timeout>
Specify the time in seconds to wait for the USSD answer.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 120 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.1.8
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.MCC – Gets mobile country code
Command syntax
$PFAL,GSM.MCC
Examples
$PFAL,GSM.MCC
Message description
This command is used to queries the current mobile country code information of the operator
where the device is registered to.
Parameter Description
None
Notes
• A valid operator is required to read out the MMC.
3.2.6.1.9
GSM.Band=<band> – Defines GSM band
Command syntax
$PFAL,GSM.Band=<band>
Examples
$PFAL,GSM.Band=Eur
Message description
This command is used to specify the GSM band the device should operate. The main purpose of
this command is to speed up the GSM registration when the correct GSM band is already
specified. The specified Band will be stored into non-volatile memory and used whenever the
device starts up. However, the MAMBO2-B6/UXFS device restarts the GSM engine when receiving
this command. This command should be entered just one time. However, the device will change
its bands automatically, if it can not find operator in the currently selected band.
Parameter Description
<band>
Specify the frequency band in which the GSM modem should operate. It can be set to:
Value
Meaning
Eur
900Mhz+1800Mhz (European GSM band)
Misc1
900Mhz+1900Mhz (only for some countries)
Misc2
850Mhz+1800Mhz (only for some countries)
USA
850Mhz+1900Mhz (USA - GSM band)
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 121 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.2
3.2.6.2.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Voice Call" command index
GSM.VoiceCall.Dial,<"p_number"> - Makes voice calls
Command syntax
$PFAL,GSM.VoiceCall.Dial,<"p_number">
Examples
$PFAL,GSM.VoiceCall.Dial,"+4912345678"
Message description
This command is used to make an outgoing voice call.
Parameter Description
<"p_number">
Wrapped in quotation marks (" "), specify the phone number you want to dial. To originate a
outgoing voice call, the <"p_number"> should include the area code, country code and phone
number as shown in example above.
3.2.6.2.2
GSM.VoiceCall.Accept - Accepts an incoming voice call
Command syntax
$PFAL,GSM.VoiceCall.Accept
Examples
$PFAL,GSM.VoiceCall.Accept
Message description
This command is used to accept an incoming voice call, which is usually indicated by an incoming
ring event.
Parameter Description
None
Notes
• No GSM voice calls are accepted while the MAMBO2-B6/UXFS is trying to attach to the
GPRS. During this time which may take approx. 10-20 seconds, the device is unreachable
(this is GSM related feature). Therefore, it is wise not to perform a GPRS attach/detach in
such short periods.
3.2.6.2.3
GSM.VoiceCall.Hangup – Ends an active voice call
Command syntax
$PFAL,GSM.VoiceCall.Hangup
Examples
$PFAL,GSM.VoiceCall.Hangup
Message description
This command is used to end an established voice call.
Parameter Description
None
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 122 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Audio" command index
This chapter contains all audio related GSM settings. Up to 5 audio profiles can be independently
configured, selected and stored into the non-volatile memory, but only one profile can then be selected
and used. The default profile is shown by using the command "PFAL,GSM.Audio.ShowProfile=0".
3.2.6.3.1
Command syntax
Examples
GSM.Audio.ActiveProfile=<profile> - Selects and activates audio profiles
$PFAL,GSM.Audio.ActiveProfile=<profile>
$PFAL,GSM.Audio.ActiveProfile,<profile>
$PFAL,GSM.Audio.ActiveProfile=0
$PFAL,GSM.Audio.ActiveProfile,0
$audio profile 1 enabled
Responses
$SUCCESS
Message description
This command is used to select and activate an audio profile.
Parameter Description
<profile>
It can be set to a value from 0 ... 4. It is not possible to select an unconfigured and unsaved
audio profile.
Value
Meaning
0
Loads the user configured profile.
1
Loads the profile for internal audio.
2
Loads the profile for hands free audio.
3
Loads the profile for headset audio.
4
Loads the profile for Bluetooth audio.
Notes
• If no audio profiles have been saved, default audio settings will be used after system start
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 123 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.3.2
Command syntax
Examples
Responses
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.Audio.ShowProfile=<profile> - Shows audio profile details
$PFAL,GSM.Audio.ShowProfile=<profile>
$PFAL,GSM.Audio.ShowProfile,<profile>
$PFAL,GSM.Audio.ShowProfile=0
$PFAL,GSM.Audio.ShowProfile,0
$audio profile[1]: currently active
$echo cancel: 1
$sidetone: 0
$speaker muted: 0
$speaker gain: 7
$microphone muted: 0
$handsfree mic gain: 5
$handset mic gain: 5
$audio ringer path: 0
$audio path: 1
$audio mode: 0
$SUCCESS
Message description
This command is used to get all settings of the specified audio profile. Shows whether this profile
is currently active (used) or inactive.
Parameter Description
<profile>
Specify a profile index to be shown. It can be set to a value from 0..4.
Notes
• Default audio settings are shown after first startup, if no audio settings have been
modified
3.2.6.3.3
Command syntax
Examples
GSM.Audio.SaveProfileAs=<profile> - Saves audio settings to a profile
$PFAL,GSM.Audio.SaveProfileAs=<profile>
$PFAL,GSM.Audio.SaveProfileAs,<profile>
$PFAL,GSM.Audio.SaveProfileAs=0
$PFAL,GSM.Audio.SaveProfileAs,0
Message description
This command is used to store the currently used audio settings to a profile.
Parameter Description
<profile>
It can be set to a value from 0..4.
Notes
• It is possible to store default audio settings to a profile too (this might be helpful if several
profiles have to be used, because it is not possible to switch to an "empty" profile)
• This command also changes the currently active profile setting – however if a profile is
stored as a profile 3, the current active profile will be 3.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 124 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.3.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.Audio.DeleteProfile=<profile> - Deletes stored profiles
$PFAL,GSM.Audio.DeleteProfile=<profile>
$PFAL,GSM.Audio.DeleteProfile,<profile>
$PFAL,GSM.Audio.DeleteProfile=0
$PFAL,GSM.Audio.DeleteProfile,0
Command syntax
Examples
Message description
This command is used to erase a stored profile.
Parameter Description
<profile>
It can be set to a value from 0..4.
Notes
• This command does NOT affect the currently active audio settings
• It also doesn't change the currently used profile !
• It can erase the currently active profile:
 En empty profile is selected in this case. After next system start, default audio settings would be
used if no other valid profile has been activated.
3.2.6.3.5
GSM.Audio.EchoCancel=<value> - Activates/deactivates echo cancellation
Command syntax
$PFAL,GSM.Audio.EchoCancel=<value>
Examples
$PFAL,GSM.Audio.EchoCancel=0
Message description
This command is used to activate or deactivate echo cancellation on a handsfree
speaker/microphone.
Parameter Description
<value>
It can be set to a value as follow:
Value
Meaning
0
Deactivates echo cancellation.
1
Activates echo cancellation (default)
Notes
• This command does NOT affect stored audio profile settings.
• In order to permanently keep selected audio settings, the settings must be stored to an
audio profile – else they are discarded after next system start.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 125 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.3.6
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.Audio.SideTone=<value> - Enables/disables side tone output
Command syntax
$PFAL,GSM.Audio.SideTone=<value>
Examples
$PFAL,GSM.Audio.SideTone=0
Message description
This command is used to disable the side tone output.
Parameter Description
<value>
It can be set to a value as follow:
Value
Meaning
0
Disables side tones (default)
1
Enables side tones
Notes
• This command does NOT affect stored audio profile settings.
• In order to permanently keep selected audio settings, the settings must be stored to an
audio profile – else they are discarded after next system start.
3.2.6.3.7
GSM.Audio.SpeakerMute=<value> - Mutes/unmutes speaker output
Command syntax
$PFAL,GSM.Audio.SpeakerMute=<value>
Examples
$PFAL,GSM.Audio.SpeakerMute=0
Message description
This command is used to activate or deactivate the speaker output.
Parameter Description
<value>
It can be set to a value as follow:
Value
Meaning
0
Unmutes (activates) the speaker output (default)
1
Mutes (deactivates) the speaker output
Notes
• This command does NOT affect stored audio profile settings.
• In order to permanently keep selected audio settings, the settings must be stored to an
audio profile – else they are discarded after next system start.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 126 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.3.8
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.Audio.SpeakerGain=<value>- Sets speaker gain (volume)
Command syntax
$PFAL,GSM.Audio.SpeakerGain=<value>
Examples
$PFAL,GSM.Audio.SpeakerGain=0
Message description
This command is used to set the speaker gain (loudness).
Parameter Description
<value>
It can be set to a value as follow:
Value
Meaning
0...14
Volume of the speaker (maximum might depends on GSM version).
Default is 4.
Notes
• This command does NOT affect stored audio profile settings.
• In order to permanently keep selected audio settings, the settings must be stored to an
audio profile – else they are discarded after next system start.
3.2.6.3.9
GSM.Audio.MicrophoneMute=<value> - Mutes/unmutes microphone’s signal
Command syntax
$PFAL,GSM.Audio.MicrophoneMute=<value>
Examples
$PFAL,GSM.Audio.MicrophoneMute=0
Message description
This command is used to activate or deactivate microphone' signal.
Parameter Description
<value>
It can be set to a value as follow:
Value
Meaning
0
Unmutes (activates) the microphone (default)
1
Mutes (deactivates) the microphone
Notes
• This command does NOT affect stored audio profile settings.
• In order to permanently keep selected audio settings, the settings must be stored to an
audio profile – else they are discarded after next system start.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 127 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.3.10
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.Audio.HandsfreeMicroGain=<value> - Sets microphone gain (volume) on
hands-free device
Command syntax
$PFAL,GSM.Audio.HandsfreeMicroGain=<value>
Examples
$PFAL,GSM.Audio.HandsfreeMicroGain=0
Message description
This command is used to set the microphone gain (loudness) on the handsfree microphone. In this
case, Handset microphone setting should be used.
Parameter Description
<value>
It can be set to a value as follow:
Value
Meaning
0...7
Volume of the microphone (maximum might depend on GSM version).
Default is 3.
Notes
• This command does NOT affect stored audio profile settings.
• In order to permanently keep selected audio settings, the settings must be stored to an
audio profile – else they are discarded after next system start
3.2.6.3.11
GSM.Audio.HandsetMicroGain=<value> - Sets microphone gain (volume) on the
handset microphone
Command syntax
$PFAL,GSM.Audio.HandsetMicroGain=<value>
Examples
$PFAL,GSM.Audio.HandsetMicroGain=0
Message description
This command is used to set the microphone gain (loudness) on the handset microphone.
Parameter Description
<value>
It can be set to a value as follow:
Value
0...7
Meaning
Volume of the handset microphone (maximum might depend on GSM
version). Default is 3.
Notes
• This command does NOT affect stored audio profile settings.
• In order to permanently keep selected audio settings, the settings must be stored to an
audio profile – else they are discarded after next system start
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 128 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.3.12
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.Audio.AudioRingPath=<value>- Chooses path for passing ring signals
Command syntax
$PFAL,GSM.Audio.AudioRingPath=<value>
Examples
$PFAL,GSM.Audio.AudioRingPath=0
Message description
This command is used to select the path to which ring signals (i.e. voice input/output) are
directed.
Parameter Description
<value>
It can be set to a value as follow:
Value
Meaning
0
Automatic path selection (depending on used path)
1
Internal speaker and microphone path
2
Bluetooth audio path
3
internal (not used) audio path
Notes
• This command does NOT affect stored audio profile settings.
• In order to permanently keep selected audio settings, the settings must be stored to an
audio profile – else they are discarded after next system start.
3.2.6.3.13
GSM.Audio.RingTone=<value> - Selects incoming call ringtone
Command syntax
$PFAL,GSM.Audio.RingTone=<value>
Examples
$PFAL,GSM.Audio.RingTone=0
Message description
This command is used to select a ring tone when an incoming call is detected.
Parameter Description
<value>
Type of ring tone. You have a choice of 33 different ring tones. All will be played on the
speaker.
Value
0..32
Meaning
Sequence 0...32
Notes
• This command does NOT affect stored audio profile settings.
• In order to permanently keep selected audio settings, the settings must be stored to an
audio profile – else they are discarded after next system start.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 129 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.3.14
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.Audio.RingGain=<value> - Sets ringtone volume
Command syntax
$PFAL,GSM.Audio.RingGain=<value>
Examples
$PFAL,GSM.Audio.RingGain=0
Message description
This command is used to set the gain (loudness) for ring tones. Note that the gain will be adjusted
at the next incoming call. It doesn't affect a current call.
Parameter Description
<value>
To adjust the ringtone volume, set one of the desired ringtone value given below.
Value
Meaning
0..4
Ringer gain (volume). Default is 3.
Notes
• This command does NOT affect stored audio profile settings.
• In order to permanently keep the selected audio settings, the settings must be stored to an
audio profile – else they are discarded after next system start.
3.2.6.3.15
GSM.Audio.AudioPath=<value> - Chooses audio path
Command syntax
$PFAL,GSM.Audio.AudioPath=<value>
Examples
$PFAL,GSM.Audio.AudioPath=0
Message description
This command is used to select the path for regular audio signals (i.e. Voice ).
Parameter Description
<value>
It can be set to a value as follow:
Value
Meaning
0
Automatic path selection (depending on used path).
1
Internal speaker and microphone path,
2
Bluetooth audio path,
3
Internal (not used) audio path.
Notes
• This command does NOT affect stored audio profile settings.
• In order to permanently keep selected audio settings, the settings must be stored to an
audio profile – else they are discarded after next system start
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 130 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.3.16
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.Audio.SoundMode=<value> - Chooses device's global sound mode
Command syntax
$PFAL,GSM.Audio.SoundMode=<value>
Examples
$PFAL,GSM.Audio.SoundMode=0
Message description
This command is used to select a global sound mode for the device.
Parameter Description
<value>
It can be set to a value as follow:
Value
Meaning
0
Normal - signals and voice are enabled (default).
1
Silent – just alarm sounds are generated.
2
Stealth – no sound is generated.
Notes
• The sound mode could not be changed during an initiated voice call.
• This command does NOT affect stored audio profile settings.
• In order to permanently keep selected audio settings, the settings must be stored to an
audio profile – else they are discarded after next system start.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 131 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"SMS" command index
3.2.6.4.1
GSM.SMS.Send,<"p_number">,<protocols>,<"text"> - Sends messages and protocols
via SMS
Command syntax
$PFAL,GSM.SMS.Send,<"p_number">,<protocols>,<"text">
$PFAL,GSM.SMS.Send,<"p_number">,<protocols>,<"text&(entry)">
Examples
$PFAL,GSM.SMS.Send,"+491111111",8,"MAMBO2-B6/UXFS"
$PFAL,GSM.SMS.Send,"+491111111",0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
$PFAL,GSM.SMS.Send,"&(SMSNumber)",0,"Auto SMS Reply&(SMSNumber)"
Message description
This command is used to transmit NMEA and user messages including dynamic entries to your
specified phone number via SMS. The format the device will use to transmit your specified data is
DEVICE.PFAL.SEND.FORMAT configuration-dependent. Such information could not be transmit only
via SMS, but also via an established GSM Data call and TCP. How to transmit messages via GSM
Data call or TCP Please read the chapters "Sends alarm messages and protocols via an established
data call" and "Sends alarm messages and protocols via TCP to an internet server".
Parameter Description
<"p_number">
Wrapped in quotation marks (""), specify the phone number max 30 digits, where your
specified data should be reported. The specified phone number should include the area,
country codes followed by the phone number. Yo can also specify a short number. It is also
possible to set up an SMS auto-response with MAMBO2-B6/UXFS. To send an SMS message to
the phone number for which you are receiving SMS messages, you have to enter in the
<"p_number"> the dynamic entry &(SMSNumber). In the last example in table above, the
sender of the last SMS message will receive an message back with the text you specify in the
<"text"> field.
<protocols>
Define the NMEA messages, which will be transmitted to the specified phone number. It has
to be specified in the hex format without leading the "0x. Supported protocols are listed in
chapter 7.4 page 332.
<"text">
Specify the text message, up to 200 characters, which will be transmitted to the specified
phone number. This entry must be wrapped in quotation marks (" ").
 Note: Each SMS message has a limit of 160 characters. SMS messages starting with a "#" sign or
"PFAL" will not be displayed on the MAMBO2-B6/UXFS's screen.
In order to add dynamic entries (entry) within this text, then use the following syntax:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Dynamic entries are listed in chapter 7.2 page 321. Between each dynamic entry use the
ampersand "&" and then without spaces enclose each of them with parentheses "( )". See
example below.
For example:
$PFAL,GSM.SMS.Send,"+491111111",0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
Notes
• Longer the <"text"> results less protocols can be attached to the SMS message. Only
protocols, which fit completely in are attached to the SMS.
• No more than 160 characters can be sent within an SMS.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 132 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.4.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.SMS.SendRaw,<"p_number">,<protocols>,<"text"> - Sends an SMS to the
phone number in raw format
Command syntax
$PFAL,GSM.SMS.SendRaw,<"p_number">,<protocols>,<"text">
$PFAL,GSM.SMS.SendRaw,<"p_number">,<protocols>,<"text&(entry)">
Examples
$PFAL,GSM.SMS.SendRaw,"+491111111",8,"MAMBO2-B6/UXFS"
$PFAL,GSM.SMS.SendRaw,"+491111111",0,"on &(Date) at &(Time) moving at &(Speed) m/s"
$PFAL,GSM.SMS.SendRaw,"&(SMSNumber)",0,"Auto SMS Reply&(SMSNumber)"
Message description
This command is used to transmit NMEA and user messages including dynamic entries to your
specified phone number via SMS in raw format. No format characters are used to display the
message text (i.e. the text appears exactly as it is – no $ in front of or CRLF at the end will be
sent ).
Parameter Description
<"p_number">
Wrapped in quotation marks (""), specify the phone number max 30 digits, where your
specified data should be reported. The specified phone number should include the area,
country codes followed by the phone number. Yo can also specify a short number. It is also
possible to set up an SMS auto-response with MAMBO2-B6/UXFS. To send an SMS message to
the phone number for which you are receiving SMS messages, you have to enter in the
<"p_number"> the dynamic entry &(SMSNumber). In the last example in table above, the
sender of the last SMS message will receive an message back with the text you specify in the
<"text"> field.
<protocols>
Define the output NMEA messages, which will be sent to the specified target phone number.
The protocol number should be specified in the hex format without leading "0x. Supported
protocols are listed in chapter 7.4 page 332.
<"text">
Specify the SMS text, up to 200 characters, that you want to sent to the specified phone
number. The text message may include the user specified text and/or system information. It
must be wrapped in quotation marks (" ").
 Note: Each SMS message has a limit of 160 characters. SMS messages starting with a "#" sign or
"PFAL" will not be displayed on the MAMBO2-B6/UXFS's screen.
If it is required to attach also system information (entry) at certain times use the following
<"text"> syntax: "text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Each dynamic entry is separated by ampersand "&" without spaces and enclosed in
parentheses "( )".
For example:
$PFAL,GSM.SMS.SendRaw,"+49111133",0,"on &(Date) at &(Time) moving at &(Speed) m/s"
Dynamic entries are listed in chapter 7.2 page 321.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 133 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.4.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.SMS.Inbox.Clear – Clears all stored SMS Messages
Command syntax
$PFAL,GSM.SMS.Inbox.Clear
Examples
$PFAL,GSM.SMS.Inbox.Clear
Message description
This command is used to clear all incoming SMS messages from the SMS memory.
Parameter Description
None
3.2.6.4.4
GSM.SMS.Inbox.State – Returns all inbox SMS Messages
Command syntax
$PFAL,GSM.SMS.Inbox.State
Examples
$PFAL,GSM.SMS.Inbox.State
Message description
This command is used to get the total number of incoming SMS messages associated with the SMS
storage.
Parameter Description
None
3.2.6.4.5
GSM.SMS.Outbox.Clear – Clears all outgoing SMS Messages
Command syntax
$PFAL,GSM.SMS.Outbox.Clear
Examples
$PFAL,GSM.SMS.Outbox.Clear
Message description
This command is used to delete all unsent SMS messages from the SMS memory.
Parameter Description
None
3.2.6.4.6
GSM.SMS.Outbox.State – Returns all outbox SMS Messages
Command syntax
$PFAL,GSM.SMS.Outbox.State
Examples
$PFAL,GSM.SMS.Outbox.State
Message description
This command is used to indicate the total number of unsent SMS messages associated with the
SMS storage.
Parameter Description
None
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 134 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Data Call" command index
3.2.6.5.1
Command syntax
Examples
GSM.DataCall.Send,<protocols>,<"text"> - Sends alarm messages and protocols via
an established data call
$PFAL,GSM.DataCall.Send,<protocols>,<"text">
$PFAL,GSM.DataCall.Send,<protocols>,<"text&(entry)">
$PFAL,GSM.DataCall.Send,08,"text to be received"
$PFAL,GSM.DataCall.Send,0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
Message description
This command is used to transmit NMEA and user messages including dynamic entries to the
remote server / GSM modem via an established GSM data call. The format that the device uses to
transmit your specified data is DEVICE.PFAL.SEND.FORMAT configuration-dependent. Such
information could not be transmit only via an established GSM Data call, but also via SMS and TCP.
How to transmit messages via SMS or TCP, please refer to the chapters "Sends messages and
protocols via SMS" and "Sends alarm messages and protocols via TCP to an internet server".
Parameter Description
<protocols>
Define the NMEA messages that will be transmitted to the remote GSM modem via an
established GSM data call. Specify a hex value without leading the "0x". Supported protocols
are listed in chapter 7.4 page 332.
<"text">
Wrapped in quotation marks (""), specify the text, max 200 character, to be transmitted to the
remote GSM modem via an established/initiated data call. In order to add dynamic entries
(entry) in the text, use the following syntax:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Dynamic entries are listed in chapter 7.2 page 321. Enclose each dynamic entry with
parentheses "( )" and use the ampersand "&" to separate them. See example below.
For example:
$PFAL,GSM.DataCall.Send,0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
3.2.6.5.2
GSM.DataCall.Accept - Accepts incoming Data calls
Command syntax
$PFAL,GSM.DataCall.Accept
Examples
$PFAL,GSM.DataCall.Accept
Message description
This command is intended to accept an incoming Data call, which is usually indicated by an
incoming ring alarm event.
Parameter Description
None
Notes
• No GSM data calls are accepted while the MAMBO2-B6/UXFS is trying to establish a GPRS
connection. During this time which takes approx. 10-20 seconds, the device is unreachable
(this is GSM related). Therefore, it is wise not to perform a GPRS attach/detach in such
short periods.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 135 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.5.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.DataCall.Hangup – Hangs up active data calls
Command syntax
$PFAL,GSM.DataCall.Hangup
Examples
$PFAL,GSM.DataCall.Hangup
Message description
This command is used to reject an incoming data call or to finish an established data call.
Parameter Description
None
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 136 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.6
3.2.6.6.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"GPRS" command index
GSM.GPRS.Connect – Performs GPRS attach
Command syntax
$PFAL,GSM.GPRS.Connect
Examples
$PFAL,GSM.GPRS.Connect
Message description
This command is used to perform a GPRS attach. After the message has been completed and the
MAMBO2-B6/UXFS is already in the requested state, the message is ignored. If the MAMBO2B6/UXFS is not able to attach for more than 5 minutes, no message is returned, but MAMBO2B6/UXFS is still trying to attach.
Parameter description
None.
Notes
• If a GPRS attach is initiated and the MAMBO2-B6/UXFS is not able to attach, please have a
look inside the configuration and adapt the settings for the following parameters
GPRS.APN, GPRS.QOS,GPRS.QOSMIN,PPP.USERNAME and PPP.PASSWORD according to
the used SIM card.
• When a MAMBO2-B6/UXFS is GPRS attached and a PLMN reselection occurs to a nonGPRS capable network or to a network where the SIM is not subscribed for using GPRS
services, the resulting GSM (GPRS mobility management) state according to GSM 24.008 is
REGISTERED/NO CELL.
• No GSM calls are accepted while the MAMBO2-B6/UXFS is trying to establish a GPRS
connection. During this time which takes approx. 10-20 seconds, the device is unreachable
(this is GSM related). Therefore, it is wise not to perform a GPRS attach/detach in such
short periods.
3.2.6.6.2
GSM.GPRS.Disconnect – Performs GPRS detach
Command syntax
$PFAL,GSM.GPRS.Disconnect
Examples
$PFAL,GSM.GPRS.Disconnect
Message description
This command is used to detach the MAMBO2-B6/UXFS from the GPRS service. Any active PDP
contexts will be automatically deactivated when the attachment state changes to detached. If the
MAMBO2-B6/UXFS is not able to detach for more than 1 minute, no message is returned, but
MAMBO2-B6/UXFS is still trying to detach. If an attachment is issued during a running detach this
message is ignored.
Parameter description
None.
Notes
• If a GPRS connection is already available and the disconnect command is performed,
ensure that the value of the parameter GPRS.AUTOSTART=<value> is set to 0 (zero)
instead of 1 (one), otherwise the MAMBO2-B6/UXFS will try to re-establish automatically
that connection after each GPRS connection failure or disconnection.
• The GSM engine will be restarted, if the GPRS connection could not be closed after multiple
attempts.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 137 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.6.6.3
Command syntax
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.GPRS.State - Returns GPRS state
$PFAL,GSM.GPRS.State
$PFAL,GSM.GPRS.State
Examples
$<GSM.GPRS.State>
$current GPRS state:GPRS disabled OR enabled
Response
$SUCCESS
Message description
This command is used to read the state of the GPRS connection.
Parameter description
None.
3.2.6.6.4
Command syntax
GSM.GPRS.Traffic[=<complete>,<incoming>,<outgoing>] – Sets GPRS traffic counter
$PFAL,GSM.GPRS.Traffic
$PFAL,GSM.GPRS.Traffic=<complete>,<incoming>,<outgoing>
$PFAL,GSM.GPRS.Traffic
$PFAL,GSM.GPRS.Traffic=0,0,0
Examples
//reads the GPRS traffic counter
//resets the GPRS traffic counter to zero - thereafter, it starts
new counting
$<GSM.GPRS.Traffic>
$traffic after 00.00.0,00:00:00 :0 kB (0 Bytes) I:0 kB (0 Bytes) O:0 kB (0
Bytes)
Response
$SUCCESS
Message description
This command is used to read out or reset the GPRS traffic counter. To read out the current GPRS
traffic, just send this command without parameters:
Parameter description
<complete>
Number of bytes in range of 0 to 4294967295 for incoming and outgoing data stream.
<incoming>
Number of bytes in range of 0 to 4294967295 for incoming data stream.
<outgoing>
Number of bytes in range of 0 to 4294967295 for outgoing data stream.
Notes
• To delete the GPRS traffic counter set all values to "0" zero.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 138 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.7
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"TCP" command type
In order to have a basic understanding about the TCP communication between the MAMBO2-B6/UXFS
device and the remote server, please refer to chapter 2.2, page 23. The PFAL-Commands listed below
are used to open a TCP connection, to send messages and close that TCP connection.
3.2.7.1
3.2.7.1.1
"TCP" command index
TCP.Client.Connect - Performs TCP connection to the used server
Command syntax
$PFAL,TCP.Client.Connect
Examples
$PFAL,TCP.Client.Connect
Message description
This command is used to initiate a TCP connection to a remote server. Before the MAMBO2B6/UXFS can send data, it needs to know the address and port number of the remote server
where this data should be sent. To assign the address, and the port use the configuration
parameter TCP.CLIENT.CONNECT=<s_enable>,<ip_address>,<port>. The server can decide
whether or not to accept the connection. After the TCP connection has been established
successfully, use the TCP.Client.Send,<protocols>,<"text"> command to send any data.
Parameter description
None.
Notes
• If a TCP connection is initiated band the MAMBO2-B6/UXFS is unable to establish that
connection, please have a look inside the configuration and adapt the settings for the
following parameter TCP.CLIENT.CONNECT according to the remote server you are going
to use.
• Before using this command, make sure that the MAMBO2-B6/UXFS is already GPRS
attached, otherwise the MAMBO2-B6/UXFS is not able to initiate a TCP connection even if
the TCP settings are correctly specified.
3.2.7.1.2
TCP.Client.Disconnect - Disconnects from the used server
Command syntax
$PFAL,TCP.Client.Disconnect
Examples
$PFAL,TCP.Client.Disconnect
Message description
This command is used to terminate an existing TCP connection with a remote server. No more
data will be sent from the MAMBO2-B6/UXFS by the TCP until a new connection to the remote
server is initiated and accepted.
Parameter description
None.
Notes
• If a TCP connection to the remote server is already available and the Disconnect message
is called, ensure that the value <s_enable> from the TCP.CLIENT.CONNECT parameter is set
to 0 (zero) instead of 1 (one), otherwise the MAMBO2-B6/UXFS will try to reconnect
automatically, to the remote server, after each TCP connection failure.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 139 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.7.1.3
Command syntax
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
TCP.Client.State – Returns TCP connection state
$PFAL,TCP.Client.State
$PFAL,TCP.Client.State
Examples
$<TCP.Client.State>
$current TCP state:disabled OR enabled
Reponds
$SUCCESS
Message description
This command is used to read the state of the TCP connection.
Parameter description
None.
3.2.7.1.4
TCP.Client.Send,<protocols>,<"text"> - Sends alarm messages and protocols via TCP
to an internet server
Command syntax
$PFAL,TCP.Client.Send,<protocols>,<"text">
$PFAL,TCP.Client.Send,<protocols>,<"text&(entry)">
Examples
$PFAL,TCP.Client.Send,8,"MAMBO2-B6/UXFS sends its GPS positions"
Message description
This command is used to stream data (GPS positions, user text etc.) to a remote server after a
connection has been established. The TCP.Client.ePacketSent event occurs each time the
MAMBO2-B6/UXFS sends successfully a TCP packet to the remote server. The remote server may
evaluate the data the device sends for further purposes. The format the device uses to transmit
your specified data is DEVICE.PFAL.SEND.FORMAT configuration-dependent. Such information
could not be transmit only via TCP, but also via SMS and GSM data call. How to transmit messages
via SMS or GSM data call, please refer to the chapters "Sends messages and protocols via SMS"
and "Sends alarm messages and protocols via an established data call".
Parameter Description
<protocols>
Define the NMEA messages that will be transmitted to the remote server via TCP. Specify a
hex value without leading the "0x". Supported protocols are listed in chapter 7.4 page 332.
<"text">
Wrapped in quotation marks (""), specify the text message, max. 200 characters, that you
want to send to the remote server. In order to add dynamic entries (entry) within this text,
then use the following syntax:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Dynamic entries are listed in chapter 7.2 page 321. Between each dynamic entry use the
ampersand "&" and then without any spaces, enclose each of them with parentheses "( )". See
example below.
For example:
$PFAL,TCP.Client.Send,8,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
Notes
• If the TCP connection is currently not established, this data will be written into the TCP
buffer and it will be sent as soon as the TCP connection is available.
• If the command fails to execute because the buffer is used up, then this data are lost.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 140 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.7.1.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
TCP.Client.ClearSendBuffer - Clears the internal TCP buffer for outbound packets
Command syntax
$PFAL,TCP.Client.ClearSendBuffer
Examples
$PFAL,TCP.Client.ClearSendBuffer
Message description
This command is used to empty the internal TCP buffer for outbound packets.
Parameter Description
None
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 141 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.7.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"STORAGE" command index
The TCP Storage is an additional TCP buffer, which enables to collect information before sent. This
reduces transmission cost and enables to send quickly various information to the remote server.
Currently the TCP storage supports two operation modes:
 Manual mode (default)
If this mode is selected, the TCP storage has to be dispatched manually (i.e. you can specify
when the stored information have to be to sent via TCP)
 Automatic dispatch
This mode allows the system to dispatch automatically the data inside the storage whenever
the TCP buffer is used up.
Both operation modes as well as the size of the TCP storage can be configured using the parameter in
chapter 3.3.14.11.
 Note: All information you are going to transmit via TCP storage is sent exactly in the
way you specified it. In order to make simple reading of this data from the server site, it
is recommended to add additional „identification" characters. Please see further nodes
inside the command „AddProtocol" below.
Using such identification characters allows you to easily distinguish between textual „AddProtocol" and
binary data (generated by „AddRecord").
3.2.7.2.1
TCP.Storage.Dispatch - Stores information in TCP storage
Command syntax
$PFAL,TCP.Storage.Dispatch
Examples
$PFAL,TCP.Storage.Dispatch
Message description
This command is used to move the currently stored information inside the TCP storage to the
outgoing TCP buffer. After this data has been appended to the outgoing buffer, then the storage
content will be cleaned to allow saving of new data.
Parameter description
None.
Notes
• If the TCP storage is set into the automatic mode (see chapter 3.3.14.11) then it is not
required to send this command for moving the data from the storage to the outgoing
buffer..
3.2.7.2.2
TCP.Storage.Clear - Clears TCP storage contents
Command syntax
$PFAL,TCP.Storage.Clear
Examples
$PFAL,TCP.Storage.Clear
Message description
This command is used to clear the content of the TCP storage. This command can be used to
discard unwanted information and empty the TCP storage completely (without sending its data
away).
Parameter description
None.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 142 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.7.2.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
TCP.Storage.AddProtocol,<protocol>,<"text"> - Adds protocols/user-text to TCP
storage
Command syntax
$PFAL,TCP.Storage.AddProtocol,<protocols>,<"text">
Examples
$PFAL,TCP.Storage.AddProtocol,0,"your text"
Message description
This command is used to write the protocols and/or user text into the TCP storage.
Parameter description
<protocols>
Define the NMEA messages that will be saved into the TCP storage. Specify a hex value
without leading the "0x". Supported protocols are listed in chapter 7.4 page 332.
<"text">
Specify the text message, up to 200 characters, to be saved into the TCP storage. This text
may also contain dynamic protocols which are listed in chapter 7.2 page 321.
Notes
• To specify more protocols, enter sum of the protocols in hex value, for example:
−
−
The hex value 27 in command "$PFAL,TCP.Storage.AddProtocol,27,"test"" means that the
GGA+GSA+GSV+VTG protocols will be sent at once,
The hex value 4F in command "$PFAL, TCP.Storage.AddProtocol,4F,"test" " means that
the GGA+GSA+GSV+RMC+IOP protocols will be sent at once.
3.2.7.2.4
TCP.Storage.AddRecord,<protocol>,<"text"> - Appends binary data frame to TCP
storage
Command syntax
$PFAL,TCP.Storage.AddRecord,<add_protocols>,<"text">
Examples
$PFAL,TCP.Storage.AddRecord,0,""
$PFAL,TCP.Storage.AddRecord,20,"user note: freeway reached "
Message description
This command is used to add a binary data frame into the TCP storage. This data frame has the
same format as a full record from the history entry (including possible extensions). The content of
the data to be written is limited by the size of the TCP storage. If there is not enough memory
available in the TCP storage, then MAMBO2-B6/UXFS will report an error to start this process.
Parameter description
<add_protocols>
Determine, in hexadecimal format (without leading "0x"), whether or not additional
information has to be stored in the TCP storage. This entry can be set to one or a combination
of the following hex numbers:
Value
Meaning
0x01
Do not use. It applies to the STEPPIII, FOX, BOLERO-LT device only.
0x02
Writes the current state of the GSM (field strength, cell id, area code, of
incoming/outgoing SMS etc.)
0x04
Writes the current operating mode of the system, GPRS, PPP, TCP, system
lifetime.
0x08
Reserved.
0x10
Do not use. It applies to the STEPPIII, FOX, BOLERO-LT device only.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 143 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
0x20
Writes a user specified message added in the <"text"> field (up to 255
characters available)
0x40
Writes the current state of the Geofences (inside or outside)
0x80
Reserved
<"text">
Wrapped in quotation marks (""), define a string value, max. 200 characters, containing user
information. The user information will be written if the corresponding hex value (20) has been
set in the <add_protocols> field.
Notes
• To specify more protocols, enter sum of the protocols in hex value, for example::
− The hex value 60 means: user text and Geofences starts will be added.
• Writing of this data frame into the TCP storage does NOT require a valid GPS fix. Also
invalid data can be added to TCP storage, which stands in contrast to the
$PFAL,GPS.History.Write command.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 144 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.7.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"SMTP" command index
3.2.7.3.1
TCP.SMTP.Send,<"email_to">,<protocols>,<"text"> - Sends Emails to remote server
Command syntax
$PFAL,TCP.SMTP.Send,<"email_to">,<protocols>,<"usertext">
$PFAL,TCP.SMTP.Send, <"email_to">,<protocols>,<"usertext&(entry">
Examples
$PFAL,TCP.SMTP.Send,"[email protected]",8,"MAMBO2-B6/UXFS sends its GPS positions"
Message description
This command is used to enable sending of E-Mails via an Internet mail server, including GPS
position data and user text. The user text can be evaluated and used for further application
processes. The remote mail server to be connected is defined by the <mail_server_address> and
<mail_server_port> from the TCP.SMTP.CONNECT parameter. Both <mail_server_address> and
<mail_server_port> must be set before executing this command. When an outgoing E-Mail
message has been successfully delivered, the TCP.SMTP.eSent event occurs. If there is an error
during sending the E-Mail (message), the TCP.SMTP.eFailed event raises and this email message
gets deleted. The format the device uses for sending out the text is DEVICE.PFAL.SEND.FORMAT
configuration-dependent.
The subject the MAMBO2-B6/UXFS device uses for outgoing E-Mail:
Subject syntax
Message from
Subject example
<hardware name>
(Name="<name>", IMEI=<GSM.IMEI>)
Message from MAMBO2-B6/UXFS (Name="my MAMBO2-B6/UXFS device", IMEI=123456789012345)
Parameter Description
<"email_to">
Wrapped in quotation marks (" "), specify the e-mail address of the message recipient. Only
one E-Mail address is permitted per message.
<protocols>
Define the NMEA messages to be sent to the recipient of the E-Mail message. It has to be
specified in the hex format without leading the "0x". Supported protocols are listed in chapter
chapter 7.4 page 332.
<"usertext">
Wrapped in quotation marks (""), specify up to 200 characters for the text message you want
to send to the recipient of the E-Mail message. In order to add dynamic entries (entry) within
this text, then use the following syntax:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Dynamic entries are listed in chapter 7.2 page 321. Between each dynamic entry use the
ampersand "&" and then without any spaces, enclose each of them with parentheses "( )". See
example below.
For example:
$PFAL,TCP.SMTP.Send,"your-email ",8,"on &(Date) at &(Time) moving at &(Speed) m/s"
To view the location of the device in the Google Earth, just enter the following link in the usertext:
$PFAL,TCP.SMTP.Send,"your-email",8,"http://maps.google.com/maps?f=q&hl=en&q=&(lat)+&(lon)"
When you receive this email, copy and paste it in the address field of your browser.
Notes
• If there is no GSM operator and no active GPRS/TCP connection currently available, the
device stores the email data into the outbox and when the GPRS connection is available
again it sends this data.
• If there is an error during sending an E-Mail message, the contents of this email message is
lost. Using only SMTP service, the configuration of "GPRS.AUTOSTART=1" is not required.
It can be set to "GPRS.AUTOSTART=0".
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 145 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.7.3.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
TCP.SMTP.SendRaw,<"email_to">,<protocols>,<"text"> - Sends an Email to the
remote SMTP server in raw format
Command syntax
$PFAL,TCP.SMTP.SendRaw,<"email_to">,<protocol>,<"usertext">
$PFAL,TCP.SMTP.SendRaw, <"email_to">,<protocol>,<"usertext&(entry)">
Examples
$PFAL,TCP.SMTP.SendRaw,"[email protected]",8,"MAMBO2-B6/UXFS positions"
Message description
This command enables sending of E-Mails, including GPS position data and user text, via an
Internet mail server. The user text can be evaluated and used for further application processes.
The address of the remote mail server to be connected is defined by the <mail_server_address>
and <mail_server_port> from the configuration parameter TCP.SMTP.CONNECT. Both
<mail_server_address> and <mail_server_port> must be set before executing this command.
When an outgoing E-Mail message has been delivered successfully, the TCP.SMTP.eSent event
occurs. If there is an error during sending of E-Mail (message), the TCP.SMTP.eFailed event raises
and this email message gets deleted. The format used for sending out the text is
DEVICE.PFAL.SEND.FORMAT configuration-dependent.
The subject the STEPPIII device uses for outgoing E-Mail:
Subject syntax
Message from:
Subject example
<hardware name>
rev: <string>
(Name="<name>", IMEI=<GSM.IMEI>)
Message from MAMBO2-B6/UXFS (Name="my MAMBO2-B6/UXFS device", IMEI=123456789012345)
Parameter Description
<"email_to">
Wrapped in quotation marks (" "), specify the e-mail address of the message recipient. Only
one E-Mail address is permitted per message.
<protocols>
Define the NMEA messages to be sent to the recipient of the E-Mail message. It must be
specified in the hex format without leading the "0x". Supported protocols are listed in chapter
7.4 page 332.
<"usertext">
Wrapped in quotation marks (" "), specify up to 200 characters for the text message you want
to send to the recipient of the E-Mail message.
If it is required to attach also system information (entry) at certain times the following syntax
of the <"text"> is also possible:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Each dynamic entry is separated by ampersand "&" without spaces and enclosed in
parentheses "( )".
For example:
$PFAL,TCP.SMTP.SendRaw,"your-email ",8,"on &(Date) at &(Time) moving at &(Speed) m/s"
To view the location of the device in the Google Earth, just enter the following link in the usertext:
$PFAL,TCP.SMTP.SendRaw,"your-email",8,"http://maps.google.com/maps?f=q&hl=en&q=&(lat)+&(lon)"
When you receive this email, copy and paste it in the address field of your browser.
Dynamic entries are listed in chapter 7.2 page 321. .
Notes
• If there is no GSM operator found and no active GPRS/TCP connection currently available,
the device stores the e-Mail data into the outbox and when the GPRS connection is
available the device sends this data. If there is an error during sending an E-Mail message,
the data of this email message is lost.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 146 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
• Using only SMTP service, the configuration of "GPRS.AUTOSTART=1" is not required. It can
be set to "GPRS.AUTOSTART=0".
• Do not try to send another email without getting response from the prior one. After an
email has been delivered successfully, a new mail can be sent with this command.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 147 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.8
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"MSG" command type
The MSG PFAL-Commands are used to request and send information.
3.2.8.1
"Send" command index
The commands in this group are used to send protocols, user text and dynamic entries* (plus additional
protocols if desired) to the specified port (incl. Bluetooth, USB, SD-Card, CSD, TCP, SMTP).
* Dynamic entries
This feature allows to create user defined messages, which may contain textual information
plus system information. For example, a message that contains the current date may be: "This
message was generated at 20.12.2004". In order to transmit system information inside the
user text you can use special entries which work as system variables. For a complete set of
dynamic entries, please refer to the chapter 7.2 page 321. .
3.2.8.1.1
MSG.Send.Serial,<protocols>,<"text"> - Sends protocols over Bluetooth
Command syntax
$PFAL,MSG.Send.Serial,<protocols>,<"text">
$PFAL,MSG.Send.Serial,<protocols>,<"text&(entry)">
Examples
$PFAL,MSG.Send.Serial,8,"GPS position"
$PFAL,MSG.Send.Serial,0,"Current speed &(Speed)"
Message description
(This option is only available for the MAMBO2-UXFS)
This command is used to transmit the specified protocols and/or user text over the Bluetooth
channel. The format the device will use to transmit your specified data is
DEVICE.PFAL.SEND.FORMAT configuration-dependent.
Parameter Description
<protocols>
Define, in hex value, the protocols you want to transmit over Bluetooth. Protocols are listed in
chapter 7.4. Please note that, if the GPS engine is sleeping or switched off when executing this
command, the device holds the last known position from the RAM and sends them out over
the Bluetooth channel. In such a case, the time within RMC protocol is steady updated by the
system time and not by GPS time.
<"text">
Wrapped in quotation marks (""), specify up to 200 characters that you want to send
additionally to the specified protocols. If you want to add also dynamic entries (entry) within
this text, then use the following syntax:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Dynamic entries are listed in chapter 7.2 page 321. Between each dynamic entry use the
ampersand "&" and then without any spaces, enclose each of them with parentheses "( )". See
example below.
For example:
$PFAL,MSG.Send.Serial,0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 148 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.8.1.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
MSG.Send.RawSerial,<protocols>,<"text"> - Sends protocols unformatted over
Bluetooth
Command syntax
$PFAL,MSG.Send.RawSerial,<protocols>,<"text">
$PFAL,MSG.Send.RawSerial,<protocols>,<"text&(entry)">
Examples
$PFAL,MSG.Send.RawSerial,8,"GPS position"
$PFAL,MSG.Send.RawSerial,0,"Current speed &(Speed)"
Message description
(This option is only available for the MAMBO2-UXFS)
This command is used to transmit the specified protocols and/or user text unformatted over the
Bluetooth. No format characters are used to display the message text (i.e. the text appears exactly
as it is – no $ in front of the text or CRLF at the end of the text is used. The format the device will
use to transmit your specified data is NOT DEVICE.PFAL.SEND.FORMAT configuration-dependent).
Parameter Description
<protocols>
Define, in hex value, the protocols you want to transmit over Bluetooth. Protocols are listed in
chapter 7.4. Please note that, if the GPS engine is sleeping or switched off when executing this
command, the device holds the last known position from the RAM and sends them out. In
such a case, the time within RMC protocol is steady updated by the system time and not by
GPS time.
<"text">
Wrapped in quotation marks (""), specify up to 200 characters that you want to send to
additionally to the specified protocols. If you want to add also dynamic entries (entry) within
this text, then use the following syntax:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Dynamic entries are listed in chapter 7.2 page 321. Between each dynamic entry use the
ampersand "&" and then without any spaces, enclose each of them with parentheses "( )". See
example below.
For example:
$PFAL,MSG.Send.RawSerial,0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 149 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.8.1.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
MSG.Send.USB,<protocols>,<"text"> - Sends protocols to USB port
Command syntax
$PFAL,MSG.Send.USB,<protocols>,<"text">
$PFAL,MSG.Send.USB,<protocols>,<"text&(entry)">
Examples
$PFAL,MSG.Send.USB,8,"GPS position"
$PFAL,MSG.Send.USB,0,"Current speed &(Speed)"
Response
$Current speed 0*1E
$GPRMC,065545.000,A,5040.4095,N,01058.8587,E,0.03,0.00,280610,,*0D
<end>
Message description
This command is used to output the specified protocols and/or user text to the USB port. The
format the device will use to transmit your specified data is DEVICE.PFAL.SEND.FORMAT
configuration-dependent.
Parameter Description
<protocols>
Define, in hex value, the protocols you want to transmit to the USB port. Protocols are listed
in chapter 7.4. Please note that, if the GPS engine is sleeping or switched off when executing
this command, the device holds the last known position from the RAM and sends them out. In
such a case, the time within RMC protocol is steady updated by the system time and not by
GPS time.
<"text">
Wrapped in quotation marks (""), specify up to 200 characters that you want to send to
additionally to the specified protocols. If you want to add also dynamic entries (entry) within
this text, then use the following syntax:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Dynamic entries are listed in chapter 7.2 page 321. Between each dynamic entry use the
ampersand "&" and then without any spaces, enclose each of them with parentheses "( )". See
example below.
For example:
$PFAL,MSG.Send.USB,0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 150 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.8.1.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
MSG.Send.RawUSB,<protocols>,<"text"> - Sends protocols unformatted to USB port
Command syntax
$PFAL,MSG.Send.RawUSB,<protocols>,<"text">
$PFAL,MSG.Send.RawUSB,<protocols>,<"text&(entry)">
Examples
$PFAL,MSG.Send.RawUSB,8,"GPS position"
$PFAL,MSG.Send.RawUSB,0,"Current speed &(Speed)"
Response
GPS Position $GPRMC,065436.000,A,5040.4202,N,01058.8556,E,0.03,0.00,2901 08,,*07
Current speed 10$<MSG.Send.RawUSB>
Message description
This command is used to output the specified protocols and/or user text unformatted to USB port.
No format characters are used to display the message text (i.e. the text appears exactly as it is –
no $ in front of the text or CRLF at the end of the text is used. The format the device will use to
transmit your specified data is NOT DEVICE.PFAL.SEND.FORMAT configuration-dependent).
Parameter Description
<protocols>
Define, in hex value, the protocols you want to transmit in raw data to the USB channel.
Protocols are listed in chapter 7.4. Please note that, if the GPS engine is sleeping or switched
off when executing this command, the device holds the last known position from the RAM
and sends them out. In such a case, the time within RMC protocol is steady updated by the
system time and not by GPS time.
<"text">
Wrapped in quotation marks (""), specify up to 200 characters that you want to send to
additionally to the specified protocols. If you want to add also dynamic entries (entry) within
this text, then use the following syntax:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Dynamic entries are listed in chapter 7.2 page 321. Between each dynamic entry use the
ampersand "&" and then without any spaces, enclose each of them with parentheses "( )". See
example below.
For example:
$PFAL,MSG.Send.RawUSB,0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 151 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.8.1.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
MSG.Send.File,<"filename">,<protocols>,<"text"> - Saves protocols to mini-SD card
Command syntax
$PFAL,MSG.Send.File,<"filename">,<protocols>,<"text">
$PFAL,MSG.Send.File,<"filename">,<protocols>,<"text&(entry)">
Examples
$PFAL,MSG.Send.File,"Start.log",8,"GPS position"
$PFAL,MSG.Send.File,"Speed.log",0,"Current speed &(Speed)"
Response
GPS Position $GPRMC,065436.000,A,5040.4202,N,01058.8556,E,0.03,0.00,2901 08,,*07
Current speed 10$<MSG.Send.File>
Message description
(SD option is no longer available)
This command is used to create a file in the mini-SD card on the MAMBO2-UXFS device and write
data on it. If file name does not exist, it is created otherwise the data to be written is added at the
end of the file. The format of data to be written in the file is " DEVICE.PFAL.SEND.FORMAT"
configuration dependent.
Parameter Description
<"filename">
Specify the name of the file in the mini-SD card where you want to write the data.
<protocols>
Define, in hex value, the protocols you want to transmit in raw data to the USB channel.
Protocols are listed in chapter 7.4. Please note that, if the GPS engine is sleeping or switched
off when executing this command, the device holds the last known position from the RAM
and sends them out into the mini-SD card. In such a case, the time within RMC protocol is
steady updated by the system time and not by GPS time.
<"text">
Wrapped in quotation marks (""), specify up to 200 characters that you want to send to
additionally to the specified protocols. If you want to add also dynamic entries (entry) within
this text, then use the following syntax:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Dynamic entries are listed in chapter 7.2 page 321. Between each dynamic entry use the
ampersand "&" and then without any spaces, enclose each of them with parentheses "( )". See
example below.
For example:
$PFAL,MSG.Send.File,"Start.log",0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 152 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.8.1.6
- FIRMWARE REVISION 2.8.0 -
MSG.Send.RawFile,<"filename">,<protocols>,<"text">
protocols and text unformatted to mini-SD card
-
DOCUMENT VERSION 3.7.0
Saves
Command syntax
$PFAL,MSG.Send.RawFile,<"filename">,<protocols>,<"text">
$PFAL,MSG.Send.RawFile,<"filename">,<protocols>,<"text&(entry)">
Examples
$PFAL,MSG.Send.RawFile,"Start.log",8,"GPS position"
$PFAL,MSG.Send.RawFile,"Speed.log",0,"Current speed &(Speed)"
Response
$SUCCESS
the
specified
Message description
(SD option is no longer available)
This command is used to create a file in the mini-SD card and write data unformatted on it. If file
name does not exist, it is created otherwise the data to be written is added at the end of the file.
No format characters are used to display the message text (i.e. the text appears exactly as it is –
no $ in front of the text or CRLF at the end of the text is used. The format the device will use to
transmit your specified data is NOT DEVICE.PFAL.SEND.FORMAT configuration-dependent).
Parameter Description
<"filename">
Specify the name of the file in the mini-SD card where you want to write the data.
<protocols>
Define, in hex value, the protocols you want to transmit in raw data to the USB channel.
Protocols are listed in chapter 7.4. Please note that, if the GPS engine is sleeping or switched
off when executing this command, the device holds the last known position from the RAM
and sends them out into the mini-SD card. In such a case, the time within RMC protocol is
steady updated by the system time and not by GPS time.
<"text">
Wrapped in quotation marks (""), specify up to 200 characters that you want to send to
additionally to the specified protocols. If you want to add also dynamic entries (entry) within
this text, then use the following syntax:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Dynamic entries are listed in chapter 7.2 page 321. Between each dynamic entry use the
ampersand "&" and then without any spaces, enclose each of them with parentheses "( )". See
example below.
For example:
$PFAL,MSG.Send.RawFile,"Start.log",0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 153 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
MSG.Send.Service,<protocols>,<"text"> - Sends the specified protocols and text in a
user-defined format to the service server
3.2.8.1.7
Command syntax
$PFAL,MSG.Send.Service,<protocols>,<"text">
$PFAL,MSG.Send.Service,<protocols>,<"text&(entry)">
Examples
$PFAL,MSG.Send.Service,8,"GPS position"
$PFAL,MSG.Send.Service,0,"Current speed &(Speed)"
Response
$SUCCESS
Message description
This command is used to send the specified protocols and user text to the service server via an
established TCP connection. The address and port of the service server to connect to should be
specified in the configuration parameter "TCP.SERVICE.CONNECT".
Parameter Description
<protocols>
Define, in hex value, the protocols you want to transmit to the service server via TCP channel.
Protocols are listed in chapter 7.4. Please note that, if the GPS engine is sleeping or switched
off when executing this command, the device holds the last known position from the RAM
and sends them out. In such a case, the time within RMC protocol is steady updated by the
system time and not by GPS time.
<"text">
Wrapped in quotation marks (""), specify up to 200 characters that you want to send to
additionally to the specified protocols. If you want to add also dynamic entries (entry) within
this text, then use the following syntax:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Dynamic entries are listed in chapter 7.2 page 321. Between each dynamic entry use the
ampersand "&" and then without any spaces, enclose each of them with parentheses "( )". See
example below.
For example:
$PFAL,MSG.Send.Service,"Start.log",0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
Notes
• If the TCP connection to the service server is currently not established, this data will be
written into the TCP history buffer and it will be sent as soon as the TCP connection will be
re-established.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 154 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.8.1.8
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
MSG.Send.CSD,<protocols>,<"text"> - Sends protocols and text in a user-defined
format via an established CSD call
Command syntax
$PFAL,MSG.Send.CSD,<protocols>,<"text">
$PFAL,MSG.Send.CSD,<protocols>,<"text&(entry)">
Examples
$PFAL,MSG.Send.CSD,8,"MAMBO2-B6/UXFS outputs its GPS position"
$PFAL,MSG.Send.CSD,0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
Message description
This command is used to send the specified protocols and/or user text to a remote modem via an
established data call.
Parameter Description
<protocols>
Define, in hex value, the protocols you want to transmit to the GSM modem via an established
CSD call. Protocols are listed in chapter 7.4. Please note that, if the GPS engine is sleeping or
switched off when executing this command, the device holds the last known position from the
RAM and sends them out. In such a case, the time within RMC protocol is steady updated by
the system time and not by GPS time.
<"text">
Wrapped in quotation marks (""), specify up to 200 characters that you want to send to
additionally to the specified protocols. If you want to add also dynamic entries (entry) within
this text, then use the following syntax:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Dynamic entries are listed in chapter 7.2 page 321. Between each dynamic entry use the
ampersand "&" and then without any spaces, enclose each of them with parentheses "( )". See
example below.
For example:
$PFAL,MSG.Send.CSD,0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 155 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.8.1.9
Command syntax
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
MSG.Send.TCP,<protocols>,<"text"> - Sends protocols via TCP to the remote server
$PFAL,MSG.Send.TCP,<protocols>,<"text">
$PFAL,MSG.Send.TCP,<protocols>,<"text&(entry)">
$PFAL,MSG.Send.TCP,8,"MAMBO2-B6/UXFS outputs its GPS position"
Examples
$PFAL,MSG.Send.TCP,0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
Message description
This command is used to send the specified protocols and/or user text to the remote server via an
established TCP connection. The address and port of the server to connect to should be specified
in the configuration parameter "TCP.CLIENT.CONNECT".
Parameter Description
<protocols>
Define, in hex value, the protocols you want to transmit to the server via TCP. Protocols are
listed in chapter 7.4. Please note that, if the GPS engine is sleeping or switched off when
executing this command, the device holds the last known position from the RAM and sends
them out. In such a case, the time within RMC protocol is steady updated by the system time
and not by GPS time.
<"text">
Wrapped in quotation marks (""), specify up to 200 characters that you want to send to
additionally to the specified protocols. If you want to add also dynamic entries (entry) within
this text, then use the following syntax:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Dynamic entries are listed in chapter 7.2 page 321. Between each dynamic entry use the
ampersand "&" and then without any spaces, enclose each of them with parentheses "( )". See
example below.
For example:
$PFAL,MSG.Send.TCP,0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
Notes
• If the TCP connection is currently not established, this data will be written into the TCP
history buffer and it will be sent as soon as the TCP connection will be re-established.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 156 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.8.1.10
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Command syntax
MSG.Send.SMTP,<"email_to">,<protocols>,<"text"> - Sends messages to an email
address
Examples
$PFAL,MSG.Send.SMTP,<"email_to">,<protocols>,<"text">
$PFAL,MSG.Send.SMTP,< "email_to">,< protocols>,<"text&(entry)">
$PFAL,MSG.Send.SMTP,"[email protected]",8,"MAMBO2-B6/UXFS outputs its GPS positions"
$PFAL,MSG.Send.SMTP,"[email protected]",0,"on &(Date) at &(Time) it is moving at
&(Speed) m/s"
Message description
This command is used to send the specified protocols and/or user text to an email address. The
address and port of the SMTP server for sending the email should be specified in the configuration
parameter "TCP.SMTP.CONNECT". Please refer to chapter TCP.SMTP.Send for further details and
general use.
Parameter Description
<"email_to">
Wrapped in quotation marks (" "), specify the recipient of the E-Mail message to be sent. Only
one E-Mail address is permitted per message.
<protocols>
Define, in hex value, the protocols you want to transmit to the email address via SMTP.
Protocols are listed in chapter 7.4. Please note that, if the GPS engine is sleeping or switched
off when executing this command, the device holds the last known position from the RAM
and sends them out. In such a case, the time within RMC protocol is steady updated by the
system time and not by GPS time.
<"text">
Wrapped in quotation marks (""), specify up to 200 characters that you want to send to
additionally to the specified protocols. If you want to add also dynamic entries (entry) within
this text, then use the following syntax:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Dynamic entries are listed in chapter 7.2 page 321. Between each dynamic entry use the
ampersand "&" and then without any spaces, enclose each of them with parentheses "( )". See
example below.
For example:
$PFAL,MSG.Send.SMTP,"[email protected]",0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 157 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.8.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Mode" command index
Commands in this group allow to define the communication mode on the supported interface (incl.
Bluetooth, USB, CSD, TCP). There are two modes, Command and Data mode, in which your MAMBO2B6/UXFS device may operate. By default all supported interfaces are configured to operate in Command
mode allowing PFAL-Commands to be executed. More information about both supported modes can be
found in the chapters below.
 Warning: You can change the communication mode from Command to Data by
sending the corresponding PFAL command to the device, but you cannot exit data
mode in this way. You can always change an already inserted Data mode to Command
mode by sending the corresponding PFAL command via SMS.
3.2.8.2.1
Command syntax
MSG.Mode.<interface>=<output_protocol>,<comunication_mode>
communication mode for receiving data
Sets
$PFAL,MSG.Mode.<channel>=<output_protocols>,<comunication_mode> //set command
$PFAL,MSG.Mode.Serial=60,D=4
$PFAL,MSG.Mode.USB=60,D=4
$PFAL,MSG.Mode.TCP=60,D=1
$PFAL,MSG.Mode.CSD=6F,C
Examples
-
$PFAL,MSG.Mode.Serial=60,E
//Sends the Data Transfer + Data Output to serial port and forwards
received data from serial to TCP.
//Sends the Data Transfer + Data Output to USB and forwards
received data from USB to TCP.
//Sends the Data Transfer + Data Output and forwards received
data from TCP to Bluetooth.
//Resets CSD interface to command mode (GPSTATE+
GPERROR+GPACTION+GPEVENT+Data Transfer+Data Output are
delivered via CSD).
//Sends the Data Transfer + Data Output to serial port and sets the
serial port into the event mode. When the device detects an
incoming text on the serial port it occurs the event Sys.eSerialData
and with &(SerialData) the text can then be sent out via TCP, SMS,
Data call.
Message description
There are three modes, Command mode, Data mode and Event mode, in which your MAMBO2B6/UXFS device may operate. This command is used to define the communication mode on the
specified channel (Bluetooth, USB, CSD or TCP). When the specified interface is in Command mode
(default), any characters sent to that channel are interpreted as a PFAL-Command to be executed.
Commands, as stand above, are preceded by the letters '$PFAL'. For example, if the MAMBO2B6/UXFS receives '$PFAL,Sys.Device.Shutdown' while operating in the command mode, it
interprets that as an instruction to shutdown the system immediately. While in command mode,
the device sends responses back to the port from where the PFAL-Command was received. When
the specified port is in data mode, any characters sent to the device through that port are
intended to be forwarded "as is" to the forwarding channel <forward_channel> you have specified
without processing them.
Parameter Description
<channel>
Specify the channel you want to configure.
Value
Meaning
Serial
Serial (Bluetooth) channel (MAMBO2-UXFS only)
USB
USB port.
CSD
CSD channel.
TCP
TCP channel.
<output_protocols>
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 158 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Define, in hex, the protocols to be transmitted to the specified channel <channel>.
Value
Meaning
1
GPSTATE.
2
GPERROR.
4
GPACTION.
8
GPEVENT.
10
Protocols (GGA, RMC.., configurable with protocol settings (see
configuration reference).
20
Data Transfer (interface shows data being transferred from other
interfaces in data transfer mode).
40
Data Output (interface shows data being created by commands like
MSG.Send.Serial etc.).
80
Reserved.
<comunication_mode>
Set the communication mode on the specified port. It can be set to:
Value
C
Meaning
Command mode (default). Note: All messages sent to the specified
channel that do not start with PFAL and ended with <LF> is considered as
event (like in event text mode). If just events are expected, event text
mode should be chosen instead of command mode (as the event text
could interfere with command text and might be misinterpreted then).
D=<forward_channel> Data transfer mode (incoming data is directly transferred to
<forward_channel>, no commands will be executed).
<forward_channel>
Define, in hex, where to forward the data received from the specified
<channel>.
Value
Meaning
1
2
Forwards any received data to Bluetooth.
Forwards any received data to CSD channel (only
during an established2 CSD call).
Forwards any received data to TCP channel (is buffered
if connection isn’t established).
Forwards rany eceived data to USB port.
4
8
E
Event mode (Required for Bluetooth/USB/CSD interfaces only.)
The data received in this channel is considered as an text (even starting
with PFAL or are PFAL commands). Each text terminated by <CRLF>
(Carriage Return and Line Feed) characters will create an event. The text
before the <CRLF> can be reported via SMS, TCP, Data call using an alarm
with dynamic protocol &(SerialData) .
Notes
• If you want to specify more than one message, i.e. GPEVENT, GPSTATE and GPERROR, then
enter the sum of all three protocols (i.e. 1+2+8=B) into the <output_protocols>.
• If you want to forward the data to several channels, i.e. Bluetooth and TCP, then enter the
sum of both channels (i.e. 1+4=5) into the <msg_output_channel> .
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 159 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.8.3
3.2.8.3.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Version" command index
MSG.Version.Complete - Gets device information
Command syntax
$PFAL,MSG.Version.Complete
Examples
$PFAL,MSG.Version.Complete
Responses
$<MSG.Version.Complete>
$Hardware: MAMBO2
$HardwareRev: 22
$HardwareOptions: default
$Software: MAMBO2-B6/UXFS_2.6 ( ....... )
$SoftwareID: MAMBO2-B6/UXFS_STD
$Production ID: 3038212233900002
$Bios: 5.0
$GPS: FAL JP18 V1.13 build 300608 [GSWLT3.2.5_FAL_3.3.01.06-SDK-LTP1.00
$SUCCESS
$<end>
Message Description
This command is used to read the complete device information.
Parameter description
None.
3.2.8.3.2
MSG.Version.Modules - Gets modules versions
Command syntax
$PFAL,MSG.Version.Modules
Examples
$PFAL,MSG.Version.Modules
Responses
$<MSG.Version.Modules>
$HardwareRev: 22
$Bios: 5.0
$GPS: FAL JP18 V1.13 build 300608 [GSWLT3.2.5_FAL_3.3.01.06-SDK-LTP1.00
$SUCCESS
$<end>
Message Description
This command is used to read out the information about hardware, BIOS, GSM and GPS version of
the device.
Parameter description
None.
3.2.8.3.3
MSG.Version.BIOS - Gets BIOS version
Command syntax
$PFAL,MSG.Version.BIOS
Examples
$PFAL,MSG.Version.BIOS
Responses
$<MSG.Version.BIOS>
$5.0
$SUCCESS
$<end>
Message Description
This command is used to read out the BIOS version of the device.
Parameter description
None.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 160 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.8.3.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
MSG.Version.HardwareRev - Gets hardware revision
Command syntax
$PFAL,MSG.Version.HardwareRev
Examples
$PFAL,MSG.Version.HardwareRev
Responses
$<MSG.Version.HardwareRev>
$22
$SUCCESS
$<end>
Message Description
This command is used to read out the hardware version of the device.
Parameter description
None.
3.2.8.3.5
MSG.Version.Hardware - Gets hardware name
Command syntax
$PFAL,MSG.Version.Hardware
Examples
$PFAL,MSG.Version.Hardware
Responses
$<MSG.Version.Hardware>
$MAMBO2-B6/UXFS
$SUCCESS
$<end>
Message Description
This command is used to read out the name of the device hardware.
Parameter description
None.
3.2.8.3.6
MSG.Version.Software - Gets software version
Command syntax
$PFAL,MSG.Version.Software
Examples
$PFAL,MSG.Version.Software
Responses
$<MSG.Version.Software>
$MAMBO2-B6/UXFS_2.6
$SUCCESS
$<end>
Message Description
This command is used to read out the software version running on the device.
Parameter description
None.
3.2.8.3.7
MSG.Version.SoftwareID - Gets software ID
Command syntax
$PFAL,MSG.Version.SoftwareID
Examples
$PFAL,MSG.Version.SoftwareID
Responses
$MAMBO2-B6/UXFS_STD
$SUCCESS
Message Description
This command is used to read out the ID of the software running on the device.
Parameter description
None.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 161 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.8.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"Info" command index
This chapter contains commands which can be used to query various information form the MAMBO2B6/UXFS device. The desired information will be returned within the PFAL answer.
3.2.8.4.1
MSG.Info.ServerLogin – Gets login information data
Command syntax
$PFAL,MSG.Info.ServerLogin
Examples
$PFAL,MSG.Info.ServerLogin
Responses
$<MSG.Info.ServerLogin>
$DeviceName=M2-John
$Software=MAMBO2-B6/UXFS_2.6.2
(bWFtYm8yXzIuNi4yAFJDNl9wZXJzb25hbF8yMDEwMDUwNjE0NDIzNQ==)
$SoftwareID=MAMBO2-B6/UXFS_STD
$Hardware=MAMBO2-B6/UXFS
$LastValidPosition=$GPRMC,075636.000,A,5040.4160,N,01058.8548,E,0.11,211.92,250510,,
$LocalIP=none
$CmdVersion=2
$SUCCESS
$<end>
Message Description
This command is used to query the login information that the device uses to identify itself on the
FALCOM server. This information consists of device name, hardware, software version, IMEI and
Local IP as well as the last valid position
Parameter description
None.
3.2.8.4.2
MSG.Info.Protocol,<protocols>,<"text"> - Gets data from protocols
$PFAL,MSG.Info.Protocol,<protocols>,<"text">
$PFAL,MSG.Info.Protocol,< protocols>,<"text&(entry)">
$PFAL,MSG.Info.Protocol,8,"MAMBO2-B6/UXFS outputs its GPS positions"
$PFAL,MSG.Info.Protocol,0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
Command syntax
Examples
Message description
This command is used to transmit the specified protocols and user text to the port from where the
command was received. The specified user text comes first followed by protocols.
Parameter Description
<protocols>
Define, in hex value, the protocols you want to send out. Protocols are listed in chapter 7.4.
<"text">
Wrapped in quotation marks (""), specify up to 200 characters that you want to send to
additionally to the specified protocols. If you want to add also dynamic entries (entry) within
this text, then use the following syntax:
"text&(<entry1>)text&(<entry2>)text…&(<entryn>)"
Dynamic entries are listed in chapter 7.2 page 321. Between each dynamic entry use the
ampersand "&" and then without any spaces, enclose each of them with parentheses "( )". See
example below.
For example:
$PFAL,MSG.Info.Protocol,0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 162 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.8.4.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
MSG.Info.Time – Gets GPS date/time
Command syntax
$PFAL,MSG.Info.Time
Examples
$PFAL,MSG.Info.Time
responses
$<MSG.Info.Time>
$current time:07:57:51
$current date:25.05.2010 week:21 weekday:2 (tuesday)
$SUCCESS
$<end>
Message description
This command is used to read out the device time, date, week number and week day.
Parameter Description
None
Notes
• The device should hasve a valid GPS fix to get a correct date and time.
3.2.8.4.4
MSG.Info.Alarm,<alarm_index> - Gets conditions used in the selected alarm
Command syntax
$PFAL,MSG.Info.Alarm,<alarm_index>
Examples
$PFAL,MSG.Info.Alarm,0
Message description
This command is used to read out what conditions are used in the selected alarm and to show
their current state (whether they are true or false).
Parameter Description
<alarm_index>
Specify an alarm index ranging from 0 to 99.
Notes
• This command can be used to check the alarm configurations step by step and validate
their behaviours. Events are always shown as „true".
3.2.8.4.5
MSG.Info.GetInterfaceName – Shows the interface name from which the commands
come
Command syntax
$PFAL,MSG.Info.GetInterfaceName
Examples
$PFAL,MSG.Info.GetInterfaceName
Responses
$USB
$SUCCESS
Message Description
This command is used to show the name of the interface you are currently communicating.
Parameter description
None.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 163 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.9
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"IEEE" command type
(IEEE option is only available for the MAMBO2-UXFS)
The IEEE interface that can be used in MAMBO2-UXFS device is optional. The IEEE commands given in
this chapter provides control to external IEEE devices that are connected to the MAMBO2-UXFS via
IEEE, e.g. Keyfob or I/O-Box from FALCOM. The number of IEEE devices that you can connect to a
MAMBO2-UXFS is limited to 6 and these can be either Keyfobs or I/O-Boxes or mixed. A Keyfob has
three buttons and each button can be pressed in three different ways - Short, Long or Double. A button
press generates a specific event in the MAMBO2-UXFS that can be used to trigger individual actions.
The action confirmation can be done by making the keyfob beep or vibrate. More detailed information
how to connect and test a Keyfob or I/O-BOX to a MAMBO2-UXFS device, refer to the application note
"AppNoteGettingStartedWithKeyfob&IObox.pdf".
3.2.9.1
"Keyfob" command index
3.2.9.1.1
IEEE.Keyfob<index>.LED<led_index>=<state> - Sets LED state on a Keyfob
Command syntax
$PFAL,IEEE.Keyfob<index>.LED<led_index>=<state>
Examples
$PFAL,IEEE.Keyfob0.LED1=hpulse,1
Command description
This command is used to configure the LED behaviour on the different Keyfobs.
Parameter description
<index>
Determine on which Keyfob device the LED should be configured/activated. The number of
IEEE devices that can be connected to the MAMBO2-UXFS is limited to 6. The index must be in
the range 0 through 5. Please enter the index of a Keyfob that is already connected to the
MAMBO2-UXFS device. The index of a Keyfob device is assigned in the configuration
parameter IEEE.KEYFOB<index> during the connection process.
<led_index>
Determine the index of the LED to be activated/deactivated. Each Keyfob has 3 LEDs. Specify a
number from 0 to 2. LED indices are shown in chapter 7.10, page 342.
<state>
Specify the state for the selected LED. It can be set to:
Value
Meaning
high
LED lights steady.
low
LED goes OFF.
hpulse,1
LED lights short then goes OFF again.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 164 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.9.1.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
IEEE.Keyfob<index>.Beep<type>=<state> – Generates beep tones on a Keyfob device
Command syntax
$PFAL,IEEE.Keyfob<index>.Beep<type>=<state>
Examples
$PFAL,IEEE.Keyfob0.Beep1=high
$PFAL,IEEE.Keyfob0.Beep1=low
$PFAL,IEEE.Keyfob0.Beep1=hpulse,1
……
$PFAL,IEEE.Keyfob0.Beep23=…..
Command description
This command is used to generate a simple beep tone on the Keyfob.
Parameter description
<index>
Determine which Keyfob device should beep. The number of IEEE devices that can be
connected to the MAMBO2-UXFS is limited to 6. The index must be in the range 0 through 5.
Please enter the index of a Keyfob that is already connected to the MAMBO2-UXFS device.
The index of a Keyfob device is assigned in the configuration parameter IEEE.KEYFOB<index>
during the connection process..
<type>
Specifies the frequency of the beep tone to be played on the Keyfob. This parameter must be
in the range 0 through 27.
<state>
Define the state of the selected beep tone. It can be set to:
Value
Meaning
high
Beeps steady
low
Beep goes OFF.
hpulse,1
One beep tone. The duration of a high pulse is limited to 1.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 165 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.9.1.3
Command syntax
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
IEEE.Keyfob<index>.Vibration=<state> – Makes Keyfob vibrating
$PFAL,IEEE.Keyfob<index>.Vibration=<state>
$PFAL,IEEE.Keyfob0.Vibration=hpulse,1
Examples
$PFAL,IEEE.Keyfob0.Vibration=low
Command description
This command is used to make a Keyfob device vibrating. It can be used as a reminder, for
example, to notify some events occurrences on the MAMBO2-UXFS device. For example, Keyfob
will vibrate when MAMBO2-UXFS receives an SMS, voice call or message.
Parameter description
<index>
Determine which Keyfob should vibrate. The number of IEEE devices that can be connected to
the MAMBO2-UXFS is limited to 6. The index must be in the range 0 through 5. Please enter
the index of a Keyfob that is already connected to the MAMBO2-UXFS device. The index of a
Keyfob device is assigned in the configuration parameter IEEE.KEYFOB<index> during the
connection process.
<state>
Determine the state of vibration. It can be set to:
Value
Meaning
high
Vibrates steady .
low
Vibrate goes OFF.
hpulse,1
Vibrates just one time. The duration of the vibration is factory predefined
to 1.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 166 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.9.1.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
IEEE.Keyfob<index>.bat.level - Gets battery charge state
Command syntax
$PFAL,IEEE.Keyfob<index>.bat.level
Examples
$PFAL,IEEE.Keyfob2.bat.level
Responses
Keyfob0 Batlevel=High
Command description
This command is used to read out the charge state of the internal AAA-batteries on a Keyfob
device.
Following values can be received:
Batlevel=Critical
Batlevel=Low
Batlevel=Medium
Batlevel=High
Parameter description
<index>
Determine the Keyfob index to be queried. The number of IEEE devices that can be connected
to the MAMBO2-UXFS is limited to 6. The index must be in the range 0 through 5. Please enter
the index of a Keyfob that is already connected to the MAMBO2-UXFS device. The index of a
Keyfob device is assigned in the configuration parameter IEEE.KEYFOB<index> during the
connection process.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 167 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.9.2
3.2.9.2.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"IOBOX" command index
IEEE.IOBox<index>.OUT<port>=<state> – Sets output state on an I/O-BOX
Command syntax
$PFAL,IEEE.IObox<index>.OUT<port>=<state>
Examples
$PFAL,IEEE.IOBOX3.OUT1=hpulse,1000
Command description
This command is used to configure digital outputs on different I/O-BOX devices.
Parameter description
<index>
Determine in which IO-BOX device should the output port be configured. The number of IEEE
devices that can be connected to the MAMBO2-UXFS is limited to 6. The index must be in the
range 0 through 5. Please enter the index of an IO-BOX that is already connected to the
MAMBO2-UXFS device. The index of a IO-BOX device is assigned in the configuration
parameter IEEE.IOBOX<index> during the connection process.
<port>
Determine the output port to be configured. The index must be in the range 0 through 3. Pin
designations and output indices are shown in chapter 7.11, page 343.
<state>
Specify the state of the selected output port. It can be set to:
Value
Meaning
high
Continuous high
low
Continuous low
hpulse,<interval>Sets to high for a specified <interval>.
<interval>
Specify the duration, in milliseconds, for the high time.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 168 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.9.2.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
IEEE.IOBox<index>.power=<mode> – Changes IO-BOX operation mode
Command syntax
$PFAL,IEEE.IOBOX<index>.power=<mode>
Examples
$PFAL,IEEE.IOBOX3.power=sleep
Responses
Command description
This command is used to change the operation modes of I/O-BOX devices. You can put an I/O-BOX
into the SLEEP mode for a predefined length of time. By default, each I/O-BOX connected to the
MAMBO2-UXFS runs in continuous mode.
Parameter description
<index>
Determine which IO-BOX should be set to sleep. It ranges from 0...5. The number of IEEE
devices that can be connected to the MAMBO2-UXFS is limited to 6. The index must be in the
range 0 through 5. Please enter the index of an IO-BOX that is already connected to the
MAMBO2-UXFS device. The index of a IO-BOX device is assigned in the configuration
parameter IEEE.IOBOX<index> during the connection process.
<mode>
Define the operation mode of the IO-BOX. Following operation modes are available:
Value
Meaning
run
Continues operation.
doze
Normal power saving (drops into the doze mode - current consumption in
this mode is higher than in sleep).
sleep
Maximum power saving (puts the device into sleep mode).
3.2.9.2.3
IEEE.IOBox<index>.bat.level - Gets battery charge state
Command syntax
$PFAL,IEEE.IOBOX<index>.bat.level
Examples
$PFAL,IEEE.IOBOX3.bat.level
Responses
Command description
This command is used to read out the state of the internal AAA batteries on an I/O-BOX device.
Following values can be received:
00
Critical
01
Low
02
Medium
03
High
Parameter description
<index>
Determine the IO-BOX device to be queried. The number of IEEE devices that can be
connected to the MAMBO2-UXFS is limited to 6. The index must be in the range 0 through 5.
Please enter the index of an IO-BOX that is already connected to the MAMBO2-UXFS device.
The index of a IO-BOX device is assigned in the configuration parameter IEEE.IOBOX<index>
during the connection process.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 169 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.2.10
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
"BT" command type
(BT option is only available for the MAMBO2-UXFS)
Your MAMBO2-UXFS integrates the Bluetooth technology that allows you to use other Bluetooth
wireless devices, such as headset and Hands-free kit, and receive your voice calls on them over a radio
link instead of a cable. Before you create a connection between MAMBO2-UXFS and your Headset, you
must have the following information:
•
A MAMBO2-UXFS with Bluetooth option (MAMBO2-UXFS-BT).
•
Address (the MAC address and pass-code) of the Bluetooth Headset device to connect to,
which must be entered into the DEVICE.BT.AUDIOGW parameter.
Detailed information can be found in the application note "AppNotesForAudioHeadSet&HandfreeSet.pdf".
3.2.10.1
BT.Audio.Bound - Pairs Bluetooth audio devices
Command syntax
$PFAL,BT.Audio.Bound
Examples
$PFAL,BT.Audio.Bound
Command description
This command is used to pair your MAMBO to a Bluetooth headset. After the devices are paired
they enter automatically into a connected state. So it is not required to execute the command
BT.Audio.Connect. Pairing process is done automatically based on the address and PIN code given
(stored) in the parameter DEVICE.BT.AUDIOGW. You need to set the target Bluetooth headset
into the pairing mode before executing the Bound command. How to do it, refer to your headset
Users's Manual.
Parameter description
none
3.2.10.2
BT.Audio.Connect - Places both Bluetooth devices in connection mode
Command syntax
$PFAL,BT.Audio.Connect
Examples
$PFAL,BT.Audio.Connect
Command description
This command is used to open a Bluetooth audio connection.
Parameter description
none.
3.2.10.3
BT.Audio.Disconnect - Closes a currently open audio connection
Command syntax
$PFAL,BT.Audio.Disconnect
Examples
$PFAL,BT.Audio.Disconnect
Command description
This command is used to close an opened Bluetooth audio connection.
Parameter description
none.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 170 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Defining configuration settings
This chapter will give you an overview of the device configuration settings that can be stored in the nonvolatile FLASH memory. The saved settings remain available in the device even when the device is
turned off. In the the next sections below you will find all configuration parameter names grouped by
major category. For example, chapter 3.3.1, "DEVICE parameters" lists all parameter names belonging
to the category "Device" while chapter 3.3.2, "DISP Parameter" lists all parameter names belonging to
the category "Display".
Each configuration setting that will be sent to the device should start with the " $PFAL,Cnf.Set"
characters followed by the parameter name you want to modify and a checksum (configuration
dependent) and terminated by a carriage return/line feed. To configure a MAMBO2-B6/UXFS device,
you have to enter a parameter name with its settings into the command "$PFAL,Cnf.Set,<parameter>"
and transmit it via SMS, TCP, USB or Bluetooth to the device. After applying the configuration, the
MAMBO2-B6/UXFS device will reply with either SUCCESS or ERROR followed by several textual
messages. The checksum is DEVICE.PFAL.SEND.FORMAT configuration dependant. The checksum in the
examples given in the next sections is not used (it is omitted).
Depending on the configuration you want to store in the device, the MAMBO2-B6/UXFS provides three
different types of configuration settings:

User Settings
Factory settings
 Default settings

Setting types
User Setting
Factory Setting
Default Setting
Meaning
This type stands for special configuration settings made by the user. This configuration is modified by the
user.
This type consists of the configuration settings preloaded at the factory in the MAMBO2-B6/UXFS device
giving you the possibility to test and show you how the MAMBO2-B6/UXFS works. This configuration is
usually loaded at the factory in the device as User Settings to make your device work. To remove the User
Settings and keep only Factory Settings use the command PFAL,Sys.Device.FactoryReset
This type of settings belong to the basis settings of the device needed during the start up. Default settings
are always called up, if there are no settings available in the User Settings.
Remark: The settings available in the Default Setting can be modified, but not deleted.
Table 9:
Setting types that are provided by the MAMBO2-B6/UXFS.
 Important: The maximum number of characters specified in a single command line that
starts with "$PFAL,Cnf.Set" is limited to 1500. More than 1500 characters per
command line will be ignored.
 Important: parameters names which are not supported by the device or are not written
as given in this document (in upper case letters) will still be stored in the device but
never used. These settings are considered as special user-settings – but do not belong
to the device settings. All configuration parameter names supported by MAMBO2B6/UXFS are case sensitive.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 171 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DEVICE parameters
3.3.1.1
DEVICE.NAME
Parameter syntax
DEVICE.NAME=<name>
This parameter sets the name of the MAMBO2-B6/UXFS device. When the device sends an SMS
message to a phone number or logs in to a remote server, it identifies itself using this name.
<name>
Define a name for the MAMBO2-B6/UXFS device. The default name is "unnamed MAMBO2B6/UXFS".
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.NAME=M2-John
Get configuration
$PFAL,Cnf.Get,DEVICE.NAME
3.3.1.2
DEVICE.CMD.PFAL.EN
Parameter syntax
DEVICE.CMD.PFAL.EN=<hex_value>
This parameter selects the channels you want to access the MAMBO2-B6/UXFS device by PFALCommands.
<hex_value>
Define the communication channels, in hex without leading "0x", to enable receiving of PFALCommands. By default this value is set to "F" - means that all channels are selected. The
following hex values are supported:
Value
Meaning
0x01
Enables receiving of PFAL-Commands sent via the Bluetooth channel.
0x02
Enables receiving of PFAL-Commands sent via the data call (CSD).
0x04
Enables receiving of PFAL-Commands sent via TCP.
0x08
Enables receiving of PFAL-Commands sent via SMS .
How to sent/get the configuration:
Set configuration
Get configuration
$PFAL,Cnf.Set,DEVICE.CMD.PFAL.EN=7 // only Bluetooth, CSD and TCP are enabled
$PFAL,Cnf.Get,DEVICE.CMD.PFAL.EN
Notes
• To enable more communication channels, enter the sum of channels into the <hex_value>
entry, for example:
−
hex C means: SMS+TCP communication channels are enabled, while all others
are blocked. The hex value "F" enables all channels.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 172 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.1.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DEVICE.COMM.<interface>
Parameter syntax
DEVICE.COMM.<port>=<mode>,<output_protocols>
There are two modes, Command and Data mode, in which your MAMBO2-B6/UXFS device may
operate. This configuration parameter is used to define the communication mode on the specified
port (Bluetooth, USB, USB, CSD or TCP). When the specified port is in command mode, any
characters sent to this port are interpreted as PFAL-Commands for the device to execute. PFALCommands are preceded by the letters '$PFAL'. For example, if the MAMBO2-B6/UXFS receives
'$PFAL,Sys.Device.Shutdown' while in command mode, it interprets that as an instruction to
shutdown the system immediately. While in command mode, the device may send responses back
to the port. When your MAMBO2-B6/UXFS is in data mode, any characters received by the device
over the specified <port> are intended to be forwarded to the forwarding channel
<forward_channel>. So you may send a string from the TCP port and output (forward) this string
the USB port without processing that string by the MAMBO2-B6/UXFS device.
<port>
Selects which port should be configured. It can be set to:
Value
Meaning
SERIAL
Bluetooth port (MAMBO2-UXFS only).
USB
USB port.
CSD
CSD channel
TCP.CLIENT
TCP channel
<mode>
Set the communication mode on the selected port. It can be set to:
Value
cmd
Meaning
Places the selected port in command mode. Everything received on this
port is processed as a PFAL-Command and responses are returned back to
the selected port. However, if <output_protocols> is greater than 0, all
selected messages will be continuously transmitted through the selected
<port>.
data=<forward_channel>,<event_mode> Places the selected port in data mode.
Everything received on this port is redirected to the specified forward
channel <forward_channel> without processing any of them. In this mode
the user may use any string without leading “PFAL” (e.g. control peripheral
devices connected to MAMBO2-B6/UXFS via CSD, TCP, Bluetooth or USB ). If the
<event_mode> is set to 1, then every incoming string on the selected port
that is terminated by <CRLF> characters cause the MAMBO2-B6/UXFS
device to generate the event " Sys.eSerialData". However, if
<output_protocols> is greater than 0, the selected messages will be
transmitted continuously through the selected < port>. See also chapter
7.9, page 341 as a reference.
<forward_channel>
Specify, in hex, the channel to forward the data received from the
selected <port>. Without leading “0x“ specify the forward channels:
Subvalue
Meaning
0x01
Forwards received data to the Bluetooth port
(MAMBO2-UXFS only).
0x02
Forwards received data to the CSD channel.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 173 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
0x04
Forwards received data to the TCP channel.
0x08
Forwards received data to the USB channel.
<event_mode>
Define whether the Sys.eSerialData should be occurred when strings
terminated by <CRLF> characters are detected on the serial line traffic.
Without leading “0x“, specify whether to enable or disable the event
notifications on the selected port:
Value
Meaning
0x0
Disables event notification.
0x1
Enables event notification (more about this
event, see section 3.4.1.5). The event
Sys.eSerialData can be used to execute other
commands.
For example:
- Report the string terminated by
characters (e.g. SMS, CSD, TCP etc).
- or store that string into the history.
<CRLF>
<output_protocols>
Without leading “0x“, specify what protocols should be transmitted each second to the
forwarded channel <forward_channel> or selected port. Enter the sum of the messages to be
transmitted.
Value
Meaning
0x01
Transmits GPSTATE.
0x02
Transmits GPERROR.
0x04
Transmits GPACTION.
0x08
Transmits GPEVENT.
0x010
Transmits protocols (GGA, RMC.., switched on with the configuration
PROT.<message_id>).
0x020
Data Transfer (interface shows data being transferred from other
interfaces in data transfer mode).
0x040
Data Output (interface shows data being created by commands like
MSG.Send.Serial etc.).
0x080
Reserved.
How to sent/get the configuration:
Set configuration
Get configuration
$PFAL,Cnf.Set,DEVICE.COMM.SERIAL=cmd,F
$PFAL,Cnf.Set,DEVICE.COMM.SERIAL=data=4,0,F
$PFAL,Cnf.Set,DEVICE.COMM.SERIAL=data=4,1,F
$PFAL,Cnf.Set,DEVICE.COMM.USB=cmd,F
$PFAL,Cnf.Set,DEVICE.COMM.CSD=cmd,60
$PFAL,Cnf.Set,DEVICE.COMM.TCP.CLIENT=cmd,0
$PFAL,Cnf.Get,DEVICE.COMM.SERIAL
$PFAL,Cnf.Get,DEVICE.COMM.USB
$PFAL,Cnf.Get,DEVICE.COMM.CSD
$PFAL,Cnf.Get,DEVICE.COMM.TCP.CLIENT
//command mode
// no event generation
// with event generation
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 174 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.1.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DEVICE.STARTUP.QUIET
Parameter syntax
DEVICE.STARTUP.QUIET=<mode>
By default, when you turn on/off your MAMBO2-B6/UXFS, a beep tone is generated. For some
security applications this feature is undesired. Using this parameter you are able to deactivate such
beep tones by setting the device into the quiet mode during boot and shutdown. Changes to this
configuration parameter affects the device immediately.
<mode>
Define in which mode the device should be set when booting up or shutting down. It can be
set to:
Value
Meaning
Enables quiet mode. This setting does not effect muting and volume
on
control of the speaker; you will still hear ring tone when an incoming
call is detected. However, if you want to switch your MAMBO2B6/UXFS into the listen-in mode, then you have also to mute the
speaker using the command GSM.Audio.SpeakerMute=1.
Disables quiet (silent) mode. Beep tones are generated during shutting
down or booting up. If the speaker is muted disabled
(GSM.Audio.SpeakerMute=1), and you want to use it then enable it by
setting its value to 0.
off
How to set/get device configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.STARTUP.QUIET=on
Get configuration
$PFAL,Cnf.Get,DEVICE.STARTUP.QUIET
3.3.1.5
DEVICE.IGNTIMEOUT
Parameter syntax
DEVICE.IGNTIMEOUT=<time_out>
This parameter is used to define the maximal time to wait before the device goes to sleep. This
time out starts when the command $PFAL,Sys.Device.Sleep is executed. When this time out
expires, the device clears all unsent messages and enters sleep mode immediately.
<time_out>
Define the maximal time, in milliseconds, before the device goes to sleep. Within this timeout
the device tries to execute all alarms, sends TCP messages, SMS etc. and when timeout
expires, the device cancels all processes and goes to sleep. The default timeout is 6000
milliseconds.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.IGNTIMEOUT=60000
Get configuration
$PFAL,Cnf.Get,DEVICE.IGNTIMEOUT
Notes
• Before MAMBO2-B6/UXFS goes to sleep or resets, it calls the <time_out> value and
prepare itself to enter sleep mode. Within this timeout the system tries to release all
actions activated by the "Sys.Device.eShutdown" event. Once the timeout <time_out>
exceeds the device cancels all other processes, even if there are still actions to be released,
and goes to sleep. However, if all processes are done before the time out expires, then the
device goes to sleep without waiting of time out.
• The system goes to sleep immediately, if the <time_out> value is set to 0 (zero).
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 175 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.1.6
Parameter syntax
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DEVICE.PROT.BINARY
DEVICE.PROT.BINARY=<id>[,<id>]
This parameter is used to define which protocols should be reported when the PFAL-Command
$PFAL,MSG.Send.<channel>,8000,"test" is received by the device.
<id>
Specify which data should be added to the protocol FDB with ID 8000. It can be to:
Value
Meaning
0x01
Binary RMC,
0x02
Motion sensor data,
0x03
Trip data (incl: mode, state, distance, duration, hight),
0x04
(if available) ANT Heartbeat data - including: state, min. max & current
values),
0x05...0x256
Reserved.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.PROT.BINARY=1,2,3,7
Get configuration
$PFAL,Cnf.Get,DEVICE.PROT.BINARY
3.3.1.7
Parameter syntax
DEVICE.KEYTONE
DEVICE.KEYTONE=<tone>
This parameter is used to activate or deactivate the key tones. By default, the key tone is turned
on.
<tone>
Determine whether to turn on or off the key tone. It can be set to:.
Value
Meaning
on
(Default) Key Tone will be heard when you press a key on the MAMBO2B6/UXFS device.
off
No Key Tone will be heard when you press a key on the MAMBO2-B6/UXFS
device.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.KEYTONE=off
Get configuration
$PFAL,Cnf.Get,DEVICE.KEYTONE
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 176 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.1.8
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DEVICE.BEEPTONE
Parameter syntax
DEVICE.BEEPTONE=<beep>
This parameter is used to activate or deactivate the beep tones. By default, the beep tone is turned
on.
<beep>
Determine whether to turn on or off beep tones. It can be set to:.
Value
Meaning
on
(Default) Beep Tones will be heard when executing the PFAL command in
chapter 3.2.4.2
off
No Beep Tone will be heard when executing the PFAL command in chapter
3.2.4.2.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.BEEPTONE=on
Get configuration
$PFAL,Cnf.Get,DEVICE.BEEPTONE
3.3.1.9
DEVICE.PHONR
Parameter syntax
DEVICE.PHONR=<number>
This parameter is used to enter the MAMBO2-B6/UXFS phone number or any desired text or
number.
<number>
Specify, max. 20 digits/chars, the phone number of your MAMBO2-B6/UXFS or any desired
number or text. This specified phone number will be shown on the Device Info dialog box.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.PHONR=0049111000111
Get configuration
$PFAL,Cnf.Get,DEVICE.PHONR
3.3.1.10
Parameter syntax
DEVICE.GSM.STARTUP
DEVICE.GSM.STARTUP=<start>
This parameter is used to turn on or off the GSM engine. By default, the GSM engine is turned on.
Changes to this configuration are done immediately. You can also GSM engine manually turn on or
off by using the commands "Sys.GSM.Enable" or "Sys.GSM.Disable".
<start>
Determine whether to turn on or off the GSM engine. It can be set to:.
Value
Meaning
on
(Default). Turns on the GSM engine immediately. All GSM/GPRS/TCP
related services are available. Returns Error if GSM module is already on.
off
Turns off the GSM engine immediately. All GSM/GPRS/TCP related services
are not available (no SMS, TCP messages can be sent)
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.GSM.STARTUP=on
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 177 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
$PFAL,Cnf.Get,DEVICE.GSM.STARTUP
Get configuration
Notes
• Note that all GSM related PFAL commands will not be executed or might result errors and
state queries (including IMEI, SIMID OwnNumber etc.) will not work, if GSM engine is not
properly initialized and running.
3.3.1.11
DEVICE.GPS.STARTUP
Parameter syntax
DEVICE.GPS.STARTUP=<control>
This parameter is used to turn on or off the GPS engine. By default, the GPS engine is turned on.
Changes to this configuration are immediately done. You can also GPS engine manually turn on or
off by using the commands "Sys.GPS.Enable" or "Sys.GPS.Disable".
<control>
Determine whether to turn on or off the GPS engine. It can be set to:.
Value
Meaning
on
(Default). Turns on the GPS engine immediately (device is able to acquire
GPS signals). Returns Error if GSM module is already turned on.
off
Turns off the GPS engine immediately (device is unable to acquire GPS
signals while remaining turned off).
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.GPS.STARTUP=on
Get configuration
$PFAL,Cnf.Get,DEVICE.GPS.STARTUP
3.3.1.12
Parameter syntax
DEVICE.GPS.AUTOCORRECT
DEVICE.GPS.AUTOCORRECT=<type>,<max_pdop>,<max_speed>,<allowed_dist_error>,<dropcount>,
[<max_acceleration>],[dynamic=<dynamic_tolerance>,<dynamic_interia>]
This parameter contains a number of specified conditions that the device will use to control
incoming of GPS positions and calculate a valid GPS fix. The specified values have no influence on
how the built-in GPS receiver actually computes its positions. The parameters specified here filter
the GPS position coordinates coming from the GPS receiver and change those positions from active
"A" to invalid "V" if disagreements with your specified condition are met. An "A" in a GPRMC
protocol indicates that the device has currently a GPS fix, whereas a value of "V" indicates the
device does NOT have currently a GPS fix.
<type>
Determine whether or not to activate the GPS auto correction. It can be set to:
Value
Meaning
on
Activates filtering of the incoming GPS positions from the GPS receiver.
off
Default value. Deactivates filtering of these incoming GPS positions.
<max_pdop>
Specify a suitable maximum PDOP (Position Dilution of Precision) value that the device will use
for the GPS positions. This value will depend on the environment in which you are using the
MAMBO2-B6/UXFS device. For example, a PDOP of 5.0 could be appropriate when using the
device in an open area but may be too low when using it in an urban environment. In general,
a maximum PDOP value of 6.0 or 7.0 is acceptable. The default value is 5.0. Floating point
numbers are also allowed e.g. 5.8.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 178 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
<max_speed>
Specify a suitable maximal speed limit in meter per second (m/s) that the device will use to
filter the incoming GPS position and calculate a valid GPS fix. Any speed exceeding the
specified value will be ignored (i.e. no GPS position will be computed from this GPS record).
Default value is 127.
<allowed_dist_error>
Specify a suitable maximal distance error in meters that the device will use to filter the
incoming GPS position and calculate a valid GPS fix. Prior GPS records are analysed. According
to their speed value, a distance is computed and compared to the distance between the
current and last (corrected) GPS records. The difference of two distances must not exceed the
specified value in <dist_error>. The default value is 50.
<dropcount>
Specify how many incoming „wrong" GPS positions should be dropped until the current GPS
position is considered as inaccurate. Default value is 10.
Advantages:
Disadvantages:
Several wrong GPS positions (showing a correct PDOP and a fix) during
early startup can be in this way eliminated.
Whenever a wrong GPS position is considered as correct, it will take
<dropcount> seconds until this error is detected.
[<max_acceleration>]
This entry is optional and can be used to specify the maximum possible GPS speed that can
change from one second to the next. For example, a <max_acceleration> value of 50 rejects a
GPS speed of 100 m/s, if the prior speed value has been lower than 50 m/s. The default value
is 50 m/s.
[dynamic=<dynamic_tolerance>,<dynamic_interia>]
<dynamic_tolerance>
It specifies the PDOP value to short PDOP changes. This tolerance is a relative
value to the last received GPS position that is already considered as correct.
Whenever a GPS position is considered as correct, then the next received
position will be considered correct if it will have a PDOP value smaller than the
last received position with a value PDOP + <dynamic_tolerance>.
Example (as reference for this example is used the configuration in table
below):
Maximum DOP <max_pdop> is set to 10, <dropcount> to 10, dynamic tolerance
<dynamic_tolerance> to 3 and dynamic inertia <dynamic_inertia> to 4.
Let's suppose the last received GPS positions have had a PDOP value of 5 and
those positions are considered as correct due to the specified <max_pdop>. The
next incoming GPS positions show a reduced accuracy with a PDOP value of 9.
A dynamic tolerance of 4 would allow these positions to be considered as
correct. Because the dynamic tolerance is set to 3, these positions will be
ignored. The <dynamic_interia> setting covers this case.
<dynamic_interia>
This setting works together with the dynamic tolerance <dynamic_tolerance>
and it specifies how many GPS positions should be ignored if the difference
between the PDOP value of the previous and present position data is greater
than your specified value <dynamic_tolerance>. When the specified number of
positions is ignored, the next incoming GPS position will be considered as correct
again, if it has a DOP value that does not exceed your specified <max_pdop>. The
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 179 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
value of the <dynamic_interia> ranges from 1 to <dropcount>-1 and always it
must be smaller than <dropcount>.
Advantages and disadvantages of dynamic autocorrect:
- If the PDOP values change very often from one position to the next
received one, then the dynamic tolerance might reject most of these
positions even when their PDOP value is lower than your specified
<max_pdop>.
Let's see an example with following settings: dynamic_tolerance=3,
dynamic_inertia=3 , max_dop=10;
Let's assume that the incoming positions from the GPS receiver have DOP
values as given in the tables below and all other Autocorrect conditions
are meat.
Example 1
Position Nr.
1
2
3
4
5
6
7
8
9
DOP values
2*
6
6
3*
7
7
2*
7
7
(* positions are considered as correct)
In the example 1, all positions that have a PDOP value 6 and 7 (not
marked with asterisk [*] sign) are rejected by the system. That means:
the position 2 is rejected because the PDOP difference between the first
(already considered as correct) and second position is greater than the
specified value of the <dynamic_tolerance>=3, but the fourth position is
considered as correct because it has a PDOP value smaller than previous
(third) position and lower than <max_pdop>. If the forth position should
have had a PDOP value equal or greater than the previous rejected
position then that position would be rejected too and the next one, due
to the <dynamic_interia> value of 3, would be considered as correct
again- as shown in the next example 2.
Example 2
Position Nr.
1
2
3
4
5
6
7
8
9
10
DOP values
2*
6
6
6
6*
7*
5*
9
8*
8*
(* position considered as correct)
Due to the dynamic_inertia=3, the 5th position is considered as correct,
and the followed positions 6 and 7 are also considered as correct because
their PDOP difference to the previous position is within the tolerance and
smaller than the specified <max_pdop>.
If the PDOP values of the GPS positions increase generally (i.e. the device
is entered into an area with poor GPS signal strength), these positions are
also considered as correct.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.GPS.AUTOCORRECT=on,7.0,60,50,10
$PFAL,Cnf.Set,DEVICE.GPS.AUTOCORRECT=on,10.0,60,50,8,50,dynamic=3,4
$PFAL,Cnf.Set,DEVICE.GPS.AUTOCORRECT=off
Get configuration
$PFAL,Cnf.Get,DEVICE.GPS.AUTOCORRECT
Notes
• No invalid RMC protocols will be displayed after the first GPS fix. If GPS becomes invalid,
the corresponding event will occur – also the current state can be retrieved.
• RMC protocols always will show the last (corrected) GPS position (or an invalid GPS fix
containing zeros during early startup).
• A valid GPS-fix is DEVICE.GPS.CFG configuration-dependent.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 180 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.1.13
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DEVICE.GPS.CFG
Parameter syntax
DEVICE.GPS.CFG=<req_sat>
This parameter is used to define how many satellites should be in use to make a GPS fix valid.
<req_sat>
Define the number of satellites required for a valid GPS fix. Default value is 3. The default
value allows the MAMBO2-B6/UXFS to get a GPS fix even in areas with very bad GPS coverage.
However, it can be set to a value from 1 to 10. The higher the value, the higher is the GPS
accuracy. Furthermore, it is strongly recommended to specify either 3 or 4 satellites
depending on GPS coverage. In that case a protocol sent by the MAMBO2-B6/UXFS device is
considered as "invalid" (depending on user set value) if the device has less than 3 or 4
satellites in the NMEA sentences.
How the parameter could be sent/ and its setting requested:
Set configuration
$PFAL,Cnf.Set,DEVICE.GPS.CFG=3
Get configuration
$PFAL,Cnf.Get,DEVICE.GPS.CFG
3.3.1.14
DEVICE.GPS.TIMEOUT
Parameter syntax
DEVICE.GPS.TIMEOUT=<enable>,<timeout>,[<hard_reset>]
This parameter is used to specify a timeout after which the device should perform a GPS reset if no
valid fix available. Such a restart forces the GPS engine to start a new search for visible GPS
satellites. This setting helps to reacquire valid GPS positions in areas with very poor GPS coverage.
<enable>
Define whether to reset the GPS engine, if no GPS fix available within your specified time out.
It can be set to:
Value
Meaning
0
Disable Reset (no GPS reset is performed if the device has inv alid GPS fix
for a long time).
1
(Default). Enable Reset (forces a regular GPS reset after <timeout>)
<timeout>
The timeout, in minutes, to rest the GPS engine if no valid GPS fix is available within your
specified time out. The time out must be in the range 0 (2 for optional setting) through 45000
(> 1 month). Default timeout is 30 minutes.
[<hard_reset>]
Optional setting. It can be set to:
1
Enables (forces a hard GPS reset after <timeout>)
Using this hard reset, causes the GPS device to perform a complete restart. Under normal
conditions it shouldn’t be necessary to use this setting.
✗
It should be used if the device losses a GPS fix and didn’t regain it even after one or
several <timeout>. If a system restart will help to reobtain a valid GPS fix, you should
enable the „hard reset".
How the parameter could be sent/ and its setting requested:
Set configuration
$PFAL,Cnf.Set,DEVICE.GPS.TIMEOUT=1,30
$PFAL,Cnf.Set,DEVICE.GPS.TIMEOUT=1,30,1
Get configuration
$PFAL,Cnf.Get,DEVICE.GPS.TIMEOUT
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 181 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.1.15
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DEVICE.GPS.HEADING
Parameter syntax
DEVICE.GPS.HEADING=<value>
This setting is used to configure the GPS heading feature. The tolerance is stored into the nonvolatile memory, and will automatically be used after booting up the device. Each time the
specified angle is exceeded, the event GPS.Nav.eChangeHeading occurs, and the driving direction
resets to zero. This state is checked each second and only when the actual vehicle speed exceeds
3.6 km/h.
<value>
Define the angle, in degrees, to occur the heading event. The value must be in the range 0 (2
for optional setting) through 359.
Value
Meaning
0
Deactivates heading event.
1 ... 359
Activates heading event (see also notes below).
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.GPS.HEADING=45
Get configuration
$PFAL,Cnf.Set,DEVICE.GPS.HEADING
Notes
• It is NOT recommended to use values below 10 and above 320 degrees. The lower the
value, the more often the event occurs.
• Values above 180 degrees doesn't make much sense, the suggested value is 45° (default).
3.3.1.16
Parameter syntax
DEVICE.GPS.NAVSTATIC
DEVICE.GPS.NAVSTATIC=<state>
This read configuration parameter can be used to know whether or not the static navigation mode
is enabled. The steady state detection allows the navigating algorithms to decrease the noise in
the position output when the acceleration is below the threshold. This improves position accuracy
especially in stationary applications.
 This configuration applies to MAMBO2 devices with SiRF GPS receiver only.
Parameter description
<state>
Shows whether or not the static navigation mode is turned on. This settings should be
changed using the corresponding PFAL command and not directly via this parameter.
Value
Meaning
on
Static navigation mode is turned on. Holds the current position as fixed
when the user is in a stationary mode.
off
Static navigation mode is turned off.
How to get device configuration:
Set configuration
Use the corresponding PFAL command instead
Get configuration
$PFAL,Cnf.Get, DEVICE.GPS.NAVSTATIC
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 182 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.1.17
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DEVICE.GPS.NAVSBAS
DEVICE.GPS.NAVSBAS=<state>
Parameter syntax
This read command can be used to show whether or not the SBAS (Satellite Based Augmentation
System) operation is enabled or disabled. A GPS receiver with SBAS enabled will offer more
accurate position. The reception of SBAS messages requires that the device locks one of the GEO
satellites with SateliteID ranging from 33 to 51. These IDs are shown in the $GPGSV NMEA
protocol, if available.
 This configuration applies to MAMBO2 devices with SiRF GPS receiver only.
Parameter description
<state>
Shows whether or not the SBAS operation is activated. This settings should be changed using
the corresponding PFAL command and not directly via this parameter.
Value
Meaning
on
SBAS operation enabled.
off
SBAS operation disabled.
How to get device configuration:
Set configuration
Use the corresponding PFAL command instead
Get configuration
$PFAL,Cnf.Get, DEVICE.GPS.NAVSBAS
3.3.1.18
DEVICE.PFAL.SEND.FORMAT
Parameter syntax
DEVICE.PFAL.SEND.FORMAT=<start_txt>,<checksum>,<end_txt>,<end_msg>
This parameter is used to freely modify the syntax of the messages sent out with PFAL command
MSG.Send…., making them easier to quickly identify parts of the message and select them for
further use. It allows to define the start and end characters for the protocols specified in the
<protocols> entry and user text <"text">. It affects the syntax of all messages that will be sent from
the MAMBO2-B6/UXFS via Bluetooth, USB, CSD, TCP and SMS.
For example:
Configuration Format: $PFAL,Cnf.Set,DEVICE.PFAL.SEND.FORMAT="$",CKSUM,"#","<end>"
Command Execution: $PFAL,MSG.Send.USB,8,"Current speed &(Speed)"
Command Response: $Current speed 0*1E#
$GPRMC,065545.000,A,5040.4095,N,01058.8587,E,0.03,0.00,280610,,*0D#
<end>
<start_txt>
Define the start characters for the specified user text (max. 10 chars). Each protocol specified
by the <protocols> field gets the <start_txt> characters as its first character. Furthermore, the
<"text"> defined by MSG.Send gets the <start_txt>, too.
By default, this parameter is set to $-character. Keep in mind, the use of the $-character inside
an SMS text might be misinterpreted. This depends on the receiving modem.
<checksum>
By default, this parameter is set to CKSUM. It can be set to:
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 183 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Value
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Meaning
CKSUM
Adds a NMEA compatible checksum at the end of text section (=default).
Note that, the checksum is computed for text only and not for a possibly
defined <start_txt> before. If protocols are specified within the MSG.Send
command then all protocols will be sent in the format, for example,
$GPRMC....*CS including „$" and checksum „*CS"
NOCKSUM
No checksum is added after user defined text. If protocols are specified
within the MSG.Send command then all protocols will be sent in the
format, for example, GPRMC.... excluding „$" and checksum „*CS". This
format is suited for SMS communication service as some modems, expect
the MAMBO2-B6/UXFS, could not receive correctly the $- dolar sign.
<end_txt>
Define the end characters for the specified user text (max. 10 chars). A CRLF will be added
automatically at the end of the defined „end characters".
<end_msg>
Define the end characters to complete the message (max. 10 chars) (by default it is set to
$<end> allowing syntax compatibility to the PFAL responses). The CRLF will be added
automatically at the end of the defined „end message"
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.PFAL.SEND.FORMAT="$",CKSUM,"","<end>"
Get configuration
$PFAL,Cnf.Get,DEVICE.PFAL.SEND.FORMAT
Notes
• Depending on the syntax you have selected, the reports of the command MSG.Send….
change the syntax as follow.
For example, you have configure the MAMBO2-B6/UXFS to output its position periodically
to the serial interface using:
$PFAL,MSG.Send.Serial,8,"MAMBO2-B6/UXFS outputs its GPS positions"
and you have selected the following format syntax:
$PFAL,Cnf.Set,DEVICE.PFAL.SEND.FORMAT="$",CKSUM,"","<end>"
The reports of that command is shown below:
$MAMBO2-B6/UXFS outputs its GPS positions<CRLF>
$GPRMC....*21<CRLF>
<end><CRLF>
If you have selected the following format syntax:
$PFAL,Cnf.Set,DEVICE.PFAL.SEND.FORMAT="$",CKSUM,"&","<end>"
The reports of that command is shown below:
$MAMBO2-B6/UXFS outputs its GPS positions&<CRLF>
$GPRMC.... *21&<CRLF>
<end><CRLF>
This command syntax will be applied to all protocols and user text specified in the PFAL
command MSG.Send.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 184 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.1.19
Parameter syntax
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DEVICE.IEEE.STARTUP
DEVICE.IEEE.STARTUP=<control>
(IEEE option is only available for the MAMBO2-UXFS)
This parameter is used to control the operation of the IEEE module which is not available in the
MAMBO2-UXFS standard version. The IEEE module is a hardware option for the MAMBO2-UXFS
device and this parameter will return an error if the IEEE module is not available. It switches on and
off the IEEE module.
<control>
Determine whether to switch on or off the IEEE module during start-up. It can be set to:
Value
Meaning
on
Switched on during start-up (default).
off
Switched off during start-up.
How to set/get device configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.IEEE.STARTUP=on
Get configuration
$PFAL,Cnf.Get,DEVICE.IEEE.STARTUP
3.3.1.20
Parameter syntax
DEVICE.BT.STARTUP
DEVICE.BT.STARTUP=<control>
(BT option is only available for the MAMBO2-UXFS)
This parameter is used to control the operation of the Bluetooth module which is not available in
the MAMBO2-UXFS standard version. The Bluetooth module is a hardware option for the
MAMBO2-UXFS device and this parameter will return an error if the Bluetooth module is not
available. It switches on and off the built-in Bluetooth module.
<control>
Determine whether to switch on or off the Bluetooth module during start-up. It can be set to:
Value
Meaning
on
Switches on during start-up (default).
off
Switches off during start-up.
How to set/get device configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.BT.STARTUP=on
Get configuration
$PFAL,Cnf.Get,DEVICE.BT.STARTUP
3.3.1.21
Parameter syntax
DEVICE.BT.LOCALNAME
DEVICE.BT.LOCALNAME=<name>
(BT option is only available for the MAMBO2-UXFS)
This parameter is used to define a name for your MAMBO2-UXFS Bluetooth device.
<name>
String type. Define the name, which will be displayed by other Bluetooth device when a
Bluetooth connection has been established.
Default name for Bluetooth services is "MAMBO2".
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 185 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
How to set/get device configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.BT.LOCALNAME=MAMBO2
Get configuration
$PFAL,Cnf.Get,DEVICE.BT.LOCALNAME
3.3.1.22
DEVICE.BT.AUDIOGW
Parameter syntax
DEVICE.BT.AUDIOGW=<MAC_address>,<passkey>
(BT option is only available for the MAMBO2-UXFS)
MAMBO2-UXFS provides the Audio Gateway Service to support the Headset Profile and the HandsFree Profile on the device. This parameter allows you to configure the Audio Gateway service, link
your MAMBO2-UXFS and headset before you can make a voice call. Your MAMBO2-UXFS will save
your headset MAC address (if known) and Bluetooth PIN Code, and will connect automatically to
your headset when it is required. Bluetooth protocol puts itself in a disconnected state when
DEVICE.BT.AUDIOGW is received. In this case you need to reconnect, if you are communicating via
Bluetooth serial channel.
<MAC_address>
Specify the MAC address (12 byte long) of the Bluetooth headset to be used. It can be set to 0
if unknown. By default it is set to 0.
<passkey>
Specify the passkey for the Bluetooth headset. A passkey is a code that is used to control
access to a Bluetooth device (headset). However, the headset that you want to connect to
may not require a passkey, please refer to the manual of the used headset. Entering of the
passkey also affects the passkey that is presently used for the Bluetooth data connection. That
means, when you reconnect the MAMBO2-UXFS to your PC you have to enter this passkey for
pairing with the device instead of the prior one.
By default it is set to 0000.
How to set/get device configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.BT.AUDIOGW=32414124,0000
Get configuration
$PFAL,Cnf.Get,DEVICE.BT.AUDIOGW
3.3.1.23
Parameter syntax
DEVICE.ANT.STARTUP
DEVICE.ANT.STARTUP=<mode>
(ANT option is no longer available)
This parameter is used to control the operation of the ANT module which is not available in the
MAMBO2-UXFS standard version. The ANT module is a hardware option for the MAMBO2-UXFS
device and this parameter will return an error if the ANT module is not available. It turns on or off
the ANT module inside the MAMBO2-UXFS. You can also turn on and off the ANT module via menu
(SHUTDOWN-view) on the GUI. Once the ANT module is turned on it starts searching for nearby
ANT devices (chest strap). On the Heart-view is displayed "searching". The ANT device supplied
with MAMBO2-UXFS-AN is called "Heart Rate Strap". This is a large elasticized strap that goes
around your chest. The heart rate strap has two built-in sensors and in the center of this strap is a
transmitter, which picks up your heartbeat and transmits it to the MAMBO2-UXFS-AN. MAMBO2UXFS-AN picks up and displays the received data as a numeric value (e.g. 130 beats per minute) on
the Heart-view. The minimum and maximum values (beats per minute) can be adjusted with
DEVICE.ANT.HEARTBEAT=<min>,<max>.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 186 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
<mode>
Determine whether to turn on or off the ANT module inside the MAMBO2-UXFS. This setting
is also called during the device boots up. It can be set to:
Value
Meaning
on
Turns on the ANT module (default).
off
Turns off the ANT module.
How to set/get device configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.ANT.STARTUP=on
Get configuration
$PFAL,Cnf.Get,DEVICE.ANT.STARTUP
3.3.1.24
Parameter syntax
DEVICE.ANT.HEARTBEAT
DEVICE.ANT.HEARTBEAT<index>=<min>,<max>[,<name>]
(ANT option is no longer available)
This parameter is used to limit the heartbeat range using the min. and max. values. Any value less
than the minimum or greater than the maximum will count as a disagreement and the system will
raise the heartbeat event.
<index>
Set a number from 0 to 2 to define your heartbeat profile. These profiles are listed on the ANT
screen and you can then select one.
<min>
Define the minimum value of the beats per minute. It ranges from 0..100. Any value less than
the minimum raises the heartbeat event.
<max>
Define the maximum value of the beats per minute. It ranges from 60..200. Any value greater
than the maximum raises the heartbeat event.
[<name>]
Set the profile name for the entered min. and max. values. On the screen of the MAMBO2UXFS with ANT option, you can then select your personal training profile you want to use.
Different min. and max. values may correspond to different training profiles.
How to set/get device configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.ANT.HEARTBEAT=60,80
Get configuration
$PFAL,Cnf.Get,DEVICE.ANT.HEARTBEAT
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 187 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.1.25
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DEVICE.ANT.CHANNEL
Parameter syntax
DEVICE.ANT.CHANNEL<index>=<Sensor>,<NetNr>,<NetType>[,<msgperiod>,<chRF>,<nwkey>]
(ANT option is no longer available)
If you want to use an ANT Sensor with MAMBO2-UXFS, the device has to be paired to work
together with your MAMBO2-UXFS. This parameter is used to define different configuration
profiles for using different ANT sensors with the MAMBO2-UXFS. When you want to pair a sensor
with the MAMBO2-UXFS, make sure that no other sensors from the same type are in the near of
MAMBO2-UXFS device. Such devices may affect pairing or will not allow to connect the right
sensor to the MAMBO2-UXFS.
<index>
Define the channel index, from 0 to 3, to specify the ANT sensor properties.
<Sensor>
Define the sensor type you want to use. The following sensor names are supported by
MAMBO2-UXFS:
Value
Meaning
CADENCE
Set this type when using a cadence bike sensor,
SPEED
Set this type when using a speed bike sensor,
HEART
Set this type when using a heart rate strap sensor,
RAW
Set this type when using any other sensor.
<NetNr>
Set the network number for the specified sensor type. This entry is automatically updated by
the system rather than by user. When pairing a sensor for the first time, set this value to 0.
<NetID>
Set the network ID for the specified sensor type. This entry is automatically updated by the
system rather than by user. When pairing a sensor for the first time, set this value to 0.
<NetType>
Set the network type for the specified sensor type. This entry is automatically updated by the
system rather than by user. When pairing a sensor for the first time, set this value to 0.
[<msgperiod>]
Define how often the sensor from the type "RAW" should send its data to the MAMBO 2.
[<chRF>]
Set the frequency channel on which the sensor from the type "RAW" will send its data.
[<nwkey>]
Set the network key that the specified sensor type uses. If the specified sensor type dose not
use any key, then set it to 0.
How to set/get device configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.ANT.CHANNEL0=HEART,0,0,0
Get configuration
$PFAL,Cnf.Get,DEVICE.ANT.CHANNEL0
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 188 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.1.26
Parameter syntax
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DEVICE.BIKESPEED.CIRCUM
DEVICE.BIKESPEED.CIRCUM=<radius>
(ANT option is no longer available)
This parameter is used to specify the circumference of the bicycle wheel to calculate the speed of
the bicycle.
<radius>
Specify, in centimeter, the circumference of the bicycle wheel.
How to set/get device configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.BIKESPEED.CIRCUM=210
Get configuration
$PFAL,Cnf.Get,DEVICE.BIKESPEED.CIRCUM
3.3.1.27
Parameter syntax
DEVICE.HEARTBEAT.PROFILE
DEVICE.HEARTBEAT.PROFILE=<index>
(ANT option is no longer available)
This parameter is used to activate an already configured heartbeat profile.
<index>
Define the index, from 0 to 2, of the heartbeat profile to be activated. The heartbeat profiles
are configured with DEVICE.ANT.HEARTBEAT.
How to set/get device configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.HEARTBEAT.PROFILE=1
Get configuration
$PFAL,Cnf.Get,DEVICE.HEARTBEAT.PROFILE
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 189 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DISP Parameter
Parameter DISP enables you to personalize the device and suit your end users needs. The display is
designed for one-handed navigation using the 5-way key and two other soft keys.
3.3.2.1
Parameter syntax
DISP.VIEWS
DISP.VIEWS=<views>
This parameter is used to determine the background view used for home screen and the views
displayed when navigating with 5-way key and left or right key on the MAMBO2-B6/UXFS device.
<views>
Define the symbols, in sequence separated by commas, to be added in the views you want to
create on the MAMMBO2 display. The figure below represents all symbols supported by the
MAMBO2-B6/UXFS device. Some views do not display an values depending on the hardware
options you have ordered with MAMBO2-B6/UXFS. A view on the MAMBO2-B6/UXFS is
represented by 4 boxes (see figure below). In each box you can add a symbol that is selected
by a value listed below. The corresponding symbols are represented on the figure below.
Value
Meaning
0
Empty symbol.
1
Battery info symbol. The symbol background provides information about
the battery charge level: Green=Full charged; Red=Battery low;
2
Network and GSM info symbol. The symbol background provides
information about the GSM and TCP connection state. Red= GSM module
is off; Blue=Registered into the GSM network; Green= TCP connected;
3
GPS info symbol. Provides the number of GPS satellites in use. The symbol
background provides information about GPS validity state. Red=GPS
module is off; Blue=Searching for GPS satellites; Green=valid GPS fix.
4
Device info symbol. Provides information about the device name, phone
number and running modules in the device such as: GSM, GPS, IEEE, ANT
and Bluetooth.
5
Keylock symbol. Allows the user to activate the keylok function for
avoiding accidental pushing of any buttons and executing false alarms.
6
Shutdown symbol. Allows the user to turn off the MAMBO2-B6/UXFS
device.
7
Settings symbol. Allows the user to customize your personal tracker and
change the settings related to each available option (enable or disable the
built-in modules, display and phone properties, activate or deactivate
motion and vibration alerts, ring volume, key tone etc.).
8
Phonebook symbol. Provides access to the phone book entries.
9
Call history symbol. Allows the user to get access to the call history list.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 190 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
10
Dialing symbol. Allows to enter and dial any phone number. If you want to
restrict user from making unauthorised telephone calls do not show this
symbol on the display.
11
Message symbol. Allows the user to get access to all received SMS and
server related messages. Allows to answer any incoming message using
up to 4 predefined text messages.
12
Credit balance symbol. Allows the user to query the state of account
(balance) when using a prepaid SIM card.
13
Trip symbol. Allows the user to record separately trip activities for later
analysis. Provides different recording profiles while moving. It also
provides information about the previous traveled routes.
14
Lamp symbol. Allows the user to turn the screen of the device completely
white allowing to find the location of keyholes in darkness.
15
SOS symbol. Activates an SOS alarm when pressed.
16
Falling symbol. Currently no functions are implemented.
17
Tilt alarm symbol. Allows the user to calibrate and activate the tilt alarm.
18
Sliding symbol. Allows the user to run the selected views in a continuous
slide show.
19
Height symbol. Allows the user to get displayed the actual height level
above the see level that is determined from the GPS signals. The unit of
the height is selectable.
20
Speed symbol. Allows the user to get displayed the actual speed that is
determined from the GPS signals. The unit of the speed is selectable.
21
Waypoint symbol. Allows the user to get displayed the direction and the
distance to the destination waypoint. Allows the user to set markers and it
offers the opportunity to navigate from point-to-point.
22
ANT option is no longer available.
23
Date symbol. Allows the user to get displayed the current date and time.
24
User menu symbol. Allows to create own menu (for detailed information,
refer to the chapter 3.3.2.2, DISP.MENU<index>).
25
Follow symbol. Allows the user to follow another MAMBO2-B6/UXFS or
FALCOM tracing device. It shows the direction and distance to the selected
device.
40..43
User menu icons. If one of these icons is pressed, the corresponding event occurs.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 191 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
How to set/get display configuration:
$PFAL,Cnf.Set,DISP.VIEWS=2,1,3,15 // Creates just one view with 4 symbols
Set configuration
$PFAL,Cnf.Set,DISP.VIEWS= 2,1,3,15,5,7,6,4 //Creates 2 views with 8 symbols
$PFAL,Cnf.Set,DISP.VIEWS= 2,1,3,15,5,7,6,4,8,10,9,11 //Creates 3 views with 12 symbols
Get configuration
3.3.2.2
Parameter syntax
$PFAL,Cnf.Get,DISP.VIEWS
DISP.MENU<index>
DISP.MENU<index>=<name>:<command>
This parameter is used to simply add items directly into the user menu or submenu and control
your device per key press. Each menu item can either be a command for your application or a
parent menu for other submenu items. Each menu (primary) can contain a set of submenus (first
level), which may contain further set of submenus (second level). With the five-way key you can
then navigate each user menu directly and confirm your choice or select an option. To remove an
item from a menu or submenu, just specify the index of the menu or submenu item and send it to
the device excluding the equal sign "=" and other settings.
<index>
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 192 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Chooses the location of a menu item or the location of a first and second level submenu item.
A submenu is a menu that opens when a menu item is selected/pressed. You can have a
primary menu and at most two levels of submenus.
 The maximum number of menu and submenu items is limited to 99.
The standard menu structure is as follows. This list shows the menu category and their order.
Value
Meaning
X.0 or X
Inserts a new menu item with or without a submenu into a primary menu.
X.X.0 or X.X
Assigns a first level submenu to a primary menu item with or without a
submenu into a secondary menu.
X.X.X
Assigns a second level submenu to a first level submenu item.
Where X is any of the numbers from 1 to 7. However, the maximum number of menu and submenu
items is limited to 99.
Followings are listed the differences between indices ending with or without 0.
X or X.X
Creates a menu or a first level submenu without submenu.
X.0 or X.X.0
Creates a menu or a first level submenu with submenu(s) (it is indicated by
an arrow [►] at the end of the menu or submenu).
 Note: You can not create a second level submenu without having created a first level
submenu before it. If you try to do it the second level submenu will not be shown.
<name>
Specify the text of the menu or submenu item. It is the name the user sees for this item in the
menu or submenu. The name should use a single, specific word and it should accurately
describe its content.
<command>
Specify the action (a command or set of commands excluding "$PFAL,") associated with the
menu or submenu item. The action is executed when the user activates that menu or
submenu item. For example: Sys.Device.Reset.
How to set/get/delete MENU configuration:
Please refer to the figure above to understand menu listing
Set configuration
$PFAL,CNF.Set,DISP.MENU1.0=Action
//primary menu
$PFAL,CNF.Set,DISP.MENU1.1=back:MENU.BACK
//first level without second level submenu
$PFAL,CNF.Set,DISP.MENU1.2.0=System
//first level with second level submenu
$PFAL,CNF.Set,DISP.MENU1.2.1=back:MENU.BACK
//second level submenu
$PFAL,CNF.Set,DISP.MENU1.2.2=Shutdown:Sys.Device.Shutdown
//second level submenu
$PFAL,CNF.Set,DISP.MENU1.2.3=Reset-ALL:Sys.Device.Reset //second level submenu
$PFAL,CNF.Set,DISP.MENU1.3.0=GSM
//first level with second level submenu
$PFAL,CNF.Set,DISP.MENU1.3.1=back:MENU.BACK
//second level submenu
$PFAL,CNF.Set,DISP.MENU1.3.2=GSM-Reset:Sys.GSM.Reset
//second level submenu
$PFAL,CNF.Set,DISP.MENU1.3.4=GSM-OFF:Sys.GSM.Disable
//second level submenu
$PFAL,CNF.Set,DISP.MENU1.3.5=GSM-ON:Sys.GSM.Enable
//second level submenu
$PFAL,CNF.Set,DISP.MENU1.4.0=GPS
//first level with second level submenu
$PFAL,CNF.Set,DISP.MENU1.4.1=back:MENU.BACK
//second level submenu
$PFAL,CNF.Set,DISP.MENU1.4.2=GPS-Reset:Sys.GPS.Reset
//second level submenu
$PFAL,CNF.Set,DISP.MENU1.4.3=GPS-OFF:Sys.GPS.Disable
//second level submenu
$PFAL,CNF.Set,DISP.MENU1.4.4=GPS-ON:Sys.GPS.Enable
//second level submenu
$PFAL,CNF.Set,DISP.MENU1.4.5=SaveAlmanac:GPS.Nav.SaveAlmanac
//second level submenu
$PFAL,CNF.Set,DISP.MENU1.5.0=Bluetooth
//first level with second level submenu 
$PFAL,CNF.Set,DISP.MENU1.5.1=back:MENU.BACK
//second level submenu 
$PFAL,CNF.Set,DISP.MENU1.5.2=Bluetooth-ON:Sys.BT.Enable //second level submenu
$PFAL,CNF.Set,DISP.MENU1.5.3=Bluetooth-OFF:Sys.BT.Disable //second level submenu
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 193 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
$PFAL,CNF.Set,DISP.MENU2.0=SMS
//primary menu 
$PFAL,CNF.Set,DISP.MENU2.1=back:MENU.BACK
//first level without second level submenu 
$PFAL,CNF.Set,DISP.MENU2.2.0=Send-SMS
//first level with second level submenu 
$PFAL,CNF.Set,DISP.MENU2.2.1=back:MENU.BACK
//second level submenu 
$PFAL,CNF.Set,DISP.MENU2.2.2=Raul:GSM.SMS.Send,"+491111111",8,"John" //second level submenu
$PFAL,CNF.Set,DISP.MENU3=Beep:IO.Beep1=hpulse,1000
//primary menu
Get configuration
$PFAL,Cnf.Get,DISP.MENU2.0
Delete
configuration
$PFAL,CNF.Set,DISP.MENU1.0
// Deletes primary menu 1.0 and hides its submenus
$PFAL,CNF.Set,DISP.MENU2.2.2 // Deletes second level submenu of the primary menu 2.0
3.3.2.3
DISP.PHONE<index>
Parameter syntax
DISP.PHONE<index>=<number>,<"name">[,<img_id>]
This parameter is used to add or delete an entry in/from the phonebook. Up to 100 number fixed
phone numbers can be added into the built-in phonebook for restricting user from making
unauthorised telephone calls.
<index>
Define the position of the entry in the phone book list. It must be in the range 1 through 100.
<number>
Specify the phone number (including the area code, country code and phone number e.g.
"+4912345678" for Germany) to be stored in the phone book.
<"name">
Enclosed in double quotation marks, define the name, max. 30 characters, to identify the
phone number.
<img_id>
If used, it loads an image for the phonebook, ranging from 301 to 399. Table below gives you
an overview about the images and the corresponding identification number available in the
firmware. To load an image, for example: "304.bmp", set the <img_id> to 304.
Supported Images
Image name
Image ID
301.bmp
301
302.bmp
302
303.bmp
303
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 194 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Supported Images
- FIRMWARE REVISION 2.8.0 -
Image name
Image ID
304.bmp
304
305.bmp
305
306.bmp
306
307.bmp
307
308.bmp
308
309.bmp
309
310.bmp
310
311.bmp
311
312.bmp
312
DOCUMENT VERSION 3.7.0
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 195 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Supported Images
- FIRMWARE REVISION 2.8.0 -
Image name
Image ID
313.bmp
313
314.bmp
314
....
..
....
399
DOCUMENT VERSION 3.7.0
How to set/get display configuration:
Set configuration
$PFAL,Cnf.Set,DISP.PHONE1=+49122222222,"Home",305
$PFAL,Cnf.Set,DISP.PHONE2=+49122222222,"Police",304
$PFAL,Cnf.Set,DISP.PHONE1=+49122222222,"ADAC"
$PFAL,Cnf.Set,DISP.PHONE2=+49122222222,"Police"
$PFAL,Cnf.Set,DISP.PHONE3=+49122222222,"Mother"
$PFAL,Cnf.Set,DISP.PHONE4=+49122222222,"Father"
$PFAL,Cnf.Set,DISP.PHONE5=+49122222222,"Grandmam"
$PFAL,Cnf.Set,DISP.PHONE6=+49122222222,"Grandpapa"
$PFAL,Cnf.Set,DISP.PHONE7=+49122222222,"Raul"
Get configuration
$PFAL,Cnf.Get,DISP.PHONE1
3.3.2.4
DISP.MESSAGE.PROT
Parameter syntax
DISP.MESSAGE.PROT =<protocol_id>
This parameter is used to define which protocol should be reported when the PFAL-Command
PFAL,Display.Message is executed as an answer for the server-related M-Box messages. The
background of the configuration setting is to report to a server two times this protocol, first when
the device receives the command PFAL,Display.Message and second when the carrier of the
MAMBO2-B6/UXFS selects an answer to the message sent from the server.
<protocol_id>
Specify which data should be report to the server when the device receives the command
PFAL,Display.Message. The protocols with corresponding IDs are listed in chapter 7.4
"Supported protocols when sending messages via SMS, CSD or TCP, USB, Bluetooth and SDCard ".
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,DISP.MESSAGE.PROT=8
Get configuration
$PFAL,Cnf.Get,DISP.MESSAGE.PROT
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 196 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.2.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DISP.ANSWER<index>
Parameter syntax
DISP.ANSWER<index>=<"text">
The MAMBO2-B6/UXFS does not offer keyboard for typing texts. Because of this, the MAMBO2B6/UXFS offers this parameter to react when you receive an SMS or a M-Box message. This
parameter is used to create a list with predefine answers to SMS or M-Box messages like: ’Yes’,
’No’, ’OK’, ’Thanks’, ’Congratulation’ etc. This list will be displayed when the device receives an
SMS or M-Box message and want to reply. When you send Mbox messages from the trace4you
server to the device you have also the possibility to send along up to 2 answers. In this case, the list
will display the answers sent from the server, and not the list you define here.
<index>
Specify the location of the message in the answer list. The index must be in the range 1
through 10.
<"answer_text">
Specify the text, max 100 characters (default = "OK"), that you will select as an answer option
to the received SMS or Mbox messages. It is also possible to enter different dynamic entries
like: "&(date),....". Dynamic entries are listed in chapter 7.2.
How to set/get display configuration:
Set configuration
$PFAL,Cnf.Set,DISP.ANSWER1="Give your answer"
$PFAL,Cnf.Set,DISP.ANSWER2="OK"
....
$PFAL,Cnf.Set,DISP.ANSWER10="I'll be there"
Get configuration
$PFAL,Cnf.Get,DISP.ANSWER1
3.3.2.6
DISP.ALARMLOOP
Parameter syntax
DISP.ALARMLOOP=<count>,<delay>,<timeout>,<waitretray>,<flag>,<prot>,<"text">
This configuration is intendet to store the settings for using the alarm loop.
[<count>]
Determine the number of beep tones which decrease itself for each delay cycles.
[<delay>]
Determine the delay time in milliseconds between two beep tones. The minimum time is 2000
ms.
[<timeout>]
Determine the timeout in milliseconds for the outgoing calls. The minimum timeout is 2000
ms.
[<waitretray>]
Specifies the time, in milliseconds, to wait between transmission retry attempts.
<flag>
Specify whether to send an SMS message when the emergency calling rutine is started or not.
The index must be set to 1 or 0.
Value
Meaning
0
SMS will NOT be sent
1
An SMS will be sent.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 197 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
<protocols>
Define the NMEA messages, which will be transmitted to the specified phone number. It has
to be specified in the hex format without leading the "0x. Supported protocols are listed in
chapter 7.4 page 332.
<"text">
Specify the text message, up to 200 characters, which will be transmitted to the specified
phone number. This entry must be wrapped in quotation marks (" "). In order to add dynamic
entries (entry) within this text, then use the following syntax: "text&(<entry1>)".
Dynamic entries are listed in chapter 7.2 page 321. Between each dynamic entry use the
ampersand "&" and then without spaces enclose each of them with parentheses "( )". See
example below.
For example:
$PFAL,Cnf.Set,DISP.ALARMLOOP=10,1000,30000,30000,0,0,"Car is moving at &(Speed) m/s"
How to set/get display configuration:
Set configuration
$PFAL,Cnf.Set,DISP.ALARMLOOP=10,1000,30000,30000,0,0,"Alarm"
Get configuration
$PFAL,Cnf.Get,DISP.ALARMLOOP
3.3.2.7
DISP.SAVER
Parameter syntax
DISP.SAVER=<mode>,<timeout>
This parameter is used to activate, deactivate the screen saver or to turn off the display. When
lunched, it will run the current system time in idle mode. The screen saver starts after the specified
period of inactivity.
<mode>
Specify the mode of screen saver. It can be set to:
Value
Meaning
0
No screen saver.
1
Shows the time and date as animation for the screen saver. Whenever the
device loses a valid GPS fix, the MAMBO2-B6/UXFS displays only the text
"MAMBO2-B6/UXFS" instead of date and time.
2
Powers off the display.
3
Shows the sliding views (default).
<timeout>
Specify how long, in milliseconds, the device must wait before launching the screen saver. The
timeout must be in the range 10000 through 2147483647.
The example in table below shows that the screen saver is enabled, and it will be stated after 10
seconds.
How to set/get display configuration:
Set configuration
$PFAL,Cnf.Set,DISP.SAVER=1,10000
Get configuration
$PFAL,Cnf.Get,DISP.SAVER
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 198 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.2.8
Parameter syntax
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DISP.TZ
DISP.TZ=<tnz><hh>.<mm>
This parameter is used to convert from time-zone name to local time and show it when screen
saver is activated. To convert time-zone value to your local time, it is necessary to know the
difference between them.
<tnz>
Three-letter time-zone name, such as UTC.
Value
Meaning
UTC
Coordinated Universal Time - the international basis for other time zones.
Time zones around the world are expressed as positive or negative offsets
from UTC.
GMT
Greenwich Mean Time - is now often used to refer to Coordinated
Universal Time (UTC) when this is viewed as a time zone, although strictly
UTC is an atomic time scale which only approximates GMT in the old
sense.
CET
Central European Time - is one of the names of the time zone that is 1
hour ahead of Coordinated Universal Time (UTC). It is used in most
European and some North African countries. Its time offset is UTC+1.
MEZ
Central European Time (Mitteleuropäische Zeit, MEZ; UTC+1)
<hh>
Specify the difference in hours between the specified time zone name and local time. Time
zones around the world are expressed as positive or negative offsets from UTC.
For example, local time in Frankfurt (Germany) is 2 hours ahead of UTC. While local time in
Los Angeles (USA) is 7 hours behind UTC. Therefore, to display the time in Frankfurt (Germany)
you have to enter +2.0 to the time zone UTC while in Los Angeles (USA) enter -7.0.
<mm>
Specify the minutes.
How to set/get display configuration:
Set configuration
$PFAL,Cnf.Set,DISP.TZ=UTC+2.0 //for Germany
$PFAL,Cnf.Set,DISP.TZ=UTC-7.0 //for Los Angeles (USA)
Get configuration
$PFAL,Cnf.Get,DISP.TZ
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 199 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.2.9
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DISP.LANG
Parameter syntax
DISP.LANG=<id>
This parameter is used to specify the language you want to use on the MAMBO2-B6/UXFS device.
<id>
Define a 2-characters language ID. It can be set to:
Value
Meaning
EN
English
RU
Russian
DE
German
FR
French
IT
Italiano
How to set/get display configuration:
Set configuration
$PFAL,Cnf.Set,DISP.LANG=DE //for German language
Get configuration
$PFAL,Cnf.Get,DISP.LANG
3.3.2.10
DISP.SLIDING
Parameter syntax
DISP.SLIDING<mode>=<timeout>[,<show_views>]
This parameter allows the users to select the order in which your specified views will be shown on
the MAMBO2-B6/UXFS screen. These views are then shown in a continuous slide show loop, with
each view being displayed for the specified time as long as no button event occurs. This
configuration is very useful e.g. during a bike trip so that you could view a series of views such as
Trip distance and duration, GPS Height, speed, heading etc. without switching manually from one
view to another. To activate sliding, press Sliding symbol (18) on the MAMBO2-B6/UXFS screen.
The sliding will run when the trip with selected mode is started.
<mode>
Define the trip mode for which you are going to use the sliding views. The mode is selected by
choosing the Trip symbol (13) and selecting one of the modes listed when you open the Mode
item. There are three different modes supported for a trip:
Value
Meaning
1
Walking. Run sliding views during the Run trip mode.
2
Bicycling. Run sliding views during the Bike trip mode,
3
Motorized. Run sliding views during the Car or Motorcycle trip mode.
<timeout>
Define how long, in seconds, a view will stay displayed on the screen before the next view is
shown. The time out must be in the range 1 through 9.
<show_views>
Define the views and the order to be displayed in a continuous slide on the MAMBO2B6/UXFS screen during the selected trip mode. Following sliding views are supported:
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 200 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Value
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Meaning
1
Height view. Display will show the current elevation in meter above sealevel.
2
Speed view. Display will show the current speed in kilometers per hour.
3
Waypoints view. Display will show the distance, in kilometers, to the next
waypoint.
4
Heart beat view. Display will show the current hard beats per minute
(requires the heart rate strap from FALCOM) - (ANT option is no longer
available) .
5
Date view. Display will show the current time and date.
6
Average and maximal height view. Display will show the average height
and the maximal height in meter.
7
Average and maximal speed view. Display will show the average speed
and the maximal speed in kilometers per hour.
8
Trip distance and duration view. Display will show the trip duration, in
hours, minutes and seconds, and the trip distance in kilometers.
9
Follow view. Display will show the direction to follow the next waypoint
and the distance to the next waypoint.
How to set/get display configuration:
$PFAL,Cnf.Set,DISP.SLIDING2=5,2,7,6,8
Set configuration
$PFAL,Cnf.Get,DISP.SLIDING1
Get configuration
3.3.2.11
//in the mode Bike trip (Bicycling), the views [2,7,6,8] are
shown in a continuous slide, with each view being
displayed for 5 seconds.
DISP.KEYLOCK
Parameter syntax
DISP.KEYLOCK=<timeout>
This parameter is used to lock the keys on the MAMBO2-B6/UXFS after a time period you specified
and protect them from being pressed accidentally (e.g. when the personal tracker is in your
pocket).
<timeout>
Specify the time period, in milliseconds, in which the device will wait to activate the keylock if
no key is pressed by the user within this time out.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 201 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Value
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Meaning
10000 .. 4294967295
The time out in milliseconds
How to set/get display configuration:
Set configuration
$PFAL,Cnf.Set,DISP.KEYLOCK=10000
Get configuration
$PFAL,Cnf.Get,DISP.KEYLOCK
3.3.2.12
DISP.SWAPBTN
Parameter syntax
DISP.SWAPBTN=<value>
This parameter is used by the system MAMBO2-B6/UXFS to sore the values of the PFAL command
$PFAL,Display.Button.Swap=<action>.
How to set/get display configuration:
Set configuration
Get configuration
3.3.2.13
Parameter syntax
-$PFAL,Cnf.Get,DISP.SWAPBTN
//gets a value (0=unswapped; 1=swapped) that indicates if the
functionality of the left and right mouse buttons has been swapped.
DISP.CALLING
DISP.CALING=<value>
This parameter is used to activate or deactivate calling window when reciving a voice call.
Value
Meaning
0
Disables calling window when reciving a voice call
1
Enables calling window when reciving a voice call
How to set/get display configuration:
Set configuration
$PFAL,Cnf.Get,DISP.CALLING=1
Get configuration
$PFAL,Cnf.Get,DISP.CALLING
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 202 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
IEEE Parameter
(IEEE option is only available for the MAMBO2-UXFS)
3.3.3.1
IEEE.PANID
Parameter syntax
IEEE.PANID=<id>,<channel>
This parameter is used to specify the PAN (Personal Area Network) identifier. See chapter 4.2 as
reference.
<id>
Specify the network identifier in hexadecimal value. The ID must be in the range 0000 through
FFFF. Default value is CAF0.
<channel>
Set the channel in which the device will listen to for other IEEE devices and create an IEEE
connection to them. The channel must be in the range 0 through 11.
How to set/get IEEE configuration:
Set configuration
$PFAL,Cnf.Set,IEEE.PANID=CAF0,5
Get configuration
$PFAL,Cnf.Get,IEEE.PANID
Notes
•
If there are the same IDs in a nearby Network, then the MAMBO2-UXFS will automatically
generate a new ID.
•
Disable and enable IEEE chip inside manually (using PFAL,Sys.IEEE.[Disable,Enable]
accordingly) after your IEEE-specified configuration completes.
3.3.3.2
IEEE.KEYFOB<index>
Parameter syntax
IEEE.KEYFOB<index>=<sec_mode>,<address>
This parameter is used to assign an index and connect to a Keyfob device. The MAMBO2-UXFS
device is the PAN coordinator in an IEEE 802.15.4 network and it is configured to start searching for
IEEE devices nearby. In this network all IEEE devices from FALCOM communicate with the PAN
coordinator. The index specified in the parameter differentiates similar Keyfob devices from each
other, while the address allows the MAMBO2-UXFS to communicate and connect only to the
Keyfob with this MAC address.
<index>
Define which index should be assigned to the Keyfob device when connected. The number of
IEEE devices (incl. Keyfobs + IO-BOXes) that can be connected to the MAMBO2-UXFS is limited
to 6. The index must be in the range 0 through 5. Do not specify any index that is already
given to other IO-BOX or Keyfob devices.
<sec_mode>
Because many devices might connect over a wireless IEEE connection and get the data that is
transmitted from, this setting specifies the type of connection security. It can be set to:
Value
Meaning
0
Disables encrypted transmissions.
1
Enables encrypted transmissions (currently not supported).
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 203 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
<address>
Define the address that identifies your Keyfob to register it to the MAMBO2-UXFS. Enter all
16-digits derived from the MAC address of the Keyfob.
The MAC address is given on the sticker on the back inside the Keyfob ( it can be seen when
you open the tray and remove batteries). Every Keyfob device has an unique MAC address.
Figure 4:
Shows the location of the Keyfob MAC address
How to set/get IEEE configuration:
$PFAL,Cnf.Set,IEEE.KEYFOB0=0,0013450100000075
$PFAL,Cnf.Set,IEEE.KEYFOB1=0,0013450100000076
$PFAL,Cnf.Get,IEEE.KEYFOB0
$PFAL,Cnf.Get,IEEE.KEYFOB1
Set configuration
Get configuration
Notes
•
To delete an existing index, set the MAC address to zero, for example:
$PFAL,Cnf.Set,IEEE.KEYFOB0=0,0000000000000000.
•
Disable and Enable IEEE chip inside manually (using $PFAL,Sys.IEEE.[Disable,Enable]
accordingly) after your IEEE-specified configuration completes.
3.3.3.3
IEEE.IOBOX<index>
Parameter Syntax
IEEE.IOBOX<index>=<sec_mode>,<in_report_mode>,<in_inval>,<ana_report_mode>,<ana_inva
l>,<address>
This parameter is used to assign an index and connect to an IO-BOX device for controlling and
requesting data from this IO-BOX device. The MAMBO2-UXFS device is the PAN coordinator in an
IEEE 802.15.4 network and it is configured to start searching for IEEE devices nearby. In this
network all IEEE devices from FALCOM communicate with the PAN coordinator. The index
specified in the parameter differentiates similar Keyfob devices from each other, while the address
allows the MAMBO2-UXFS to communicate and connect only to the Keyfob with this MAC address.
<index>
Define which index should be assigned to the IO-BOX device when connected. The number of
IEEE devices (incl. Keyfobs + IO-BOXes) that may be connected to the MAMBO2-UXFS is
limited to 6. The index must be in the range 0 through 5. The index differentiates similar IOBOX devices from each other. Do not specify any index that is already given to other IO-BOX
or Keyfob devices.
<sec_mode>
Specifies the type of data transmition. It can be set to:
Value
Meaning
0
Disables encrypted transmissions.
1
Enables encrypted transmissions (currently not supported).
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 204 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
<in_report_mode>
Define when the MAMBO2-UXFS device should request the status of the digital inputs on the
IO-BOX. It can be set to:
Value
Meaning
0
No status request.
1
Periodically request. How often the status is requested depends on the
specified time <in_inval>.
2
Request only when an digital input changes its state.
<in_inval>
Define, in hex (seconds), how often the status of the digital input on the I/O-BOX should be
requested if <in_report_mode>= 1. The interval must be in range 0x01 to 0xFF without leading
"0x".
<ana_report_mode>
Define when the MAMBO2-UXFS device should request the status of the analogue inputs on
the IO-BOX. It can be set to:
Value
Meaning
0
No status request.
1
Periodically request. How often a report is requested depends on the userspecified time on the <ana_inval>.
2
Request only when the value <ana_inval> and current delta value on a
analog input results different.
<ana_inval>
The value to be specified here depends on the specified value of the <ana_report_mode>.
If <ana_report_mode>=1:
Define, in hex (seconds), how often the status of the analog inputs on the I/O-BOX
should be requested. In this case, the interval must be in range 0x01 to 0xFF
without leading "0x".
If <ana_report_mode>=2:
Specify a delta value, in hex, that will be compared to the current value on the
analog inputs. If the current voltage on the analog inputs is above or below the
voltage when this configuration wan sent ± the specified delta value then the IOBOX will report the status of that analogue input. The value must be in range
0x0000 to 0xFFFF without leading "0x".
<address>
Define the MAC address of that IO-BOX that you want to connect to the MAMBO2-UXFS
device. Enter all 16-digits derived from the MAC address of the I/O-BOX. The MAC address is
available on a sticker on the back of the I/O-BOX unit named "MIEEE: ....", see figure below.
Each I/O-BOX unit has an unique MAC address.
Figure 5: Shows the location of the I/O-BOX's MAC address
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 205 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
How to set/get IEEE configuration:
Set configuration
$PFAL,CNF.Set,IEEE.IOBOX0=0,2,0,2,F,0017920030000077
$PFAL,CNF.Set,IEEE.IOBOX1=0,2,0,2,F,0017920030000078
Get configuration
$PFAL,Cnf.Get,IEEE.IOBOX1
Notes
•
To delete/remove an existing device, set the MAC address to zero, for example:
$PFAL,cnf.set,IEEE.IOBOX2=0,0,0,0,0,0000000000000000.
•
Disable and enable IEEE chip inside manually (using $PFAL,Sys.IEEE.[Disable,Enable]
accordingly) after your IEEE-specified configuration completes.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 206 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.3.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
IEEE.INDOOR=<fieldstrength>,<enable>
Parameter Syntax
IEEE.INDOOR=<RF_range>,<enable>
This parameter is used to specify the minimum signal range and activate indoor features on the
MAMBO2-UXFS. MAMBO2-UXFS device is also an indoor location system. Upon request the
MAMBO2-UXFS device can be supplied with a special RF transceiver that allows the system
integrators to complete their tracking solutions for both areas indoor and outdoor. MAMBO2-UXFS
uses a signal-quality based technique to provide indoor location information such as rooms or
parts of rooms. To use this feature you need two hardware components, the Beacons themselves
provided by FALCOM, and a MAMBO2-UXFS-IE device. The most common way to use the
MAMBO2-UXFS-IE for indoor applications is to deploy beacons on ceilings and/or walls in a building
and MAMBO2-UXFS-IE devices to persons whose location needs to be obtained. The MAMBO2UXFS-IE device periodically requests on the user-set radio frequency (RF) channel and each
beacons having the same radio frequency (RF) channel and IEEE network identifier, and are within
the RF range will receive such requests and response by transmitting its own unique identifier (set
by the manufacturer) together with the payload. An application example is graphically represented
in the figure next to. For more details, refer to the document "AppNote_INDOOR_Howto.pdf"
<RF_range>
Specify the minimum signal range to generate the INDOOR event when an IEEE device gets
into the specified range. It must be in a range 0 through 254. Default = 70. The higher the RF
range, the shorter the distance between MAMBO2-UXFS from beacon.
<enable>
Define whether to activate or deactivate the indoor tracking features. It can be set to:
Value
Meaning
0
(default) Deactivates indoor tracking.
1
Activates indoor tracking. The event "IEEE.Device.eIndoor" is occurred
whenever a Beacon device gets into the specified RF range.
How to set/get IEEE configuration:
Set configuration
$PFAL,CNF.Set,IEEE.INDOOR=100,1
Get configuration
$PFAL,Cnf.Get,IEEE.INDOOR
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 207 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Optional Settings
The settings in the following configuration parameters are created by system itself and therefore is not
need to be changed manually. They are just named and explained as a reference.
3.3.4.1
Parameter syntax
STORAGE<id>
STORAGE<id>
This parameter is used to store user data such as current trigger, counter timer or position
information to non-volatile memory. These 5 storage slots can be used to keep certain information
even when MAMBO2-B6/UXFS is shut down. Each storage slot may contain only one user data set
(i.e. a position or a trigger/counter/timer value).
Example:
If a timer value is saved to slot 0, only a system timer may load its value and setting from this
configuration slot. Any attempt to load e.g. Trigger0 from storage slot 0 will fail as the type of
stored data doesn’t match.
However it is possible to overwrite a storage slot with other user data (e.g. with a position).
<id>
Specify a number form 0 to 4.
3.3.4.2
Parameter syntax
GSM.BANDPREF
GSM.BANDPREF
This setting is managed internally and should be modified only by PFAL command. It selects at
which band the GSM engine starts to search for operators and allows to find operators more
quickly when being outside of Europe (which is the default setting).
3.3.4.3
Parameter syntax
GSM.Version
GSM.Version
This setting is used for identifying GSM and hardware type of MAMBO2-B6/UXFS. Actually it is the
only setting used with small letters (historical reason). This setting may not be modified by user!.
All system settings which may be modified by user are in capital letters !!!
3.3.4.4
Parameter syntax
GSM.PROFILE.AUDIO<prof_index>
GSM.PROFILE.AUDIO<id>=<echo_cancel>,<side_tone>,<spk_mute>,<spk_volume>,<mic_mute>,<
hfmic_vol>,<hsmic_vol>,<ring_path>,<ring_tone>,<ring_vol>,<path>,<mode>
These settings are used to configure audio profiles. All these settings are managed by system and
by PFAL commands and shouldn't be modified directly with Cnf.Set commands!
<id>
It can be set to a value from 0.. 4. See also Notes below.
Value
Meaning
0
User profile (audio settings can manually be selected).
1
Profile for internal audio.
2
Profile for hands free audio.
3
Profile for headset audio.
4
Profile profile for Bluetooth audio.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 208 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
<echo_cancel>
It can be set to a value as follow:
Value
Meaning
0
Disables echo cancelling.
1
Enables echo cancelling (default)
<side_tone>
It can be set to a value as follow:
Value
Meaning
0
Disables side tones (default)
1
Enables side tones
<spk_mute>
It can be set to a value as follow:
Value
Meaning
0
Unmutes (activates) the speaker (default)
1
Mutes (deactivates) the speaker
<spk_volume>
It can be set to a value as follow:
Value
0...14
Meaning
Loudness of the speaker (maximum might depend on GSM version).
Default is 7.
<mic_mute>
It can be set to a value as follow:
Value
Meaning
0
Unmutes (activates) the microphone (default)
1
Mutes (deactivates) the microphone.
<hfmic_vol>
It can be set to a value as follow:
Value
0...7
Meaning
Loudness of the handfree microphone (maximum might depend on GSM
version). Default is 5.
<hsmic_vol>
It can be set to a value as follow:
Value
0...7
Meaning
Loudness of the handset microphone (maximum might depend on GSM
version). Default is 5.
<ring_path>
It can be set to a value as follow:
Value
Meaning
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 209 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
0
Automatic path selection (default)
1
Handsfree audio path
2
Handset audio path
3
Internal (not used) audio path
DOCUMENT VERSION 3.7.0
<ring_tone>
Type of ring tone (default is 24). You have a choice of 33 different ring tones and melodies. All
will be played from the audio output.
Value
0..32
Meaning
Sequence 0...32
<ring_vol>
It can be set to a value as follow:
Value
0..4
Meaning
Ringer gain(loudness). Default is 3.
<path>
It can be set to a value as follow:
Value
Meaning
0
Automatic path selection.
1
Handsfree audio path (default).
2
Handset audio path.
3
Internal (not used) audio path.
<mode>
It can be set to a value as follow:
Value
Meaning
0
Automatic path selection.
1
Handsfree audio path (default).
2
Handset audio path.
3
Internal (not used) audio path.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GSM.PROFILE.AUDIO0=1,0,0,7,0,5,5,0,24,3,1,0
Get configuration
$PFAL,Cnf.Get,GSM.PROFILE.AUDIO0
$PFAL,Cnf.Get,GSM.PROFILE.AUDIO1
$PFAL,Cnf.Get,GSM.PROFILE.AUDIO2
Notes
• The audio profiles 1 to 4, in the MAMBO2-B6/UXFS (hardware version 7b) running with
software version 2.5.10_RC7 and later, are factory-preconfigured:
"GSM.PROFILE.AUDIO1=1,0,0,13,0,5,5,1,24,3,1,0"
"GSM.PROFILE.AUDIO2=1,0,0,7,0,5,5,1,24,3,1,0"
"GSM.PROFILE.AUDIO3=1,0,0,12,0,5,5,1,22,2,2,0"
"GSM.PROFILE.AUDIO4=1,0,0,7,0,5,5,1,24,3,1,0"
// Internal audio profile
// Hands-free audio profile
// Headset audio profile
// Bluetooth audio profile
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 210 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.4.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.PROFILE.CURRENTAUDIO
Parameter syntax
GSM.PROFILE.CURRENTAUDIO=<id>
Specifies the audio profile to be used. This parameter shouldn't be modified directly with Cnf.Set
command but using the corresponding PFAL command.
<id>
The id must be in the range 0 through 4.
How to sent/get the configuration:
Set configuration
-
Get configuration
$PFAL,Cnf.Get,GSM.PROFILE.CURRENTAUDIO
Notes
• The audio profiles 1 to 4, in the MAMBO2-B6/UXFS running with software version 2.6.0
and later, are factory-preconfigured:
"GSM.PROFILE.AUDIO1=1,0,0,13,0,5,5,1,24,3,1,0"
// Internal audio profile
"GSM.PROFILE.AUDIO2=1,0,0,7,0,5,5,1,24,3,1,0"
// Hands-free audio profile
"GSM.PROFILE.AUDIO3=1,0,0,12,0,5,5,1,22,2,2,0"
// Headset audio profile
"GSM.PROFILE.AUDIO4=1,0,0,7,0,5,5,1,24,3,1,0"
// Bluetooth audio profile
• It may only be set to valid profiles. If the specified profile isn’t valid (i.e. configured before)
this setting will not be updated and return an error.
3.3.4.6
Parameter syntax
MACRO<index>
MACRO<index>=<command1>&….&command10>
This parameter is used to configure a Macro. A Macro can consist of more alarm actions than a
usual alarm. It is possible to specify the command e.g. „Sys.Macro0" as an alarm action. Thereby, it
activates this macro (0 in our example). If such a macro is activated, all commands defined inside
this macro will be executed. REPLACE parameter can also be used within commands in a Macro.
Keep in mind that the MACRO parameter is case sensitive. It must always be written in
capital letters; otherwise no action within a MACRO will be executed.
Macros are designed to make possible executing of the large numbers of commands within a single
line. Macro can also be used to store several commands, which can be used frequently inside the
alarm configuration. This configuration improves the style of a clearly arranged alarm
configuration; it prevents the configuration mistakes and can ease the readability of a
configuration.
<index>
Specify the macro index - a number that ranges from 0 to 9 (10 macros) at the moment.
<command1>&….&command10>
Specify the command to be released for a specific task. Up to 5 commands separated by
ampersand "&" can be specified and executed. However, the maximum number of
characters in a single command line is limited to 1500. The rest will be ignored.
To specify a command, please, refer to chapter 3.1.1, "Command syntax". All commands within
that chapter can be set as alarms without leading the "$PFAL,". Examples in the table below
illustrate the use of the MACRO parameter.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,MACRO0=IO11.Set=hpulse,3000
$PFAL,Cnf.Set,MACRO1=GSM.SMS.Send,"+491234567",8,"AL1 SMS"
$PFAL,Cnf.Set,MACRO2=IO13.Set=cyclic,2000,5000
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 211 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
$PFAL,Cnf.Get,MACRO0
$PFAL,Cnf.Get,MACRO1
$PFAL,Cnf.Get,MACRO2
Get configuration
Notes
• The maximal number of commands that can be specified in a MACRO is limited to 5 and
the maximum number of characters in a single alarm line is limited to 1500.
• It is not recommended to set the read commands inside the macros because this would
only slow down the system performance. (The information to be read out cannot be
displayed in this way. Use the MSG.send commands for such purposes).
• It is NOT allowed to activate other macro commands inside a macro configuration
parameter as the activation of them might lead to endless loops of set commands.
NOT allowed: $PFAL,Cnf.Set,MACRO0=IO.LED1=hpulse,3000&Sys.Macro0
3.3.4.7
DEVICE.LOWPOWER
Parameter syntax
DEVICE.LOWPOWER=<mode>,<ontime>[,<offtime>]
This parameter provides the low power information of the MAMBO2-B6/UXFS device. It is used to
save the values you specified with the command $PFAL,Sys.Power.Mode.
<mode>
Determines whether a low power mode has been enabled. It can be:
Value
Meaning
0
Low power mode disabled.
1
Low power mode "auto" has been enabled.
2
Low power mode "doze" has been enabled.
<ontime>
Determines the number of seconds the device stays on before going back to the specified low
power mode "auto" or "doze".
mode,.
[<offtime>]
Specify the number of seconds that the device will stay in deep sleep "doze" before waking
up. If no value is available, then the device is either set into low power mode "auto" or the
low power is already disabled.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,DEVICE.LOWPOWER=0,30
$PFAL,Cnf.Set,DEVICE.LOWPOWER=1,30
$PFAL,Cnf.Set,DEVICE.LOWPOWER=2,30,60
Get configuration
$PFAL,Cnf.Get,DEVICE.LOWPOWER
//low power disabled
//"auto" mode enabled
//"doze" mode enabled
Notes
• The Doze mode is not recommended to be used in combination with GPS trickle power (for
MAMBO2 with SiRF receiver only).
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 212 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
REPLACE Parameter
REPLACE<index>
3.3.5.1
Parameter syntax
REPLACE<index>=<replace_string>
Additionally replacement marks can be set within any AL<alarms>. Each replacement mark belongs
to a replacement configuration setting. The mark will be replaced automatically with its contents
when an alarm is configured. This is useful to store (e.g. phone numbers) within replacement
configuration settings. Instead of using this number within an alarm, you can simply add the proper
replacement mark. This way allows you to quickly change the replacement configuration later –
that changes all occurrences within your alarm configuration. So you don't have to search and
replace the whole alarm configuration anymore.
Of course this comes in handy only if you use e.g. a phone number very often within the alarm
configuration. Changing this number now requires just the change of one replacement
configuration – not each configured alarm AL.
Example:
For example, instead of writing alarm such as the following:
$PFAL,Cnf.Set,AL0=IO.BTN.e0=long:GSM.SMS.Send," +1234567",8,"BNT0 pressed"
$PFAL,Cnf.Set,AL1=IO.BTN.e1=long:GSM.SMS.Send," +1234567",8,"BNT1 pressed"
Your alarm would look as follows:
$PFAL,Cnf.Set,AL0=IO.BTN.e0=long:GSM.SMS.Send,(REPLACE0),8,"BNT0 pressed"
$PFAL,Cnf.Set,AL1=IO.BTN.e1=long:GSM.SMS.Send,(REPLACE0),8,"BNT1 pressed"
$PFAL,Cnf.Set,REPLACE0="+1234567"
// the phone number to which all SMS have to be sent
Now lets assume you want to change this phone number. Without using the replacement marks,
you would have to enter that number within each alarm, so you would have to change all 4 alarms.
Using replacement marks, you can simply change the phone number into the REPLACE0 setting –
e.g. from REPLACE0="+1234567" to REPLACE0="+7654321".
After restarting the device, all alarms using REPLACE0 will dial or send SMS to the new phone
number.
<index>
Specify the replace index, it ranges from 0 to 9. These settings contain text that is inserted
into alarm configuration settings (AL<x>=....) at any occurrence of (REPLACE<x>).
<replace_string>
Specify the text to be replaced – with a maximum length of 200 characters .
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,REPLACE0="+1234567"
Get configuration
$PFAL,Cnf.Get,REPLACE0
Notes
• When changing any REPLACE parameter, a system restart is necessary to update all alarms.
• You have to configure this parameter before using it in alarms.
• When configuring new alarms after setting up the REPLACE parameter, these new alarms
will already use the new values specified in the REPLACE parameter– so there is no need to
restart the device for updating these new values.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 213 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.6
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
MOTION parameter
3.3.6.1
MOTION.FILTER
Parameter syntax
MOTION.FILTER=<a_coe>,<g_coe>,<max_abs>,<min_abs>,<force>
This parameter is used to filter the device motions. Based on the filter values you define, the
system MAMBO2-B6/UXFS will raise the event IO.Motion.eMoving or IO.Motion.eStanding when
moving or stop moving correspondly – use figure below as reference. Additionally to these events,
you can also define a force value to raise the event IO.Motion.eForce. The first four entries in this
configuration will also be used to wake up the MAMBO2-B6/UXFS device from the Motion sleep
mode (see command - Sys.Device.Sleep=IGN+motion). For preventing false alarms, the moving
events are deactivated while the MAMBO2-B6/UXFS device is beeping or vibrating.
<a_coe>
Define the sensitivity on which an average acceleration vector will be calculated each second.
It must be in the range 0 through 40. The lower the set value, the more sensitive is the motion
detection of the device. Default value is 4.
<g_coe>
Define the sensitivity on which an average gravitation vector will be calculated each second . It
must be in a range 0 through 60. The lower the set value, the more sensitive is the motion of
the device in g-axes. Default value is 20.
<max_abs>
Specify a maximum difference value between the gravitation vector and acceleration vector
for the device to detect that it is moving. It must be in a range 0 through 1023. Any other
value greater than the set value counts as a disagreement and the device will raise moving
event IO.Motion.eMoving. Default value is 20.
<min_abs>
Specify a minimum value difference value between the gravitation vector and acceleration
vector for the device to detect that it is standing. It must be in a range 0 through 10. Any
other value less than this minimum value counts as a disagreement and the device will raise
standing event IO.Motion.eStanding. Default value is 2.
<force>
Specify a minimum value for generating the force event. It must be in the range 0 through
1023. The event IO.Motion.eForce is generated when the device will reach or exceed this
value. This entry is independent from other parameters in this configuration.
The configuration below shows that the acceleration vector will be calculated in 4 steps and
gravitation vector in 20 steps to generate IO.Motion.eMoving and IO.Motion.eMoving event. The
IO.Motion.eMoving and IO.Motion.eStanding events will be occurred when the difference value
between the gravitation and acceleration vectors is greater than 10 and less than 2 accordingly (see
first example below).
How to set/get Motion configuration:
Set configuration
Get configuration
$PFAL,Cnf.Set,MOTION.FILTER=4,20,10,2
$PFAL,Cnf.Set,MOTION.FILTER=4,20,10,2,90
// force event disabled
// force event enabled
$PFAL,Cnf.Get,MOTION.FILTER
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 214 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Figure 6:
3.3.6.2
Parameter syntax
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Filtering in motion
MOTION.BEARING
MOTION.BEARING<index>=<min_x>,<min_y>,<min_z>,<max_xx>,<max_xy>,<max_xz>,<timeout>
This parameter is used to filter the rotating bearing of device motions. Based on the filter values,
system raises the event IO.Bearing.e<0..4> when rotating of the device exceeds the specified min.
or max. values and raises the event IO.Bearing.e<5> when the device is within the min. and max.
values . In order to define the correct values for the device bearing you have to test the MAMBO2B6/UXFS locally and find out the values that you application requires. The current bearing values of
the device are added into the $GP3DP protocol and output each second to the USB and Bluetooth
port. To view such values the $GP3DP protocol must be switched on using the configuration
"$PFAL,CNF.Set,PROT.3DP=1". On the USB or Bluetooth port you will see the following values
giving you information how this values change when you rotate the device around one of the axes
to a specific angle:
$GP3DP,504,504,592,504,503,591,505,509,593,4*33
The faster the device rotates, the higher the values for the rotate axis will be. To identify which
output values correspond to an axis you need to rotate the device around one of the axes and see
the output values that change in the protocol. First, place the device in horizontal position. In this
position the values would be more or less the same as shown in the protocol above. Thereafter,
start rotating the device to the left (the first 90 degrees of rotation) and see which values change.
Write down these values and then start rotating the device to the other direction (right and
vertically). When the rotation angles with corresponding values for your application are found,
enter these values in the parameter MOTION.BEARING and send it to the device. For test purposes
you may configure an alarm (AL) to generate a beep tone whenever IO.Bearing.e<index> event
occurs (e.g. $PFAL,Cnf.Set,AL99=IO.Bearing.e0:IO.Beep3=hpulse,2000).
<index>
Specify the index for storing the bearings values. The index must be in the range 0 through 5.
These values are defined as follow:
Value
Meaning
0 .. 4
Generates the corresponding event when the rotating of the device
exceeds the specified min. or max. values.
5
Represents the negation of one of the Bearings 0 to 4. Generates the event
"IO.Bearing.e5" when the device is within the specified Min. and Max.
bearing values. To use this event you should configure it with the same
values as specified by one of the bearing 0 .. 4.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 215 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
<min_x>
Specify the minimum value for the x-axis. It must be in the rang 0 through 1023. If the
minimum value for the x-axis is not required set it to 0.
<min_y>
Specify the minimum value for the y-axis. It must be in the rang 0 through 1023. If the
minimum value for the y-axis is not required set it to 0.
<min_z>
Specify the minimum value for the z-axis. It must be in the rang 0 through 1023. If the
minimum value for the z-axis is not required set it to 0.
<max_xx>
Specify the maximum value for the x-axis. It must be in the rang 0 through 1023. If the
maximum value for the x-axis is not required set it to 0.
<max_xy>
Specify the maximum value for the y-axis. It must be in the rang 0 through 1023. If the
maximum value for the y-axis is not required set it to 0.
<max_xz>
Specify the maximum value for the z-axis. It must be in the rang 0 through 1023. If the
maximum value for the z-axis is not required set it to 0.
<timeout>
Define the period of time on which the device will check the user-defined values to generate
an event if the current bearing values (0..4) of the device are below or above, or within when
using bearing 5.
The example in table below shows that: the event will be occurred every 5 seconds if the specified
minimum and maximum values are exceeded.
How to set/get Bearing configuration:
$PFAL,Cnf.Set,MOTION.BEARING0=420,420,420,580,700,580 ,5 //bearing event 0 occurs every 5 seconds if
current values of the device are exceeded
Set configuration
$PFAL,Cnf.Set,MOTION.BEARING5=420,420,420,580,700,580 ,5 //bearing event 5 occurs every 5 seconds if
current values of the device are withinte
specified ones
Get configuration
$PFAL,Cnf.Get,MOTION.BEARING0
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 216 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.6.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
MOTION.TILT
Parameter syntax
MOTION.TILT=<mode>,<value1>,[<value2>],[<value3>]
This parameter is used to configure the detection of the device position and generate the tilt event
(IO.Bearing.e6) when the device detects a change of orientation more then the predefined userrange from the calibrated position. The calibration of the device position must be done from the
MAMBO2-B6/UXFS display. With this parameter you can only specify how far the device may tilt
from the calibrated position without generating the event (IO.Bearing.e6).
To calibrate the tilt feature of the MAMBO2-B6/UXFS device, follow the steps below:
1) Define, in degrees, how far the device may tilt from the calibrated position without
generating the tilt event (e.g. $PFAL,Cnf.Set,MOTION.TILT=vector,40). If this angle of 40
degrees is exceeded from the left or right side of the calibrated position, the device will
generate the tilt event (IO.Bearing.e6) which you can use it to execute any alarm.
2) Using the Left or Right key, browse to the Tilt symbol
available on the MAMBO2B6/UXFS display.
3) Position the MAMBO2-B6/UXFS device in a way that this is the device base position to be
calibrated.
4) Using the 5-way navigation key, press the Tilt symbol on the display and wait until the
calibration count-down ends and on the MAMBO2-B6/UXFS the message "Calibration
completed" is shown.
5) After the configuration of the tilt feature is stored in the device, to test the calibrated
device, just position the device to the calibrated position and then tilt it left or right until
the specified angle is exceeded and the tilt event (IO.Bearing.e6) is occured.
6) If the defined tilt angle rate is too small or too high for your application, you can change
it by using the command $PFAL,Cnf.Set,MOTION.TILT=vector,xx and defining another
value in the range 0 through 180 e.g. 30. The smaller the angle value, the more sensitive
is the tilt of the device.
<mode>
Specify the method of calculation of the tilt. There are two ways to calculate the device tilt:
Value
Meaning
diff
Calculation uses the specified values in
and Z axes.
vector
Calculation uses the allowed angle you specify in <value1>.
<value1>,[<value2>],[<value3>]
for X, Y,
<value1>
Specify how far the device may tilt from the calibrated position. Depending on your defined
calculation mode, you may specify either an angle in the range 0 through 180, or the amount
of tilt along the x-axis in the range 0 through 1023.
[<value2>]
Specify the amount of tilt along the y-axis from the calibrated position. This value must be in
the range 0 through 1023. It applies only for diff - mode.
[<value3>]
Specify the amount of tilt along the z-axis from the calibrated position. This value must be in
the range 0 through 1023. It applies only for diff - mode.
The example in table below shows that the tilt event is occurred when the device tilts more than 30
degrees from the calibrated position.
How to set/get Tilt configuration:
Set configuration
$PFAL,Cnf.Set,MOTION.TILT=vector,30
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 217 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Get configuration
3.3.6.4
Parameter syntax
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
$PFAL,Cnf.Get,MOTION.TILT
MOTION.FALLING
MOTION.FALLING=<minx>,<miny>,<minz>,<maxxx>,<maxxy>,<maxxz>
When the MAMBO2-B6/UXFS device is dropped from a distance above the Earth, it will accelerate
downward at a constant rate due to gravity. During free-falling the acceleration sensor inside the
device delivers the same values for all three axes. To detect such events, you must define the limit
values for all these three axes. This parameter can be used to define the minimum and maximum
values during the device is falling down and to generate the falling event IO.Motion.eFalling. In
order to define correct falling values for a device you have to test it locally and find out the values
your application requires. For example, during the test, the device delivers the same value of 500
for all three axes. In this case, you specify in this configuration parameter a delta value of 100
between the minimum and maximum (see example in table below). The current values of the
device during falling are added into the $GP3DP protocol and output each second to the USB and
Bluetooth port. To view such values, the $GP3DP protocol must be switched on using the
configuration "$PFAL,CNF.Set,PROT.3DP=1".
In order to set values in the Bearing and Falling parameters, take the values from the GP3DP and
add to each value 512 so that the value -512 in the $GP3DP protocol corresponds to the value 0 (512+512=0) in the Motion value.
<minx>
Specify the minimum value for the x-axis. It must be in the rang 0 through 1023.
<miny>
Specify the minimum value for the y-axis. It must be in the rang 0 through 1023.
<minz>
Specify the minimum value for the z-axis. It must be in the rang 0 through 1023.
<maxxx>
Specify the maximum value for the x-axis. It must be in the rang 0 through 1023.
<maxxy>
Specify the maximum value for the y-axis. It must be in the rang 0 through 1023.
<maxxz>
Specify the maximum value for the z-axis. It must be in the rang 0 through 1023.
The example in table below shows that, the event IO.Motion.eFalling is occurred when the values
the motion sensor are within this range (min. and max.).
How to set/get Falling configuration:
Set configuration
$PFAL,Cnf.Set,MOTION.FALLING=450,450,450,550,550,550
Get configuration
$PFAL,Cnf.Get,MOTION.FALLING
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 218 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.7
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
ALIAS parameter
3.3.7.1
ALIAS.<type>
Parameter syntax
ALIAS.<type_subindex>=<alias_name>
This parameter is used to define an alias name for each command c_type/c_index and c_subindex
and use it further with the defined alias name instead of its default name.
<type_subindex>
Specify the command c_type/c_index and c_subindex to be otherwise called.
<alias_name>
Specify the alias name which will correspond to the last <type_subindex> specified command
c_type/c_index and c_subindex.
How to sent/get the configuration:
Set configuration
Get configuration
$PFAL,Cnf.Set,ALIAS.SYS=System
$PFAL,Cnf.Set,ALIAS.CNF=Config
$PFAL,Cnf.Get,ALIAS.SYS
$PFAL,Cnf.Get,ALIAS.CNF
Notes
• The "$PFAL,Cnf.Set,ALIAS.IO.LED1=_GSM" input message sent to the MAMBO2-B6/UXFS does
not mean that the "LED1" is equal to "_GSM", but the alias name for "1" is "_GSM". An
example how to declare alias names if they are already defined.
$PFAL,Cnf.Set,ALIAS.IO.LED1=_GSM
$PFAL,CNF.Set,AL1=SYS.TIMER.e2&GSM.sOpInvalid:IO.LED_GSM=hpulse,5000
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 219 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.8
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DBG parameter
3.3.8.1
DBG.EN
Parameter syntax
DBG.EN=<enable>[,<interface>][,<protocols>]
This parameter is used to enable a special debugging mode for displaying all of the data currently
being sent to the device and responses received via the interface you specify. The integrated
debugger which helps you to track down the initialization/execution of the firmware/ your
application, to monitor the specified values and settings and runtime errors, etc. can be monitored
from a terminal program that is able to send and receive data via USB or Bluetooth e.g. Workbench
software from FALCOM.
<enable>
Determine whether or not to run the debug mode. It can be set to:
Value
Meaning
0
Switch debug mode off.
1
Switch debug mode on.
<interface>
Optional. Specify the interface on which the debug mode will be turned on or off. If omitted
the debug mode is turned on/off for Bluetooth (serial port).
Value
Meaning
USB
If debug mode is switched on, it outputs debug information to the USB
port.
TCP
If debug mode is switched on, it outputs debug information on TCP
interface.
SD
If debug mode is switched on, it stores debug information and the selected
protocols on Mini-SD-card. (SD option is no longer available)
<protocols>
Optional, for USB and SD interface. Selects protocols to be saved /outputted together with
debug information into the SD card under /sd/dbg directory or on the USB interface. If this
directory does not exists, it will be created automatically. Protocols to be selected are listed in
chapter 7.4 page 332.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,DBG.EN=1,USB
$PFAL,Cnf.Set,DBG.EN=1,SD,8
Get configuration
$PFAL,Cnf.Get,DBG.EN
//Saves debug data+RMC protocol in mini-SD card.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 220 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.9
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
PROT parameters (protocols supported over Bluetooth and USB port)
The configuration of the protocols in this chapter is intended to provide real time navigation data to the
host device. The MAMBO2-B6/UXFS uses the satellite signals to calculate its exact current location by
calculating its distance from the satellites. The position data within the device is then converted into
latitude and longitude coordinates, which are usually provided in the geodetic datum on which the GPS
is based (WGS84) and the configured protocols are transmitted via serial interface or USB to the
connected host device (PC, laptop).
This configuration is intended only for Bluetooth (MAMBO2-UXFS only) and USB Interfaces and it does
NOT apply the configuration of protocols that have to be transferred via SMS, CSD and TCP applications.
To send GPS data via SMS, CSD or TCP, please, refer to chapter 3.2.8.1, page 149.
In addition to the configuration protocol, if a last valid position has been already saved from the prior
operation and there is no GPS fix currently available, for example during system startup procedure, then
the last valid position will be shown in the RMC and GGA output protocols (with state: invalid).
Whenever the GPS fix gets lost, the last valid position is still displayed (just the state inside the protocol
changes to invalid), which works even if a last valid position has not been saved yet.
Note:
If the MAMBO2-B6/UXFS resides in an area without GPS coverage or acquiring a GPS
fix fails, then the last saved valid position will be shown during system startup.
3.3.9.1
PROT.<message_id>
Parameter syntax
PROT.<message_id>=<value>
This parameter is used to switch on or off certain messages and specify the rate at which they are
delivered to Bluetooth, USB etc..
<message_id>
Specify the message identifier to be enabled or disabled. Following are the identifiers
corresponding to the message supported by the MAMBO2-B6/UXFS device software.
Protocols
Meaning
Default setting
GGA
GSA
GSV
RMC
GLL
VTG
IOP
GSM
AREA
BIN
3DP
Enables or disables the $GPGGA message (NMEA).
Enables or disables the $GPGSA message (NMEA).
Enables or disables the $GPGSV message (NMEA).
Enables or disables the $GPRMC message (NMEA).
Enables or disables the $GPGLL message (NMEA).
Enables or disables the $GPVTG message (NMEA).
Enables or disables the $GPIOP message (FALCOM).
Enables or disables the $GPGSMmessage (FALCOM)
Enables or disables the $GPAREA message (FALCOM).
Enables or disables the BIN message (FALCOM).
Enables or disables the $GP3DP message (FALCOM).
1
1
1
1
0
0
0
1
0
$
1
<value>
Specify the rate at which the selected message is sent to the serial interface.
Value
Meaning
1 ... 255
Enables the selected message.
0
Disables the selected message.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 221 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
How to set/get Protocol configuration:
Set configuration
Get configuration
3.3.9.2
Parameter syntax
$PFAL,Cnf.Set,PROT.GGA=1
$PFAL,Cnf.Set,PROT.GSA=1
$PFAL,Cnf.Set,PROT.GSV=1
$PFAL,Cnf.Set,PROT.RMC=1
$PFAL,Cnf.Set,PROT.GLL=1
$PFAL,Cnf.Set,PROT.VTG=1
$PFAL,Cnf.Set,PROT.IOP=1
$PFAL,Cnf.Set,PROT.GSM=1
$PFAL,Cnf.Set,PROT.AREA=1
$PFAL,Cnf.Set,PROT.BIN=1
$PFAL,Cnf.Set,PROT.3DP=1
$PFAL,Cnf.Get,PROT.GGA
PROT.START.BIN
PROT.START.BIN=$<value>
This parameter is used to specify your own protocol that your application needs. It consists of the
user specified text which will be attached at the begin of the BIN protocol.
<value>
String type. Consists of 18 Bytes. If specified, the value will be shown at the beginning of the
BIN protocol, including the dollar sign "$".
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,PROT.START.BIN=$user protocol
Get configuration
$PFAL,Cnf.Get,PROT.START.BIN
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 222 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.10
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPS parameters
3.3.10.1
Parameter syntax
GPS.TRIP.WPOINT<index>
GPS.TRIP.WPOINT<index>=<lat>,<lon>,<alt>,<radius>,<mode>,“<name>“
The MAMBO2-B6/UXFS device has the capability of storing up to 20 waypoints. Waypoints are
used to store the location that are of interest to the user. A waypoint refers to a geographic point
location that contains latitude, longitude, altitude, radius and name and can be used as a point for
general use, to START or STOP a trip.
This parameter is used to store different waypoints in the list. The user usually creates waypoints
either by marking a location with the MAMBO2-B6/UXFS device or by using a map - preferably with
mapping software on a computer. Each waypoint is numbered by an unique index ranging from 1
to 20. You can run the list of waypoints forward, manual, follow or backward. This should be
specified in the GPS.TRIP.POIMODE configuration. Once you start the trip on the TRIP-View, the
device calls GPS.TRIP.POIMODE=<mode> setting and will tell you the distance and direction you
need to reach the first waypoint. Once you have reached the first waypoint, the device will
automatically select the next waypoint in the route and give you distance and direction to that
one. When you reach the specified radius of waypoints, the device will occur the corresponding
event "Display.Pois.e<index>". This event can then be used to execute specific user alarms such as
send an SMS/TCP packet or display a message "e.g. WPOINT 1 reached" on the screen. Refer to the
figure below for a graphical representation of waypoints.
<index>
Set the index of the waypoint, ranging from 1 to 20, to be saved.
<lat>
Specify the latitude, in decimal format, of this waypoint (e.g. 50.2536).
<lon>
Specify the longitude, in decimal format, of this waypoint (e.g. 10.3567).
<alt>
Specify the altitude, in meter, of this waypoint (e.g. 450).
<radius>
Specify the radius, in meter, of this waypoint (e.g. 30). When this waypoint is reached the
device generates the event Display.Pois.e<index>.
<mode>
Define the operation mode for the set index. There are three different operation modes:
Value
Meaning
0
Use this point as a standard waypoint for general use.
1
Use this point as a STOP trip. When this point is reached, the trip will be
stopped.
2
Use this point as a START trip. When this point is left, the trip will be
started.
<"name">
String type. Specify the name of this waypoint (e.g. "WPOINT1").
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 223 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GPS.TRIP.WPOINT1=50.2536,10.3567,450,30,0,"WPOINT1"
Get configuration
$PFAL,Cnf.Get,GPS.TRIP.WPOINT1
3.3.10.2
GPS.TRIP.POIMODE
Parameter syntax
GPS.TRIP.POIMODE=<method>,<trip_category>
This parameter defines how the existing waypoints in the list (stored with
GPS.TRIP.WPOINT<index>) should be navigated and what kind of activity the trip should be. This
function is enabled only when a Trip (on the TRIP-View) is started. When the user reaches the
radius of the of the currently used waypoint the corresponding event Display.Pois.e<index> will
occur.
<method>
String type. Define how the existing waypoints on the list (added with GPS.TRIP.WPOINT)
should be selected. The method you want to use the stored waypoints can also be selected
from the Waypoint symbol (index 21) on the MAMBO2-B6/UXFS screen.
auto
This setting follows waypoints in the list forward starting from 1 to the
last one (e.g. 7 - see figure in chapter above) in sequence. In other words,
the next waypoint on the list is automatically selected when the prior
waypoint is reached. It is very useful for delivery services, canoe trips, bike
trips, geocaching, hiking or wandering.
manual
This setting follows waypoints in the list forward starting from the
selected one (e.g. 3) forward to the last one (e.g. 7 see figure in chapter
above) in sequence. In other words, the next waypoint on the list is
automatically selected when the selected one is reached. It is very useful
for canoe trips, bike trips, hiking or wandering.
back
This setting follows waypoints backward starting from the last (e.g. 7 see
figure in chapter above) to the first one 1 in sequence. In other words, the
next waypoint in the list is automatically selected when the prior one is
reached. This setting is very useful when the user wants to go back to the
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 224 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
first waypoint in the list. It is very useful for canoe trips, bike trips, hiking
or wandering.
<trip_category>
String type. Define what kind of activity the trip should be. The category of the trip can also be
selected from the Trip symbol (index 13) on the MAMBO2-B6/UXFS screen.
walk
The activity of the trip you are going to do is Walking.
bike
The activity of the trip you are going to do is Bicycling.
car
The activity of the trip you are going to do is Driving.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GPS.TRIP.POIMODE=auto,walk
Get configuration
$PFAL,Cnf.Get,GPS.TRIP.POIMODE
3.3.10.3
GPS.TRIP.ROUTE<index>
Parameter syntax
GPS.TRIP.ROUTE<index>="<name>",<way_point1>[,<way_pointN>]
The MAMBO2-B6/UXFS device has the capability of storing up to 20 waypoints using the
parameter GPS.TRIP.WPOINT<index>. These waypoints are used to store the location that are of
interest to the user. This parameter is used to specify which waypoints stored with
GPS.TRIP.WPOINT<index> belong to your route.
<index>
Set the index of the route, ranging from 1 to 5, to be saved.
"<name>"
Specify the name, max. 20 characters, of the route to be saved.
<way_points>
Separated by commas
GPS.TRIP.WPOINT<index>.
specify
the
waypoints,
max.
20,
available
the
list
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GPS.TRIP.ROUTE1="Office",1,2,4,5,6
Get configuration
$PFAL,Cnf.Get,GPS.TRIP.ROUTE1
3.3.10.4
Parameter syntax
GPS.TRACE.DEV<index>
GPS.TRACE.DEV<index>=<"name">
This parameter is used to add the name of other MAMBO2-B6/UXFS devices that you want to
covertly follow/track when the situation requires. The name of devices given here will be listed
under the "Settings" symbol on the MAMBO2-B6/UXFS display. When you select a device from
that list the corresponding event "Display.Follow.eSelect=<index>" occurs. An example how to use
such an application is explained below. This configuration make sense when using more than one
MAMBO2-B6/UXFS device.
<index>
Specify an index to identify the devices. The index must be in the range 1 through 5.
"<name>"
Specify the name of the device to be shown on the MAMBO2-B6/UXFS's screen.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 225 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
This setting always follows the coordinates of the selected GPS.TRACE.DEV name. The coordinates
of the selected GPS.TRACE.DEV name can sequentially be updated via SMS or TCP by using the PFAL
command Display.POIs.Follow=<lat>,<lon>,<alt>,<radius>. This setting is very useful for tracing
people (e.g. criminals, kids, family members etc.). To automate this tracing feature in a MAMBO2B6/UXFS device, please refer to the example below:
Example:
Let's assume your kid is playing in a children playground and left that place after a short time.
The kid's MAMBO2-B6/UXFS device sends automatically an SMS to the parent's MAMBO2B6/UXFS because the playground is covered by a Geo-fence. The parents don't know in which
direction the kid is going to. With the help of the feature "Trace a MAMBO2-B6/UXFS", the
parents can build a special configuration in both MAMBO2-B6/UXFS devices that updates
periodically the location of the kid on their MAMBO2-B6/UXFS and the MAMBO2-B6/UXFS
points you to find the kid in a short time. To make such a trace application the configurations
given below should be loaded on the kids' and parents' MAMBO2-B6/UXFS device respectively.
This configuration works in this way:
when the parents receive an SMS message telling the kid left that Geo-fence, they browse to
the Follow symbol (with index 25) on the MAMBO2-B6/UXFS's screen, press the left-key and
then select the MAMBO2-B6/UXFS device that the kid is carrying (e.g. Kid). Once selected, an
SMS with contents "#78124" will be sent to the kid's MAMBO2-B6/UXFS. When the kid's
MAMBO2-B6/UXFS receives the text "#78124" it checks the GPS validity and starts
transmitting of the current location via SMS to the parent's MAMBO2-B6/UXFS every 60
seconds. The on-screen compass points the parents to the received location of the kid. This
view will also show the bee-line distance, in kilometer, between your current location and the
last received location of the kid. When the last received position of the kid's MAMBO2B6/UXFS is reached, this feature is automatically stopped.
Please note that, this is just an example to show the concept how to use this feature. In this
example kid's location is updated event every 60 seconds, that means the longer its takes to
find the kid, the more SMS are sent out from the kid's MAMBO2-B6/UXFS. In the same way
you may also implement this feature in your server by sending the position via TCP.
Configuration to be load on the kid's MAMBO2-B6/UXFS with phone number e.g.
+49333333:
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 226 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
$PFAL,CNF.Set,AL1=GSM.SMS.eIncoming.Number="+49111111"&GSM.SMS.eIncoming.Text="#78124":Sys.Timer0.Start=cyc
lic,60000
$PFAL,CNF.Set,AL2=GPS.Nav.sFix=valid&Sys.Timer.e0:GSM.SMS.SendRaw,"+49111111",0,"PFAL,Display.POIs.Follow=&(Lat),
&(Lon),&(Alt),20"
$PFAL,CNF.Set,AL3=GSM.SMS.eIncoming.Number="+49111111"&GSM.SMS.eIncoming.Text="#42187":Sys.Timer0.Stop
Configuration to be load on the parent's MAMBO2-B6/UXFS with phone number e.g.
+49111111:
$PFAL,CNF.Set,GPS.TRACE.DEV1="Kid"
$PFAL,CNF.Set,GPS.TRACE.DEV2="Kid2"
$PFAL,CNF.Set,GPS.TRACE.DEV3="Wife"
$PFAL,CNF.Set,AL4=Display.Follow.eSelect=1:GSM.SMS.SendRaw,"+49333333",0,"#78124"
$PFAL,CNF.Set,AL5=Display.Follow.eDest:GSM.SMS.SendRaw,"+49333333",0,"#42187"
$PFAL,CNF.Set,AL6=GSM.SMS.eIncoming.Number="+49333333":IO.Vibration=hpulse,1000
Note: SMS messages starting with a "#" sign or "PFAL" are not displayed on the MAMBO2-B6/UXFS
screen.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GPS.TRACE.DEV1="Kid"
Get configuration
$PFAL,Cnf.Get,GPS.TRACE.DEV1
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 227 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.11
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM parameters
3.3.11.1
GSM.PIN
Parameter syntax
GSM.PIN=<new_pin>
This parameter is used to enter and store the PIN <new_pin> for the used SIM card.
<new_pin>
Specify the PIN number of the used SIM card. This may be for example the SIM PIN to register
onto the GSM network, or the SIM PIN to replace the current PIN number with a new one.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GSM.PIN=1321
Get configuration
-
Notes
• Successful PIN authentication only confirms that the entered PIN was recognized and
correct. The PIN acception does not necessarily imply that the MAMBO2-B6/UXFS is
registered to the desired network. Typical example: PIN was entered and accepted, but the
MAMBO2-B6/UXFS fails to register to the network. This may be due to missing network
coverage, denied network access with currently used SIM card, no valid roaming
agreement between home network and currently available operators etc.
• To verify the present status of network registration, you can configure an alarm that
controls an LED to indicate the current state. The next way to verify if it is available,
establish remotely a voice or data call or just debug the firmware and check the
corresponded events.
• No PIN request is more pending, if the PIN number of used SIM card once has been
specified and it is sent to the MAMBO2-B6/UXFS device. The MAMBO2-B6/UXFS stores
that specified PIN and uses it upon request of the GSM part. No more PIN entry is required
from your side, as long as the used SIM card is not replaced with a new one.
• A PIN message sent without value deletes the existent entry, in this case, the command in
chapter 3.2.6.1.1, page 120 can be used to insert the SIM PIN.
3.3.11.2
GSM.BALANCE.DIAL
Parameter syntax
GSM.BALANCE.DIAL=<dial_text>
This parameter is used to dial a specific GSM number to get the remaining credit for your used prepaid card. By default, the device dials "*100#", however you might have to modify it if your
operator does not rely on this standard dial number.
<dial_text>
Specify the GSM dial number for retrieving balance information.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GSM.BALANCE.DIAL=*100#
Get configuration
$PFAL,Cnf.Get,GSM.BALANCE.DIAL
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 228 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.11.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.CALLID.EN
Parameter syntax
GSM.CALLID.EN=<enable>
This parameter is used to control the caller identification. This feature allows you to identify
incoming calls for accepting or rejecting them by using the events with specific numbers
accordingly. This parameter refers to the GSM supplementary services CLIP (Calling Line
Identification Presentation) and CLIR (Calling Line Identification Restriction). The CLIP enables a
called subscriber to get the calling line identity (CLI) of the calling party. The CLIR determines if
your participant will see or not your phone number.
<enable>
Define whether to enable or disable the caller identification. Following values can be set:
Value
Meaning
0
Disables caller identification (CLIP + CLIR)
1
(default) Enables caller identification (CLIP + CLIR)
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GSM.CALLID.EN=1
Get configuration
$PFAL,Cnf.Get,GSM.CALLID.EN
Notes
• If the value is omitted, then it is set to the factory default value.
3.3.11.4
GSM.OPERATOR.BLACKLIST
Parameter syntax
GSM.OPERATOR.BLACKLIST=<value>
This parameter is used to create a customized blacklist containing the GSM operator names that
will be considered unacceptably during GSM registration attempts.
<value>
Create a customized blacklist with GSM network names to which the device shouldn't be
registered. Following values can be set:
Value
disable
Meaning
(default)
Disables
the
blacklist
addresses.
If
the
GSM.OPERATOR.SELECTION mode is set to any or auto, this setting
speeds up the first GPRS attachment after powering on the device.
<"operator_1">,…..,<"operator_20">
Specify the operator name or the operator ID
for roaming. Up to 40 either operator names or Operator IDs separated by
commas can be specified. (e.g. T-Mobile, E-Plus, D2, 26201 etc.). Each
specified operator name or operator ID will not be used while GSM
registration prevent roaming or direct GSM connection to those operators.
Each entry must be enclosed in quotes (" "). See also the example in the
table below.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GSM.OPERATOR.BLACKLIST=disable
$PFAL,Cnf.Set,GSM.OPERATOR.BLACKLIST="E-Plus","D2"
Get configuration
$PFAL,Cnf.Get,GSM.OPERATOR.BLACKLIST
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 229 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.11.5
Parameter syntax
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.OPERATOR.SELECTION
GSM.OPERATOR.SELECTION=<value>
This parameter is used to define the operator selection mode. it is strongly not recommended to
change operator selection mode during normal operation (i.e. by setting alarms). The device
should be restarted after this mode has been changed. Also special care has to be taken when
configuring operator selection modes which restrict the usage of certain networks. In worst case,
GPRS and Data/Voice/SMS service may become unavailable in specific situations (i.e. when being in
foreign countries and using home_country as operator selection mode)
<value>
Create an operator selection list with GSM network names to which the device can be
registered. Following values can be set:
Value
any
Meaning
Automatically search for the GSM operator. If a permitted operator is
found, it registers to that operator. If the network is not found, it goes on
searching process and it remains unregistered.
manual,<desired_op>
Forces MAMBO2-B6/UXFS to select and register itself to any GSM
operator found in the list. If none of the listed GSM operator is found, the
MAMBO2-B6/UXFS will also register to the Roaming Networks, but it stays
GPRS detached all the time until one of the listed operators is found.
This option is not recommended for security based applications, as it is
possible to configure the system in a way which prevents
Voice/Datacall/SMS and GPRS connections.
A configured blacklist will be considered. Note that GPRS startup might be
delayed a bit if the blacklist feature is used.
A whitelist is optional and may be used to specify which operators HAVE
to be used for registration.
It is possible that no operators can be found and the device keeps
searching for them Voice calls and SMS are available when the device can
register to a GSM operator. If foreign countries Voice calls/SMS might
cause additional costs due to roaming.
<desired_op>
Specify the whitelist containing the GSM operator names which are
considered acceptably during the GSM registration attempts. Up to 20
operator names comma-separated can be specified. (e.g. T-Mobile, EPlus, D2, etc.). Do not specify any GSM operator name that is already
listed in the GSM.OPERATOR.BLACKLIST. Each entry must be enclosed in
quotes (" "). See also the example in the table below.
GPRS
Forces the MAMBO2-B6/UXFS to select only GSM network operators that
offer GPRS service. For each cell changes the MAMBO2-B6/UXFS performs
GPRS cell selection and re-selection processes. If the new cell does not
support GPRS services, the current operator will be changed. If no GSM
operator with GPRS enabled is found, the MAMBO2-B6/UXFS remains
unregistered for that time, but it is still searching.
auto
(Default) Forces the MAMBO2-B6/UXFS to select and register itself to the
any GSM network operator that is currently available. Whenever a GPRS
or PPP initialisation fails, the <value> will be switched automatically to
„GPRS".
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 230 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
restrictive_manual[,<desired_op>,<<desired_op>,...] This option is not recommended for
security based applications, as it is possible to configure the system in a
way which prevents voice/datacall/SMS and GPRS connections.
➢
no_roaming
Same functionality like manual selection. Additional, no voice/data
calls are possible and no outgoing SMS may be sent if no desired
operator can be found.
GSM starts up with any available operator, but performs GPRS only if no
roaming operator has been found. If within roaming, voice calls and SMS
are available.
restrictive_no_roaming Like no_roaming, except that no voice/data calls are possible and
no outgoing SMS may be sent if no desired operator can be found.
home_country,<mcc> GPRS connection is allowed only for operators within the configured
home country. Roaming in foreign country networks can be prevented this
way.
<mcc>:
Mobile country code for the desired country. This is usually a 3 digit
integral number - i.e. 262 for Germany. In order to get a mobile
country code for another country, simply set the operation mode to
any and if the device is within the desired country and finds a GSM
operator there, then use the PFAL command $PFAL,GSM.MMC to read
out the current mobile country code.
restrictive_home_country,<mcc> Like home_country, except that no voice/data calls are
possible and no outgoing SMS may be sent when being registered to
foreign networks. See description above what values can be set into the
<mcc> entry.
home_op
The device first searches for a home network service provider and enables
GPRS section as soon as it finds a GSM home operator. When the device is
registered at a foreign network (roaming), the GPRS section is disabled. If
the registration to the current GSM operator is lost (i.e. when driving
through tunnels etc.), the GPRS section is kept active until the GPRS
section timeout occurs. After the GPRS times out, the device will close that
GPRS section. This allows to re-use the current GPRS session when GSM
signal is weak or not available for a short time.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GSM.OPERATOR.SELECTION=any
$PFAL,Cnf.Set,GSM.OPERATOR.SELECTION=manual,"D1","O2"
$PFAL,Cnf.Set,GSM.OPERATOR.SELECTION=GPRS
$PFAL,Cnf.Set,GSM.OPERATOR.SELECTION=auto
Get configuration
$PFAL,Cnf.Get,GSM.OPERATOR.SELECTION
Notes
• The GPRS attachment might be delayed for a few minutes if the GSM.OPERATOR.BLACKLIST
is used.
• Do NOT change the GSM.OPERATOR.SELECTION mode during normal operation. The
device performs a restart process after the value is changed.
• Keep in main, that during a voice call no operator selection will be performed.
• Factory default value is set, if the value is omitted.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 231 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.11.6
Parameter syntax
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.OPLOST.RESTART
GSM.OPLOST.RESTART=<enable>,<interval>[,<fieldstrength>]
This parameter is used to restart the GSM engine in areas with bad GSM coverage. If the GSM
operator is lost, the MAMBO2-B6/UXFS device reinitializes the GSM engine periodically (at
specified intervals of time), until the device has found a GSM operator.
<enable>
Define whether to re-initialize the GSM engine in the event of bad GSM coverage or not.
Following values can be set:
Value
Meaning
0
Disables GSM re-initialization, if no GSM operator available.
1
(Default) Enables GSM re-initialization, if no valid GSM operator has been
found within the user-specified <interval>.
<interval>
Define the amount of time, in milliseconds, to wait before GSM engine reinitializes, if no GSM
operator found. Following values can be set:
Value
Meaning
0 .. 2147483647 The amount of time, in milliseconds, after which the system reinitializes
the GSM engine, if no GSM operator found. Default value is 1200000.
[<fieldstrength>]
Optional. Define the minimum GSM field strength from 1 to 20. If used the system checks
additionally whether GSM signal strength drops below the specified minimal field strength
within the <interval>.
Note: If the field strength drops just for a short time, the GSM engine does not restart.
Default value is 8.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GSM.OPLOST.RESTART=1,300000
$PFAL,Cnf.Set,GSM.OPLOST.RESTART=1,300000,7
Get configuration
$PFAL,Cnf.Get,GSM.OPLOST.RESTART
3.3.11.7
Parameter syntax
GSM.SMS.RESPONSE
GSM.SMS.RESPONSE=<enable>,<amount>
This Parameter enables the MAMBO2-B6/UXFS device to be set up as a SMS responder, on which it
reacts and automatically informs the SMS sender for the received SMS. It forwards the received
SMS message back to the SMS sender.
<enable>
Define whether to send SMS responses to the SMS sender or not. Following values can be set:
Value
Meaning
0
Disables SMS responses
1
(Default) Enables SMS responses
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 232 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
<amount>
Specify how many SMS responses should be sent by SMS if the SMS contents does not fits
within a SMS (e.g. when you query the configuration by SMS using the command
$PFAL,Cnf.Show). Default value is 5. Following values can be set:
Value
Meaning
1..5
The number of SMS responses !!!!
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GSM.SMS.RESPONSE=1,5
Get configuration
$PFAL,Cnf.Get,GSM.SMS.RESPONSE
Notes
• Warning: the maximum number of responses should not exceed the maximal number of
SMS output slots (else default value will be used).
• If too less output slots are free when a SMS PFAL command is detected, the response will
be queued inside the remaining output slots. Additional SMS will be deleted, if there are no
more free slots available.
• If all output buffers are used up, no SMS responses can be sent at the moment. Retry later.
3.3.11.8
GSM.CALL.SIGNALING
Parameter syntax
GSM.CALL.SIGNALING=<ringer>,<vibration>
This parameter enables Call Progress Tones.
<ringer>
Define whether to enable or disable Call Progress Tones. Following values can be set:
Value
Meaning
0
Disables Call Progress Tones (No audible signals will be heard during call
set up).
1
Enables Call Progress Tones. Audible signals returned by a network to a
call originator to indicate the status of a call. Examples of call progress
tones include dial tones and busy signals.
<vibration>
Define whether to enable or disable the vibration. Following values can be set:
Value
Meaning
0
Disables vibration in the device.
1
Enables vibration in the device.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GSM.CALL.SIGNALING=7,1
Get configuration
$PFAL,Cnf.Get,GSM.CALL.SIGNALING
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 233 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.11.9
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.SMS.SIGNALING
Parameter syntax
GSM.SMS.SIGNALING=<ringtone>,<vibration>
This parameter enables signalling of the received and sent SMS messages.
<ringtone>
Type of ring tone. You have a choice of 20 different ring tones. The selected ring tone will be
played on the speaker.
Value
Meaning
0
Disabels ringtones when receiving or sending SMS messages
1..20
Enables ringtones when receiving or sending SMS messages. Sequence
1 ... 20
<vibration>
Define whether to enable or disable signaling of received and sent SMS messages. Following
values are available:
Value
Meaning
0
Disables signaling when receiving or sending SMS messages.
1
(Default) Enables signaling when receiving or sending SMS messages.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GSM.SMS.SIGNALING=7,1
Get configuration
$PFAL,Cnf.Get,GSM.SMS.SIGNALING
3.3.11.10 GSM.MSG.SIGNALING
Parameter syntax
GSM.MSG.SIGNALING=<ringtone>,<vibration>
This parameter enables signalling when receiving a message via TCP.
<ringtone>
Type of ring tone. You have a choice of 20 different ring tones. The selected ring tone will be
played on the speaker.
Value
Meaning
0
Disabels ringtones when receiving a message via TCP
1..19
Enables ringtones when receiving a message via TCP. Sequence 1 ... 19.
<vibration>
Define whether to enable or disable signalling when receiving a message via TCP. Following
values are available:
Value
Meaning
0
Disables signaling when receiving a message via TCP.
1
(Default) Enables signaling when receiving a message via TCP.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GSM.MSG.SIGNALING=7,1
Get configuration
$PFAL,Cnf.Get,GSM.MSG.SIGNALING
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 234 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3.3.11.11 GSM.SMS.RETRIES
Parameter syntax
GSM.SMS.RETRIES=<counter>,<interval>
This parameter is used to enable the device to re-send failed SMS messages.
<counter>
Define how many times to try to re-send a SMS that reported error. Default is five (3). The
ranges from 1 to 9. It is not recommended to set this value greater than 5.
<interval>
Specify the time, in milliseconds, for device to wait before trying to re-send the filed SMS
message. Default is 5000 = 5 seconds.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GSM.SMS.RETRIES=5,5000
Get configuration
$PFAL,Cnf.Get,GSM.SMS.RETRIES
3.3.11.12 GSM.SMS.ALWAYSREAD
Parameter syntax
GSM.SMS.ALWAYSREAD=<value>
This parameter is used to enable reading of incoming SMS during an active voice call. Please notice
that, the indication of incoming SMS may be too loud when the user is on the phone.
<value>
Define whether to enable or disable the reading of incoming SMS during an active voice call.
Value
Meaning
0
(Default) Disables reading of incoming SMS.
1
Enables reading of incoming SMS.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GSM.SMS.ALWAYSREAD=1
Get configuration
$PFAL,Cnf.Get,GSM.SMS.ALWAYSREAD
3.3.11.13 GSM.SPYCALL.SELECTION
Parameter syntax
GSM.SPYCALL.SELECTION=<list>
This parameter is used to define a list of spy calls and to listen what’s happening in the MAMBO2’s
surroundings. This feature can be used to automatically answer the incoming authorised calls
without the phone rings or displays something on the screen. This feature is related only to the
phone numbers that added in the list of spy calls. To accept the spy calls that are available in the
list, you have to configure an alarm that uses the event GSM.VoiceCall.eIncoming="spy" as a
condition and the corresponding command as an action, as shown below:
$PFAL,Cnf.Set,AL98=GSM.VoiceCall.eIncoming="spy":GSM.VoiceCall.Accept&Display.Alarm=CALL,20,"spy call"
The second action "Display.Alarm=CALL,20,"Incoming call"" in AL98 is given only for test purposes.
It can be removed after tested.
<list>
Wrapped in quotation marks ("") and separated by commas, specify the list of spy calls. A part
of a phone number (belonging to a group of numbers) can also be specified (e.g. "+49633" for
all phone numbers starting with "+49633"). The max. number of spy calls to be specified is 4.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 235 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GSM.SPYCALL.SELECTION="+49311110","+493156111","+49511411","+49633"
Get configuration
$PFAL,Cnf.Get,GSM.SPYCALL.SELECTION
3.3.11.14 GSM.SPYCALL.EXCEPT
Parameter syntax
GSM.SPYCALL.EXCEPT="<value>"[,"<value>"]
This parameter is used to specify a list of spy numbers that will be excepted from the
GSM.SPYCALL.SELECTION list.
"<value>"
Wrapped in quotation marks ("") and separated by commas, you can specify either the phone
numbers from the list of spy calls that will be excepted. This value can be set to:
Value
Meaning
disable
(Default) Disables excepting of spy calls
....
Separated by commas, enter the phone numbers that will be excepted
from the list of spy calls.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GSM.SPYCALL.EXCEPT =+493111110","+4931561111"
Get configuration
$PFAL,Cnf.Get,GSM.SPYCALL. EXCEPT
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 236 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.12
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPRS parameters
3.3.12.1
Parameter syntax
GPRS.APN
GPRS.APN=<value>
This parameter is used to specify the APN Access Point Name (text string) used during GPRS
connection attempts. The APN is logical name that is used to select the GGSN or the external
packet data network. In other words, the APN name that your network operator has provided to
connect the MAMBO2-B6/UXFS to the Internet. The APN specifies the external network that a
MAMBO2-B6/UXFS can access. It also defines the type of IP address to be utilized, security
mechanisms to invoke, available value added services, redundancy, and fixed-end connections.
<value>
Specify the Access Point Name (APN). The logical name that will be used to select the GGSN or
the external packet data network. Consult your Network Operator for the correct APN
settings). Default name is "internet.eplus.de"
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GPRS.APN=internet.t-d1.de
Get configuration
$PFAL,Cnf.Get,GPRS.APN
Notes
• If the value is omitted, then it is set to the default value.
3.3.12.2
Parameter syntax
GPRS.AUTOSTART
GPRS.AUTOSTART=<value>
This parameter is used to specify the mode to start up a GPRS connection.
<value>
Specify the start-up mode of the GPRS connection. It can be set to:
Value
Meaning
0
(default) Disables the automatic attachments to the GPRS network.
1
Enables the automatic attachments to the GPRS network. If the GPRS
network connection gets lost, it tries to reconnect automatically as soon
as the network is available again.
How the parameter could be sent/ or its settings requested:
Set configuration
$PFAL,Cnf.Set,GPRS.AUTOSTART=1
Get configuration
$PFAL,Cnf.Get,GPRS.AUTOSTART
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 237 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.12.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPRS.DIAL
Parameter syntax
GPRS.DIAL=<dial_text>
This parameter is used to establish a communication to the external PDN (Public Data Network).
The V.250 'D' (Dial) command causes the MAMBO2-B6/UXFS to enter the V.250 online data state.
<dial_text>
Specify the GPRS dial text. Please contact your network provider to specify the correct dial
text. Default dial text is "ATD*99***1#".
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GPRS.DIAL=ATD*99***1#
Get configuration
$PFAL,Cnf.Get,GPRS.DIAL
Notes
• Usually, this setting needs not to be changed as most regions use the default dial text
(ATD*99***1#).
• If the value is omitted, then it is set to the default value.
3.3.12.4
GPRS.TIMEOUT
Parameter syntax
GPRS.TIMEOUT=<enable>,<G_timeout>
This parameter is used to detach the device from GPRS network if no TCP communication available
and timeout has passed.
<enable>
Define whether to start the GPRS timeout <G_timeout> or not. By default, this value is set to
1. However, the following values are available:
Value
Meaning
0
Disables GPRS timeout.
1
(Default) Enables GPRS timeout. If the GPRS.TIMEOUT is enabled you have
to manually disable the PPP.AUTOPING parameter.
<G_timeout>
Specify the period of time (in milliseconds) on which the device re-initializes GPRS connection,
if there is no TCP communication established within the user specified timeout. Please note
that, the specified value <G_timeout> must be greater than the timeout value <C-timeout>
defined by the TCP.CLIENT.TIMEOUT parameter, otherwise the GPRS connection will be
closed (and might be restarted) periodically, which may lead to an unreachable of the target
device. Default value is 600000. It means, GPRS restarts every 10 minutes if there is no TCP
communication available.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GPRS.TIMEOUT=1,600000
Get configuration
$PFAL,Cnf.Get,GPRS.TIMEOUT
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 238 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.12.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPRS.QOSMIN
Parameter syntax
GPRS.QOSMIN=<precedence>,<delay>,<reliability>,<peak>,<mean>
This parameter is used to specify a minimum acceptable profile checked by the MAMBO2-B6/UXFS
device against the negotiated profile returned in the Activate PDP Context Accept message.
<precedence>
Precedence class (numeric)
Value
Meaning
0
Network subscribed value
1
High Priority. Service commitments shall be maintained ahead of
precedence classes 2 and 3
2
Normal Priority. Service commitments shall be maintained ahead of
precedence class 3
3
Low Priority. Service commitments shall be maintained
<delay>
Delay class (numeric). The Delay parameter defines end-to-end transfer delay incurred in the
transmission of SDUs through GPRS network(s).
Value
0
Meaning
Network subscribed value
SDU size:128 octets:
Delay Class
Mean Transfer Delay
1 (Predictive)
2 (Predictive)
3 (Predictive)
4 (Best Effort)
<0.5
<5
<50
Unspecified
95 percentile Delay
<1.5
<25
<250
SDU size: 1024 octets:
Delay Class
Mean Transfer Delay
1 (Predictive)
2 (Predictive)
3 (Predictive)
4 (Best Effort)
<0.5
<5
<50
Unspecified
95 percentile Delay
<1.5
<25
<250
<reliability>
Reliability class (numeric)
Value
Meaning
0
Network subscribed value
1
Non real-time traffic, error-sensitive application that cannot cope with
data loss
2
Non real-time traffic, error-sensitive application that can cope with
infrequent data loss
3
Non real-time traffic, error-sensitive application that can cope with data
loss
4
Real-time traffic, error-sensitive application that can cope with data loss
5
Real-time traffic, error non-sensitive application that can cope with data
loss
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 239 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
<peak>
(numeric). Peak throughput class (in octets per second)
Value
0
Meaning
network subscribed value
Peak Throughput Class
1
2
3
4
5
6
7
8
9
Peak Throughput (in octets per second)
Up to 1 000 (8 kbit/s).
Up to 2 000 (16 kbit/s).
Up to 4 000 (32 kbit/s).
Up to 8 000 (64 kbit/s).
Up to 16 000 (128 kbit/s).
Up to 32 000 (256 kbit/s).
Up to 64 000 (512 kbit/s).
Up to 128 000 (1 024 kbit/s).
Up to 256 000 (2 048 kbit/s).
<mean>
(numeric). Mean throughput class
Value
0
Meaning
network subscribed value
Mean Throughput Class
Mean Throughput (in octets per hour)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
31
100 (~0.22 bit/s)
200 (~0.44 bit/s)
500 (~1.11 bit/s)
1 000 (~2.2 bit/s)
2 000 (~4.4 bit/s)
5 000 (~11.1 bit/s)
10 000 (~22 bit/s)
20 000 (~44 bit/s)
50 000 (~111 bit/s)
100 000 (~0.22 kbit/s)
200 000 (~0.44 kbit/s)
500 000 (~1.11 kbit/s)
1 000 000 (~2.2 kbit/s)
2 000 000 (~4.4 kbit/s)
5 000 000 (~11.1 kbit/s)
10 000 000 (~22 kbit/s)
20 000 000 (~44 kbit/s)
50 000 000 (~111 kbit/s)
best effort.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GPRS.QOSMIN=3,4,3,0,0
Get configuration
$PFAL,Cnf.Get,GPRS.QOSMIN
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 240 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.12.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPRS.QOS
Parameter syntax
GPRS.QOS=<precedence>,<delay>,<reliability>,<peak>,<mean>
This parameter is used to specify a Quality of Service Profile used when the device sends an
Activate PDP Context Request message to the GPRS network.
<precedence>
Precedence class (numeric)
Value
Meaning
0
Network subscribed value
1
High Priority. Service commitments shall be maintained ahead of
precedence classes 2 and 3
2
Normal Priority. Service commitments shall be maintained ahead of
precedence class 3
3
Low Priority. Service commitments shall be maintained
<delay>
Delay class (numeric). The Delay parameter defines end-to-end transfer delay incurred in the
transmission of SDUs through GPRS network(s).
Value
0
Meaning
network subscribed value
SDU size:128 octets:
Delay Class
Mean Transfer Delay
1 (Predictive)
2 (Predictive)
3 (Predictive)
4 (Best Effort)
<0.5
<5
<50
Unspecified
95 percentile Delay
<1.5
<25
<250
SDU size: 1024 octets:
Delay Class
Mean Transfer Delay
1 (Predictive)
2 (Predictive)
3 (Predictive)
4 (Best Effort)
<0.5
<5
<50
Unspecified
95 percentile Delay
<1.5
<25
<250
<reliability>
Reliability class (numeric)
Value
Meaning
0
network subscribed value
1
Non real-time traffic, error-sensitive application that cannot cope with
data loss
2
Non real-time traffic, error-sensitive application that can cope with
infrequent data loss
3
Non real-time traffic, error-sensitive application that can cope with data
loss
4
Real-time traffic, error-sensitive application that can cope with data loss
5
Real-time traffic, error non-sensitive application that can cope with data
loss
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 241 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
<peak>
(numeric). Peak throughput class (in octets per second)
Value
0
Meaning
network subscribed value
Peak Throughput Class
1
2
3
4
5
6
7
8
9
Peak Throughput (in octets per second)
Up to 1 000 (8 kbit/s).
Up to 2 000 (16 kbit/s).
Up to 4 000 (32 kbit/s).
Up to 8 000 (64 kbit/s).
Up to 16 000 (128 kbit/s).
Up to 32 000 (256 kbit/s).
Up to 64 000 (512 kbit/s).
Up to 128 000 (1 024 kbit/s).
Up to 256 000 (2 048 kbit/s).
<mean>
(numeric). Mean throughput class
Value
0
Meaning
network subscribed value
Mean Throughput Class
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
31
Mean Throughput (in octets per hour)
100 (~0.22 bit/s)
200 (~0.44 bit/s)
500 (~1.11 bit/s)
1 000 (~2.2 bit/s)
2 000 (~4.4 bit/s)
5 000 (~11.1 bit/s)
10 000 (~22 bit/s)
20 000 (~44 bit/s)
50 000 (~111 bit/s)
100 000 (~0.22 kbit/s)
200 000 (~0.44 kbit/s)
500 000 (~1.11 kbit/s)
1 000 000 (~2.2 kbit/s)
2 000 000 (~4.4 kbit/s)
5 000 000 (~11.1 kbit/s)
10 000 000 (~22 kbit/s)
20 000 000 (~44 kbit/s)
50 000 000 (~111 kbit/s)
best effort.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GPRS.QOS=3,4,3,0,0
Get configuration
$PFAL,Cnf.Get,GPRS.QOS
Notes
• If the value is omitted, it is set to the default value.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 242 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.13
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
PPP parameters
3.3.13.1
Parameter syntax
PPP.USERNAME
PPP.USERNAME=<value>
This parameter is used to specify a user name that together with the password will be used to log
(attach) itself into the GPRS network.
<value>
String type, supplied by your GPRS provider. Default value is "eplus".
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,PPP.USERNAME=t-d1
Get configuration
$PFAL,Cnf.Get,PPP.USERNAME
Notes
• Most providers do not require the user name. However, if it is required your GPRS provider
should have provided the details with your GPRS subscription.
3.3.13.2
Parameter syntax
PPP.PASSWORD
PPP.PASSWORD=<value>
This parameter is used to specify the password that together with the user-name will be used to
log (attach) itself into the GPRS network.
<value>
String type, supplied by your GPRS provider. Default value is "none".
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,PPP.PASSWORD=gprs
Get configuration
$PFAL,Cnf.Get,PPP.PASSWORD
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 243 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.13.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
PPP.AUTOPING
Parameter syntax
PPP.AUTOPING=<type>,<time>
This parameter is used to enable or disable the maximal idle time before the next ping is sent to
the GPRS network for keeping the GPRS connection alive.
<type>
By default, it is set to 0 (disabled). However, It can be set to:
Value
Meaning
0
Disables sending of pings to the GPRS network.
1
Enables sending of pings to the GPRS network for keeping the GPRS
connection alive. It is recommended to enable it if the GPRS.TIMEOUT
remains disabled, otherwise set it to 0.
<time>
Specify the amount of time, in milliseconds, on which a ping will be sent to the GPRS network.
Default value is 300000.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,PPP.AUTOPING=1,180000
Get configuration
$PFAL,Cnf.Get,PPP.AUTOPING
Notes
• The GPRS.TIMEOUT parameter replaces the functionality of the PPP.AUTOPING.
3.3.13.4
PPP.AUTH
Parameter syntax
PPP.AUTH=<auth_type>
This parameter is used to define the authentication method over PPP. By default, the
authentication over PPP is selected automatically. However, in some GSM networks it might be
required to define the authentication method manually.
<auth_type>
Specify the authentication method over PPP. It can be set to:
Value
Meaning
none
No authentication is done (NOT recommended to use this setting).
auto
(default) authentication method is selected automatically.
pap
Only PAP authorization method is used.
chap
Only CHAP authorization method is used.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,PPP.AUTH=auto
Get configuration
$PFAL,Cnf.Get,PPP.AUTH
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 244 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.14
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
TCP parameters
3.3.14.1
TCP.CLIENT.CONNECT
Parameter syntax
TCP.CLIENT.CONNECT=<s_enable>,<ip_address>,<port>
This parameter is used to specify the type, IP-address and port that your application will use to
connect to the remote server. MAMBO2-B6/UXFS actively initiates a connection to a remote server
when GPRS state is online. Firstly, set the IP-address and Port number and then execute manually
(if <s_enable> is set to 0) the "TCP.Client.Connect" command to connect to the server, as shown in
chapter 3.2.7.1.1, page 140. When the connection has been established successfully, the
"TCP.Client.sConnected" event occurs. If the remote server rejected the connection, a Error event
occurs. After a connection has been established, use the TCP.Client.Send,<protocols>,<"text">
command to stream data to a remote server. A "TCP.Client.ePacketSent" and a
"TCP.Client.eReceived" event occur when there is outgoing and incoming data accordingly. If the
<s_enable>=0, use the "TCP.Client.Disconnect" command to terminate the connection , otherwise
set the <s_enable>=0 before using the "TCP.Client.Disconnect" command.
<s_enable>
Activates/deactivates automatically connection to the remote server. Following values can be
used:
Value
Meaning
0
Deactivates automatically connection to the remote server.
1
(default) Activates automatically connection to the remote server. If the
TCP connection to the remote server gets lost, the MAMBO2-B6/UXFS will
automatically attempt to reconnect as soon as the remote server will be
available again.
<ip_address>
IP address in dotted-four-byte format. It is the IP address to which the MAMBO2-B6/UXFS will
be registered and send its data. The format of this address is "xxx.xxx.xxx.xxx". See also
chapter 2.3, page 25.
It is also possible to specify a DNS address in the form (for example www.falcom.de) instead
of a dynamic or static IP-address. In such a case it is not required to set up any DNS provider,
it is automatically done.

IMPORTANT:
[1] The port number must be specified .
[2] Using DNS can cause much traffic if the specified domain does not exist (the device keeps
requesting of the IP-address until one is returned)
[3] The MAMBO2-B6/UXFS clears automatically the implemented DNS cache (inside the unit)
if the server refuses that connection immediately (it deletes an old DNS entry that maybe
not up to date. During the next reconnection the MAMBO2-B6/UXFS retrieves
automatically a new IP-address and can continue normal operation)
[4] Note that, if the server login fails (i.e. the server closes the TCP connection without
requiring any acknowledge), DNS query process will be restarted during the next
reconnection.
<port>
Specify the port number used for TCP communication between the MAMBO2-B6/UXFS device
and the remote server. See also See also chapter 2.3, page 25.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,TCP.CLIENT.CONNECT=1,80.237.154.33,2222
Get configuration
$PFAL,Cnf.Get,TCP.CLIENT.CONNECT
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 245 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Notes
• The values are comma-separated ",".
• Contact your network administrator to specify a correct server IP address and port
number.
3.3.14.2
TCP.CLIENT.ALTERNATIVE
Parameter syntax
TCP.CLIENT.ALTERNATIVE=<a_enable>,<a_ip_address>,<a_port>
This parameter is used to define an alternative server in case the primary server fails. This allows to
define a fallback server which can be used in case the primary server gets disconnected/doesn't
respond anymore. If both servers aren't available, the device continues to attempt a connection
(alternately to defined "primary" and "alternative" server). A wait time between 2 connection
attempts can be specified using the setting TCP.CLIENT.TIMEOUT.
<a_enable>
Enables/disables automatically connection to the remote server. Following values can be
used:
Value
Meaning
0
Disables automatically connection to the alternative server (default).
1
The specified server address will be used for each second connection
attempt.
<a_ip_address>
IP address in dotted-four-byte format. It is the IP address to which the MAMBO2-B6/UXFS will
be registered and send its data. The format of this address is "xxx.xxx.xxx.xxx". See also
chapter 2.3, page 25.
It is also possible to specify a DNS address in the form (for example www.falcom.de) instead
of a static IP-address. In such a case it is not required to set up any DNS provider, it is
automatically done.
<a_port>
Specify the port number used for communication between the MAMBO2-B6/UXFS device and
alternative remote server. See also See also chapter 2.3, page 25.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,TCP.CLIENT.ALTERNATIVE=0,217.119.194.35,2222
Get configuration
$PFAL,Cnf.Get,TCP.CLIENT.ALTERNATIVE
Notes
• All values are separated by commas ",".
• Contact your network administrator to specify a correct server IP address and port
number.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 246 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.14.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
TCP.CLIENT.PING
Parameter syntax
TCP.CLIENT.PING=<type>,<time>
This parameter is used to activate or deactivate the maximum idle time before the next ping is sent
to the remote server.
<type>
Define whether to activate or deactivate sending of pings to remote server. It can be set to:
Value
Meaning
0
Deactivates sending of pings to the remote server.
1
Activates sending of pings to the remote server (it is recommended). These
pings are used to ensure the remote server that the MAMBO2-B6/UXFS
device is still present in an active TCP connection.
<time>
Specify the amount of time, in milliseconds, on which a ping will be sent to the remote server.
The value is server dependent time out.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,TCP.CLIENT.PING=1,120000
Get configuration
$PFAL,Cnf.Get,TCP.CLIENT.PING
3.3.14.4
TCP.CLIENT.TIMEOUT
Parameter syntax
TCP.CLIENT.TIMEOUT=<C-timeout>,<wait_time>
This parameter is used to specify the number of reconnections to the remote server when TCP
connection fails.
<C-timeout>
Specify the period of time, in milliseconds, the target device will wait for a response (an
acknowledgement) from the remote server about the received data and the next data
transmission. Default value is 300000.
<wait_time>
Specify the length of time, in milliseconds, the MAMBO2-B6/UXFS device waits between two
connection attempts. Please note that, the specified value <C-timeout> must be smaller than
the timeout value <G_timeout> defined by the GPRS.TIMEOUT parameter, otherwise the
MAMBO2-B6/UXFS device closes the GPRS connection before it is trying to perform a TCP
connection to the remote server. Default value is 30000.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,TCP.CLIENT.TIMEOUT=300000,30000
Get configuration
$PFAL,Cnf.Get,TCP.CLIENT.TIMEOUT
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 247 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.14.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
TCP.CLIENT.DNS.TIMEOUT
Parameter syntax
TCP.CLIENT.DNS.TIMEOUT=<dns_cache_timeout>
The MAMBO2-B6/UXFS has the feature to cache the DNS records for a fixed period of time. This
parameter is used to control caching of DNS records. The DNS cache consists of a fixed portion of
SRAM memory. The DNS cache is lost whenever the MAMBO2-B6/UXFS device is switched off and
no user-backup-battery is already connected.
<dns_cache_timeout>
Specify the DNS cache timeout. The length of time (in seconds) to keep the DNS cache valid.
After the time expires, the DNS memory cache will be updated with new data. It can be set to
a value from 0 to 4294967295.
Setting the DNS cache timeout to 0 results that the MAMBO2-B6/UXFS always performs a new
DNS query process.
Setting the DNS cache timeout to 4294967295 results that MAMBO2-B6/UXFS each 49.7 days
(converted from seconds to days) performs a new DNS query process. By default, it is set to
86400 resulting each 1 day the MAMBO2-B6/UXFS performs a new DNS query process.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,TCP.CLIENT.DNS.TIMEOUT=86400
Get configuration
$PFAL,Cnf.Get,TCP.CLIENT.DNS.TIMEOUT
Notes
• However, a DNS query process will automatically be performed, whenever the MAMBO2B6/UXFS tries to perform a TCP connection and the TCP connection establishment fails.
• note that device resets will still clear all TCP data
3.3.14.6
TCP.CLIENT.LOGIN
Parameter syntax
TCP.CLIENT.LOGIN=<logindata>
This parameter is used to activate sending of login data to the remote server.
<logindata>
It can be set to:
Value
Meaning
0
Deactivates sending of login-information to remote server.
1
(Default). Activates sending of login-information to remote server. It sends
the same data as the "MSG.Info.ServerLogin" message described in
chapter 3.2.8.4.1, page 163. This data is sent after the MAMBO2-B6/UXFS
has successfully established a TCP connection to the remote server. The
login data can then be used to ensure the connection of the MAMBO2B6/UXFS to the remote server.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,TCP.CLIENT.LOGIN=1
Get configuration
$PFAL,Cnf.Get,TCP.CLIENT.LOGIN
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 248 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.14.7
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
TCP.CLIENT.LOGIN.EXT
Parameter syntax
TCP.CLIENT.LOGIN.EXT="<version>"
This parameter is used to define the login extension data to be additionally sent to the remote
server.
"<version>"
Wrapped in quotation marks (" "), specify up to 256 chars. The specified text can be used as
an extension to the login data the MAMBO2-B6/UXFS will send to the TCP server after the
connection is established.
The text send to the server will look like:
DeviceName=...
Ext=2.5.11
Software=....
In order to add dynamic entries (entry) within this text, then use the following syntax:
"text&(<entry1>)"
Dynamic entries are listed in chapter 7.2 page 321. Between each dynamic entry use the
ampersand "&" and then without spaces enclose each of them with parentheses "( )". See
example below.
For example:
$PFAL,GSM.SMS.Send,"+491111111",0,"on &(Date) at &(Time) it is moving at &(Speed) m/s"
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,TCP.CLIENT.LOGIN.EXT="2.5.11"
Get configuration
$PFAL,Cnf.Get,TCP.CLIENT.LOGIN
3.3.14.8
TCP.SERVICE.CONNECT
Parameter syntax
TCP.SERVICE.CONNECT=<s_enable>,<ip_address>,<port>
This setting allows to configure a TCP service connection, which allows to run services like
remote control, configuration, remote updates, AGPS etc.. without the need to reconfigure a
currently used TCP client connection.
<s_enable>
For detailed information about this setting, refer to the chapter "TCP.CLIENT.CONNECT".
<ip_address>
For detailed information about this setting, refer to the chapter "TCP.CLIENT.CONNECT".
<port>
For detailed information about this setting, refer to the chapter "TCP.CLIENT.CONNECT".
How the configuration could be set/requested:
Set configuration
$PFAL,Cnf.Set,TCP.SERVICE.CONNECT=1,217.119.194.35,2222
Get configuration
$PFAL,Cnf.Get,TCP.SERVICE.CONNECT
Notes
• Contact your network administrator to specify a correct server IP address and port number.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 249 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.14.9
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
TCP.SERVICE.TIMEOUT
Parameter syntax
TCP.SERVICE.TIMEOUT=<C-timeout>,<wait_time>
This parameter is used to define the period of time the device will wait for a response and between
two connection attempts when the connection to the TCP service server fails.
<C-timeout>
Refer to chapter "TCP.CLIENT.TIMEOUT " for more details.
<wait_time>
Refer to chapter "TCP.CLIENT.TIMEOUT " for more details.
How the configuration could be set/requested:
Set configuration
$PFAL,Cnf.Set,TCP.SERVICE.TIMEOUT=240000,60000
Get configuration
$PFAL,Cnf.Get,TCP.SERVICE.TIMEOUT
Notes
• In general, the timeout should never exceed 10 days (10*24*3600*1000).
• The standard specification for a TCP timeout is 5 minutes. The timeout above 15 minutes is
not recommended.
3.3.14.10 TCP.CLIENT.SENDMODE
Parameter syntax
TCP.CLIENT.SENDMODE=<mode>
This parameter is used to select the type of TCP transmissions between fast and safe.
<mode>
Specify how fast TCP packets should be sent to. It can be set to:
Value
Meaning
0
Safe mode (default). Safe transmission prevents loosing packets during
TCP/GPRS reconnects. Only one single packet is sent at a time. When the
server has confirmed a packet with „ack sent", the next packet is sent.
Even if a TCP timeout occurs no packets can get lost.
1
Fast mode. Fast transmission speeds up large transmissions. Multi
packets are sent at a time. If a TCP/GPRS timeout occurs, sent but not yet
acknowledged packets could get lost.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,TCP.CLIENT.SENDMODE=0
Get configuration
$PFAL,Cnf.Get,TCP.CLIENT.SENDMODE
Notes
• When the device resets, all TCP data will be cleared.
• It is not recommended to change this setting during a transmission.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 250 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3.3.14.11 TCP.STORAGE
Parameter syntax
TCP.STORAGE=size=<value>,dispatch=<mode>
This parameter is used to specify the size of TCP storage and the operation mode.
<value>
Specify the size in bytes of the TCP storage to be set. It must be an integer number between 1
and 4096. The TCP storage holds the data that should be transferred by means of the TCP
storage. By means of TCP.Storage.Dispatch command the contents of data in the TCP storage
can be moved to an internal outgoing TCP buffer when the TCP storage is created. If there is
no enough memory available to satisfy a TCP storage requirement, MAMBO2-B6/UXFS will
report an error upon attempting to start TCP.Storage.Dispatch command.
<mode>
Currently the TCP storage supports two operation modes.
Value
Meaning
manual
If this mode is selected, the TCP storage has to be dispatched manually
(i.e. you have to determine when to send the stored information via TCP)
auto
This mode allows the system to dispatch automatically the data inside the
TCP storage whenever it is used up.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,TCP.STORAGE=size=512,dispatch=manual
Get configuration
$PFAL,Cnf.Get,TCP.STORAGE
3.3.14.12 TCP.SMTP.CONNECT
Parameter syntax
TCP.SMTP.CONNECT=<enable>,<mail_server_address>,<mail_server_port>
This parameter is used to configure the sending of E-Mails via an Internet mail server. It opens a
connection to the SMTP server using the <mail_server_address> and <mail_server_port> values
when the device attempts to send out E-Mail messages.
<enable>
Enables/disables the sending of E-Mail via an Internet mail server. Following values can be
used:
Value
Meaning
0
(default) Disables sending of E-Mail.
1
Enables sending of E-Mail.
<mail_server_address>
Specify a string used to identify the address of the remote computer system. It can contain an
IP address in dotted-decimal form, such as "129.3.1.24", or a name, such as
"smtp.mail.yahoo.com ".
Sending email from your MAMBO2-B6/UXFS device over GPRS will probably be connecting
using the GPRS service of your network operator, and will need to use your ISPs SMTP server,
not their SMTP server. As an example, if you use D1 as your GPRS network operator and
yahoo.com as your email provider, you will not be able to send email using smtp.o2.co.uk,
you would need to use smtp.mail.yahoo.com.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 251 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
<mail_server_port>
An integer value used to identify the port number on the remote computer system in
<mail_server_address>.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,TCP.SMTP.CONNECT=1,217.119.194.35,2222
Get configuration
$PFAL,Cnf.Get,TCP.SMTP.CONNECT
Notes
• All values are separated by comma ",".
• Contact your ISP provider to specify a correct outgoing mail server address and port
number.
3.3.14.13 TCP.SMTP.LOGIN
Parameter syntax
TCP.SMTP.LOGIN=<"domain">,< timeout>,<"username">,<"password">
This parameter is used to configure the authentication for the SMTP session when sending E-Mail
to an Internet mail server. Set the Username and Password values before performing the
TCP.SMTP.Send command. If the Username or Password is invalid, or blank and the Username and
Password are required, the authentication to the remote mail server will fail.
<"domain">
String type. Specify the domain name from the Internet address. For example "fal.de".
<timeout>
Specify the amount of time (in seconds) to wait for a response from the socket before the
current operation is aborted.
<"username">
Specify a string of your email account that contains the authentication identity provided when
using the authentication mechanisms for the SMTP client in the authenticate process.
<"password">
Specify a string of your email account that contains the authentication credentials provided
when using the authentication mechanisms for the SMTP in the authenticate process.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,TCP.SMTP.LOGIN ="<domain>",180,"<Username>,"<password>"
Get configuration
$PFAL,Cnf.Get,TCP.SMTP.LOGIN
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 252 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
3.3.14.14 TCP.SMTP.FROM
Parameter syntax
TCP.SMTP.FROM=<"fromaddress">
This parameter is used to configure the E-Mail address of the sender of the message.
<"fromaddress">
String email formatted. Specify the E-Mail address of the sender of the message. Please, enter
a valid email address. If your email address is incorrect or invalid your massage may be
cancelled.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,TCP.SMTP.FROM="email_address"
Get configuration
$PFAL,Cnf.Get,TCP.SMTP.FROM
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 253 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.15
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GF parameters (Geofence)
This section describes how the Geo-fence works and how to set up a Geo-fence to the MAMBO2B6/UXFS device. It is assumed that the users have a basic understanding of conditional logic and
geographic coordinates.
3.3.15.1
How to setup a GeoFence in the MAMBO2-B6/UXFS
The Geo-fence is a term used to describe an event when the vehicle fitted with a GSM/GPS unit enters
or leaves an electronic geographic boundaries. Once a geo-fence is setup, users can be automatically
notified, as a result of event occurring, if a vehicle enters or leaves the user pre-defined area(s)/Geofences. This functionality can be used for territory management, route verification, arrival/departure
notification and prohibited locations. Exception reporting can also be applied to a wide variety of
additional events, such as arrivals, departures, deliveries, pick-ups, illegal entries, unauthorized
movement, and more. The MAMBO2-B6/UXFS device based on the GPS system recognizes if the vehicle
crosses a user-defined geographic boundary, therefore, a SMS alert is issued or other services can be
used for notification. The constructed form of geographic boundary zones (Geo-fences) may be either a
rectangular or circular one in different sizes.
The figure below shows possibilities of defining Geo-fences within an area (the area’s boarder is
coloured blue).
Figure 7:
3.3.15.2
Possibilities of defining Geo-fences within an area
Determine the Zone’s Grid Coordinates
The MAMBO2-B6/UXFS firmware supports one kind of coordinate format for latitude and longitude
(decimal format). The supported format is based on the output of NMEA protocol format.
 Latitude, longitude (in decimal format, indicated in red and blue color).
$GPRMC,141128.638,A,50.712222,N,10.881944,E,0.07,103.22,280104,,*3E
If you use a mapping software (e.g. Map&Guide) to determine the rectangle coordinates of the Geofences to be set, then open it and locate the coordinate text that displays the geographic coordinates of
your cursor location on the map:
 For the Map&Guide, by moving the mouse cursor on the map the current coordinates
(Longitude/Latitude in degrees, minute and second) are displayed at the bottom corner on the
first panel of the viewer window.
Locate the zone you want to define on the map, and note down the min. longitude/Latitude and the
max. longitude/Latitude coordinates of a rectangle that defines the zone/Geo-fence, as shown in figure
below.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 254 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Figure 8:
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Determine the Zone’s Grid Coordinates
In our example (in degrees, minutes, seconds):
Longitude (min.) = 10°53’11" E
Latitude (min.) = 50°40’16" N
Longitude (max.) = 10°57’17" E
Latitude (max.) = 50°42’41" N
In order to convert coordinates from degrees, minutes, seconds format into decimal format, refer to
chapter 7.7, "How to convert the coordinates", page 339.
After you have determined the grid coordinates for your rectangular zone/Geo-fence, one last step
before setting up the configuration is to determine the sign of the coordinate values. Please remember
that, Latitude North and Longitude East are positive and Latitude South and Longitude West are
negative (see also figure below):
Figure 9:
Determining the sign of the coordinate values
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 255 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.15.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Setting up Geofences and areas
Set up the configuration as normal based on the parameter syntax, and enter the parameters as
indicated in chapter 3.3.15.6, "GF<id>", page 260. The set values of GF3 are obtained from chapter 7.7,
page 339.
$PFAL,Cnf.Set,GF.Area4="Ilmenau-City"
$PFAL,Cnf.Set,GF3=area<flag>,"name",R,<La_Min>,<Lo_Min>,<La_Max>,<Lo_Max>
$PFAL,Cnf.Set,GF3=area<flag>,"Ilmenau",R,50.6711,10.8863,50.7113,10.9547
A set up Geo-fence index always generates two different events:

GPS.Geofence.e<index>=inside - occurs when the vehicle enters into the pre-defined Geo-fence boundaries.

GPS.Geofence.e<index>=outside - occurs when the vehicle leaves the pre-defined Geo-fence boundaries.
An automatically established area index also generates two different events:

GPS.AREA.e<index>=inside - occurs when the vehicle enters into the area boundaries*.

GPS.AREA.e<index>=outside - occurs when the vehicle leaves the area boundaries*.
* Geographic boundaries are automatically generated from a collection of set up Geo-fences
For our example:
"GPS.Geofence.e3=outside" and "GPS.AREA.e4=outside" events occur when the Latitude of the
vehicle’s current position is bigger than 10°57’17" AND smaller than 10°53’11" AND the
Longitude of the vehicle’s current position is bigger than 50°42’41" AND smaller than
50°40’16".
"GPS.Geofence.e3=inside" and "GPS.AREA.e4=inside" events occur when the Latitude of the vehicle’s
current position is smaller than 10°57’17" AND bigger than 10°53’11" AND the Longitude of
the vehicle’s current position is smaller than 50°42’41" AND bigger than 50°40’16".

The MAMBO2-B6/UXFS device can store up to 100 Geo-fences, and up to 32 areas where
one of them is parking area. The parking area is pre-defined and is not configurable; it can
only be activated using the command in chapter 3.2.5.3.1. The ID-number of the parking
area is "0".
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 256 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.15.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GF.CONFIG
Parameter syntax
GF.CONFIG=maxdop=<max_dop>,parkradius=<park_radius>,changes=<changes>
This parameter is used to manage the global configuration of the Geo-fence functionalities. Based
on this configuration you are able to control vehicle's entries and leaves within and out of your set
up Geo-fences.
<max_dop>
This setting specifies the allowed maximal PDOP (GPS position accuracy error) value for
Geofencing. If this value is exceeded, no Geofence events will be generated. The background
is, that if DOP exceeds the defined limit, positioning errors increase more and more, which
usually result in wrong geofence or area events. Therefore, Geofence checks are performed
only when the PDOP value is inside the defined range (i.e. 5 means approx. 50 metres
maximal error). This means that only if GGA is inside range then the updated geofence states
are available. If e.g. a geofence is configured while PDOP is out of range, its status will initially
be set to outside.
<park_radius>
Define the radius in meter of the circular area to be used as Geo-fence park area. The center
point is the MAMBO2-B6/UXFS GPS position. It places the MAMBO2-B6/UXFS (vehicle) into a
restricted circle zone (park radius), where the current position (including Latitude and
Longitude) of the MAMBO2-B6/UXFS is the center of circle and the <park_radius> is the radius
of circle. Default value is 200.
<changes>
This parameter may be set to „on“ or „off“, which can be used to prevent occurring of any
Geo-fence (GF.e<ID>) event. The area events will be displayed always.
Value
Meaning
on
(default) Enables occurring of the Geo-fence events (GF.e<ID>).
off
Disables occurring of the Geo-fence events (GF.e<ID>). (It does not affect
the AREA events. These events always will be occurred).
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GF.CONFIG=maxdop=5,parkradius=200,changes=on
Get configuration
$PFAL,Cnf.Get,GF.CONFIG
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 257 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.15.5
Parameter syntax
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GF.AREA<id>
GF.AREA<ID>=<"text">
This parameter is used to create areas for setting up Geo-fences in a range of 0 to 31. An area may
be a Geo-fence or a collection of up to 100 separate Geo-fences. Area boundaries are
automatically increased or decreased in size according to the set of the size of set up Geo-fences.
As reference, see also figure attached in chapter 3.3.15.6 on page 260. Each area consists of two
events ("GPS.Area.e<id>=inside" and "GPS.Area.e<id>=outside") and two states ("GPS.Area.s<id>=inside"
and "GPS.Area.s<id>=outside") that automatically rise whenever the corresponding area<ID> is
entered or left respectively. If an area includes more than one overlapped Geo-fences, then no
event rises (area event) while the MAMBO2-B6/UXFS is moving within the set Geo-fences of that
area. Geo-fences and their size can be set up and (re-)configured using the "GF<id>" parameter.
Also, several names of set areas can be linked to available ID-numbers of the set areas.
<ID>
Specify the ID-number of an area. It is used to separate areas and to group Geo-fences. Up to
32 areas in range of 0 to 31. The configuration is stored in the on-board FLASH memory of the
MAMBO2-B6/UXFS.
<"text">
Define the text for an area index that will be displayed together also with each area event. For
example, "AREA.e0=outside" without quotation marks. The maximal length of string to be
specified is limited to 50 characters.
How to sent/get the configuration:
Set configuration
Get configuration
$PFAL,Cnf.Set,GF.AREA0="park area"
$PFAL,Cnf.Set,GF.AREA1="City East"
$PFAL,Cnf.Set,GF.AREA2="City West "
$PFAL,Cnf.Set,GF.AREA3="City Centre"
$PFAL,Cnf.Set,GF.AREA4="City"
$PFAL,Cnf.Get,GF.AREA0
$PFAL,Cnf.Get,GF.AREA1
Notes
• The text of the GF.AREA0="park area" parameter may be redefined, however the
GF.AREA0 should not be used as an area for other Geo-fences, if the parking area is
set/activated (see chapter 3.2.5.3.1, "GPS.Geofence.Park.Set – Places and activates
parking area", for more details).
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 258 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.15.6
Parameter syntax
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GF<id>
GF<ID>=area<flag>,<"name">,<shape>
This parameter is used to set up to 100 Geo-fences in arrange of 0 to 99, define the form of Geofences and place them to a specific area(s) (GF.AREA). The purpose of Geo-fences is to be
automatically notified about the entries and exits of the MAMBO2-B6/UXFS unit into or from a
preset area by using the corresponding events. The MAMBO2-B6/UXFS device can hold up to 100
Geo-fences setup either as a rectangle or as a point with a radius zone. The coordinates of each
Geo-fences can be obtained from any map software, and then converted (if needed) into the
format supported by the MAMBO2-B6/UXFS (please, refer to chapter 3.3.14.12 on page 252, for
more details). The MAMBO2-B6/UXFS device stores the specified configuration into the on board
FLASH memory, and this configuration will be available until it is overwritten. Each Geo-fence
consists of two events and two states that automatically rise whenever the corresponding Geofence is entered or left (more details about events and states can be found in chapter 3.4.5.4 on
page 293). Several Geo-fences can be set up into a single area, which allow you to define and cover
up a very complex moving direction. In this way the MAMBO2-B6/UXFS device can move through
several Geo-fences, but within a single area, without occurring of any area events. Additionally, if
within an area are placed several Geo-fences, then a part of each set Geo-fences must overlap its
neighbour in the moving direction, otherwise area events rise when a Geo-fence is entered or left.
Overlapping of these Geo-fences prevent occurring of area events or alarm notification while the
MAMBO2-B6/UXFS moves within the set Geo-fences of an area. Geo-fences may also be attached
to several areas (if certain regions in the map belong to different areas, see Example 2 for more
details).
<ID>
Specify the ID-number of a Geo-fence. It is used to separate Geo-fences. Up to 100 Geofences, in range of 0 to 99. A Geo-fence<ID> can be set/attached to several areas<ID> if the
setup conditions allow it. Geo-fences are automatically stored for use in the on-board FLASH
memory of the MAMBO2-B6/UXFS and these will be available all the time until manually
updated or deleted.
<flag>
The <flag> is used to place/attach specific Geo-fence<ID> to one or several areas<ID>. The
string "area" preceding the <flag> is predefined and must be written as is in small letters. Geofences could not work alone; they work only in connection with areas. That means, if you
specify a Geo-fence you have to determine the area where this Geo-fence will be placed.
The <flag> consists of a 32 bit (4 byte) hexadecimal number in the range 0x0 … 0xFFFFFFFF.
Each bit in this value stands for a single area (0 – 31).
For example, if you configure an area GF.AREA10="Street 21", the <ID>10 means that bit 10
from 32 is set high (1) and this value corresponds to hexadecimal value of 0x400
(^=100000000002).
The conversion to binary format will help you have a better understanding:
Format
BIN
Range Value in binary format (32-bit)
0000 0000 0000 0000 0000 0000 0000 00002 … 1111 1111 1111 1111 1111 1111 1111 11112
Each bit shown in table above consists of a single area (0 – 31).
Before starting to set up a Geo-fence, make sure you have already done the configuration of
that area that will cover up that Geo-fence.
After the user has set up the configuration into the MAMBO2-B6/UXFS device, it starts
comparing its current location with the location of set areas and Geo-fences based on the
area<flag> value. If there are disagreements with the user set configuration alarm, you will be
automatically notified when alarms are executed.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 259 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Examples (Example 1 and Example 2) will help you have a better understanding of areas and
Geo-fences configuration settings.
<"name">
String type, up to 30 characters, it specifies the name of a Geo-fence. The specified name
must be wrapped in quotation marks (" ").
<shape>
Define the Geo-fences shape to be created. The shape can be either an square/rectangle or a
point with radius zone (circle). The easiest way to obtain the coordinates of shapes is to use a
mapping software. As reference, see chapter 7.7 on page 339 and chapter 3.3.15.2 on page
255.
Note that, the number of fractional digits for the Longitude/Latitude value is limited to 5
digits, like "50.67340".
Value
Meaning
C,<lat>,<lon>,<alt>,<radius>
Creates a circle shape.
<lat>
Specify the latitude, in decimal format.
<lon>
Specify the longitude, in decimal format.
<alt>
Specify the altitude, in meter. It corresponds to the centre of the circle.
<radius>
Specify the radius of the circle, in meter. When the device enters into
such Geofencing zones, the firmware compares the calculated angle
between the centre of the specified circle (longitude, latitude) and
altitude with the current position of the device rather than the given
radius value. That means if the altitude is given wrong and does not
match the altitude where the circle is set, results a wrong calculation
of the radius, so false alarms may be activated.
R,<la_LL>,<lo_LL>,<la_UR>,<lo_UR> Creates a square/rectangle shape. Based on the
longitude and latitude it allows you to restrict a zone you want to
determine on the earth. The upper left corner (LL) and the lower right
corner (UR) coordinates of the rectangle are required to define the zone.
function Supports
<la_LL>
Latitude, in decimal format. Specify the Lower Left corner of value the
rectangle.
<lo_LL>
Longitude, in decimal format. Specify the Lower Left corner value of
the rectangle.
<la_UR>
Latitude, in decimal format. Specify the Upper Right corner value of the
rectangle.
<lo_UR>
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 260 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Longitude, in decimal format. Specify the Upper Right corner value of
the rectangle.
How to sent/get the configuration:
Set configuration
$PFAL,Cnf.Set,GF1=area8000,"Falcom Office",R,50.67340,10.98060,50.67350,10.98070
$PFAL,Cnf.Set,GF1=area8000,"Falcom Office",C,50.67340,10.98060,482,100
Get configuration
$PFAL,Cnf.Get,GF1
Example 1:
This example represents how to cover up a driving route using several Geo-fences within just an
area. The purpose of such configurations is to notify users whenever the MAMBO2-B6/UXFS
device enters/exits a Geo-fence or only when it enters/exits an area - features for
arrival/departure notifications.
As reference use the diagram attached to this example.
For example you have configure just one area (e.g. GF.AREA4) with following settings:
GF.AREA4="City" // corresponds to hex value 10 (1403020100 - 100002)
Later on, based on the area settings you may configure the Geo-fences that will be attached to.
The defined GF.AREA4="City" means that bit 4 is set to high (1) all other bits are low (1403020100).
So the Binary value of 100002 converted to the hexadecimal value is 10, which will be entered to
the area<flag>.
GF1=area10,"B88",R,50.67340,10.98060,50.67350,10.98070
GF2=area10,"Street 1",R,….
GF3=area10,"Street 5",R,….
GF4=area10," B104",R,….
GF5=area10,"Street 256",R,….
Setting the value of area<flag> to 10, means that all Geo-fences GF1, GF2, GF3, GF4 and GF5
belong to the single area GF.AREA4.
Figure 10:
Covering up a driving route using several Geo-fences within just an area
The GF.AREA4 boundaries are outlined in the diagram below. Its colour definition is given on the
left side of the diagram. While the device is moving in or out the GF.AREA4 and GF1 to GF5 the
corresponding in/out events are also occurred.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 261 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Once the MAMBO2-B6/UXFS unit enters into the first Geo-fence (GF1) it enters also into the
GF.AREA4, so two events and two states are automatically generated "GPS.Geofence.e1=inside",
"GPS.AREA.e4=inside" and "GPS.Geofence.s1=inside" and "GPS.AREA.s4=inside" respectively. You may
connect these events and states to alarm configuration parameter, so that when the MAMBO2B6/UXFS device enters into the first Geo-fence (GF1) and also into the GF.AREA4 your application
executes the action in the configuration (e.g. SMS notifications, TCP packets, history entries etc.).
In the same way you may be notified whenever the MAMBO2-B6/UXFS device enters/exists a
Geo-fence or only when it enters/exits an area.
Example 2:
This example represents how to cover up a driving route using several Geo-fences allocated in
different areas. The purpose of such configurations is to store the GPS position data in internal
memory when the area events rise - features for route verification).
As reference use the diagram attached to this example. Supposed you have configured four
areas (using GF.AREA parameter) with following settings (see also the figure attached below).
GF.AREA1="City East"
// corresponds to hex value 2 (0403021100 - 000102),
GF.AREA2="City West"
// corresponds to hex value 4 (0403120100 - 001002),
GF.AREA3="City Centre"
// corresponds to hex value 8 (0413020100 - 010002).
GF.AREA4="City" // corresponds to hex value 10 (1403020100 - 100002)
Based on the set configuration of the areas you can start the configuration process of Geofences. For example (some of coordinates are not given):
GF1=areaE,"B88",R,50.67340,10.98060,50.67350,10.98070
GF2=areaE,"Street 1",R,….
GF3=area1C,"Street 5",R,…
GF4=area1E," B1004",R,….
GF5=area12,"Street 256",R,….
areaE
means that the GF1 and GF2 belong to both areas GF.AREA2 and GF.AREA4. The
hexadecimal value 0xE represents the sum of the hexadecimal values GF.AREA2
(^=0x4) and GF.AREA4 (^=0x10).
area1C means that the GF3 belongs to the three areas GF.AREA2, GF.AREA3 and GF.AREA4.
The hexadecimal value 0x1C represents the sum of the hexadecimal values GF.AREA2
(^=0x4), GF.AREA3 (^=0x8) and GF.AREA4 (^=0x10).
area1E means that the GF4 belongs to the four areas GF.AREA1, GF.AREA2, GF.AREA3 and
GF.AREA4. The hexadecimal value 0x1E represents the sum of the hexadecimal values
GF.AREA1 (^=0x2), GF.AREA2 (^=0x4), GF.AREA3 (^=0x8) and GF.AREA4 (^=0x10).
area12 means that the GF5 belongs to the areas GF.AREA1 and GF.AREA4. The hexadecimal
value 0x12 represents the sum of the hexadecimal values GF.AREA1 (^=0x2) and
GF.AREA4 (^=0x10).
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 262 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Figure 11:
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Covering up a driving route using several Geo-fences allocated in different areas.
This is only a classification of areas and Geo-fences. The areas boundaries 1 to 4 are outlined in
different colours, and their colour is given on the left side of the diagram. While the device is
moving in or out an area or Geo-fence the corresponding event of that area and Geo-fence always
are occurred.
However, depending on your application to be implemented only some of area/Geo-fence events
can be set as condition to execute actions.
Notes
• The GF0 should not be used as a standard Geo-fence zone, if the parking are is
set/activated (see chapter 3.2.5.3.1, for more details). Based on the user specified
<park_radius> value, the GF0 is automatically set up and attached to the GF.AREA0
parameter, if the GPS.Geofence.Park.Set command is executed.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 263 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.3.16
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
AL<index> parameter (Alarm configuration)
 FEATURES OF THE ALARM CONFIGURATION
✔ Clearly arranged functional structured alarm conditions.
✔ Events can be combined to define very complex conditions.
✔ Several actions can be specified and will be executed when all conditions are true.
✔ Alias names, which are defined for PFAL commands like IN/Output names, Timer, Trigger or Counter names, can
be used for conditions as well. This improves clearly arranged easy to understand system configurations.
✔ Can be extended very flexible and easily.
 LIMITATIONS
✔ Currently it is not possible to transmit various system states by using alarms (i.e. sending TCP state periodically
via SMS).
✔ It is not possible to evaluate the execution of alarm actions (whether they are successfully executed or resulting
errors). No conditions can be defined to react on failed alarm actions before. (The only way is using i.e. state
conditions, which should be changed if the action was successfully executed).
✔ PFAL responses cannot be transmitted or displayed for executed alarm commands.
✔ None of read commands cannot be efficiently used as alarm actions.
 The purpose of read commands (i.e. all commands which retrieve a state or other information) is to provide
information on demand.
 This information is returned only within the PFAL response, which is not available for alarm commands
 To sent information automatically use "MSG.Send" commands, see chapter 3.2.8.1, page
149.
AL<index>= <conditions>:<actions> -Set Alarm Configuration
3.3.16.1
Parameter syntax
AL<index>=<conditions>:<actions>
This parameter is used to configure alarms that response of event occurrences. User-specified
configuration is stored into the FLASH memory, and it will be available after each power up of the
MAMBO2-B6/UXFS unit.
The user specified alarms allow the MAMBO2-B6/UXFS unit to react and to perform different
actions under certain conditions. To allow a very flexible but still structured configuration, each
alarm is divided into the conditions and actions. Actions will be executed when defined conditions
are evaluated to True.
For example:
 A MAMBO2-B6/UXFS will transmit a TCP packet to the remote server including the current GPS
position of the device ($PFAL,TCP.Client.Send,48,"BTN0 pressed"), when
E

the user presses the right on the MAMBO2-B6/UXFS (the event IO.BTN.e0=long raises).
Alarm declaration: $PFAL,Cnf.Set,AL0=IO.BTN.e0=long:TCP.Client.Send,48,"BTN0 pressed: "
A

Or send a SMS to the predefined phone number (GSM.SMS.Send,"+491234",0,"location
unknown"), when
E
MAMBO2-B6/UXFS unit fails to acquire its GPS location (Once the MAMBO2-B6/UXFS unit fails to
acquire its GPS position the event "GPS.Nav.eFix=invalid" occurs)
Alarm declaration: $PFAL,Cnf.Set,AL1=GPS.Nav.eFix=invalid:GSM.SMS.Send,"+49123445",0,"location unknown"
A
- executed command (action), when E - event raises.
An event is one that only notifies the system that the particular event happened. An action is a
command that will be executed when a particular event occurs. An alarm (AL) may contain up to 5
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 264 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
actions/commands and up to 5 conditions. All conditions have an AND- or OR-Conjunction. The
block of commands specified within the <actions> field that follow the <conditions> field will be
executed once the block of conditions specified within the <conditions> field are evaluated true.
The common syntax of the AL-parameter is shown above. The configuration settings for an alarm
(AL) can be transferred to and stored in the MAMBO2-B6/UXFS device using the
"$PFAL,Cnf.Set,AL<index>" command. You can combine several configuration settings into a
single command line, but it is not recommended. However, the maximum number of characters
specified in a single command line is limited to 1500. More than 1500 characters per command
line will be ignored.
The command syntax for combining several alarm configuration settings in a single command line
is:
$PFAL,Cnf.Set,AL<index>=<conditions>:<actions>;Cnf.Set,AL<index>=<conditions>:<actions>;…

Setting up a large number of complex alarms is not recommended, as it may affect the
performance of the device. Therefore, we strongly advice to verify correct behaviour of
the system under real term conditions.
Set Parameter Description
<index>
Specify the alarm index to be configured. The index <index> is a number, which can be set to a
value from 0 to 99, without leading "0", e.g. AL0, AL1, AL8, AL10. The index specified, for
example, AL05 is invalid and in such a format it will be ignored by the system. The number of
indices depends on the used firmware version. In the greater firmware versions the index
range may be increased.

Please note, that alarms with lower index will be executed first, if different alarms are
triggered at the same time upon a certain event.
<conditions>
Determine the list of condition(s) to be monitored. More specifically, determine when the
MAMBO2-B6/UXFS should generate an action (alarm). When you are specifying conditions for
alarms (AL), to apply the filter to the condition field, use the logical operators such as either
"&" or "?". The logical operators enable an alarm to be more precisely executed when the set
conditions are met. Up to 5 conditions separated either by ampersand "&" or question mark
"?" without spaces can be specified.
 The ampersand character "&" represents the "AND" conjunction which it is used to test
whether all set events and states within the condition field are evaluated to True,
 While the question mark character "?" represents the "OR" conjunction, which it may be
used to test whether at least one of the set events and states within the condition field is
evaluated to True.
Hint: The conjunctions "&" and "?" could not be mixed/nested within the condition field.
Within the condition field the user is able to use either "&" or "?"
The syntax to define several conditions is:
What do conditions mean?
Conditions are system events and states, which rise or set to True either when a
command/action is manually or automatically executed during the system runtime. Conditions
are requirements for one or more actions that have to be released at a specific time or wehen
something happens. As above, you can define up to 5 conditions. In that case all userspecified actions are released, only if the event and states within the condition field are
evaluated to True.
Additionally, the condition field <conditions> consists of one event and/or up to 4 states.
What are the differences between Events and States?
Events:
are a link between occurrences in the system e.g. the device indicates an incoming
voice call or an input changes or a lost GPS signal. More specifically, an event is a
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 265 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
pointer that points to a process in a specific case. The conditions containing an event
are evaluated just when the event occurs (making it possible to release actions only
one time) - so it makes no sense to combine two event in one condition. In chapter
3.4, page 271 the events are grouped by major category. The Events are represented
by adding an "e" character directly after the last dot-delimiter [.], for example
Sys.Device.eStart or Sys.Timer.e1 etc..
States:
are conditions of the unit, which will be checked all the time (every 1 second). Once
they are True, the specified actions will permanently be released, so use it with
caution or in combination with an event by using the ampersand character "&"
representing the "AND" conjunction and NOT the question mark character "?"
representing the "OR" conjunction. In chapter 3.4, page 271 the States are grouped
by major category. The States are represented by adding an "s" character directly
after the last dot-delimiter [.], for example Sys.Timer.s1=erased or
Sys.Trigger.s0=high etc..
If the <conditions> field includes only STATES and they are set to True, the MAMBO2-B6/UXFS
will permanently execute the specified action, from the <actions> field, until the specified
STATES returns False. The combination of states with an event prevents permanently
executing of actions. To configure the <conditions> field use the events and states, available
in chapter 3.4, "Supported System Events and States" page 271.
The following table shows the events and states grouped by major category. Some events and
states might have special communication interface requirements and others might have special
design considerations. The links in the table take you to chapter that provides overview
description of these events and states and including specific information for you to consider
when adding these events and states to your application.
Major category
Chapter
Description
Sys.Geofence
3.4.1.1
Provides Geo-fence events and states and shows the event signatures.
Sys.Tracking
3.4.1.2
Provides tracking events and states and shows the event signatures.
Sys.Sliding
3.4.1.3
Provides sliding events and states and shows the event signatures.
Sys.Motion
3.4.1.4
Provides motion events and shows the event signatures.
Sys.eSerialData
3.4.1.5
Provides the event on the serial line and shows the event signatures.
Sys.UserEvent
3.4.1.6
Provides user events and states and shows their signatures.
Sys.Devic
3.4.1.7
Provides device events and shows their signatures.
Sys.Timer
3.4.1.8
Provides events and states of Timer and shows their signatures.
Sys.Trigger
3.4.1.9
Provides states of the Trigger and shows their signatures.
Sys.Counter
3.4.1.10
Provides events and states of Counter and shows their signatures.
Sys.Power
3.4.1.11
Provides events and states of external power and shows their signatures.
Sys.Bat
3.4.1.12
Provides events and states of Battery and shows their signatures.
Sys.BT
3.4.1.13
Provides events and states of Bluetooth and shows their signatures.
Sys.GPS
3.4.1.14
Provides GPS events and states and shows their signatures.
Sys.GSM
3.4.1.15
Provides GSM events and statesand shows their signatures.
Sys.SD
3.4.1.16
Provides SD-card events and states and shows their signatures.
System
Bluetooth (BT option is only available for the MAMBO2-UXFS)
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 266 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Major category
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Chapter
Description
3.4.2.1
Provides Bluetooth audio events and states and shows their signatures.
IO.Motion
3.4.3.1
Provides motion events and states and shows their signatures.
IO.BTN
3.4.3.2
Provides buttons events and states and shows their signatures.
DISPLAY.DIALOG
3.4.4.2
Provides dialog events and states and shows their signatures.
DISPLAY.Menu
3.4.4.1
Provides menu events and states and shows their signatures.
DISPLAY.Trip
3.4.4.3
Provides trip events and states and shows their signatures.
DISPLAY.Tripmode
3.4.4.4
Provides Trip mode events and states and shows their signatures.
DISPLAY.Popup
3.4.4.5
Provides popup events and states and shows their signatures.
DISPLAY.Pois
3.4.4.6
Provides POI events and states and shows their signatures.
DISPLAY.Phone
3.4.4.7
Provides phone events and states and shows their signatures.
DISPLAY.Tilt
3.4.4.8
Provides Tilt events and states and shows their signatures.
DISPLAY.Follow
3.4.4.9
Provides follow events and states and shows their signatures.
GPS.Nav
3.4.5.1
Provides GPS navigation events and states and shows their signatures.
GPS.Time
3.4.5.2
Provides GPS Time states and shows their signatures.
GPS.History
3.4.5.3
Provides History states and shows their signatures.
GPS.Geofence
3.4.5.4
Provides Geo-fence events and states and shows their signatures.
GPS.Area
3.4.5.5
Provides Area events and states and shows their signatures.
GSM
3.4.6.1
Provides GSM operator events and states and shows their signatures.
GSM.eCell
3.4.6.2
Provides GSM cell events and states and shows their signatures.
GSM.VoiceCall
3.4.6.3
Provides Voice Call events and states and shows their signatures.
GSM.SMS
3.4.6.4
Provides SMS events and shows their signatures.
GSM.DataCall
3.4.6.5
Provides Data Call events and states and shows their signatures.
GSM.GPRS
3.4.6.6
Provides GPRS events and states and shows their signatures.
TCP.Client
3.4.7.1
Provides TCP events and states and shows their signatures.
TCP.SMTP
3.4.7.2
Provides TCP events and states and shows their signatures.
BT.Audio
IO
Display
GPS
GSM
TCP
IEEE (IEEE option is only available for the MAMBO2-UXFS)
INDOOR
3.4.8.1
Provides Indoor events and states and shows their signatures.
IEEE.IOBOX<id>.St
ate
3.4.8.2
Provides IOBOX events and states and shows their signatures.
IEEE.IOBOX<id>.IN
3.4.8.3
Provides IOBOX input events and states and shows their signatures.
IEEE.IOBOX<id>.A
NA
3.4.8.4
Provides IOBOX analogue input events and states and shows their signatures.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 267 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Major category
Chapter
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Description
ANT (ANT options is no longer available)
ANT.Heartbeat
3.4.9.1
Provides ANT heartbeat events and states and shows their signatures.
ANT.Speed
3.4.9.2
Provides ANT speed events and states and shows their signatures.
ANT.Cadence
3.4.9.3
Provides ANT cadence events and states and shows their signatures.
Table 10:
The events and states grouped by major category.
Either use the links (in blue text) in table above or the PDF document bookmarks to
navigate the events and states you need.
<actions>
Specify the commands/action(s) to be executed, when the set conditions (states and event)
are True. Up to 5 commands/actions separated by ampersand "&" can be specified with some
restrictions. The order of the commands/actions in the action field is significant. For details,
read important nots listed at the end of this chapter.
The commands/alarms within the action field will NOT be executed in the same order as they
are specified. Timers and Triggers have more priority. Therefore, it is recommended to
combine these actions in such a way that no false alarms are being executed.
Except the read commands that are used to read the specific system states, all other
commands within the chapter 3.2, "PFAL Commands" can be used as alarm without leading
the "$PFAL,".
The syntax to define several actions (commands) is:
Important Notes
● It's not recommended to use read commands inside alarms because this would only
slow down system performance (such information can’t be displayed in this way –
use $PFAL,Msg.Send commands for such purposes).
●
Configuration commands starting with $PFAL,Cnf.Set:
➢
It should be used with caution and never executed in a periodical matter. Each
use of such a command drains the lifetime of the internal flash memory. There
are several 100000 write/erase cycles, but these could be reached with alarms
executed periodically.
➢
Only one configuration command (Cnf.Set command) may be entered in an
alarm and it should always be set as the last entry on it, since everything that
comes after it will be considered by the device as a part of the configuration
settings to that parameter.
➢
Do not combine configuration commands (listed in chapter 3.3) with display
commands (listed in chapter 3.2.2.13) in alarms. If you specify a display
command within an alarm it should be the last entry on it (see AL3 in the table
below).
How the configuration could be set/ or the settings requested:
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 268 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Set configuration
Get configuration
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
$PFAL,Cnf.Set,AL0=Sys.Device.eStart:IO.LED1=hpulse,3000
$PFAL,Cnf.Set,AL1=Sys.Bat.eLow:GSM.SMS.Send,"+491234567",8,"Battery Low"
$PFAL,Cnf.Set,AL2=GPS.Nav.eFix=valid:IO.LED1=hpulse,5000
$PFAL,Cnf.Set,AL3=Sys.Bat.eLow:IO.LED1=cyclic,1000,2000&Display.Alarm=WARNING,5,"Batter
y low"
//not
$PFAL,Cnf.Set,AL3=Sys.Bat.eLow:Display.Alarm=WARNING,5,"Battery
low"&IO.LED1=cyclic,1000,1000
$PFAL,Cnf.Set,AL99….
$PFAL,Cnf.Get,AL0
$PFAL,Cnf.Get,AL1
$PFAL,Cnf.Get,AL2
$PFAL,Cnf.Get,AL99
Notes
• Please, consider the permanent action execution by specifying only state conditions.
• When an action will be released, the corresponding event or state (if it is specified) is also
called by the internal firmware.
• If the MAMBO2-B6/UXFS device is configured to release an action via SMS, please,
consider that the maximum length of SMS text <text> is predefined up to 160 characters
using the 7-bit GSM coding scheme.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 269 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Supported System Events and States
Creating applications with MAMBO2-B6/UXFS is very easy. What you should know is how to handle the
events and states supported by the running firmware in the MAMBO2-B6/UXFS device. Here below you
find explained what are events and states and when they are generated. Events are generated at runtime (for example, when the GPS fix switches for invalid-to-valid or vice-versa) or by user actions (for
example, when the user press a button or executes a PFAL command). In such a case, the MAMBO2B6/UXFS device is notified of this action and your application may respond to the generated events by
executing one or more alarms.
All condition types <c_type> and their definition using the Firmware version 2.6.xx are listed below.
Each of them is used to separate the huge amount of conditions to different types. Depending on the
alarm configuration to be set inside the <conditions> field, the following states and events can be used:
1. Sys (System) accomplishes a number of system states and events such as:
✔ System management tasks, including: Reset, Shutdown/power management, etc.
✔ Initialization/interruption of system processes, including: Timers, Counters, etc.
2. DISPLAY accomplishes a number of Display events, including menus, dialog boxes, Trips and POIs.
3. GPS accomplishes a number of GPS events including navigation, history logging and Geofencing
data.
4. GSM accomplishes a number of GSM events, including SMS, voice and data calls, GPRS
attachment/detachment, etc..
5. TCP accomplishes a number of TCP events including connecting disconnection and sending of TCP
packets to the predefined address of remote server, etc.
6. IEEE and Indoor accomplishes a number of events that occur during the IEEE connections and
operation with such devices such as connecting, disconnecting and when a button is pressed.
7. ANT accomplishes a number of events when operating with ANT devices such as when hartbeats
are below or above the specified training zones.
Creating an Alias:
As explained in chapter 3.1.1.2 above, you can create an alternative name for each PFAL command
using the alias. For example: ALIAS.SYS.TIMER2=_7SEC; where the alias for the Timer2 is "_7SEC". The
event of this timer will also have te same name and used as "SYS.TIMER.e_7SEC". Such alias names
will help you to have a clear overview inside your configuration.
Comparators:
In some conditions the comparators listed in table below are used to compare, i.e. the current speed
of the device with a user specified value or the current state of the device inputs, etc.
Comparators
Operation
Example
Comparators
Operation
Example
=
equality
Sys.Timer.s0=running
>
greater-than
GPS.Nav.sSpeed>10
!=
enequality
Sys.Counter.s0!=0
<=
less-than-or-equal-to
Sys.Counter.s0<=10
<
less-than
GSM.DataCalll.sRingCounter<2
>=
greater-than-or-equal-to
Sys.Counter.s0>=10
Table 11:
The comparators list.
For most simple types, comparison is straightforward. For example, Sys.Timer.s0=running is True just in
case the Sys.Timer.s0 is running and stays True until the Timer 0 changes its state. The following rule
applies to comparators.

No string values (supported by the firmware) can be compared by using the
comparators <, >, <=, >= , and !=. In such cases use only the comparator =.

Do not change the order of comparators (<= and >=).
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 270 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.1
3.4.1.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys (System states and events)
Sys.Geofence
STATES - are checked every second
State notification code
Meaning
Sys.Geofence.s=<state>
True when the corresponding command $PFAL,Sys.Geofence=<state> is executed.
Define what kind of state should be checked:
high
True when executing the command $PFAL,Sys.Geofence=high.
low
True when executing the command $PFAL,Sys.Geofence=low.
load
True when executing the command $PFAL,Sys.Geofence=load.
save
True when executing the command $PFAL,Sys.Geofence=save.
<state>
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
Sys.Geofence.e=<state>
This event occurs when the corresponding command $PFAL,Sys.Geofence=<state> is executed
Avoid the execution of loop alarms when using this event. Make sure, that alarms to be executed does not affect
other alarms except the premeditated one. A false alarm configuration may bring your device into a state that it
does not work anymore.
Define when and what kind of the event should occur.
high
when executing the command $PFAL,Sys.Geofence=high
low
when executing the command $PFAL,Sys.Geofence=low
load
when executing the command $PFAL,Sys.Geofence=load.
save
when executing the command $PFAL,Sys.Geofence=save.
<state>
Table 12:
3.4.1.2
Alarm states and events.
Sys.Tracking
STATES - are checked every second
State notification code
Meaning
Sys.Tracking.s=<state>
True when the corresponding command Sys.Tracking=<state> is executed.
Define what kind of state should be checked:
high
True when executing the command $PFAL,Sys.Trackin=high
low
True when executing the command $PFAL,Sys.Tracking=low
load
True when executing the command $PFAL,Sys.Tracking=load
save
True when executing the command $PFAL,Sys.Tracking=save
<state>
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
Sys.Tracking.e=<state>
This event occurs the corresponding command Sys.Tracking=<state> is executed. .
Avoid the execution of loop alarms when using this event. Make sure, that alarms to be executed does not affect
other alarms except the premeditated one. A false alarm configuration may bring your device into a state that it
does not work anymore.
<state>
Define when and what kind of the event should occur.
high
when executing the command $PFAL,Sys.Tracking=high
low
when executing the command $PFAL,Sys.Tracking=low
load
when executing the command $PFAL,Sys.Tracking=load
save
when executing the command $PFAL,Sys.Tracking=save
Table 13:
Tracking states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 271 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.1.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.Sliding
STATES - are checked every second
State notification code
Meaning
Sys.Sliding.s=<state>
True when the user selects the Sliding-item on the MAMBO2-B6/UXFS display.
Define what kind of state should be checked:
high
True when executing the command $PFAL,Sys.Sliding=high
low
True when executing the command $PFAL,Sys.Sliding=low
load
True when executing the command $PFAL,Sys.Sliding=load
save
True when executing the command $PFAL,Sys.Sliding=save
<state>
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
Sys.Sliding.e=<state>
Occurs when the user selects the Sliding-item on the MAMBO2-B6/UXFS display.
Avoid the execution of loop alarms when using this event. Make sure, that alarms to be executed does not affect
other alarms except the premeditated one. A false alarm configuration may bring your device into a state that it
does not work anymore.
Define when and what kind of the event should occur.
high
when executing the command $PFAL,Sys.Sliding=high
low
when executing the command $PFAL,Sys.Sliding=low
load
when executing the command $PFAL,Sys.Sliding=load
save
when executing the command $PFAL,Sys.Sliding=save
<state>
Table 14:
3.4.1.4
Sliding states and events.
Sys.Motion
STATES - are checked every second
State notification code
Meaning
Sys.Motion.s=<state>
True when the corresponding command $PFAL,Sys.Motion=<state> is executed.
Define what kind of state should be checked:
high
True when executing the command $PFAL,Sys.Motion=high
low
True when executing the command $PFAL,Sys.Motion=low
load
True when executing the command $PFAL,Sys.Motion=load
save
True when executing the command $PFAL,Sys.Motion=save
<state>
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
Sys.Motion.e=<state>
This event occurs when the corresponding command $PFAL,Sys.Motion=<state> is executed.
Avoid the execution of loop alarms when using this event. Make sure, that alarms to be executed does not affect
other alarms except the premeditated one. A false alarm configuration may bring your device into a state that it
does not work anymore.
<state>
Define when and what kind of the event should occur.
high
when executing the command $PFAL,Sys.Motion=high
low
when executing the command $PFAL,Sys.Motion=low
load
when executing the command $PFAL,Sys.Motion=load
save
when executing the command $PFAL,Sys.Motion=save
Table 15:
Motion states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 272 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.1.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.eSerialData
STATES
None
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
Sys.eSerialData<port>[=<"text">]
Occurs when the MAMBO2-B6/UXFS device detects receiving data in the Bluetooth or USB port. The port
where the event should be occurred must be set either into the event mode using the PFAL command
$PFAL,MSG.Mode.USB=6F,E or into the command mode $PFAL,MSG.Mode.USB=6F,C whereby the received
text on the specified port should not start with $PFAL.
To reset the port from event into the command mode, you have to send the following command via SMS or TCP to the
MAMBO2-B6/UXFS device:
$PFAL,MSG.Mode.USB=6F,C // if you send it via SMS, exclude the "$" sign from the command.
Example: Sys.eSerialData1 or Sys.eSerialData1="test"
Specify the port for the occurrence of the event.
0 = Bluetooth
1 = USB
Optional. If <"text"> not empty, the incoming text will be compared with specified <"text"> and when they
match exactly (case sensitive) then this event is occurred. If serial text contains more characters as you have
specified inside the <"text"> only the specified characters will be compared.
<port>
[<"text">]
Table 16:
3.4.1.6
SerialData states and events.
Sys.UserEvent
STATES
None
EVENTS – are evaluated just when the event occurs
Event notification code
Sys.UserEvent.e<index>
<index>
Meaning
Occurs when the corresponded PFAL command ($PFAL,Sys.UserEvent<index>) is executed. This event can be used
to combine/link directly several alarms (AL<index>) i.e. for optimizing larger configurations or simply if more than 5
conditions are needed. To raises such an event, use the corresponding PFAL command and enter the corresponding
index number.
The UserEvent is not recommended to be used, as it allows to create „endless loops" which can slow down the
system or even it may affect the stability of other functions.
The UserEvents may be use at own risk, however think about all consequences of (maybe recursively) launching
alarms when using it. Especially in combination with various states which can itself be influenced by actions, the
system behaviour can be very unpredictable and complex.
Therefore, no support will be given for configurations containing the UserEvents.
Example: Sys.UserEvent.e1
Define the index of user event to be executed. It can be set to a value from 0 to 9.
Table 17:
UserEvent states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 273 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.1.7
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.Device
STATES - are checked every second
State notification code
Meaning
This state shows the kind of reason when the device wakes up from a sleep mode. True when
the wake up type match the specified reason. If no type and no wake up reason is specified,
then this state is always True after booting up your device.
Example: Sys.Device.sStart
Sys.Device.sStart=doze,Standing
Sys.Device.sStart[=<type>,<wakeup_reason>]
$PFAL,Cnf.Set,AL1=Sys.Device.sStart=Wakeup,Ring&Sys.Timer.e1: MSG.Send.TCP,8,"Trace-
M2"
Timer 1 must be started when the event "TCP.Client.eConnected" is occurred.
Specify an optional startup type:
PowerUp
Device was booted from shutdown.
Reset
Device was booted from reset.
Wakeup
Device was booted from sleep mode.
Doze
Device was booted from doze mode.
[<type>]
If the <type>=Wakeup . Specify an optional wakeup reason for the <type>=Wakeup.
Ign
The device was woken up by pressing the ON/OFF button.
Ring
The device was woken up by the received SMS or voice call.
Timer
The device was woken up by the expired timer.
Motion
The device was woken up by the detected motion.
If the <type>=Doze . Specify an optional wakeup reason for the <type>=Doze.
Ign
The device was woken up by pressing the ON/OFF button.
Ring
The device was woken up by the received SMS or voice call.
Timer
The device was woken up by the expired timer.
Motion
The device was woken up by the detected motion.
Standing
The device was woken up by no detected motion within 30 seconds.
[<wakeup_reason>]
If the <type>=Reset. Specify an optional wakeup reason for the <type>=Reset.
Watchdog
The device was restarted by the watchdog
GSM_CommERROR When a GSM communication problem was met.
RemoteUpdate
When the firmware update is executed.
Serial2GSM
The device has left the Serial GSm Modus.
User<X>
Device reset has been sent by User via an Alarm. An index X = 0..2 can
be submitted in order to distinguish between different reset reasons.
DelayedUser
Delayed reset has been sent by User (i.e. special PFAL commands or
Alarm Actions like $PFAL,Sys.CfgUpdateMode)
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
Occurs when the device restarts or wakes up from sleep. If no type and no wake up reason is
specified, then this event is always occurred after booting up your device.
Note: This event can be used to launch actions after the device awakes by a specific wakeup
reason. Without start <type> and start <wakeup_reason> it can be used to initialize
certain timers, counters etc.. during system startup (independent from wakeup reason).
Example:
Sys.Device.eStart
Sys.Device.eStart[=<type>[,<wakeup_reason>]]
Sys.Device.eStart=Reset
Sys.Device.eStart=doze,Standing
Sys.Device.eStart=doze,Motion
$PFAL,Cnf.Set,AL1=Sys.Device.eStart=doze:GSM.SMS.send,"+49123",8,"SOS"
[<type>]
Specify an optional startup type:
PowerUp
Device was booted from shutdown
Reset
Device was booted from reset.
Wakeup
Device was booted from sleep mode.
Doze
Device was booted from doze mode.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 274 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
If the <type>=Wakeup . Specify an optional wakeup reason for the <type>=Wakeup.
Ign
The device was woken up by pressing the ON/OFF button.
Ring
The device was woken up by the received SMS or voice call.
Timer
The device was woken up by the expired timer.
Motion
The device was woken up by the detected motion.
If the <type>=Doze . Specify an optional wakeup reason for the <type>=Doze.
Ign
The device was woken up by pressing the ON/OFF button.
Ring
The device was woken up by the received SMS or voice call.
Timer
The device was woken up by the expired timer.
Motion
The device was woken up by the detected motion.
Standing
The device was woken up because no motion detected within 30 seconds
after going into the doze mode with parameter PTI.
If the <type>=Reset. Specify an optional wakeup reason for the <type>=Reset.
Watchdog
The device was restarted by the watchdog.
GSM_CommERROR
When a GSM communication problem was met.
RemoteUpdate
When the firmware update is executed.
Serial2GSM
The device has left the Serial GSm Modus.
User<X>
Device reset has been sent by User via an Alarm. An index X =
0..2 can be submitted in order to distinguish between different
reset reasons.
DelayedUser
Delayed reset has been sent by User (i.e. special PFAL
commands or Alarm Actions like $PFAL,Sys.CfgUpdateMode).
[<wakeup_reason>]
This event is occurred right before the system enters the sleep mode.
If the command $PFAL,Sys.Device.Shutdown is executed the system shuts down immediately
without occurring this event.
Sys.Device.eShutdown
$PFAL,Cnf.Set,AL1=Sys.Device.eShutdown:GPS.Nav.SaveLastValid
Table 18:
Device’s states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 275 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.1.8
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.Timer
STATES - are checked every second
State notification code
Meaning
Sys.Timer.s<index>=<status>
Checks the current operating mode of the executed timer index. True when the timer <index> is at the
specified timer status until it changes to another status.
Example: Sys.Timer.s1=erased
Sys.Timer.s1=initialized
<index>
Specify the timer index. It can be set to a value from 0 to 19.
<status>
Set the state of the timer to be compared. The various states are not exclusive (e.g. a running timer is always
active and initialized). It can be set to.
Status
Description
erased
Determines whether the specified timer is currently erased.
initialized
Determines whether the specified timer is currently initialized.
active
Determines whether the specified timer is currently started.
inactive
Determines whether the specified timer is currently stopped.
running
Determines whether the specified timer is currently running.
paused
Determines whether the specified timer is currently paused.
armed
Determines whether the specified timer is currently armed.
disarmed
Determines whether the specified timer is currently disarmed.
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
Occurs when the started Timer<index> is expired. Hint: Only the armed timers raise events.
Sys.Timer.e<index>
Example: Sys.Timer.e1
$PFAL,CNF.Set,AL1=SYS.TIMER.e1&GPS.Nav.Position.s1>50&GPS.Nav.sSpeed>0&GPS.Nav.sFix=
valid:GPS.Nav.Position1=current&GPS.History.Write,0,""
<index>
Specify a timer index or its preconfigured alias. It must be in the range 0 through 19.
Table 19:
Timer’s states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 276 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.1.9
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.Trigger
STATES - are checked every second
State notification code
Sys.Trigger.s<index>=high
Sys.Trigger.s<index>=low
<index>
Meaning
True when the Trigger <index> is High until it changes to Low. The state of a Trigger can be set to high using the
corresponding PFAL command $PFAL,Sys.Trigger<index>=high.
Example: Sys.Trigger.s0=high
$PFAL,CNF.Set,AL1=GPS.Nav.sSpeed>=2&Sys.Trigger.s0=high:Sys.Trigger0=low&SYS.Timer0.stop&TCP.Client.Send,8,
"Position: "&SYS.Timer1.start
True when the Trigger <index> is Low until it changes to High. Trigger states can be set to low using the corresponding
PFAL command $PFAL,Sys.Trigger<index>=low.
Example: Sys.Trigger.s0=low
$PFAL,CNF.Set,AL1=GPS.Nav.sSpeed<2&Sys.Trigger.s0=low:Sys.Trigger0=high&SYS.Timer0.start=cyclic,10000&Sys.C
ounter0.Set=0
Specify the trigger index. It must be in the range 0 through 19.
EVENTS
None
Table 20:
3.4.1.10
Trigger’s states and events.
Sys.Counter
STATES - are checked every second
State notification code
Meaning
Sys.Counter.s<index><comp><value>
True when the value of the Counter<index> matches the specified value. Counters do not automatically
increment or decrement themselves. To reach a certain value for a counter, the corresponding
command (see chapter 3.2.2.18.1) should be executed x-times until the counter reaches the supposed
value. When the system starts all counters are initialized to 0.
Example: Sys.Counter.s0>30
$PFAL,Sys.Counter0.set=25;Sys.Counter0.save1
$PFAL,CNF.Set,AL1=Sys.Device.eStart:Sys.Counter0.load1
$PFAL,CNF.Set,AL2=GSM.SMS.eSent:Sys.Counter1.Decrement=1
$PFAL,CNF.Set,AL3=GSM.SMS.eIncoming.Number="+491234567"&GSM.SMS.eIncoming.Text="#req.p
os"&Sys.Counter.s0>0:GSM.SMS.Send,"+491234567",8,"Requested position: "
<index>
Specify the counter identifier. It can be set to a value from 0 to 19
<comp>
Compares two values and return a Boolean (True/False) value that represents the result of the
comparison. It can be set to =, !=, <, >, <= or >=.
<value>
Specify the value to be compared. 32-bit integer value from 0 to 4294967295.
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
Occurs when a configured system Counter reaches its minimum value zero (0) . To reach a certain value
for a counter, the corresponding command (see chapter 3.2.2.18.1) should be executed x-times until
the counter reaches the supposed value.
For example:
Decrements a counter (counts toward the minimum 0) when a SMS is sent. When the specified counter
reaches the value 0, then send a TCP packet to the connected remote server.
$PFAL,Sys.Counter0.set=5;Sys.Counter0.save1
$PFAL,Cnf.Set,AL0=Sys.Device.eStart:Sys.Counter0.Load1
$PFAL,Cnf.Set,AL1=GSM.SMS.eSent:Sys.Counter0.Decrement=1
Sys.Counter.e<index>
$PFAL,Cnf.Set,AL2=Sys.Counter.e0:TCP.Client.Send,8,"positions:"
This configuration means after the device has delivered five SMS, it transmits a TCP packet to the
remote server.
<index>
Specify the counter index. It can be set to a value from 0 to 19.
Table 21:
Counter’s events and states.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 277 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.1.11
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.Power
STATES-are checked every second
State notification code
Meaning
Sys.Power.sVoltage<comp><value>
Checks the current voltage of a connected external power supply.
Sys.Power.sMode=<mode>
This state shows the mode of the device operation. If there is no power saving mode activated this state
shows disabled, otherwise auto or doze.
<comp>
Compares two values and return a Boolean (True/False) value that represents the result of the
comparison. It can be set to =, !=, <, >, <= or >=.
<value>
It is a signed decimal value (in volts). Its range is nothing to care about - basically any voltage can be
specified (ranges from - 2 exp 31 -1 to +2 exp 31 -1). Also a fractional value can also be specified ranging
from 0 to .999.
<mode>
Define the type of mode in which the device is currently running. It can be set to:
disable Device is running in full power mode (no power saving mode activated)
auto
Device is running in auto power saving mode
doze
Device is running in doze power saving mode
EVENTS-are evaluated just when the event occurs
Event notification code
Description
Sys.Power.eDetected
This event occurs when you connect your device to an external power source (external voltage is higher
than battery voltage).
Sys.Power.eDropped
This event occurs when you disconnect your device from an external power source (external voltage
drops below battery voltage).
Table 22:
3.4.1.12
System power states and events.
Sys.Bat
STATES - are checked every second
State notification code
Sys.Bat.sVoltage<comp><value>
Meaning
Checks the currently available battery voltage.
Example: Sys.Bat.sVoltage<3800
//means 3800 mV= 3.8 V
Sys.Bat.sCharge[=<state>]
Checks the current state of the internal battery.
Sys.Bat.sMode
The condition is true when a battery is being charged.
<comp>
Compares two values and return a Boolean (True/False) value that represents the result of the comparison. It
can be set to =, !=, <, >, <= or >=.
<value>
It is a signed decimal value (in millivolts). It ranges from 0 to 5000.
Specify the battery charging state that you need for this state. It can be set to:
start
Battery is currently charging.
stop,[<stop_reason>]
Charging was stopped, a <stop_reason> can also be specified..
An optional parameter can be specified to the Stop state to check the reason of stop:
<stop_reason>
Optional setting for stop charging
full
Battery is fully charged
disabled
Battery charger is disabled (e.g. by PFAL command or an alarm action)
no_power
External power dropped, so charging wasn't possible anymore.
[<state>]
EVENTS – are evaluated just when the event occurs
Event notification code
Sys.Bat.eLow
Meaning
This event occurs if battery voltage drops below a defined minimum. If the battery voltage drops below the
minimum and reaches a critical level an emergency sleep is automatically entered (wakeup reason: external
power). The event eShutdown is created in this case. Usually there is enough energy to send a few SMS and/or
some TCP packets if this emergency sleep occurs.
Note: It can be used to send e.g. a notification to call center or inform the user of a low battery in order to
prevent an emergency sleep. The device will exit its emergency sleep mode if external power is
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 278 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
detected.
Sys.Bat.eCharge[=<state>]
This event occurs when a battery changes its charge state.
Note that the battery charger will attempt to keep a battery fully charged. This means the charge state might
change sometimes from full to start and vice versa if the battery is almost fully charged.
Specify the battery charging state that you need for this state. It can be set to:
start
Charging started
stop,[<stop_reason>]
Charging stopped, a <stop_reason> can be specified (see reasons listed below).
An optional parameter can be specified to the Stop state to check the reason of stop:
<stop_reason>
Optional setting for stop charging
full
Battery is full charged
disabled
Battery charger is disabled (e.g. by PFAL command or an alarm action)
no_power
External power dropped, so charging isn't possible anymore.
error
During charging an error occurs.
[<state>]
Table 23:
3.4.1.13
Battery states and events.
Sys.BT
STATES-are checked every second (BT option is only available for the MAMBO2-UXFS)
State notification code
Meaning
Sys.BT.sConnected
True when the device is connected to a Bluetooth device, until disconnected again. The Bluetooth operation
state constantly changes as an application processes data. Opening a Bluetooth connection changes State from
Sys.BT.sDisconnected to Sys.BT.sConnected.
Sys.BT.sDisconnected
True when the device is completely disconnected from a previously connected Bluetooth device, until
reconnected.
Sys.BT.sEnable
True when the Bluetooth hardware is enabled via corresponding command, until disabled.
Sys.BT.sDisable
True when the Bluetooth hardware is disabled via corresponding command, until enabled.
EVENTS-are evaluated just when the event occurs (BT option is only available for the MAMBO2-UXFS)
Event notification code
Sys.BT.eConnected
Sys.BT.eDisconnected
Meaning
Occurs when the device is connected to the remote Bluetooth device.
$PFAL,Cnf.Set,AL1=Sys.BT.eConnected:IO.LED2=high
Occurs when the device is disconnected from the remote Bluetooth device.
$PFAL,Cnf.Set,AL1=Sys.BT.eDisconnected:IO.LED2=low
Sys.BT.eEnable
Occurs when the Bluetooth module of the device is enabled via corresponding command ($PFAL,Sys.BT.Enable).
Sys.BT.eDisable
Occurs when the Bluetooth module of the device is disabled via corresponding command ($PFAL,Sys.BT.Disable).
Table 24:
Bluetooth states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 279 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.1.14
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.GPS
STATES-are checked every second
State notification code
Sys.GPS.sEnable
Sys.GPS.sDisable
Meaning
True when the GPS part of the MAMBO2-B6/UXFS device is powered up and communicates with the operating
firmware, until the GPS results disabled.
True when the GPS part of the MAMBO2-B6/UXFS device is turned off and does not communicate with the
operating firmware, until the GPS results enabled.
EVENTS-are evaluated just when the event occurs
Event notification code
Meaning
Sys.GPS.eEnable
Occurs when the GPS module of the device is enabled via corresponding command ($PFAL,Sys.GPS.Enable).
Sys.GPS.eDisable
Occurs when the GPS module of the device is disabled via corresponding command ($PFAL,Sys.GPS.Disable).
Table 25:
3.4.1.15
GPS states and events.
Sys.GSM
STATES-are checked every second
State notification code
Meaning
Sys.GSM.sEnable
True when the GSM engine of the MAMBO2-B6/UXFS device is enabled via corresponding command
($PFAL,Sys.GSM.Enable), until disabled.
Sys.GSM.sDisable
True when the GSM engine of the MAMBO2-B6/UXFS device is disabled via corresponding command
($PFAL,Sys.GSM.Disable), until enabled.
EVENTS-are evaluated just when the event occurs
Event notification code
Meaning
Sys.GSM.eEnable
Occurs when the GSM engine of the device is enabled via corresponding command.
Sys.GSM.eDisable
Occurs when the GSM engine of the device is disabled via corresponding command.
Table 26:
GSM states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 280 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.1.16
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Sys.SD
STATES-are checked every second (SD option is no longer available)
State notification code
Meaning
Sys.SD.sInserted
True when there is an Mini- SD card inserted in the card reader.
Sys.SD.sRemoved
True when there is no Mini-SD card inserted in the card reader.
EVENTS-are evaluated just when the event occurs
Event notification code
Meaning
Sys.SD.eInserted
Occurs when an Mini- SD card is inserted into the card reader.
Sys.SD.eRemoved
Occurs when an Mini- SD card is removed from the card reader.
Table 27:
3.4.1.17
GSM states and events.
Sys.IEEE
STATES-are checked every second (IEEE option is only available for the MAMBO2-UXFS)
State notification code
Meaning
Sys.IEEE.sEnable
True when IEEE module is enabled via corresponding command ($PFAL,Sys.IEEE.Enable), until disabled.
Sys.IEEE.sDisable
True when IEEE module is disabled via corresponding command ($PFAL,Sys.IEEE.Disable), until enabled.
EVENTS-are evaluated just when the event occurs (IEEE option is only available for the MAMBO2-UXFS)
Event notification code
Meaning
Sys.IEEE.eEnable
Occurs when IEEE module is enabled via corresponding command ($PFAL,Sys.IEEE.Enable).
Sys.IEEE.eDisable
Occurs when IEEE module is disabled via corresponding command($PFAL,Sys.IEEE.Disable).
Table 28:
3.4.1.18
IEEE states and events.
Sys.Alarmloop
STATES-are checked every second
State notification code
Sys.Alarmloop.sActive
Meaning
True while the alarm loop is running.
EVENTS-are evaluated just when the event occurs
Event notification code
Sys.Alarmloop.eStop
Meaning
Occurs when the alarm loop is stopped.
Table 29:
IEEE states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 281 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
BT (Bluetooth states and events)
3.4.2.1
BT.Audio
STATES-are checked every second (BT option is no longer available)
State notification code
Meaning
BT.Audio.sBound
True when a Bluetooth audio headset is paired with MAMBO2-UXFS device until connected. Once disconnected
this state changes also to true. Opening a Bluetooth audio connection changes State from BT.Audio.sBound to
BT.Audio.sConnected. After the devices are paired (executing the command BT.Audio.Bound) they enter into a
connected state (sConnected).
BT.Audio.sConnected
True when a Bluetooth audio headset is connected to the device until disconnected. This state can be used when
you want to know whether a audio headset is connected to the MAMBO2-UXFS device.
EVENTS-are evaluated just when the event occurs (BT option is no longer available)
Event notification code
Meaning
BT.Audio.eBound
Occurs when a Bluetooth audio headset/hands-free set is paired with MAMBO2-UXFS device and when you
disconnects the audio set from MAMBO2-UXFS
BT.Audio.eConnected
Occurs when a Bluetooth audio headset is connected to MAMBO2-UXFS device. When executing the command
BT.Audio.Bound during pairing, the connection goes from eBound to eConnected. After the devices are paired
(executing the command BT.Audio.Bound) they enter into a connected state. The events (eBound and
eConnected) occur consecutively.
Table 30:
Bluetooth audio states and events
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 282 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
IO (IO states and events)
3.4.3.1
IO.Motion
STATES - are checked every second
Event notification code
Meaning
IO.Motion.sMoving
True when the device is moving with changeable velocity. During the device beeps no motion can be detected e.i if
this state was true before the beep tone is generated then it stays true during the beep until it ends.
IO.Motion.sStanding
True when the device is moving at a constant velocity or not moving.
EVENTS – are evaluated just when the event occurs
Event notification code
IO.Motion.eMoving
IO.Motion.eStanding
IO.Bearing.e<index>
Meaning
Occurs when the device starts moving (changes velocity).
$PFAL,CNF.Set,AL1=IO.Motion.eMoving:Sys.Trigger1=high&Sys.Timer1.Start=cyclic,10000
Occurs when the device stops moving or has a constant velocity.
$PFAL,CNF.Set,AL1=IO.Motion.eStanding:Sys.Trigger1=low&Sys.Timer1.Stop
Occurs when the BEARING[0..4] values are exceeded or within the BEARING5. This event will be occurred
periodically. The frequency of occurrence of the event depends on the configuration of MOTION.BEARING
parameter.
$PFAL,CNF.Set,AL1=IO.Bearing.e1&Sys.Trigger.s1=low&Sys.Counter.s1>10:Display.Popup=1,red,Cancel,WARNIN
G,20,"Bearing Alarm occurred"
The index must be in the range 0 through 6 as follow:
0 .. 4
For bearing configuration "MOTION.BEARING" with index 0 through 4.
5
For bearing configuration "MOTION.BEARING" with index 5.
6
This event is generated only when you want to use the Tilt function with "MOTION.TILT".
<index>
IO.Motion.eForce
IO.Motion.eFalling
Occurs when the assigned value of the <force> entry in the MOTION.FILTER is reached or exceeded
$PFAL,CNF.Set,AL1=IO.Motion.eForce:Display.Popup=1,red,Cancel,WARNING,20,"Force Alarm occurred?"
Occurs when the device drops from a distance above the earth and the current values of the motion sensor are
within the range assigned to the MOTIOM.FALLING parameter.
$PFAL,CNF.Set,AL1=IO.Motion.eFalling:Display.Popup=1,red,Cancel,WARNING,20,"Falling Alarm occurred"
IO.Motion.ePTI
The device will automatically occur this event if the device does not detect motion for 30 seconds (that means if
30 seconds have passed since the IO.Motion.eStanding event was occurred or when the device wakes up from the
doze mode with wakeup reason Standing).
Table 31:
Input states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 283 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.3.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
IO.BTN
STATES-are checked every second
None
EVENTS-are evaluated just when the event occurs
Event notification code
IO.BTN.e<id>=short
Meaning
Occurs when the button<id> on a MAMBO2-B6/UXFS or Keyfob is pressed and within 2 seconds released. In
the following example, the event "IO.BTN.e3=long" is occurred when you press and hold the Button 3 (SOS) on
a Keyfob for longer than 2 seconds.
Example: IO.BTN.e3=short
$PFAL,Cnf.Set,AL1=IO.BTN.e3=long:GSM.SMS.send,"+491236576",8,"SOS"
IO.BTN.e<id>=long
Occurs when the button<id> on the MAMBO2-B6/UXFS or a Keyfob is pressed and hold for longer than 2
seconds.
IO.BTN.e<id>=double
Occurs when the button<id> on a Keyfob is double pressed within 500 milliseconds. MAMBOP2 does not
support this event.
<id>
Identifies which button the user pressed. To know what IDs are assigned to the buttons on the MAMBO2B6/UXFS and Keyfob, refer to the chapter 7.10. The following indices are used to identify the buttons on the
MAMBO2-B6/UXFS and Keyfob.
0
Left-Button on the MAMBO2-B6/UXFS.
1
Right-Button on the MAMBO2-B6/UXFS.
2
Middle-Button on the MAMBO2-B6/UXFS.
3
Middle-Button on the Keyfob (labelled SOS).
4
Left-Button on the Keyfob.
5
Right-Button on the Keyfob.
6
Button on the Bluetooth headset.
X
Any button (0...6) .
Table 32:
Button states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 284 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.4
3.4.4.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DISPLAY (DISPLAY states and events)
DISPLAY.Menu
STATES -are checked every second
None
EVENTS-are evaluated just when the event occurs
Event notification code
Meaning
DISPLAY.Menu.e=<item_level>
Define the menu event sender, the location of a menu item (e.g. DISPLAY.Menu.e=1.2 - occurs when you
start the first level sub-menu of the primary menu 1). See chapter 3.3.2.2 for more details.
<item_level>
Table 33:
3.4.4.2
Occurs when the user has executed/pressed the last entry of the selected menu item.
e.g. DISPLAY.Menu.e=1.2
Display menu states and events.
DISPLAY.DIALOG
STATES-are checked every second
None
EVENTS-are evaluated just when the event occurs
Event notification code
Meaning
DISPLAY.DIALOG.e<id>=<btn>
Occurs when a specific dialog box prompts/appearers and the user presses either the left or right button or
the time out expires.
<id>
Identifies which dialog box caused a specific button event. It must be in the range 0 through 99.
<btn>
Identifies which button contained on the dialog box the pressed.
inactive When the specified dialog box hides
btn2
When the left button on the dialog box is pressed.
bnt1
When the right button on the dialog box is pressed.
Table 34:
Dialog states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 285 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.4.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DISPLAY.Trip
STATES - are checked every second
Event notification code
Meaning
DISPLAY.Trip.s=<state>
True as long as the selected trip state is true.
Define when the trip state should be true. It can be set to:
Active
True during a trip is active (Trip has started).
Inactive True during a trip is inactive (Trip has stopped ).
<state>
EVENTS - are evaluated just when the event occurs
Event notification code
Meaning
DISPLAY.Trip.e=<event>
Occurs when the specified trip event is generated.
Define when the trip event should be occurred. These events are also occurred when you Start, Stop, Pause or
Resume a Trip from the MAMBO2-B6/UXFS screen. It can be set to:
Start
Occurs when a trip has been started.
Stop
Occurs when a trip has been stopped.
Pause
Occurs when a trip has been paused.
Resume Occurs when a trip has been resumed.
<event>
Table 35:
3.4.4.4
Trip states and events.
DISPLAY.Tripmode
STATES - are checked every second
Event notification code
Meaning
DISPLAY.Tripmode.s=<mode>
True as long as the selected trip mode is checked. This can be done using the Trip view on the MAMBO2B6/UXFS screen.
Define, when the trip state should be true. It can be set to:
walk
True while the trip is in the Walk-mode.
bicycle
True while the trip is in Bicycle-mode.
motor
True while the trip is in Motor-mode.
<mode>
EVENTS-are evaluated just when the event occurs
None
Table 36:
3.4.4.5
Trip-Mode states and events.
DISPLAY.Popup
STATES-are checked every second
none
EVENTS-are evaluated just when the event occurs
Event notification code
Meaning
DISPLAY.Popup.e<id>=<type>
Occurs when the popup <id> is prompted/appeared, the user has pressed a button or waits
until the time out is expired.
Identifies which dialog box caused a specific button event. It must be in the range 0 through 99.
Please note that, the <id>=1 occurs when you press the SOS symbol on the MAMBO2-B6/UXFS.
Therefore, if you want to trigger an SOS alarm by using the SOS symbol on the MAMBO2B6/UXFS, do not use the <id>=1 in other alarms.
<id>
Define when the popup event should be occurred. It can be set to:
Start
Occurs when the popup dialog is called/appeared.
Success Occurs when the OK is pressed.
Cancel
Occurs when the Cancel is pressed.
Expire
Occurs when the timeout is expired.
<type>
Table 37:
Popup states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 286 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.4.6
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
DISPLAY.Pois
STATES-are checked every second
none
EVENTS-are evaluated just when the event occurs
Event notification code
Meaning
DISPLAY.Pois.e<id>
Occurs when the radius of the waypoint specified in the GPS.TRIP.WPOINT<index> is reached.
Define the index of the waypoint in the list.
1 ..20
Occurs when the radius of the corresponding waypoint in the list is reached.
x
Occurs when the radius of any of waypoint in the list is reached.
<id>
Table 38:
3.4.4.7
POI states and events.
DISPLAY.Phone
STATES -are checked every second
Event notification code
Meaning
Display.Phone.s<id>=<state>
Check the state of a phonebook entry whether it is empty and the phone number assigned to the specified ID is
valid or not.
<id>
Define the id of the phonebook entries in the range 1 through 100.
<state>
Define the which state of the phonebook entry in the list should be checked:
valid Check the specified ID whether it is not empty and the phone number assigned to this entry is valid.
invalid Check the specified ID whether the phone number assigned to this entry is invalid.
EVENTS-are evaluated just when the event occurs
None
Table 39:
3.4.4.8
Phonebook states and events
DISPLAY.Tilt
STATES -are checked every second
Event notification code
Meaning
DISPLAY.Tilt.sCounters<comp><value>
This Tilt-counter increments itself by 1 each time the event "IO.Bearing.e6" is occurred. Once the
device goes back to the calibrated position this counter is rest to 0. With this state you can define
how many times the event "IO.Bearing.e6" should be occurred before this state is set to True
without the device goes back the the calibrated position.
$PFAL,Cnf.Set,AL1=IO.Bearing.e6&Display.Tilt.sCounter=5:IO.Beep20=hpulse,1000
Display.tilt.sState=deactivated
Check the state of tilt function whether it is deactivated.
Display.tilt.sState=activated
Check the state of tilt function whether it is activated.
<comp>
It can be set to =, !=, <, >, <= or >=.
<value>
Define a value to be compared with the calibrated position of the tilt alarm in the range 0 to 100.
EVENTS-are evaluated just when the event occurs
Event notification code
Display.Tilt.e=<state>
<state>
Meaning
Occurs when the Tilt-function is called, stopped or the calibration process started, completed,
deactivated or failed. The Tilt event is also occurred when the user presses the Tilt symbol in the
MAMBO2-B6/UXFS screen.
Define when the event should be occurred.
start
when the user calls the tilt function.
stop
when the user stops the tilt function.
calibrate
when the calibration process starts.
activate
when the calibration process successfully completes.
deactivate when the user deactivates an activated Tilt alarm.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 287 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
error
Table 40:
3.4.4.9
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
when the calibration process fails (the device moves during the calibration process).
Tilt alarm states and events.
DISPLAY.Follow
STATES-are checked every second
none
EVENTS-are evaluated just when the event occurs
Event notification code
Meaning
Display.Follow.eSelect=<id>
<id>
Occurs when the user selects a device with the specified ID to be traced from the list.
Define the ID of the device in the list - see parameter "GPS.TRACE.DEV<index>" for more details.
Display.Follow.eDest
Occurs when the destination is reached - see parameter "GPS.TRACE.DEV<index>" for more details.
Table 41:
3.4.4.10
Follow states and events.
DISPLAY.User
STATES-are checked every second
none
EVENTS-are evaluated just when the event occurs
Event notification code
Display.User.e<id>
<id>
Meaning
Occurs when the user selects a menu icon from the display.
Define the ID in the range from 1 .. 4 corresponding to the user icons 40 .. 43 (see configuration parameter :
DISP.VIEWS)
Table 41:
User states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 288 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPS (GPS states and events)
3.4.5.1
GPS.Nav
STATES - are checked every second
State notification code
Meaning
GPS.Nav.sFix=valid
True when the device obtains a valid GPS-fix until it loses that fix (GPS data goes from invalid to valid).
This state is DEVICE.GPS.AUTOCORRECT configuration-dependent.
$PFAL,CNF.Set,AL1=Sys.Timer.e1&GPS.Nav.sFix=valid&GPS.Nav.sSpeed>0&GPS.Nav.Position.s1>100:GP
S.Nav.Position1=current&GPS.History.Write,0,""
GPS.Nav.sFix=invalid
True when the device loses a valid GPS-fix until obtained again (GPS data goes from valid to invalid).
GPS.Nav.sFix=correct
True when the current GPS position is valid and passed GPS.AUTOCORRECT conditions. It can be true only
if GPS.AUTOCORRECT feature is used.
GPS.Nav.sDist<comp><value>
True when the current distance (in meter) of the device matches the user-defined value.
GPS.Nav.sDeltaSpeed<comp><value>
True when the speed difference of the device matches the user-defined value.
GPS.Nav.sSpeed<comp><value>
True when the current speed of the vehicle matches the user-specified value. The user-set comparator
determines when this state should be true. Example: GPS.Nav.sSpeed>40
<comp>
Compares two values and return a Boolean (True/False) value that represents the result of the
comparison. It can be set to =, !=, <, >, <= or >=.
<value>
Set the value of speed, in metres per second, between 0 and 4294967295 that matches your application.
GPS.Nav.Position.s<buffer_index><co
mp><value>
True when the current distance of the device from a stored position <buffer_index> matches the userdefined value. The user-set comparator determines when this state should be true. Hint: This state can be
used to monitor the distance of the device from a stored position. In combination with a counter it is
possible to calculate the distance of the device on which it has been moved since e.g. MAMBO2-B6/UXFS is
turned on. (= the driven kilometres without breaks). Example: GPS.Nav.Position.s1>120
it is a number ranging from 0 to 4, which determines how far from a stored position the MAMBO2B6/UXFS is. The system gets the contents of the defined buffer index and calculates the distance the
MAMBO2-B6/UXFS device has moved from that point.
A GPS position can be temporarily stored using the following command:
$PFAL,GPS.Nav.Position<buffer_index>=<type>
A GPS position can be permanently stored using the following command, if the content of <buffer_index>
is not empty.
$PFAL,GPS.Nav.Position<buffer_index>=save<slot_id>
Whenever system starts up the contents of the <slot_id> has to be loaded into the <buffer_index> for
further use.
$PFAL,GPS.Nav.Position<buffer_index>=load<slot_id>
Compares two values and return a Boolean (True/False) value that represents the result of the
comparison. It can be set to =, !=, <, >, <= or >=.
<buffer_index>
<comp>
<value>
Set the value of the distance, in meter, between 0 and 4294967295 that matches your application.
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
Occurs when more than 3 GPS satellites are in use.
GPS.Nav.eFix=valid
$PFAL,CNF.Set,AL1=Sys.Timer.e1&GPS.Nav.eFix=valid&GPS.Nav.sSpeed>20:GPS.History.Write,0,""
GPS.Nav.eFix=invalid
Occurs when three or less GPS satellites are in use (just when the GPS position goes from valid to invalid).
This event is generated whenever the device changes its heading for more than the specified heading
tolerance (e.g. > 22°). It can be used e.g. to archive or send to the server device's current position
whenever the device deviates the direction of predefined degrees. Once an event is generated, the
heading angle resets to 0, the next event will occur when the heading angle reaches or /exceeds the
specified value.
GPS.Nav.eChangeHeading
$PFAL,CNF.Set,AL1=GPS.Nav.eChangeHeading&GPS.Nav.sSpeed>0&GPS.Nav.sFix=valid:TCP.Client.Sen
d,8,"Heading changed"
Table 42:
Navigation states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 289 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.5.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPS.Time
STATES - are checked every second
State notification code
GPS.Time.sYear<comp><value>
<value>
True when the current year obtained from the GPS date matches the specified <value>
Example: GPS.Time.sYear=2006
Specify the year in the range 1 through 10000 that matches your application. The format is "yyyy", e.g. 2006.
GPS.Time.sMonth<comp><value>
<value>
GPS.Time.sMDay<comp><value>
<value>
GPS.Time.sWeek<comp><value>
<value>
True when the current month obtained from the GPS date matches the specified <value> .
Example: GPS.Time.sMonth=12
Integer value between 1 and 12, where January is the first month of the year and December is the twelfth.
The format is "mm", e.g. 12.
True when the current day of month obtained from the GPS date matches the specified <value>
Example: GPS.Time.sMDay=8
Integer value between 1 and 31. Valid Day values are 1 through 28, 29, 30, or 31, depending on the current
Month value. For example, the possible Day values for month 2 (February) are 1 through 28 or 1 through 29,
depending on whether or not the Year value specifies a leap year. If the specified value is not within range,
this state never results True. The format is "dd" without leading "0" , e.g. 8.
True when the current number of weeks obtained from the GPS date matches the specified <value>
Example: GPS.Time.sWeek=40
Integer value between 1 and 52. The format is "ww" without a leading "0", e.g. 40.
GPS.Time.sWDay<comp><value>
<value>
GPS.Time.sHour<comp><value>
<value>
GPS.Time.sTimespan=<value>
True when the current week day obtained from the GPS date matches the specified <value>
Example: GPS.Time.sWDay=2
Integer value between 1 and 7, where Monday is the first day of the week and Sunday is the seventh. The
format is "ww", e.g. 12.
True when the current hour obtained from the GPS date matches the specified <value>.
Example: GPS.Time.sHour=12
Integer value between 0 and 23. If the specified value is not within range, this state never results True. The
value 0 corresponds to midnight, 12 corresponds to noon, and so on. The format is "hh" without a leading
"0", e.g. 40.
True, when the current GPS time is within the user specified <value>. Note: This state can be used to
generate activity reports or stop reports for a period of time (e.g. generate activity reports between 8:30:00
and 14:45:00).
Example: GPS.Time.sTimespan=8:30:40-14:45:51
Represents a period of time as separate start time and end time values separated by dash "-" without spaces
The format is "hh:mm:ss-hh:mm:ss" e.g. 8:30:40-14:45:51. Valid Hour (hh) values are 0 through 23, without a
leading zero. Valid Minute (mm) and Second (ss) values are 0 through 59, without a leading zero.
<value>
GPS.Time.sDatespan=<value>
True when the current GPS date is within the user specified <value>. State is checked every second. Note:
This state can be used to generate activity reports or stop reports for a range of date (e.g. generate activity
reports from Tuesday 31th January 2006 until Thursday 16th February 2006).
Example: GPS.Time.SDataspan=10.01.2006-20.01.2006
Represents a range of date as separate start date and end date values delimited by dash "-" (DateStamp as a
string in the format dd.mm.yyyy-dd.mm.yyyy). The start and end dates consist of the number of day, month
and year. depending on the specified Month value (mm), valid Day (dd) values are 1 through 28, 29, 30, or
31, without a leading zero. For example, the possible Day values for month 2 (February) are 1 through 28 or 1
through 29, depending on whether or not the Year value specifies a leap year. Valid Month (mm) values are 1
through 12, without a leading zero and Year (yyyy) values are 2000 through 9999.
<value>
GPS.Time.sLocalTimespan=<value>
True, when the current system time is within the user specified <value>. Note: This state can be used to
generate activity reports or stop reports for a period of time (e.g. generate activity reports between 8:30:00
and 14:45:00).
Represents a period of time as separate start time and end time values separated by dash "-" without spaces
The format is "hh:mm:ss-hh:mm:ss" e.g. 8:30:40-14:45:51. Valid Hour (hh) values are 0 through 23, without a
leading zero. Valid Minute (mm) and Second (ss) values are 0 through 59, without a leading zero.
<value>
GPS.Time.sLocalDatespan=<value>
<value>
Meaning
True when the current system date is within the user specified <value>. State is checked every second. Note:
This state can be used to generate activity reports or stop reports for a range of date (e.g. generate activity
reports from Tuesday 31th January 2006 until Thursday 16th February 2006).
Represents a range of date as separate start date and end date values delimited by dash "-" (DateStamp as a
string in the format dd.mm.yyyy-dd.mm.yyyy). The start and end dates consist of the number of day, month
and year. depending on the specified Month value (mm), valid Day (dd) values are 1 through 28, 29, 30, or
31, without a leading zero. For example, the possible Day values for month 2 (February) are 1 through 28 or 1
through 29, depending on whether or not the Year value specifies a leap year. Valid Month (mm) values are 1
through 12, without a leading zero and Year (yyyy) values are 2000 through 9999.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 290 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Compares two values and return a Boolean (True/False) value that represents the result of the comparison.
It can be set to =, !=, <, >, <=, >=.
<comp>
EVENTS
None
Table 43:
3.4.5.3
GPS Time states and events.
GPS.History
STATES - are checked every second
State notification code
Meaning
GPS.History.sDist<comp><value>
True when the current distance of the device from the position of the last stored history entry matches
the specified <value>. The set comparator determines how the comparison of both values (device's
location and user's value) will take place.
$PFAL,Cnf.Set,AL1=GPS.History.sDist>=500:GPS.History.Write,0,""
<comp>
Compares two values and return a Boolean (True/False) value that represents the result of the
comparison. It can be set to =, !=, <, >, <= or >=.
<value>
Specify the distance, in meter from 0 to 4294967295, to be compared with the current distance from
the last stored position in the history.
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
Occurs when the memory used for history data gets low (approx. 93% of this memory has been used
up). As mentioned in chapter 3.2.5.2 page 108, the history operates on a first-in-first-out (FIFO) basis,
limiting the amount of memory space used by history. Use this event to prevent overwriting of
available data in the history. You may configure an alarm that notifies the user to download the history
data on the server.
GPS.History.eTaut
$PFAL,Cnf.Set,AL1=GPS.History.eTaut:Display.Popup=1,red,OK,WARNING,20,"History
memory
almost full"
GPS.History.ePushFinished
Occurs when the history push command completes. It can be used to clear the history after reading out
via History.Push. Note that history events which are written during the readout are erased too.
Note: This event will be generated in any case – even if push mode fails (i.e. no SetRead has been
performed before)
$PFAL,Cnf.Set,AL1=GPS.History.ePushFinished:GPS.History.Clear
In this example, the history entries that have been written during or after the read out are also cleared.
Table 44:
History states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 291 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.5.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPS.Geofence
STATES - are checked every second
State notification code
Meaning
True when the device leaves the Geo-fence<id>.
GPS.Geofence.s<id>[=<state_type>]
Example: GPS.Geofence.s1=inside
GPS.Geofence.s1=outside
$PFAL,Cnf.Set,AL1=SYS.Timer.e0&GPS.Nav.sSpeed>=40&GPS.Geofence.s1=inside:TCP.Client.Send,
8,"Inside Geofence1at &(Speed) m/s"
<id>
Used to identify the configured areas and to split states from different Geo-fences
Following are listed all supported Geo-fence IDs.
0
- checks the state of parking area.
1..99
- checks the state of a specific user-configured geofences.
x
- used for any user-configured geofences.
Please, specify an Geofence <id> that is already configured. How to configure a Geofence <id>
refer to chapter 3.3.15.6.
[<state_type>]
Define the type of an Geofence state.
inside True when the device enters into the pre-configured Geofence<id>. Once it
results outside the Geo-fence <id> this state goes false, and the state
"GPS.Geofence.s<id>=outside" goes true.
outside - True when the device leaves the area <id>.
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
Occurs when the device enters into and/or leaves a Geofence <id>.
GPS.Geofence.e<id>[=<event_type>]
Example: GPS.Geofence.e1=inside
GPS.Geofence.eX=inside
GPS.Geofence.e1=outside
GPS.Geofence.eX
$PFAL,Cnf.Set,AL1=GPS.Geofence.e1=inside:GSM.SMS.Send,"+491234567",8,"Inside Geofence1"
$PFAL,Cnf.Set,AL2=GPS.Geofence.eX=inside:GSM.SMS.Send,"+491234567",8,"Inside
Geofence
&(LastGFName)"
<id>
Used to identify the configured areas and to split events from different Geofences.
Following are listed all supported Geofence IDs.
0
- used for parking area.
1 .. 99
- used for user-configured geofences.
x
- used for any user-configured geofences.
Please, specify a Geofence <id> that is already configured, otherwise no event occurs. How to
configure a Geofence <id> refer to chapter 3.3.15.6.
[<event_type>]
It is optional. Define the type of the geofence event.
inside
- Occurs only when the device enters into a Geofence <id>
outside - Occurs only when the device leaves a Geofence <id>
If it is omitted, event occurs when the device enters into and leaves a Geofence <id>
Table 45:
Geo-fence states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 292 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.5.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GPS.Area
STATES - are checked every second
State notification code
Meaning
True when the e device is in or out the specified area <id> (created from one or several Geofences).
GPS.Area.s<id>[=<state_type>]
Example: GPS.Area.s1=inside
GPS.Area.s1=outside
$PFAL,Cnf.Set,AL1=SYS.Timer.e0&GPS.Nav.sSpeed>=0&GPS.Area.s0=outside:TCP.Client.Send,8,"Outside
parking area"
$PFAL,Cnf.Set,AL1=SYS.Timer.e0&GPS.Nav.sSpeed>=40&GPS.Area.s1=inside:TCP.Client.Send,8,"Inside
Area1 at &(Speed) m/s"
<id>
Used to identify the configured areas and to split states from different Areas.
Following are listed all supported area IDs.
0
- Checks the state of parking area
1 .. 31
- Checks the state of a specific user-configured area
Please, specify an area <id> that is already configured. How to configure an area <id> refer to chapter
3.3.15.5.
[<state_type>]
Optional. Define the type of an area state, when the state will be set to true.
inside
- True when the device enters into area <id>. Once it results outside area <id>, this
state goes false, while the state "GPS.Area.s<id>=outside" goes true.
outside - True when the device leaves area <id>.
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
Occurs when the device enters into and/or leaves an Area <id>.
GPS.Area.e<id>[=<event_type>]
Example: GPS.Area.e1=inside
GPS.Area.eX=inside
GPS.Area.e1=outside
GPS.Area.eX
$PFAL,Cnf.Set,AL1=GPS.Area.e1=inside:GSM.SMS.Send,"+491234567",8,"Inside Geofence0"
$PFAL,Cnf.Set,AL2=GPS.Area.eX=inside:GSM.SMS.Send,"+491234567",8,"Inside Area &(LastAreaName)"
<id>
Used to identify the configured areas and to split events from different Areas.
Following are listed all supported area IDs.
0
- used for parking area
1 .. 31
- used for user-configured areas.
Please, specify an area <id> that is already configured, otherwise no event occurs. How to configure an
area <id> refer to chapter 3.3.15.5.
[<event_type>]
It is optional. Define the type of an area event.
inside
- Occurs only when the device enters into Area <id>
outside - Occurs only when the device leaves Area <id>
If it is omitted, event occurs when the device enters into and leaves Area <id>
Table 46:
Area states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 293 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.6
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM (GSM states and events)
3.4.6.1
GSM
STATES - are checked every second
State notification code
Meaning
True when the device is registered into the GSM network operator until GSM network lost. Once
lost, the "GPS.sOpInvalid" state returns true.
GSM.sOpValid[=<"operator_name">]
Example: GSM.sOpValid="T-Mobile D" or GSM.sOpValid="26201"
$PFAL,Cnf.Set,AL1=GSM.sOpValid="26201"&Sys.Trigger.s1=low:Sys.Trigger1=high&Display.Popup
=1,red,OK,CONNECT,20,"Registered to T-Mobile"
GSM.sOpInvalid[=<"operator_name">]
True when the GSM network operator fails until the GSM network operator found. Once found the
"GPS.sOpValid" state returns true.
$PFAL,Cnf.Set,AL1=GSM.sOpInvalid&Sys.Trigger.s1=high:Sys.Trigger1=low&Display.Popup=1,red,
OK,CONNECT,20,"T-Mobile lost"
GSM.sFieldstrength<comp><value>
True when the GSM signal strength matches the specified <value>.
GSM.sRoaming
True when the device is currently roaming between networks (not registered into home network).
GSM.sNoRoaming
True when GSM is currently registered via Roaming.
[<"operator_name">]
See the description of the "operator_name" used for events.
<value>
Represents a value from 0 to 99 (recommended 0.. 32)
<comp>
Compares two values and return a Boolean (True/False) value that represents the result of the
comparison. It can be set to =, !=, <, >, <= or >=.
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
GSM.eOpFound[=<"operator_name">]
Occurs when the device finds a (specific) GSM network operator and registered to that GSM
operator.
Example: GSM.eOpFound="T-Mobile D" or GSM.eOpFound="26201"
GSM.eOpLost[=<"operator_name">]
Occurs when the device loses a (specific) GSM network operator.
Optional. Specify in quotation marks (" ") the GSM operator name (i.e. "T-Mobile D") or operator
ID (i.e. "26201") to be compared. The comparison is case sensitive and must match exactly the
obtained operator name. The operator ID (i.e. "26201") may be specified only for the state
"GSM.sOpValid..." and the event "GSM.eOpFound" not for other states and events.
The mobile network code (operator ID) of the GSM operator is a 5 digit decimal number: first 2
digits are country code, followed by 3 digits containing the operator ID.
Note: It is possible to enter just the beginning of an operator name or ID – i.e. 26 would match all
German operator IDs (26XXX).
<"operator_name">]
Table 47:
Operator’s states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 294 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.6.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM.eCell
STATES
None
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
Occurs when the device is already connected to the GSM network and it changes the GSM network cell (handover).
GSM.eCellChange
Example: GSM.eCellChange
Table 48:
3.4.6.3
Cell’s states and events.
GSM.VoiceCall
STATES - are checked every second
State notification code
GSM.VoiceCall.sReady
GSM.VoiceCall.sNotReady
GSM.VoiceCall.sIncoming[=<"p_number">]
GSM.VoiceCall.sRingCounter<comp><value>
Meaning
True when the device is ready to receive or dial a voice call (currently there is no incoming or
established voice call).
True when the device is not ready to receive or dial a voice call.
Notice: If this state results true, it means that the GSM engine is not ready to dial, due to no
GSM network or SIM card available.
True when the device receives an incoming voice call [or a call from a specific phone number].
Example: GSM.VoiceCall.sIncoming="+4913131313"
True when the ring count value (i.e., number of rings) of an incoming call exceeds the
maximum ring count defined by the user.
Example: GSM.VoiceCall.sRingCounter>2
GSM.VoiceCall.sOutgoing[=<"p_number">]
True when the device makes an outgoing voice call [or a call from a specific phone number],
until the call is accepted or cancelled.
Example: GSM.VoiceCall.sOutgoing="+4913131313"
GSM.VoiceCall.sInside[=<"p_number">]
True when the device is inside a GSM voice call [or specific phone number]
Example: GSM.VoiceCall.sInside="+4913131313"
GSM.VoiceCall.sNotInside[=<"p_number">]
[<"p_number">]
True when a GSM voice call [or a call from a specific phone number] is cancelled, until
accepted.
Example: GSM.VoiceCall.sNotInside="+4913131313"
Optional. Specify in quotation marks (" ") the phone number of the other party(e.g.
+493677XXXX, including country and area code) to be compared. If it is omitted, the event
occurs for all incoming/outgoing voice call.
Compares two values and return a Boolean (True/False) value that represents the result of
the comparison. It can be set to =, !=, <, >, <= or >=.
It
is
an
integer
value
between
0
and
255, which determines the number of rings of an incoming call to wait for releasing an alarm
(e.g. accept that call) .
<comp>
<value>
EVENTS – are evaluated just when the event occurs
Event notification code
GSM.VoiceCall.eIncoming[=<"p_number">]
Meaning
Occurs when the device receives a GSM voice call. This event can then decide whether to
accept that call or not.
Example: GSM.VoiceCall.eIncoming="+4913131313"
GSM.VoiceCall.eIncoming="spy"
Occurs when the device receives a GSM voice call and its number is available in the spy call
list (GSM.SPY.SELECTION). The example below shows that when a voice call comes in and its
number is in the spy list, it will be accepted immediately.
$PFAL,Cnf.Set,AL1=GSM.VoiceCall.eIncoming="spy":GSM.VoiceCall.Accept
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 295 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
GSM.VoiceCall.eRingStopped[=<"p_number">]
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Occurs when the device is already set into the ringing mode and the caller hangs up the
phone.
Example: GSM.VoiceCall.eRingStopped="+4913131313"
GSM.VoiceCall.eOutgoing[=<"p_number">]
GSM.VoiceCall.eEstablished[=<"p_number">]
Occurs when the device sets up an outgoing voice call, before the recipient’s phone rings.
Example: GSM.VoiceCall.eOutgoing="+4913131313"
Occurs when an incoming voice call has been established successfully.
Example: GSM.VoiceCall.eEstablished="+4913131313"
Occurs when an established voice call has been hanged up.
GSM.VoiceCall.eHangup[=<"p_number">]
Example: GSM.VoiceCall.eHangup="+4913131313"
$PFAL,Cnf.Set,AL1=GSM.VoiceCall.eHangup="<spy call number>":GSM.Audio.RingGain=3
Optional. Specify in quotation marks (" ") the phone number of the other party (e.g.
+493677XXXX, including country and area code) to be compared. If it is omitted, the event
occurs for all incoming/outgoing voice call.
[<"p_number">]
Table 49:
3.4.6.4
Voice Call states and events.
GSM.SMS
STATES
None
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
GSM.SMS.eIncoming
Occurs when the device receives a SMS message.
Occurs when the device receives a SMS message from a specific phone number.
GSM.SMS.eIncoming.Number=<"p_number">
Example: GSM.SMS.eIncoming.Number="+4913131313"&
GSM.SMS.eIncoming.Text="test"
Occurs when the device receives a SMS message with a specific contents.
GSM.SMS.eIncoming.Text=<"text">
GSM.SMS.eSent
Example: GSM.SMS.eIncoming.Number="+4913131313"&
GSM.SMS.eIncoming.Text="test"
Occurs when the device sends an SMS message. Using this event you can set up an SMS counter
inside the device as given in the example below (for example know how many SMS messages
have been sent in 1 month by the device).
Example for SMS counter:
$PFAL,Sys.Counter10.save1
//saves the initial value (0) of the Counter10
$PFAL,Cnf.Set,AL0=Sys.Device.eStart:Sys.Counter10.Load1
//loads the value of the saved of the Counter10
$PFAL,Cnf.Set,AL1=Sys.Device.eShutdown:Sys.Counter10.save1
//saves the current value of the Counter10
$PFAL,Cnf.Set,AL2=GSM.SMS.eSent:Sys.Counter10.Increment=1
//increments Counter10 by 1 when an SMS is sent out
$PFAL,Cnf.Set,AL3=GPS.Time.sMDay=1&Sys.Trigger.s10=low:Sys.Trigger10=high&Sys.Timer10.Start=single,5000 //starts a single timer. Timer10
event is needed to reset the value of the Counter10 to 0 on the first
day of any month. Trigger10 prevents Timer10 from starting
periodically during the first day.
$PFAL,Cnf.Set,AL4=Sys.Device.eStart&GPS.Time.sMDay!=1&Sys.Trigger.s10=high:Sys.Trigger10=low //resets Trigger10 to low if the day is not 1.
$PFAL,Cnf.Set,AL5=Sys.Timer.e10:Display.Dialog=1,"Counter",0,20,"OK","Cancel","SMS=&(Counter10)"&Sys.Counter10.set=0&Sys.Counter10.save1
Occurs when the device sends a SMS message to the specified phone number.
GSM.SMS.eSent.Number=<"p_number">
Example: GSM.SMS.eSent.Number="+4913131313"&
GSM.SMS.eSent.Text="test"
Occurs when the device sends an SMS message with the specified contents.
GSM.SMS.eSent.Text=<text>
Example: GSM.SMS.eSent.Number="+4913131313"&
GSM.SMS.eSent.Text="test"
GSM.SMS.eFailed
Occurs when SMS sending failed.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 296 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
<"p_number">
Specify in quotation marks (" ") the phone number (e.g. +493677XXXX, including country and area
code) to be compared.
<"text">
Specify in quotation marks (" ") the text (i.e. "your text") to be compared. The comparison is case
sensitive.
Hint:
Because both events (".Text="your text"" and ".Number="+493677XXXX"") may occur
at the same time, you may combine them within a condition field.
Table 50:
3.4.6.5
SMS states and events.
GSM.DataCall
STATES - are checked every second
State notification code
GSM.DataCall.sReady
GSM.DataCall.sIncoming[="p_number"]
GSM.DataCall.sRingCounter<comp><value>
Meaning
True when the device is ready to receive a data call, but before the data call is established.
True when the device receives an incoming data call [or a call from a specific phone number].
Example: GSM.DataCall.sIncoming ="+4913131313"
True when the number of ring that have elapsed since an incoming data call was generated
match the user specified value.
Example: GSM.DataCall.sRingCounter>2
True when a GSM data call [with specific phone number] is accepted, until the call is cancelled.
GSM.DataCall.sInside[="p_number"]
Example: GSM.DataCall.sInside="+4913131313"
$PFAL,Cnf.Set,AL1=GSM.DataCall.sInside:MSG.Send.CSD,8,"&(DeviceName)"
<"p_number">]
It is optional. Specify in quotation marks (" ") the phone number (e.g. +493677XXXX, including
country and area code) to be compared. If it is omitted, the event occurs for
incoming/outgoing data call.
<comp>
Compares two values and return a Boolean (True/False) value that represents the result of
the comparison. It can be set to =, !=, <, >, <= or >=.
<value>
It is an integer value between 0 and 255, which determines the number of rings of an incoming
call to wait for release an alarm.
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
Occurs when the device receives a CSD call or a CSD call from a specific phone number.
GSM.DataCall.eIncoming[="p_number"]
Example: GSM.DataCall.eIncoming="+4913131313"
$PFAL,Cnf.Set,AL1=GSM.DataCall.eIncoming:GSM.DataCall.Accept
GSM.DataCall.eRingStopped[="p_number"]
Occurs when the device is already set into the ringing mode and the caller hangs up the
phone.
Example: GSM.DataCall.eRingStopped="+4913131313"
GSM.DataCall.eEstablished[="p_number"]
GSM.DataCall.eHangup[="p_number"]
Occurs when a CSD call has been established successfully.
Example: GSM.DataCall.eEstablished="+4913131313"
Occurs when hanging up an established CSD call
Example: GSM.DataCall.eHangup="+4913131313"
Occurs when receiving an packet.
GSM.DataCall.eReceived[="text"]
["p_number"]
Example: GSM.DataCall.eReceived="User text"
$PFAL,Cnf.Set,AL1=GSM.DataCall.eReceived="GPGSA":MSG.Send.CSD,2,"&(DeviceName)"
It is optional. Specify in quotation marks (" ") the phone number (e.g. +493677XXXX, including
country and area code) to be compared. If it is omitted, the event occurs for
incoming/outgoing data call.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 297 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Text of which the packet starts. This text has to match exactly the packet text (case sensitive)
to launch alarm actions. If the packet text contains more characters as specified inside <text>
only the specified characters will be compared.
["text"]
Table 51:
3.4.6.6
Data Call states and events.
GSM.GPRS
STATES - are checked every second
State notification code
Meaning
GSM.GPRS.sConnecting
True when the device tries to perform a GPRS attach until the GPRS is successfully attached.
GSM.GPRS.sOnline
True when the device is successfully attached to the GPRS until it is detached.
GSM.GPRS.sDisconnecting
True when the device tries to perform a GPRS detach until the GPRS successfully detached.
GSM.GPRS.sOffline
True when the device is successfully detached from the GPRS, or a GPRS connection is currently
inactive until the device is attached to the GPRS again.
GSM.GPRS.sTraffic<comp><value>
True when the complete current GPRS traffic (in Bytes) match the user specified traffic value.
<comp>
Compares two values and return a Boolean (True/False) value that represents the result of the
comparison. It can be set to =, !=, <, >, <= or >=.
<value>
It is an integer value between 0 and 4294967295 that specifies the number of bytes for GPRS traffic
completeness.
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
Occurs when the device initiates a connection to the GPRS network.
GSM.GPRS.eConnecting
$PFAL,Cnf.Set,AL1=GSM.GPRS.eConnecting:Sys.Counter0.Increment=1
$PFAL,Cnf.Set,AL2=Sys.Counter.s0>5:GSM.SMS.Send,"+491111111",0,"No GPRS attach"
Occurs when the device is successfully attached to the GPRS network. Depending on the user
application, the GPRS.eConnected event can execute the TCP.Client.Connect command to initiate a
TCP connection to the server.
GSM.GPRS.eConnected
$PFAL,Cnf.Set,AL2=GSM.GPRS.eConnected:Sys.Counter0.Set=0
GSM.GPRS.eDisconnecting
Occurs when the device initiates a disconnection from the GPRS services.
GSM.GPRS.eDisconnected
Occurs when GPRS connection between MAMBO2-B6/UXFS and the GPRS network is broken.
Table 52:
GPRS states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 298 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.7
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
TCP (TCP states and events)
3.4.7.1
TCP.Client
STATES - are checked every second
State notification code
Meaning
TCP.Client.sConnecting
True when the device initiates a TCP connection to the serve until it is successfully connected.
TCP.Client.sConnected
True when the device is successfully connected to the server until it attempts to disconnect.
TCP.Client.sDisconnecting
True when the device is trying to disconnect from the TCP server until it is disconnected.
TCP.Client.sDisconnected
True when the connection to the TCP Server is broken until it attempts to connect again.
TCP.Client.sIdle
True when the TCP connection is currently inactive until it is connected. (TCP.Client.Connect command
can be used to establish the TCP connection). Usually TCP parameters are configured to automatically
connect to the TCP server when GPRS state is already online. This state can be used to retrieve the
connection state when manual connection to the server is desired.
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
Occurs when the device initiates a TCP connection to the server, but still not connected.
TCP.Client.eConnecting
$PFAL,Cnf.Set,AL1=TCP.Client.eConnecting:Sys.Counter0.Increment=1
$PFAL,Cnf.Set,AL2=Sys.Counter.s0>5:GSM.SMS.Send,"+491111111",0,"No TCP connection"
Occurs when the device has successfully established a TCP connection to the server.
TCP.Client.eConnected
Example: $PFAL,Cnf.Set,AL3=TCP.Client.eConnected:Sys.Counter0.Set=0
TCP.Client.ePacketSent
Occurs when the device has sent a TCP packet to the connected remote server.
TCP.Client.ePingSent
Occurs when the device has sent a ping to the remote TCP server.
TCP.Client.eReceived[="text"]
Occurs when the device has received a TCP packet (with a specific text) from the remote TCP server.
Example: TCP.Client.eReceived="test"
It is optional. In quotation marks (" "), Specify the text (i.e. "your text") to be compared. If it is omitted, the
event occurs for each incoming message sent from remote server. This comparison is case sensitive. The
text to be sent from the remote server must be terminated with <CR><LF>.
["text"]
TCP.Client.eDisconnecting
Occurs when the device attempts to disconnect from to the remote TCP server.
TCP.Client.eDisconnected
This event occurs whenever the connection to the TCP Server is broken .
Table 53:
TCP Client states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 299 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.7.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
TCP.SMTP
STATES
None
EVENTS – are evaluated just when the event occurs
Event notification code
Meaning
TCP.SMTP.eSent
Occurs when the device has sent out an e-Mail.
TCP.SMTP.eFailed
Occurs when the device is not able to complete a send Email operation to a SMTP server. The connection to
the SMTP server failed, or authentication failed or the operation timed out etc.
Table 54:
SMTP states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 300 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.8
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
IEEE (states and events)
STATES-are checked every second (IEEE option is only available for the MAMBO2-UXFS)
None
EVENTS-are evaluated just when the event occurs
Event notification code
Meaning
IEEE.Device.eRequest="<mac_addr>"
Occurs automatically when an IEEE device/beacon is trying to make a connection to
the MAMBO2-UXFS. The <mac_addr> shows the MAC address of that IEEE device.
Table 55: IEEE states and events.
3.4.8.1
INDOOR
STATES-are checked every second (IEEE option is only available for the MAMBO2-UXFS)
None
EVENTS-are evaluated just when the event occurs
Event notification code
Meaning
Occurs whenever a nearby beacon returns with the same MAC address and payload as you
specified. If MAMBO2 gets out of range of Indoor devices the event
IEEE.Device.eIndoor="0","nodevice" will be generated.
IEEE.Device.eIndoor[="<mac_addr>","<payload>"] $PFAL,CNF.Set,AL1=IEEE.Device.eIndoor:Display.Dialog=1,"INDOOR MSG TEST",0,10,"Cancel
","OK","&(IDName), &(IDQL)"
$PFAL,Cnf.Set,AL90=IEEE.Device.eIndoor:MSG.Send.TCP,0,"&(DeviceName)=&(IDMac),&(ID
Name),&(IDQL)"
Optional. MAC address is an unique identifier set to a beacon by the manufacture. If used,
<mac_addr>
define it in quotation marks (" ") .
Optional. Payload is the name or identifier you have set to a beacon via configuration. If used,
specify it in quotation marks (" ").
<payload>
Table 56: IOBOX states and events.
3.4.8.2
IEEE.IOBOX<index>.State
STATES-are checked every second (IEEE option is only available for the MAMBO2-UXFS)
None
EVENTS-are evaluated just when the event occurs (IEEE option is only available for the MAMBO2-UXFS)
Event notification code
Meaning
Occurs when the I/O-BOX is successfully connected to the device.
IEEE.IOBox<index>.State.eConnected
$PFAL,Cnf.Set,AL1=IEEE.IOBox0.State.eConnected: Display.Popup=2,red,OK,WARNING,10,"
IOBox0 connected"
Occurs when the connection between the device and the I/O-BOX is broken.
IEEE.IOBox<index>.State.eDisconnected
$PFAL,Cnf.Set,AL1=IEEE.IOBox0.State.eDisconnected: Display.Popup=2,red,OK,WARNING,1
0,"IOBox0 disconnected"
Occurs when the battery of the I/O-BOX is critically low.
IEEE.IOBox<index>.Bat.eLow
$PFAL,Cnf.Set,AL1=IEEE.IOBox0.Bat.eLow:Display.Popup=2,red,OK,WARNING,10,"IOBox0
battery low"
Identifies which I/O-BOX device caused a specific event. It is used as a device identifier at the
time of the event. It can be set from 0 .. 5.
<index>
Table 57:
IOBOX states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 301 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.8.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
IEEE.IOBOX<index>.IN
STATES-are checked every second (IEEE option is only available for the MAMBO2-UXFS)
State notification code
IEEE.IOBox<index>.IN.s<port>=low
IEEE.IOBox<index>.IN.s<iport >=high
Meaning
True when the input <port> on the I/O-BOX <index> goes low.
True when the input <port> on the I/O-BOX <index> goes high.
Identifies which I/O-BOX device caused an specific event. It is used as a device identifier at the time of
the event. It can be set to a value from 0 .. 5.
NOTE: Both states will work properly only when the report mode <in_report_mode> on the IEEE
Configuration parameter is set to 1 or 2.
Identifies which input port changed its state. Depending on the order option, it can be set to:
<index>
0 ... 3
if the IOBOX device with 16-pin MOLEX connector ordered (see chapter 7.11, page 343).
0 or 4
if the IOBOX device with 8-pin connector (extension cable) is ordered (see chapter 7.11,
page 343).
Pin designations for the 16-pin MOLEX and 8-pin connector are shown in chapter.
<port>
EVENTS-are evaluated just when the event occurs (IEEE option is only available for the MAMBO2-UXFS)
Event notification code
Meaning
Occurs when a rising-edge on the specified input <port> is triggered.
IEEE.IOBox<index>.IN.e<port>=redge
$PFAL,Cnf.Set,AL1=IEEE.IOBox0.IN.e2=redge: Display.Popup=2,red,OK,WARNING,10,"IN2
on
IOBox0 triggered to high"
Occurs when a falling-edge on the specified input <port> is triggered.
IEEE.IOBox<index>.IN.e<port>=fedge
$PFAL,Cnf.Set,AL1=IEEE.IOBox0.IN.e2=fedge: Display.Popup=2,red,OK,WARNING,10,"IN2
on
IOBox0 triggered to low"
Identifies which I/O-BOX device caused a specific event. It is used as a device identifier at the time of
the event. It can be set to a value from 0 .. 5.
NOTE: Both events will work properly only when the report mode <in_report_mode> on the IEEE
Configuration parameter is set to 1 or 2.
Identifies which input on the I/O-BOX caused the event. Depending on the order option, it can be set
to:
0 ... 3
if the IOBOX device with 16-pin MOLEX connector ordered (see chapter 7.11, page 343).
0 or 4
if the IOBOX device with 8-pin connector (extension cable) is ordered (see chapter 7.11).
<index>
<port>
Pin designations for the 16-pin MOLEX and 8-pin connector are shown in chapter .
Table 58:
3.4.8.4
IOBOX Input states and events.
IEEE.IOBOX<index>.ANA
STATES-are checked every second (IEEE option is only available for the MAMBO2-UXFS)
State notification code
Meaning
IEEE.IOBOX<index>.ANA.s<port><comp><voltage>
True when the comparison of both values the current voltage on the analog input <port>
and the user specified <voltage> is evaluated true.
Example: IEEE.IOBOX0.ANA.s1<12.25
Identifies which I/O-BOX device changed a specific state. It is used as a device identifier at the
time of the event. It can be set to a value from 0 .. 5.
<index>
Identifies which analog input on the I/O-BOX changed its state. It can be set to 0 or 1. Pin
designations for the connectors are shown in chapter 7.11, page 343.
<port>
To show correct voltages on the analog inputs, they have to be calibrated before using.
<comp>
Compares two values and return a Boolean (True/False) value that represents the result of
the comparison. It can be set to =, !=, <, >, <= or >=.
<voltage>
iDefine the value of voltage which can be set from 0 to 12 (number can be represented with
floating-point notation).
EVENTS - are checked every second (IEEE option is only available for the MAMBO2-UXFS)
None
Table 59:
IOBOX Analogue Input states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 302 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.9
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
ANT (ANT states and events)
3.4.9.1
ANT.Heartbeat
STATES-are checked every second (ANT option is no longer available)
State notification code
Meaning
ANT.Heartbeat.sConnected
True when the device results connected to the remote ANT heartbeat sensor until disconnected again.
ANT.Heartbeat.sDisconnected
True when the device results disconnected from the remote ANT heartbeat sensor until connected again.
ANT.Heartbeat.sUnderrun
True as long as the heartbeats results below the specified minimum value.
ANT.Heartbeat.sOverrun
True as long as the heartbeats results above the specified maximum value.
EVENTS-are evaluated just when the event occurs (ANT option is no longer available)
Event notification code
Meaning
ANT.Heartbeat.eConnected
Occurs when an ANT+ connection between heartbeat sensor and MAMBO2-UXFS is successfully done.
ANT.Heartbeat.eDisconnected
Occurs when an ANT+ connection between heartbeat sensor and MAMBO2-UXFS is broken.
ANT.Heartbeat.eUnderrun
Occurs when the heartbeats run below the specified minimum value.
ANT.Heartbeat.eOverrun
Occurs when the heartbeats run above of the specified maximum value.
Table 60:
3.4.9.2
Heartbeat states and events.
ANT.Speed
STATES-are checked every second (ANT option is no longer available)
State notification code
Meaning
ANT.Speed.sConnected
True when the device results connected to the remote ANT Speed sensor until disconnected again.
ANT.Speed.sDisconnected
True when the device results disconnected from the remote ANT Speed sensor until connected again.
EVENTS-are evaluated just when the event occurs (ANT option is no longer available)
Event notification code
Meaning
ANT.Speed.eConnected
Occurs when a ANT+ connection between Speed sensor and MAMBO2-UXFS is successfully done.
ANT.Speed.eDisconnected
Occurs when a ANT+ connection between Speed sensor and MAMBO2-UXFS is broken.
Table 61:
Speed states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 303 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
3.4.9.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
ANT.Cadence
STATES-are checked every second (ANT option is no longer available)
State notification code
Meaning
ANT.Cadence.sConnected
True when the device results connected to the remote ANT Cadence sensor until disconnected again.
ANT.Cadence.sDisconnected
True when the device results disconnected from the remote ANT Cadence sensor until connected again.
EVENTS-are evaluated just when the event occurs (ANT option is no longer available)
Event notification code
Meaning
ANT.Cadence.eConnected
Occurs when a ANT connection between Cadence sensor and MAMBO2-UXFS is successfully done.
ANT.Cadence.eDisconnected
Occurs when a ANT connection between Cadence sensor and MAMBO2-UXFS is broken.
Table 62:
Speed states and events.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 304 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
4 APPLICATION DEVELOPMENT GUIDE
The MAMBO2-B6/UXFS operating with firmware version later can be simply configured using the
FALCOM Workbench software. For more details, please refer to a separate manual
"FALCOMWorkbenchUserGuide.pdf".
For more detailed information how to setup a serial connection, please refer to a separate manual
"MAMBOIIEvalKitGettingStarted.pdf".
4.1
What kind of rules should be considered to prepare application with MAMBO2B6/UXFS
✔
Read carefully this document and write down all events, states and actions, which will be used
in your application.
✔
Decide, what kind of alarms will be executed and which channels will be used (Serial, SMS,
TCP).
✔
Decide, when these alarms will execute
✔
Determine, which system state must already be present and which particular event the system
will be waiting for to execute one or more alarms.
✔
Try always to filter alarms by using 1 event and up to 4 states. A small difference between
alarms enables you to reproduce more than 1 alarm for one event.
✔
Make sure, when an event occurs, it does not affect other alarms except the premeditated one.
✔
Use TIMER-events to activate events and execute actions at regular interval. Use TRIGGERevents to execute various actions at a particular time. Use COUNTER-events to limit the
number of alarms. However, be careful when you use them. Write down all alarms, which will
be executed either the TIMER, COUNTER or TRIGGER and compare them with other already
configured alarms, to check if conflicts between them take place. They should never create a
situation in which an empty action causes an error, the errors may be caused repeatedly
affecting on system performances.
✔
Avoid executing of false alarms when TIMER, COUNTER and TRIGGER are in use.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 305 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
4.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Test your MAMBO2-B6/UXFS by creating a simple configuration
As explained in this document above events are a key part of your application logic. Events correspond
to the activities in your system MAMBO2-B6/UXFS. In this tutorial you will find explained how to use
event and states in the MAMBO2-B6/UXFS device.
For example, MAMBO2-B6/UXFS device contains IO.BTN<index>=long button events that can be
programmed to respond when the user presses a button on the device. If the incoming event is a
button-press event, the system wants to know both which button the user pressed and how long. In
these cases, you need the number of the button and the type of the press as additional information.
MAMBO2-B6/UXFS’s internal firmware knows the following button actions: short-press, long-press and
double-press. MAMBO2-B6/UXFS itself does not support short-press and double-press events, it
supports only long-press. However, the firmware running on the MAMBO2-B6/UXFS device it is able to
detect also any key-press events occurred on a Keyfob device that is already connected to the
MAMBO2-B6/UXFS device via IEEE.
A short-press event
occurs when a button on the Keyfob device is pressed and released
within 2 seconds.
A long-press event
occurs when a button on the Keyfob device or MAMBO2-B6/UXFS is
pressed and after 3 seconds released.
A double-press event
occurs when a button on the Keyfob is double pressed within 500
msec.
When a button is pressed, the following event occurs.
IO.BTN.e<index>=<time>
<index> - Identifies which button the user pressed:
0,1,2
3,4,5
x
= MAMBO2-B6/UXFS’s button (left, right and middle button accordingly - only long
press
events supported)
= Keyfob's button
= Any button
<time> - Identifies the type of press [short, long, double].
In the example below, an application accepts a long-press event occurred from BTN3.
IO.BTN.e3=long
To handle button events on different devices, attach the sender of the event to the event of the button
using "&" conjunction.
In the example below, an application accepts a short-press event occurred from BTN4.
IO.BTN.e4=short
The configuration you write to respond to an event is called Alarm. Each alarm MUST include at least
one event within the condition field as its source and one command within the action field as its target.
An alarm awaits the occurrence of one event and then performs the action attached to the event that
occurred. When an event occurs, and it is available in more than one alarm, then the selection of the
activity to perform depends on the index of the alarm (AL<index>). The low indices are executed first. In
most cases, the action for an event you define can be simple a notification.
$PFAL,IO.Beep3=hpulse,1000
$PFAL,IEEE.Keyfob0.LED1=High
The following procedure shows the steps you must take to test a simple configuration on the MAMBO2B6/UXFS device.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 306 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
To enable an application to respond when a button is pressed, attach the action to the button’s event
and send it to the MAMBO2-B6/UXFS device by adding the "$PFAL,Cnf.Set,AL1=" at the front of the
configuration.
$PFAL,Cnf.Set,AL1=IO.BTN.e0=long:IO.Beep3=cyclic,500,1000
$PFAL,Cnf.Set,AL2=IO.BTN.e1=long:IO.Beep3=low
$PFAL,Cnf.Set,AL3=IO.BTN.e3=short:IEEE.Keyfob0.LED1=high
$PFAL,Cnf.Set,AL4=IO.BTN.e3=long:IEEE.Keyfob0.LED1=low
For more details how to connect a Keyfob or I/O-BOX to the MAMBO2-UXFS with IEEE option, refer to
the application note "AppNoteGettingStartedWithKeyfob&IOBOX_x.x.x.pdf ".
4.2.1
How to connect a Bluetooth audio headset to a MAMBO2-UXFS
Please refer to the application note "AppNotesMAMBO2-UXFSAudioHeadSet&HandfreeSet.pdf".
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 307 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
4.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Start a GPRS/TCP connection
To get connected to the GPRS and then to a TCP server, you have to change all GPRS and TCP settings to
your application conditions (see table below). These settings can be changed using the command
"$PFAL,Cnf.Set,<parameter>*Checksumm". When these settings are changed, then enter the PIN
number of the used SIM card. Your SIM card must already be inserted into the SIM card holder on the
device.
The configuration given in table below must be done locally via Bluetooth or USB.
SETUP
COMMENT
SETUP
COMMENT
SETUP
COMMENT
Enter the GPRS Settings, only if the Remote server is already available and your application interface
requires a TCP connection:
$PFAL,Cnf.Set,GPRS.APN=internet.t-d1.de (for example)
$PFAL,Cnf.Set,GPRS.QOS=3,4,3,0,0
$PFAL,Cnf.Set,GPRS.QOSMIN=0,0,0,0,0
$PFAL,Cnf.Set,PPP.USERNAME=t-d1 (if your provider is T-D1 and requires it)
$PFAL,Cnf.Set,PPP.PASSWORD=gprs (if your provider requires)
$PFAL,Cnf.Set,GPRS.AUTOSTART=1 (default = 0)
(Once parameter setting is changed to $PFAL,Cnf.Set,GPRS.AUTOSTART=1 and sent to the MAMBO2B6/UXFS device, it tries immediately to attach itself to the GPRS services, unimportant in which
operating state the MAMBO2-B6/UXFS is).
Enter the TCP Settings, only if Remote server is already available and your application interface
requires a TCP connection:
$PFAL,Cnf.Set,TCP.CLIENT.CONNECT=1,2222.222.222.222,2222 (for example)
(the remote server that use the entered IP address and port number must be already running,
otherwise no TCP connection can be performed).
Enter the SIM PIN:
$PFAL,Cnf.Set,GSM.PIN=1111 (for example)
Enter the PIN of the used SIM card (your SIM card inserted into the MAMBO2-B6/UXFS device which is
supplied by your GSM operator or retailer) and not 1111.
Table 63:
Adapt your configuration settings to your application conditions.
Once you enter the PIN number of the used SIM card and GPRS.AUTOSTART=1, then the STEPPIII device
will automatically try to connect to the GPRS and TCP services using the user-defines settings. To know
the GPRS and TCP connection state you have to monitor both events GSM.GPRS.eConnected and
TCP.Client.eConnected which are displayed on the terminal program when connected. Note that, both
events can be shown only if the debug port is already turned on ($PFAL,Cnf.Set,DBG.EN=1). If problems
are met, regarding the TCP settings, contact your network administrator and request the correct server
IP address, Port number and login data. To note, the STEPPIII device is responsible for initiating the
connection to the remote server using the IP address and the Port number that you specified. While,
the used remote server is responsible for accepting the connection requested from the STEPPIII device
based on the logging data the device sends out.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 308 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
5 HOW TO SEND SMS MESSAGE TO THE MAMBO2-B6/UXFS
DEVICE
Write Command
The text mode has to be set using AT+CMGF=1
AT+CMGS=<MAMBO2-B6/UXFS_phone_number><CR>
<text> <ctrl-z>/<esc>
Response
+ CMGS: <m_ref>
OK/ERROR
Command Description
The write command transmits a short message from GSM modem (connected to a PC/laptop) to
the MAMBO2-B6/UXFS device using a terminal program. After invoking the write command wait
for the prompt ">" and then start to write the message to be sent to the MAMBO2-B6/UXFS
device. To send the message, simply press <CTRL-Z>. After the prompt a timer will be started to
observe the input. To abort sending, use <ESC>. Abortion is acknowledged with "OK", though the
message will not be sent. The message reference <m_ref> is returned to the GSM modem on
successful message delivery. This description is applied for the GSM modems distributed by
Falcom GmbH. For other modems or mobile phones, please, refer to the user’s guide of the used
device and read how to send SMS message to the network.
Parameter Description
<MAMBO2-B6/UXFS_phone_number>
Specify the phone number of the MAMBO2-B6/UXFS device.
<CR>
Specify the <RETURN> key or carriage return ASCI code (13), which has to be entered to
enable the text entry <text>.
<text>
Specify the message or PFAL command to be sent to the MAMBO2-B6/UXFS device.
<ctrl-z>
Specify the keyboard shortcut <CTRL+Z> for sending the message to the specified phone
number.
Notes
• SMS messages sent to the MAMBO2-B6/UXFS device must not be longer than 160
characters.
• The maximum length of the SMS to be sent from the MAMBO2-B6/UXFS device to the
receiver is predefined up to 160 characters using the 7-bit GSM coding scheme. If the
length of the SMS is longer than 160 characters, the MAMBO2-B6/UXFS does not split and
deliver that SMS message in two or more messages. The specified protocols to be sent out
that exceed the maximum length of the SMS (>160 characters) will be not attached into
(delivered with) that SMS message.
• The text entered behind the prompt ">" will be recognized by the MAMBO2-B6/UXFS
device as an input message or PFAL command.
• Do not use "$" sing in front of the PFAL commands when they are sent via SMS. The "$"
sing can be misinterpreted by the GSM, and couldn't be executed by device.
Example:
AT+CMGS=012345678
> PFAL,Cnf.Set,DEVICE.NAME=myMAMBO2-B6/UXFS<CTRL+Z>
or
> PFAL,CNF.Set,AL1=IO.Motion.eMoving:GSM.SMS.Send,"+491234567",8,"test"<CTRL+Z>
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 309 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
6 NMEA MESSAGES SUPPORTED BY MAMBO2-B6/UXFS DEVICE
The MAMBO2-B6/UXFS device transmits NMEA sentences every second, depending on the
configuration. The identifiers for the NMEA messages transmitted by the MAMBO2-B6/UXFS device are
listed below. Excepting GPIOP, GPGSM, AREA and BIN all other messages are based on the NMEA
standard messages.
GPGGA
GPS Fix Data.
GPRMC
Recommended Minimum Specific GPS Data.
GPGSV
GPS Satellites in View.
GPGSA
GPS DOP and Active Satellites.
GPVTG
Course Over Ground and Ground Speed.
GPGLL
Geographic Position in Latitude/Longitude.
GPIOP
MAMBO2-B6/UXFS Device Input/Output Ports.
GPGSM
GSM operator and reception status.
GP3DP
State of the Accelerator Sensor
AREA
Geofence AREA state protocol.
BIN
Binary format protocol.
A full description and definition of the listed messages above is provided in the next sections of this
chapter.
6.1
Description of NMEA output messages
The following table is intended as a quick reference to explain the formats used in the tables below.
Format
Description
hhmmss.ss
ddmmyy
ddmm.mmmm
dddmm.mmmm
dd.dddddd
dd'mm'ss"
x
xx
x.x
hh
bbbbbbbb
a
"a"
<CR><LF>
Time: hh hours, mm minutes, ss.ss seconds.
Date: day dd, month mm, year yy.
Latitude: dd degrees, mm.mmmm minutes.
Longitude: ddd degrees, mm.mmmm minutes.
Latitude/longitude: dd.dddddd degrees.
Latitude/longitude: dd - degrees, mm - minutes, ss - seconds
Integer having one digit.
Integer having exactly two digits (using leading zeros).
Number including fraction.
Two-digit hexadecimal number (using uppercase A–F).
Eight-digit binary number.
ASCII text.
ASCII text in quotation marks.
Carriage return and line feed.
Table 64:
Description of NMEA output messages.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 310 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
6.1.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
$GPGGA message
The $GPGGA message includes time, position, GPS quality and number of satellites in use.
Example:
$GPGGA,133726.569,5040.4365,N,01058.5646,E,1,03,8.9,92.9,M,,,,0000*3F
Field
Format
Example
Description
1
$GPGGA
$GPGGA
Start of sentence
2
hhmmss.ss
133726.569
UTC time133726.569
3
ddmm.mmmm
5040.4365
Latitude
4
a
N
Latitude direction (N/S)
5
dddmm.mmmm
01058.5646
Longitude
6
a
E
Longitude direction (W/E)
7
x
1
8
xx
03
GPS fix quality:
0: invalid
1: GPS fix
2: DGPS fix
Number of satellites in use
9
x.x
8.9
10
11
12
13
14
15
16
17
x.x
M
x.x
M
x
xxxx
*hh
<CR><LF>
92.9
M
Table 65:
6.1.2
0000
*3F
Horizontal dilution of precision (relative accuracy of horizontal
position)
Altitude above mean sea level (geoid)
Altitude units (meters)
Height of geoid above earth ellipsoid
Geoid height units (meters)
Time since last DGPS update (seconds)
DGPS reference station ID
Checksum
End of message termination
The GPGGA message data format.
$GPRMC message
The $GPRMC message includes time, date, position, course and speed data.
Example:
$GPRMC,133725.569,A,5040.4365,N,01058.5650,E,0.05,302.98,251004,,*00
Field
Format
Example
Description
1
2
3
4
5
6
7
8
9
10
11
12
13
14
$GPRMC
hhmmss.ss
a
ddmm.mmmm
a
dddmm.mmmm
a
x.x
x.x
ddmmyy
x.x
a
*hh
<CR><LF>
$GPRMC
133725.569
A
5040.4365
N
01058.5650
E
0.05
302.98
251004
Start of sentence
UTC time
Position validity (A: valid, V: invalid)
Latitude
Latitude direction (N/S)
Longitude
Longitude direction (W/E)
Speed (knots)
Heading (degrees)
Date
Magnetic variation (degrees)
Magnetic variation direction (W/E)
Checksum
End of message termination
Table 66:
*00
The GPRMC message data format.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 311 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
6.1.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
$GPGSV message
The $GPGSV includes the number of satellites in view, satellite ID numbers and their evaluation,
azimuth and signal-to-noise ratio.
Example:
$GPGSV,3,1,10,05,79,067,39,30,63,277,35,14,37,269,,09,36,145,*78
$GPGSV,3,2,10,24,28,098,36,06,24,212,,04,24,058,29,17,16,129,*7F
$GPGSV,3,3,10,01,13,328,34,25,05,311,*74
Field
Format
Example
Description
1
2
3
4
5
$GPGSV
x
x
xx
xx
$GPGSV
3
3
10
01
6
7
8
9
10
11
12
13
xx
xxx
xx
14
328
34
25
05
311
*74
Start of sentence
Number of messages (1 to 3)
Message number (1 to 3)
Number of satellites in view (1 to 12)
Satellite PRN number - Range 1 to 51 (SBAS 33...64). The SV Numbers (Fields
'Sv') are in the range of 1 to 32 for GPS satellites, and 33 to 64 for SBAS satellites
(33 = SBAS PRN 120, 34 = SBAS PRN 121, and so on)
Satellite elevation (degrees) (00 to 90), may be null
Satellite azimuth (degrees) (000 to 359), may be null
Satellite signal to noise ratio in dB (00 to 99), may be null
Similar to 5–8 for next satellite, may all be null
Similar to 5–8for next satellite, may all be null
Similar to 5–8 for next satellite, may all be null
Checksum
End of message termination
*hh
<CR><LF>
Table 67:
6.1.4
The GPGSV message data format.
$GPGSA message
The $GPGSA message includes the list of satellites being used.
Example:
$GPGSA,A,2,05,09,04,,,,,,,,,,13.4,8.9,10.0*3D
Field
Format
Example
Description
1
2
$GPGSA
a
$GPGSA
A
3
x
2
4
5
6
7
8
9
xx,xx, . . .
x.x
x.x
x.x
*hh
<CR><LF>
05
13.4
8.9
10.0
*3D
Start of sentence
Operating mode:
M:
Manual, operate in 3-D mode.
A:
Automatically choose 2-D or 3-D mode.
Fix mode:
1:
Fix not available
2:
2-D fix
3:
3-D fix
PRN numbers of satellites in use (unused fields null)
Position dilution of precision
Horizontal dilution of precision
Vertical dilution of precision
Checksum
End of message termination
Table 68:
The GPGSA message data format.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 312 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
6.1.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
$GPVTG message
The $GPVTG message includes course over ground and ground speed.
Example:
$GPVTG,309.62,T, ,M,0.13,N,0.2,K,A*23
Field
Format
Example
Description
1
2
3
4
5
6
7
8
9
$GPVTG
x.x
T
M
x.x
a
x.x
K
a
$GPVTG
309,62
*hh
<CR><LF>
*23
Start of VTG sentence
Course over ground (True) in degrees
Fixed field (True)
Course over ground (magnetic) in degrees, not output
Fixed field: magnetic
Speed over ground - horizontal speed in knots
Fixed field: knots
Speed over ground - horizontal speed in (km/h)
Fixed field: kilometers per hour
Mode Indicator: N=No Fix, A=Autonomous Fix,
E=Estimated/Dead Reckoning Fix
Checksum
End of message termination
10
11
Table 69:
6.1.6
T
M
0,13
N
0,2
K
A
D=Differential
Fix,
The GPVTG message data format.
$GPGLL message
The $GPGLL message includes the latitude, longitude, UTC time of position fix and status.
Example:
$GPGLL,5040.4025,N,01058.8342,E,113704.665,A*32
Field
Format
Example
Description
1
2
3
4
5
6
7
8
9
$GPGLL
ddmm.mmmm
a
dddmm.mmmm
a
hhmmss.sss
a
*hh
<CR><LF>
$GPGLL
5040.4025
N
01058.8342
E
113704.665
A
*32
Start of sentence
Latitude
Latitude direction (N/S)
Longitude
Longitude direction (W/E)
UTC Position
Position validity (A: valid, V: invalid or S*: invalid)
Checksum
End of message termination
Table 70:
The GPGLL message data format.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 313 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
6.1.7
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
$GPIOP message
The $GPIOP message includes the status of the digital/analog inputs and output ports (This message is
intended to be used with FALCOM STEPPIII unit only).
Example:
$GPIOP,00000000,00000000,0.00,0.00,0.00,0.00,0,00,4.00*47
Field
1
2
3
4
5
6
7
8
9
10
11
Format
$GPIOP
bbbbbbbb
bbbbbbbb
x.xx
x.xx
x.xx
x.xx
x.xx
x.xx
*hh
<CR><LF>
Table 71:
6.1.8
Example
$GPIOP
00000000
0
0.00
0.00
0.00
0.00
0.00
4.00
47
Description
Start of sentence
Inputs (IN7-IN0) (1: high, 0: low) - unused
Outputs (OUT3-OUT0): (1: on, 0: off) - unused
Analog input 0 (V) - IN0
Analog input 1 (V) - IN1
Analog input 2 (V) - IN2
Analog input 3 (V) - IN3
Main power voltage (V)
Internal battery voltage (V)
Checksum
End of message termination
The GPIOP message data format
$GPGSM message
The $GPGSM message includes the GSM operator and reception status. Table below shows mode 0
indicating the GSM status.
Example:
$GPGSM,0,1,0,"T-Mobile D",20,5518,4caa*32
Field
Format
Example
Description
1
2
3
$GPGSM
x
b
$GPGSM
0
1
4
x
0
5
6
7
8
9
10
"a"
xx
a
a
*hh
<CR><LF>
"T-Mobile D"
20
5518
4caa
*32
Start of sentence
GSM status mode: 0
Registration state:
0 - not registered, GSM is not currently searching a new operator to
register to.
1 - registered, home network .
2 - not registered, but GSM is currently searching a new operator to
register to.
3 - registration denied.
4 -unknown.
5 - registered, roaming .
GSM activity status:
0 - ready.
1 - unavailable.
2 - unknown.
3 - ringing (the ringer is active) .
4 - call in progress .
Network operator name
GSM field strength (0 to 31) 0: $-$113 dB 31: $-$51 dB
Area code
Cell ID
Checksum
End of message termination
Table 72:
The GPGSM message data format in GMS status mode.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 314 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
6.1.9
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
$GPAREA message
The $GPAREA message includes state of 32 areas. The example below shows that the MAMBO2B6/UXFS device is currently inside the Area0 and outside all other areas.
Example:
$GPAREA,0000 0001*0D
Field
Format
Example
Description
1
2
$GPAREA
xxxx
$GPAREA
0000
3
xxxx
0001
4
<CR><LF>
Start of sentence
Areas 31 to 16 (16 bit -> 2 byte Hexadecimal value)
The hexadecimal value represents the index of the entered area.
Areas 15 to 0 (16 bit -> 2 byte Hexadecimal value)
The hexadecimal value represents the index of the entered area.
End of message termination
Table 73:
6.1.10
The GPGSM message data format in GMS status mode.
$GP3DP message
The $GP3GP message includes the state of the Accelerator Sensor. This message is periodically
transmitted to the USB or Bluetooth port on the MAMBO2-B6/UXFS device (if enabled).
The output values in the protocol GP3DP have been changed. MAMBO2 outputs negative and positive
values. Negative value of the X-axes means it is oriented downwards. Positive means it is upwards. The
range of the outputs for every axes is from -512..+511. The minus and plus of the x, y and z axes is just
to identify the direction of the axes. To set the Bearing and Falling parameters, take the values from the
GP3DP and add to each value 512. For example the value -7 in the $GP3GP corresponds to the value
505 (-7 + 512) in the Motion.Tild/Falling/Bearing configuration parameters.
Example:
$GP3DP,-7,2,96,-9,1,95,-6,5,97,1*2F
Field
1
2
3
4
5
6
7
8
9
10
11
12
Format
$GP3DP
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxx
xxxx
<CR><LF>
Table 74:
Example
$GP3GP
-7
2
96
-9
1
95
-6
5
97
1
2F
Description
Start of sentence
Average x-axis value
Average y-axis value
Average z-axis value
Minimum x-axis value
Minimum y-axis value
Minimum z-axis value
Maximum x-axis value
Maximum y-axis value
Maximum z-axis value
The time on which these values are checked and event is generated.
End of message termination
The GP3GP message data format in 3DP status mode.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 315 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
6.1.11
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
BIN protocol and its format
The binary format sent from the MAMBO2-B6/UXFS device has the following structure.
<DEVICE.PROT.BINARY=test><binary protocol><CRLF>
Text
Format
text
<binary protocol>
24
1305820D23331E34231B068B86270001000000C8
(the value is in hexadecimal)
Example
End Sequence
<CR><LF>
0D0A
Field
Format
Example
Description
1
text
$
2
3
Binary protocol
<CR><LF>
<binary protocol>
0D0A
The specified text by the PROT.BIN.START parameter (see chapter
3.3.9.2, page 223), "$"=default.
See table below.
End of message termination (2 bytes)
Table 75:
The BIN binary data format.
The following table is intended as a quick reference to explain the binary data that can be sent to a
remote server.
<binary protocol>=<DATE><VALID><TIME><LAT><LON><SPEED><COURSE><ALT>1)
Field
1
Name
DATE
Format
dd mm yy
2
VALID
v
3
TIME
v hh mm ms
32
.4
LAT
xxxxxxxx
5
LON
6
7
81)
Bits
16
Bit selection
11…15 = Day (5 bits)
7…10 = Month (4 bits)
0…6 = Year (7 bits)
bit 31 in the TIME field
Range
1..31
1..12
00..99
E.g.
02
06
05
Description
DATE format including the current Day,
Month and year.
(e.g. 02.06.05)
0..1
1
32
31=validity (1bit), see field 2.
22…26= Hours (5 bits)
16…21= minutes (6 bits)
0..15= msec. (16 bits)
0..31=Latitude (32 bits)
0..1
0..23
00..59
0..59999
0..31
1
08
13
9011
506733339*
The current GPS validity bit 31 of the
TIME format (1=valid; 0=invalid), see
field 3.
TIME format including the current GPS
validity (1=valid; 0=invalid), hour,
minutes and miliseconds
xxxxxxxx
32
0.31=Longitude (32 bits)
0..31
109807143*
SPEED
xxxx
16
0..15=Speed (16 bits)
0..15
1
COURSE
xxxx
16
0..15=course (16 bits)
0..15
0
LAT format [+90 to –90] with
resolution of 0.0000001. The value
represents a 2's complement number
of latitude.
LON format [+180 to –180] with
resolution of 0.0000001. The value
represents a 2's complement number
of longitude.
Speed Over Ground in m/sec with
resolution of 0.01
Course Over Ground [0 to 360] with
resolution of 0.01
Altitude
200
ALT
xxxx
16
0.15=Altitude (16 bits)
0..15
Available in the protocol with ID 4000 only.
* The most significant (leftmost) bit indicates the sign of the LAT or LON value:
✔ If the sign bit (leftmost) is 0, then the LAT and LON are positive (e.g. 109807143 =000110100010111000011000100111).
✔ If the sign bit (leftmost) is 1, then the LAT and LON are negative. LAT and LON should be inverted by applying bitwise NOT (e.g. LON =
[fbe81682]  in binary [11111011111010000001011010000010]  bitwise NOT [00000100000101111110100101111101]  add 1
[00000100000101111110100101111110]  convert to decimal [68675966]). To calculate it, invert the 32-bit digits by changing all of
the 1 to 0 and all of the 0 to 1, then add 1 to inverted binary value and convert the result to decimal. Finally, multiply it by 0.0000001
and place a "−" sign in front of it. The LON in decimal results [- 6.8675966°]. The same procedure should be made for negative LAT.
1)
Table 75.1:
The <binary protocol> in bitwise data format.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 316 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
6.1.12
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
FDB protocol and its format
The FDB protocol format sent from the MAMBO2-B6/UXFS device has the following structure.
<DEVICE.PROT.BINARY=text><binaryprotocol><CRLF>
Text
Format
Specified text
<binary protocol>
24
1305820D23331E34231B068B862700010000
(the value is in hexadecimal)
Example
End Sequence
<CR><LF>
0D0A
Field
Format
Example
Description
1
text
$
The text specified within the <"text"> entry on the MSG.Send...
command, (see chapter 3.3.9.2, page 223)
2
3
Binary protocol
<CR><LF>
<binary protocol>
0D0A
See table below.
End of message termination (2 bytes)
Table 76:
The BIN binary data format.
The following table is intended as a quick reference to explain the sent binary data.
<binary protocol>=<Syn><ID><Length><Subprot_0><Subprot_1>..<Subprot_N><CRC>
Field
Syn
ID
Length
<Subprot 0>
<Subprot 1>
....
<Subprot N>
CRC
0xFB
0x01
1 or 2 Bytes
Description
Pre-defined hex value.
Pre-defined identifier for the dynamic binary protocol.
Indicates the length to be read of the followed
<Subprot> entries.
<ID><Length><Data>
See next table below.
Payload checksum
Table 76.1:
The <binary protocol> in bitwise data format.
The following table explains the conversation of the <Subprot X> binary data.
<Subprot 0><Subprot 1>...<Subprot N>
<Subprot X>=<ID><Length><Data>
ID (value)
Length
(Bytes)
Data
Description
0x01
20
<DATE><VALID><TIME><LAT><LON><SPEED><COURSE>
0x02
20
<XYZ><MinXMinYMinZ><MaxXMaxYMaxZ><Abs_Acceleration>
0x03
14
<Mode><State><Distance><Duration><Hight>
0x04
4
<State><Min_range><Max_range><Beat>
0x05
0x06
0x06
0x07
0x08
0x09
0xA
-
Table 76.2:
Shows an RMC protocol in binary data how to convert it see table below.
Shows Motion sensor data in binary how to convert it see table below.
Shows Trip data in binary - how to
convert it see table below.
Shows ANT heartbeat data in binary how to convert it see table below. ANT
options is no longer available
Reserved.
Reserved.
Reserved.
Reserved.
Reserved.
Reserved.
Reserved.
The <binary protocol> in bitwise data format.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 317 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
RMC protocol format = <DATE><VALID><TIME><LAT><LON><SPEED><COURSE>
Name
Format
Bits
Bit selection
Range in
dec.
E.g.
Description
11…15 = Day (5 bits)
7…10 = Month (4 bits)
0…6 = Year (7 bits)
1..31
1..12
00..99
02
06
05
DATE format including the current Day,
Month and year.
(e.g. 02.06.05)
v
bit 31 in the TIME
0..1
1
The current GPS validity bit 31 of the
TIME format (1=valid; 0=invalid), see
field 3.
TIME
v hh mm 32
ms
31=validity(1bit), see VALID.
22…26= Hours (5 bits)
16…21= minutes (6 bits)
0..15= msec. (16 bits)
0..1
0..23
00..59
0..59999
1
08
13
9011
TIME format including the current GPS
validity (1=valid; 0=invalid), hour,
minutes and miliseconds
LAT
xxxxxxxx
32
0..31=Latitude (32 bits)
0..31
506733339*
LAT format [+90 to –90] with
resolution of 0.0000001. The value
represents a 2's complement number of
latitude.
LON
xxxxxxxx
32
0.31=Longitude (32 bits)
0..31
109807143*
LON format [+180 to –180] with
resolution of 0.0000001. The value
represents a 2's complement number of
longitude.
SPEED
xxxx
16
0..15=Speed (16 bits)
0..15
1
Speed Over Ground in m/sec with
resolution of 0.01
COURSE
xxxx
16
0..15=course (16 bits)
0..15
0
Course Over Ground [0 to 360] with
resolution of 0.01
DATE
dd mm yy
VALID
16
Motion sensor data format = <XYZ><MinXMinYMinZ><MaxXMaxYMaxZ><Abs_Acceleration>
Name
Format
Bits
Bit selection
Range in dec.
E.g.
Description
X
Y
Z
xxxx
xxxx
xxxx
16
16
16
32…47 = X
16…31 = Y
0…15 = Z
0..1023
0..1023
0..1023
560
430
200
Show the average values of X-,Y- and Zaxes.
MinX
MinY
MinZ
xxxx
xxxx
xxxx
16
16
16
32…47 = MinX
16…31 = MinY
0…15 = MinZ
0..1023
0..1023
0..1023
560
430
200
Show the minimum values of X-,Y- and
Z-axes.
MaxX
MaxY
MaxZ
xxxx
xxxx
xxxx
16
16
16
32…47 = MaxX
16…31 = MaxY
0…15 = MaxZ
0..1023
0..1023
0..1023
560
430
200
Show the minimum values of X-,Y- and
Z-axes.
Abs_Accel
eration
xxxx
16
0…15
0..1023
100
Shows the current acceleration value.
Trip data format = <Mode><State><Distance><Duration><Hight>
Name
Format
Bits
Bit selection
Range in dec.
E.g.
0
Description
Mode
xx
8
0..7
0
0 = normal; 1,2,3 = reserved
State
xx
8
0..7
0..FF
FF = none;
0 = stop;
1 = start;
2 = active;
3 = Tag/marker;
4 = resum;
Distance
xxxxxxxx
32
0..31
0..FFFFFFFF
Shows the distance in meter.
Duration
xxxxxxxx
32
0..31
0..FFFFFFFF
Shows the duration in seconds.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 318 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Hight
xxxxxxxx
32
81..113
- FIRMWARE REVISION 2.8.0 -
0..FFFFFFFF
DOCUMENT VERSION 3.7.0
Shows the hight in meter.
ANT heartbeat data format = <State><Min_range><Max_range><Beat>
Name
Format
Bits
Bit selection
Range in dec.
E.g.
0
Description
State
xx
8
0..7
0..6
Min.range
xx
8
0..7
0..FF
Shows the minimum allowed heartbeat
value.
Max.range
xxxxxxxx
32
0..31
0..FFFFFFFF
Shows the maximum allowed heartbeat
value.
Beats
xxxxxxxx
32
0..31
0..FFFFFFFF
Shows the current heartbeat value.
Table 76.3:
0 = Channel off;
1 = Not connected;
2 = Searching;
3 = Timeout;
4 = Invalid data;
5 =Valid data;
6 = ANT error (not defined);
The <binary protocol> in bitwise data format.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 319 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
7 APPENDIX
7.1
How to update a new firmware into the MAMBO2-B6/UXFS
Please refer to the application note "AppNoteMAMBO2-B6/UXFSSoftwareUpdate.pdf".
7.2
Supported dynamic entries
The following table shows the dynamic entries that can be attached to the user specified text using the
PFAL command $PFAL,MSG.Send.<channel>,0,"&(Entry)".
For example: $PFAL,MSG.Send.TCP,0,"&(Speed)"
Entry
Meaning (for more details to each entry, refer also to the corresponding PFAL command respectively)
SYS
SecurityLock
DeviceName
VAccu
PVbat
TXT_ID:<id>
Timer<index>
Trigger<index>
Counter<index>
SerialData
StartupReason
Used to report whether the MAMBO2-B6/UXFS device is locked.
1
locked
0
unlocked
Used to report the name of the device specified in the DEVICE.NAME configuration parameter.
Used to report the internal battery voltage. Note that, the battery voltage will be available approx. 6-10
seconds after the system startup. The unit of the returned value is Volt (e.g. 3.982).
Used to report the battery charge level in percent (%). e.g. 80%
Reads and reports the text assigned to the specified ID in the language resource (e.g. TXT_ID:5 reports the
text "Batterie-Info"). The specified ID depends on the selected language. For more details, see chapter
Language Resources.
Used to request the state of the selected Timer. <index> determines the index of the timer to be requested.
<index> ranges from 0 through 19.
Used to request the state of the selected Trigger. <index> determines the index of the trigger to be
requested. ranges from 0 through 19
Used to request the state of the selected Counter. <index> determines the index of the counter to be
requested. ranges from 0 through 19
Used to report the last string received from the serial interface, which is terminated by a Carriage Return and
Line Feed. Serial interface needs to be configured as data and <event_mode> has to be set to 1. i.e.
$PFAL,Cnf.Set,DEVICE.COMM.SERIAL=data=0,1,F or $PFAL,MSG.Mode.Serial=60,E
Used to report in which way system is last started. Following strings can be reported:
Start
Normal boot.
Reset
When it reboots.
Motion Woken up from the MOTION-sleep.
Ign
Woken up from IGN-sleep.
Ring
Woken up from Ring-sleep.
Time
Woken up from Timer-sleep.
GPS
Time
Date
SysTime
SysDate
LocalTime
LocalDate
Lat.n
Lon.n
Used to report the current GPS time (e.g. 14:35:16) . The GPS time is expressed in Coordinated Universal Time
(UTC). If no GPS fix available, the internal time will be used. The internal time is the time at which the system
began running or the time running from last known position, if the last valid position is already saved and
loaded. The GPS time may differ from the local time.
Used to report the current GPS date, in dd.mm.yyyy (e.g. 10.01.2006). If no GPS fix available, the internal date
will be used. The GPS date may differ from the local date (see also Time above)
Used to request the current internal time of the device, in format "hh:mm:ss". The internal time is the time at
which the system began running (e.g. 00:35:16). The time value will be set to 0 each approx. 50 days.
Used to request the current internal date of the device in format "dd.mm.yyyy". The internal date is the date
at which the system began running (e.g. 01.01.1980). The time value will be set to 0 each approx. 50 days.
Used to request the current local time of the device, in format "hh:mm:ss" (e.g. 14:35:16). The local time is
Time zone dependant.
Used to request the current local date of the device in format "dd.mm.yyyy" (e.g. 06.06.2010). The local date
is Time zone dependant.
Used to report the current GPS latitude value in nautical coordinates.
Format: is e.g. 50N40'23" for north, 50°40‘23".
Used to report the current GPS longitude value in nautical coordinates.
Format: is e.g. 010E58'50 for east, 10°58‘50".
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 320 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Entry
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Meaning (for more details to each entry, refer also to the corresponding PFAL command respectively)
Lat
Lon
Used to report the current GPS latitude value in decimal degrees with an accuracy of 7 digits after the decimal
point (e.g. 50.6733478).
Used to report the current GPS longitude value in decimal degrees with an accuracy of 7 digits after the
decimal point (e.g. 10.9806871).
Alt
Used to report the current GPS altitude value in meters (e.g. 450.5).
Speed
Used to report the current GPS velocity value in meters/second (e.g. 30).
Speed.cmps
Used to report the current GPS velocity value in the format <SpeedInMPS>.<SpeedInCPS> (e.g. 05.50)
<SpeedInMPS>
Value in meter/second.
<SpeedInCPS>
Value in centimeter/second.
Course
DOP
SatsUsed
Fix
NavDist
PosDist<idx>
GFName<ID>
GF<ID>
AreaName<ID>
Area<ID>
LastGF
LastGFName
LastGFState
LastArea
LastAreaName
LastAreaState
LastTime
LastDate
LastLat
LastLon
LastAlt
Wpoint
Trip
TDistance<id>
TDuration<id>
Used to report the current course over ground, indicating the current direction of the MAMBO2-B6/UXFS
device (e.g. 30.54).
Used to report the current DOP value (GPS position accuracy error) of the device (e.g. 4.05).
Used to report the number of satellites that currently are in use (e.g. 7).
Used to report whether or not the MAMBO2-B6/UXFS device has already got a valid GPS-Fix. If MAMBO2B6/UXFS has a valid GPS-Fix it returns 1, otherwise 0.
Used to report the actual distance, in meters, from the last set point (e.g. 2390).
Used to report the total distance, in meters, to the specified point (e.g. 2300).
<idx> : The index of the saved position (0 .. 4).
Used to report the name of the specified Geofence (e.g. Playground). <ID> ranges from 0 through 99 .
Used to report the current status of the specified Geofence ID whether the device's position is inside or
outside the pre-configured geo-fence boundary.
0
inside the Ge-fence index
1
left the Ge-fence index
<ID> ranges from 0 through 99 .
Used to report the name of the specified Geofence area (e.g. Langewiesen). <ID> ranges from 0 through 31 .
Used to report the current state of the specified area ID whether the device's position is inside or outside the
pre-configured Area boundary.
0
inside the Area index
1
left the Area index
<ID> ranges from 0 through 31 .
Used to report the identification number <id> of last entered or left Geo-fence (e.g. 10). "none" is reported if
the device never entered or left any Geo-fence.
Used to report the name of the last entered or left Geo-fence (e.g. Playground). "none" is reported if the
device never entered or left any Geo-fence.
Used to report the status of the setup geofences whether any one has been entered or left (1= Yes; 0= No).
"?" is reported if the device never entered or left any Geo-fence.
Used to report the identification number <id> of the last entered or left area. "none" is reported if the device
never entered or left any Area.
Used to report the name of the last entered or left area (e.g. Langewiesen). "none" is reported if the device
never entered or left any Area.
Used to report the status of the setup areas whether any one has been entered or left (1= Yes; 0= No). "?" is
reported if the device never entered or left any area.
Used to report the last known time (e.g. 09:45:33). The time can be the same one as the GPS time, if the
device has a valid GPS Fix.
Used to report the last date (e.g. 10.01.2000). The date can be the same one as the GPS date, if the device has
a valid GPS Fix.
Used to report the last valid latitude (e.g. 10.9806871).
Used to report the last valid longitude (e.g. 50.6733478).
Used to report the last valid altitude (e.g. 450).
Used to report the name of the last reached Waypoint (e.g. School) .
Used to report the total distance traveled, in meter, during the trip <id> (e.g. 1.5). Only the last 4 Trips, in the
range from 1 through 4, can be stored on the MAMAO2 and requested by this dynamic entry. To get them
shown on the MAMBO2-B6/UXFS display, navigate to the Trip symbol and then select "History".
Used to report the total duration, in format hh:mm:ss, of the trip <id> (e.g.01:30:44). Only the last 4 Trips, in
the range from 1 through 4, can be stored on the MAMAO2 and requested by this dynamic entry. To get them
shown on the MAMBO2-B6/UXFS display, navigate to the Trip symbol and then select "History".
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 321 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Entry
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Meaning (for more details to each entry, refer also to the corresponding PFAL command respectively)
TSpeed<id>
THeight<id>
TDate<id>
TDepth<id>
GSM
IMEI
SIMID
SIMCCID
OperatorID
Operator
CallerNumber
OwnNumber
Fieldstrength
CID
LAC
Used to report the maximum speed reached, in kilometer per hour, during the trip <id> (e.g. 120.4). Only the
last 4 Trips, in the range from 1 through 4, can be stored on the MAMAO2 and requested by this dynamic
entry. To get them shown on the MAMBO2-B6/UXFS display, navigate to the Trip symbol and then select
"History".
Used to report the total height, in meter, during the trip <id> (e.g. 500). Only the last 4 Trips, in the range
from 1 through 4, can be stored on the MAMAO2 and requested by this dynamic entry. To get them shown on
the MAMBO2-B6/UXFS display, navigate to the Trip symbol and then select "History".
Used to report the start date and time, in format dd.mm.yy hh:mm, of the trip <id> (06.06.10 14:45). Only the
last 4 Trips, in the range from 1 through 4, can be stored on the MAMAO2 and requested by this dynamic
entry. To get them shown on the MAMBO2-B6/UXFS display, navigate to the Trip symbol and then select
"History".
Used to report the ascend and descend, in meter, anlong the trip <id>. Only the last 4 Trips, in the range from
1 through 4, can be stored on the MAMAO2 and requested by this dynamic entry. To get them shown on the
MAMBO2-B6/UXFS display, navigate to the Trip symbol and then select "History".
Used to report the current IMEI number of the device (e.g. 354234982746251).
Used to report the mobile subscriber ID of the used SIM (e.g. 262011644210351). The PIN must be entered
before requesting the ID.
Used to report the subscriber identity module or subscriber identification module.
Used to report the currently used GSM operator ID (e.g. 26203).
Used to report the current GSM operator name used by the device (e.g. E-Plus).
Used to report the phone number of the currently incoming call. The incoming call may be established, but
after it is finished, no caller number will be transmitted (an error will be delivered instead) (e.g.
+491030223023).
Used to report the phone number of the SIM card inserted in the MAMBO2-B6/UXFS device.
Used to report the field strength of the currently used GSM cell (e.g. 28).
Used to report the currently used GSM cell ID e.g. 6864 (for Location-based services - If the MAMBO2B6/UXFS device was unable to calculate the coordinates and the last valid position is not available, then you
can use the Cell ID information to determine the location of the device).
Used to report the currently used GSM local area code (e.g. 02CA).
Used to report the state of incoming calls.
The following possible values may be retrieved:
Call
PHONE<id>
SMSNumber
SMSText
GPRSOnline
- idle
- incoming voice call (ring:3)
- incoming data call (ring:1)
- inside incoming voice call
- establish data call
- inside data call
- outgoing ring
- inside outgoing. voice call
Used to report the phone number from the phonebook list. <id> specifies the entry ID to look up.
Used to report the phone number of the last incoming SMS (e.g. +491777834555). No value will be shown if
there was no SMS received after the system has been started.
Used to request the text of last incoming SMS (e.g. „Hello World!“). No value will be shown if there was no
SMS received after the system has been started.
Used to report the online state of the GPRS.
0
Detached from GPRS network
1
Attached to the GPRS network.
GPRSTraffic
Used to report the complete GPRS traffic information. For example: (if GPRS is deactivated).
$traffic after 00.00.0,00:00:00 :0 kB (0 Bytes) I:0 kB (0 Bytes) O:0 kB (0 Bytes)
GPRS
Used to report the current state of the GPRS connection.
disabled
GPRS is disconnected from or deactivated.
connected
GPRS is connected to.
connecting
GPRS is trying to connect to.
disconnecting
GPRS is trying to disconnect from.
TCP
TCPClientOnline
Used to report the online status of the TCP.
0
Detached from GPRS network
1
Attached to the GPRS network.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 322 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Entry
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Meaning (for more details to each entry, refer also to the corresponding PFAL command respectively)
TCPClient
TCPText
IEEE
IDMac
IDName
IDQL
IEEEMAC
ANT
Hbeat
Cadence
BikeSpeed
BikeDistance
ANTRaw
Used to report the current status of the TCP connection.
disabled
TCP is disconnected from or deactivated.
connected
TCP is connected to.
connecting
TCP is trying to connect to.
disconnecting
TCP is trying to disconnect from.
Used to report the last received TCP packet (e.g. „Hello World!“).
Requires IEEE connectivity (optional for MAMBO2-UXFS only)
Used to report the last received MAC address from an Indoor device (e.g. 0017920010002BB0).
Used to report the last received name, max 255 bytes, from the Indoor device (e.g. Meeting Raum).
Used to report the last received field strength (max. 255) of the connected Indoor device (e.g. 120)
Used to report the MAC address of the last spoken IEEE device to MAMBO2-B6/UXFS (e.g.
0017920010002BB0).
Requires ANT+Sport connectivity (ANT options is no longer available) to support wireless heartrate monitor,
cadence/speed sensor
Used to report the heartbeats measurements, in bpm (beats per minute), from the chest strap transmitter
(e.g. 120).
Used to report the pedaling cadence measurements, in rpm (revolutions per minute), from a cadence sensor
transmitter (e.g. 220).
Used to report the speed measurements, in cm/s (centimeter per second), from a speed sensor transmitter
(e.g. 35).
Used to report the total distance, in centimeter, traveled by the bycicle (e.g. 1500).
Used to report the information in raw data supplied by a sensor with ANT+Sport connectivity that could not
be processed by the MAMBO2-B6/UXFS.
Phone
Phone<index>
Used to report the phone number from the phonebook. <index> <id> defines the position of the phone entry
in the phone book ranging from 1 through the Max. allowed phone entries in the DISP.PHONE<index>.
Table 77:
Supported dynamic entries.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 323 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
7.3
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Language Resources
The following table shows the contents of the resource files containing the translated strings to display in
the user interface for each language supported by the MAMBO2-B6/UXFS device. These strings can be
reported by entering the corresponding ID into the dynamic entry &(TXT_ID:<ID>). For example, if you want
to report via TCP the test assigned to the ID=7, then enter the
Category
ID
English
Français
Español
Deutsch
Portuguese
Русский
Norsk
Svenska
Vlaams
Italiano
saver
199
MAMBO2
-B6/UXFS
MAMBO2
-B6/UXFS
MAMBO2
-B6/UXFS
MAMBO2
-B6/UXFS
MAMBO2B6/UXFS
MAMBO2B6/UXFS
MAMBO2
-B6/UXFS
MAMBO2B6/UXFS
MAMBO
2B6/UXFS
MAMBO2B6/UXFS
info
1
Phone
Number
Numéro
GSM
Phone
Number
Mobilfun
knummer
Номер
телефона
Telefon
nummer
Phone
Number
Phone
Number
Numero
telefono
2
Device
Name/IM
EI
Nom
IMEI
/
Device
Name/IM
EI
Geräte
Name/IM
EI
Имя
прибора/
IMEI
Enhets
versjon
Device
Name/
IMEI
Device
Name/
IMEI
Nome
dispositivo/
IMEI
3
Firmware
Firmware
Firmware
Firmware
Фирмвер
Firmware
Firmware
Firmwar
e
Firmware
4
Informati
on
Informati
on
Informati
on
Informati
onen
Информац
ия
Informati
on
Informatio
n
Informati
on
Informazioni
5
BatteryInfo
Info
batterie
Info
Bateria
BatterieInfo
InfoBateria
Батареяинфо
Batteriinfo
Batteriinfo
Batteriinfo
Info-Batteria
6
State
Statut
Estado
Status
Estado
Статус
Status
Status
Status
Stato
7
charging
En charge
cargando
laden
Carregand
o
зарядка
lader
laddar
laddar
In carica
8
dischargi
ng
En
décharge
descarga
entladen
Descarga
разрядка
i bruk
Laddar ur
Laddar
ur
In uso
9
Level
Niveau
Nivel
Füllstand
Nível
Уровень
Nivå
Nivå
Nivå
Livello
10
Battery
Batterie
Bateria
Batterie
Bateria
Батарея
Batteri
Batteri
Batteri
Batteria
11
Powersav
e
Mode éco
Bajo
consumo
Energie
Spa.
Baixo
Consumo
Экономия
энергии
Strømspa
ring
Sparläge
ström
Sparläge
ström
Basso
consumo
12
on
on
on
An
on
ВКЛ
on
on
on
on
13
off
off
off
Aus
off
ВЫКЛ
off
off
off
off
14
Alert!
Alerte!
Alarm!
Аларм!
Allarme!
15
Attention
!
Attention
!
Achtung!
Внимание!
Attenzione!
16
No SIMcard\nOnl
y
emergenc
y\ncall
function.
Carte SIM
absente\
nAppels
d'urgence
\nunique
ment.
Keine
SIMKarte\nN
ur
Notruf\n
möglich
Нет
SIM
карты\nТо
лько
экстренны
й\nвызов
No
SIMcard\nSolo
Chiamate\nd'
emergenza.
17
deactivat
ed
désactivé
e
deaktivier
t
деактивир
ован
Disattivato
18
module
Module
Modul
Модуль
modulo
20
GSM-Info
Info GSM
Info GSM
GSM-Info
GSM-Info
GSM-инфо
GSM-Info
GSM-Info
GSMInfo
GSM-Info
21
Provider
Opérateu
r
Operador
Netz
Provedor
Провайде
р
Nett
Nät
Provider
Operatore
22
Service
Service
Servicio
Type
Serviço
Сервис
Type
Tjänst
Service
Servizio
23
Signal
Signal
Señal
Signal
Sinal
Сигнал
Signal
Signal
Signal
Segnale
24
Cell-ID
Cell-ID
Cell-ID
Cell-ID
ID Célula
Cell-ID
Cell-ID
Cell-ID
Cell-ID
Cell-ID
Battery
GSM
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 324 of 352
di
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Category
GPS
SIM PIN
Shutdow
n
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
ID
English
Français
Español
Deutsch
Portuguese
Русский
Norsk
Svenska
Vlaams
Italiano
25
GPRS
GPRS
GPRS
GPRS
GPRS
GPRS
GPRS
GPRS
GPRS
GPRS
26
Server
Serveur
Servidor
Server
Servidor
Сервер
Server
Server
Server
Server
27
none
-
Ninguno
Kein Netz
Nenhum
нет
Ingen
nett
Inget nät
None
Nessuno
28
allow
Autoriser
permitir
erlaubt
permitir
разрешен
tillat
tillåt
allow
Autorizzare
29
forbidden
Interdire
denegado
verboten
proibido
запрещен
forby
ogiltig
forbidde
n
Negato
30
home
Accueil
nacional
home
Início
домашний
hjem
hem
home
Inizio
31
no
network
Pas
de
réseau
sin red
kein Netz
sem rede
нет сети
nett ikke
tilgj.
Inget nät
no
network
Rete
non
presente
32
roaming
Roaming
roaming
roaming
roaming
Роуминг
roaming
roaming
roaming
roaming
33
searching
Recherch
e…
buscar
suche
Procurar
поиск
søk
sök
search
In ricerca...
34
online
Connecté
conectad
o
verbunde
n
ligado
онлайн
tilkoblet
påslagen
online
Connesso
35
offline
Déconnec
té
desconec
tado
nicht ver.
desligado
офлайн
frakoblet
avslagen
offline
Non connesso
40
GPS-Info
Info GPS
Info GPS
GPS-Info
GPS-инфо
GPS-Info
GPS-Info
GPS-Info
GPS-Info
41
Satellites
Satellites
Satelites
Satelliten
Спутники
Satelitter
Sateliter
Sateliter
Satelliti
42
Signal
Signal
Posicion
Signal
Сигнал
Signal
Signal
Signal
Segnale
43
valid
Valide
valida
gültig
валидный
sterkt
Stark
Stark
valido
44
invalid
Invalide
no valida
ungültig
невалидн
ый
svakt
svag
svag
non valido
45
Lon.
Long.
Longitud
Länge
Долгота
L-grad
Longitud
Longitud
Long.
46
Lat.
Lat.
Latitud
Breite
Широта
B-grad
Latitud
Latitud
Lat.
47
Height
Alt.
Altitud
Höhe
Высота
Høyde
Höjd
Höjd
Alt.
48
Accuracy
Précision
Genauigk
eit
Точность
60
PUK Code
Code PUK
PUK Code
PUK Code
PUK код
PUK Code
PUK Code
PUK
Code
Codice PUK
61
PIN:PUK
PIN:PUK
PIN:PUK
PIN:PUK
PIN:PUK
PIN:PUK
PIN:PUK
PIN:PUK
PIN:PUK
62
Wrong
Erreur
Wrong
Falsch
Неверный
Wrong
Wrong
Wrong
Errato
63
SIM PIN
Code PIN
SIM PIN
SIM PIN
SIM PIN
SIM PIN
SIM PIN
SIM PIN
Codice PIN
64
only %d
attempt(s
)
Plus que
%d essais
only %d
attempts
noch %d
Versuch(e
)
только %d
попытки
only %d
attempts
only
%d
attempts
only %d
attempts
Ancora
tentativi
65
PUK
required
Code PUK
requis
PUK
required
PUK
erforderli
ch
Требуется
PUK
PUK
required
PUK
required
PUK
required
PUK richiesto
66
confirme
d
bestätigt
Подтверж
ден
70
Turn off
Eteindre?
Apagar?
Ausschalt
en
Desligar?
Выключит
ь
Slå av
Stäng av
uitschak
elen
Spegnere?
71
Please
wait
Veuillez
patienter
Espere
Bitte
warten
Espere
por favor
Подожди
те
Var vänlig
vänta
Var
vänlig
vänta
Gelieve
wachten
72
Shutdow
n
Veille
Выключит
ь
Shutdow
n
Shutdown
Shutdow
n
Spegnere
Ausschalt
en
Precisione
%d
Confermato
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 325 of 352
te
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Deutsch
Portuguese
Русский
Norsk
DOCUMENT VERSION 3.7.0
Category
ID
English
Français
blanko
75
Empty
Menu
Menu
vide
Leeres
Menü
Пустое
меню
Menu vuoto
Slider
76
Sliding
Mode
Mode de
défilemen
t
SlidingModus
Режим
Sliding
Modalità
slide
Ring
tone
80
Tone off
Aucune
sonnerie
Ton aus
Тон выкл.
Nessuna
suoneria
81
Tone 1
Sonnerie
1
Ton 1
Тон 1
Suoneria 1
82
Tone 2
Sonnerie
2
Ton 2
Тон 2
Suoneria 2
83
Tone 3
Sonnerie
3
Ton 3
Тон 3
Suoneria 3
84
Tone 4
Sonnerie
4
Ton 4
Тон 4
Suoneria 4
85
Tone 5
Sonnerie
5
Ton 5
Тон 5
Suoneria 5
86
Tone 6
Sonnerie
6
Ton 6
Тон 6
Suoneria 6
87
Tone 7
Sonnerie
7
Ton 7
Тон 7
Suoneria 7
88
Tone 8
Sonnerie
8
Ton 8
Тон 8
Suoneria 8
89
Tone 9
Sonnerie
9
Ton 9
Тон 9
Suoneria 9
90
Tone 10
Sonnerie
10
Ton 10
Тон 10
Suoneria 10
91
Tone 11
Sonnerie
11
Ton 11
Тон 11
Suoneria 11
92
Tone 12
Sonnerie
12
Ton 12
Тон 12
Suoneria 12
93
Tone 13
Sonnerie
13
Ton 13
Тон 13
Suoneria 13
94
Tone 14
Sonnerie
14
Ton 14
Тон 14
Suoneria 14
95
Tone 15
Sonnerie
15
Ton 15
Тон 15
Suoneria 15
96
Tone 16
Sonnerie
16
Ton 16
Тон 16
Suoneria 16
97
Tone 17
Sonnerie
17
Ton 17
Тон 17
Suoneria 17
98
Tone 18
Sonnerie
18
Ton 18
Тон 18
Suoneria 18
99
Tone 19
Sonnerie
19
Ton 19
Тон 19
Suoneria 19
100
Settings
Paramètr
es
Einstellun
gen
Настройки
Impostazioni
101
Modules
Modules
Module
Модули
Moduli
102
ANT
pairing
Appairag
e ANT
ANTSensoren
АNT
сенсор
Interfaccia
ANT
103
Telephon
Téléphon
Telefon
Телефон
Telefono
Setting
Español
- FIRMWARE REVISION 2.8.0 -
Svenska
Vlaams
Italiano
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 326 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Category
ID
Español
Deutsch
- FIRMWARE REVISION 2.8.0 -
Portuguese
Русский
Norsk
DOCUMENT VERSION 3.7.0
English
Français
Svenska
Vlaams
Italiano
e
e
104
other
Autre
sonstige
другие
Altro
105
GSM
GSM
GSM
GSM
GSM
106
GPS
GPS
GPS
GPS
GPS
107
ANT sport
ANT
ANT
Sport
ANT спорт
ANT Sport
108
IEEE
IEEE
IEEE
IEEE
IEEE
109
Bluetooth
Bluetooth
Bluetooth
Bluetooth
Bluetooth
110
reconnect
Reconnec
tion
neu
verbinden
Подсоеди
нить
Riconnession
e
111
Heart
Cœur
Herz
Сердце
Cuore
112
Stepp
Stepp
Schritt
Шаг
Passi
113
Cadence
Cadence
Trittfrequ
enz
Частота
шагов
Cadenza
114
Speed
Vitesse
Geschwin
digkeit
Скорость
Velocità
115
Ring tone
vol.
Volume
sonnerie
Ruftonlau
tstärke
Громкость
тона
Volume
suoneria
116
Ring tone
Sonnerie
Rufton
Тон
Suoneria
117
Handsfree
Mainslibres
Freisprec
hen
Громкогов
оритель
Viva-voce
118
Key tone
Bips
Touches
Tastentön
e
Тоны
клавишей
Suono tasti
119
Off
Off
aus
Выкл.
off
120
Tone
Sonnerie
Ton
Тон
Suoneria
121
Tone+vibr
ation
Sonnerie+
vibreur
Ton+Vibr
ation
Тон+вибра
ция
Suoneria+vibr
azione
122
Vibration
Vibreur
Vibration
Вибрация
Vibrazione
123
Tracking
Tracking
Tracking
Режим
поиска
Tracciamento
124
Geofence
Geofenci
ng
Geofence
ГеоФенс
Geofence
125
Motion
alarm
Alarme
sur
mouveme
nt
MotionAlarm
Аларм
движения
Allarme
su
movimento
126
Fall alarm
Alarme
sur chute
Sturzalar
m
Аларм
падения
Allarme
caduta
127
Switch %s
off?
Eteindre
? %s
%s
ausschalt
en
%s
выключить
Spegnere %s?
128
Display
Affichage
Anzeige
Дисплей
Display
129
Screensav
er
Ecran de
veille
Bildschir
mschoner
Скринсейв
ер
Screensaver
130
Trip
sliding
Défileme
nt trajets
Sliding
bei Trip
Маршрут.
Sliding
Slide percorso
131
off
off
aus
Выкл.
off
132
Clock
Horloge
Uhrzeit
Время
Orologio
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 327 of 352
su
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Category
View
Keylock
View
speed
View
height
Español
Deutsch
- FIRMWARE REVISION 2.8.0 -
Portuguese
Русский
Norsk
DOCUMENT VERSION 3.7.0
ID
English
Français
Svenska
Vlaams
133
blank
Vide
Anzeige
aus
Дисплей
выкл.
Schermo nero
134
sliding
défilemen
t
Sliding
Sliding
Slide
135
SMS tone
Sonnerie
SMS
SMS-Ton
Тон
SMS
136
Message
tone
Sonnerie
message
Nachricht
enton
Тон
про
сообщени
и
Suoneria
messaggi
137
Saver
timeout
Délai de
veille
Timeout
Тайм-аут
Screensaver
dopo
138
Auto
keylock
Blocage
touches
auto.
Tastenspe
rre
авт. блок.
Auto-blocco
tasti
139
Language
Langage
Sprache
Язык
Lingua
148
Speaker
volume
Vol. H.P.
Lautstärk
e
Громкость
Vol.
altoparlante
149
Setting
Paramètr
es
Einstellun
g
Настройки
Impostazioni
150
Keylock
Verrouilla
ge
Tastenspe
rre
Блокировк
а
Blocco tasti
151
activate?
activer ?
aktivieren
?
активиров
ать?
Attivare?
152
deactivat
e?
désactive
r?
deaktivier
en?
деактивир
овать?
Disattivare?
153
Press left
button
Appui sur
bouton
gauche
linke
Taste
drücken
нажать на
левую
клавишу
Premere
tasto sx
154
>
2
seconds
> à 2 sec.
>2
Sekunden
>2-х
секунд
> 2 sec.
155
activated
activé
aktiviert
активиров
ана
Attivato
156
deactivat
ed
désactivé
deaktivier
t
деактивир
ована
Disattivato
200
Speed
Vitesse
Geschwin
digkeit
Скорость
Velocità
201
Trip
speed
Vitesse
du trajet
TripGeschw.
Скорость
маршрута
Velocità del
percorso
202
Max.
speed
Vitesse
max.
max.
Geschw.
макс.
скорость
Max velocità
203
Avg.
speed
Vitesse
moy.
mittl.
Geschw.
средн.
скорость
Velocità
media
250
Elevation
Altitude
Höhe
Высота
Altitudine
251
Trip
altitudes
Altitude
du trajet
TripHöhen
Высота
маршрута
Dislivello
252
Max.
altitude
Altitude
max.
max.
Höhe
макс.
высота
Max. altitud.
253
Avg.
altitude
Altitude
moy.
mittl.
Höhe
средн.
высота
Altitud.
Media
254
Source
Source
Qelle
Ресурс
Sorgente
при
Italiano
Suoneria SMS
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 328 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Category
Trip
distance
/duratio
n
Waypoin
ts
Heart
Message
Español
Deutsch
- FIRMWARE REVISION 2.8.0 -
Portuguese
Русский
Norsk
DOCUMENT VERSION 3.7.0
ID
English
Français
Svenska
Vlaams
Italiano
255
set
normal
ICAO
ICAO
standard
CICAOStandard
Стандарт
CICAO
ICAO normale
256
Altitude
from
Server
Altitude
du
serveur
Höhe
vom
Server
Высота из
сервера
Altitudine dal
server
257
adjust
manually
Ajuster
manuelle
ment
manuell
anpassen
настроить
вручную
Imposta
manualm.
258
GPS
GPS
GPS
GPS
GPS
259
barometri
c
Baromètr
e
barometri
sch
барометри
ческая
Barometro
260
GPS/baro
metric
GPS/Baro
metre
GPS/baro
metrisch
GPS/баро
метр.
GPS/Baromet
ro
290
Trip
distance
Distance
du trajet
TripDistanz
Расстояни
е
маршрута
Lunghezza
tragitto
291
Duration
Durée
Dauer
Продолжи
тельность
Durata
292
Distance
Distance
Distanz
Расстояни
е
Distanza
320
Waypoint
s
Etapes
Wegpunk
te
Точки
маршрута
Tappe
459
No Image
Pas
d'image
kein Bild
Без
иконки
Nessuna
immagine
500
Heart
Beat
Battemen
ts Cœur
Herzschla
g
Биение
сердца
Battito
cardiaco
501
select
range
Paramètr
es
Bereich
auswähle
n
Выбрать
диапазон
Selez.
Intervallo
502
start
rating
Commenc
er
la
mesure
Messung
starten
Начать
измерени
е
Inizio misura
550
Messages
Messages
Nachricht
en
Сообщени
я
Messaggi
551
Show
Afficher
Anzeigen
Показать
Mostra
552
Answer
Répondre
Antworte
n
Ответить
Rispondi
553
Delete
Effacer
Löschen
Стереть
Elimina
554
Delete all
Effacer
tout
alle
löschen
Все
стереть
Elimina tutti
555
Send
Envoyer
senden
послать
Invia
556
Deleted
Effacé
gelöscht
стерто
Cancellato
557
Sent
Envoyé
gesendet
послано
Inviato
558
Error
Erreur
Fehler
Ошибка
Errore
559
From
De
von
от
Da
560
Message
Message
Nachricht
:
Сообщени
е:
Messaggio
561
Successful
Réussi
erfolgreic
h
успешно
riuscito
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 329 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
459
No Image
Pas
d'image
kein Bild
Без
иконки
Nessuna
immagine
562
To
A
An
к:
A
Lamp
600
Light
Function
Fonction
Eclairage
Licht
Освещени
е
Torcia
Dial
650
dial pad
Clavier
tél.
Wähltast
en
Клавишна
я панель
Tastierino
Date
700
Date
Date
Datum
Дата
Data
701
Time
Heure
Uhrzeit
Время
Ora
702
Date
Date
Datum
Дата
Data
750
Emergenc
y
Urgence
Notfall
Экстр.
вызов
Emergenza
751
SOS
Alarm
Alarme
SOS
SOS
SOS
Allarme SOS
752
Fall Alarm
Alarme
PTI
Sturzerke
nnung
Опознани
е падения
Allarme
caduta
753
activate?
activer ?
aktivieren
?
активиров
ать?
Attivare?
800
Balance
Balance
Guthaben
Кредит
Credito
801
Request?
Récupére
r?
abfragen?
запросить
?
Richiedere?
802
Please
wait:Requ
esting..
Attendre
SVP …
Anfrage
läuft...
Запрос
произведе
н...
Attendere:
richiesta
in
corso..
803
GSM not
ready
GSM
inactif
GSM
nicht
bereit
GSM
готов
GSM
attivo
Falling
810
Fall Alarm
Alarme
PTI
Sturzalar
m
Аларм
падения
Allarme
caduta
Tilt
820
Tilt Alarm
Alarme
TILT
Kippalar
m
Аларм при
наклоне
Allarme
inclinazione
Emergen
cy
Balance
Table 78:
не
Language.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 330 of 352
non
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
7.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Supported protocols when sending messages via SMS, CSD or TCP, USB,
Bluetooth and SD-Card
Following are listed the protocols in the hexadecimal format that can be attached to message being set
using
the
PFAL-Command
$PFAL,MSG.Send......
or
$PFAL,GSM.SMS.Send,...
or
$PFAL,GSM.SMS.SendRaw,...
or $PFAL,GSM.DataCall.Send,..... or $PFAL,TCP.Client.Send,... or
$PFAL,TCP.Storage.AddProtocol,... or $PFAL,TCP.Storage.AddRecord,..... or $PFAL,TCP.SMTP.Send,...
or $PFAL,TCP.SMTP.SendRaw,... . The value to be assigned in the <protocols> parameter in the above
PFAL-Commands must be in hexadecimal format without leading "0x0". Formatting of the text to be
transmitted is affected by the user settings made in the configuration parameter
DEVICE.PFAL.SEND.FORMAT. In the chapter "3.3.1.18" you will find an example of how the text is
formatted when the user has made changes in the DEVICE.PFAL.SEND.FORMAT configuration parameter.
For more details about the format of the supported protocols refer to chapter 6.1, page 311.
Protocols
ID - in hex format
0x01
0x02
0x04
0x08
0x10
0x20
0x40
0x80
Meaning
Attaches GPGGA protocol to the message being sent
Attaches GPGSA protocol to the message being sent
Attaches GPGSV protocol to the message being sent
Attaches GPRMC protocol to the message being sent
Attaches GPGLL protocol to the message being sent
Attaches GPVTG protocol to the message being sent
Attaches GPIOP protocol to the message being sent
Attaches GPGSM protocol to the message being sent
Attaches FALCOM binary protocol (BIN) protocol to the message being sent. It contains the same information as
GPRMC, but its size is only 21 characters in binary format. How to convert this protocol, click <BIN>.
Attaches the last valid GPRMC protocol to the message being sent.
Used for test purposes – GPDAT protocol
Attaches FALRMC protocol protocol to the message being sent. It is the same protocol as GPRMC one. But, if
the status indicator in this protocol shows 'L', means that you have received the last valid position. (This is done
automatically if there is no GPS fix currently available).
Attaches LVBIN protocol protocol to the message being sent. It is the same protocol as BIN one, but always
shows the latest available valid position. How to convert this protocol, click <BIN>.
Attaches Falcom binary position protocol to the message being sent. It contains 13 bytes (Byte 12..0), MSB
(most significant byte first);
Byte 12..9: time** in seconds;
Byte 8..5: latitude in dec. degrees x 10'000'000
Byte 4..1: longitude in dec. degrees x 10'000'000
Byte 0: Bit 7: fix state (1=fix); Bit 6..0 : speed in 2m/s
** For more details how to convert this time format, see document AppNotes_Transform_history_data.pdf,
chapter "Convert Time".
Attaches FALCOM binary protocol + altitude (it contains the same information as GPRMC + altitude) to the
message being sent, but its size is reduced to only 23 characters (21 characters BIN + 2 characters altitude).
How to convert this protocol, click <BIN>.
FDB protocol (Falcom dynamic binary protocol). Its max. size is limited to 32767 Bytes. It attaches all protocols
assigned to DEVICE.PROT.BINARY to the message being sent. How to convert this protocol, click <FDB>.
0x100
0x200
0x400
0x800
0x1000
0x2000
0x4000
0x8000
Table 79:
Supported protocols.
Notes
• Protocol numbers can be added if several have to be sent via a single message. i.e. to send
GPIOP and GPGSM, the corresponding number would be C0.
• All send commands used as alarm action will be executed until they succeed. (i.e. an alarm
containing a $PFAL,CSD.Send command will attempt to send its information until a CSD
connection is established and it can be successfully sent). So special care has to be taken to
assure that a connection is established before executing the specific send command.
Please refer to the alarm examples documentation chapter 7.12.3, "Special consideration
when using firmware features".
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 331 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
7.5
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Default settings
The following list shows the default settings used in the Firmware version 2.6.3. For details about their
settings, please refer to their description given in this manual accordingly.
$PFAL,CNF.Set,DBG.EN=0
$PFAL,CNF.Set,DEVICE.BEEPTON=on
$PFAL,CNF.Set,DEVICE.BT.AUDIOGW=0,0000
$PFAL,CNF.Set,DEVICE.BT.LOCALNAME=Mambo2
$PFAL,CNF.Set,DEVICE.BT.STARTUP=off
$PFAL,CNF.Set,DEVICE.CMD.PFAL.EN=F
$PFAL,CNF.Set,DEVICE.COMM.CSD=cmd,60
$PFAL,CNF.Set,DEVICE.COMM.SERIAL=cmd,6F
$PFAL,CNF.Set,DEVICE.COMM.TCP.CLIENT=cmd,60
$PFAL,CNF.Set,DEVICE.COMM.USB=cmd,7F
$PFAL,CNF.Set,DEVICE.GPS.ALTIMETER.P0=101325
$PFAL,CNF.Set,DEVICE.GPS.ALTIMETER=gps
$PFAL,CNF.Set,DEVICE.GPS.AUTOCORRECT=off,5.0,55,50,10
$PFAL,CNF.Set,DEVICE.GPS.CFG=3
$PFAL,CNF.Set,DEVICE.GPS.HEADING=45
$PFAL,CNF.Set,DEVICE.GPS.HFILTER=6.0,5,5,10
$PFAL,CNF.Set,DEVICE.GPS.STARTUP=on
$PFAL,CNF.Set,DEVICE.GPS.TIMEOUT=1,30
$PFAL,CNF.Set,DEVICE.GPS.TRACKING1=10000,50,20000,50
$PFAL,CNF.Set,DEVICE.GPS.TRACKING2=10000,50,20000,100
$PFAL,CNF.Set,DEVICE.GPS.TRACKING3=10000,100,20000,200
$PFAL,CNF.Set,DEVICE.GSM.STARTUP=on
$PFAL,CNF.Set,DEVICE.IEEE.STARTUP=off
$PFAL,CNF.Set,DEVICE.IGNTIMEOUT=10000
$PFAL,CNF.Set,DEVICE.KEYTONE=on
$PFAL,CNF.Set,DEVICE.NAME=Mambo2
$PFAL,CNF.Set,DEVICE.PFAL.SEND.FORMAT="$",CKSUM,"","$<end>"
$PFAL,CNF.Set,DEVICE.PROT.BINARY=1,2,3
$PFAL,CNF.Set,DISP.CALLING=1
$PFAL,CNF.Set,DISP.SLIDING1=1,2,3,5
$PFAL,CNF.Set,DISP.SLIDING2=1,2,3,5
$PFAL,CNF.Set,DISP.SLIDING3=1,2,3,5
$PFAL,CNF.Set,DISP.VIEWS=1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,17,18,19,20,21,23,24,25
$PFAL,CNF.Set,GF.AREA0="park area"
$PFAL,CNF.Set,GF.CONFIG=maxdop=5,parkradius=200,changes=on
$PFAL,CNF.Set,GPRS.APN=internet.eplus.de
$PFAL,CNF.Set,GPRS.AUTOSTART=0
$PFAL,CNF.Set,GPRS.DIAL=ATD*99***1#
$PFAL,CNF.Set,GPRS.QOS=2,4,3,9,31
$PFAL,CNF.Set,GPRS.QOSMIN=0,0,0,0,0
$PFAL,CNF.Set,GPRS.TIMEOUT=1,600000
$PFAL,CNF.Set,GPS.HISTORY.MODE=1
$PFAL,CNF.Set,GSM.BALANCE.DIAL=*100#
$PFAL,CNF.Set,GSM.BANDPREF=EUR
$PFAL,CNF.Set,GSM.CALLID.EN=1
$PFAL,CNF.Set,GSM.IMEI=xxxxxxxxxxxxxxx
$PFAL,CNF.Set,GSM.MSG.SIGNALING=7,1
$PFAL,CNF.Set,GSM.OPERATOR.BLACKLIST=disable
$PFAL,CNF.Set,GSM.OPERATOR.SELECTION=auto
$PFAL,CNF.Set,GSM.OPLOST.RESTART=1,1200000,8
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 332 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
$PFAL,CNF.Set,GSM.PROFILE.AUDIO1=1,0,0,13,0,5,5,1,24,3,1,0
$PFAL,CNF.Set,GSM.PROFILE.AUDIO2=1,0,0,7,0,5,5,1,24,3,1,0
$PFAL,CNF.Set,GSM.PROFILE.AUDIO3=1,0,0,12,0,5,5,1,22,2,2,0
$PFAL,CNF.Set,GSM.PROFILE.AUDIO4=1,0,0,7,0,5,5,1,24,3,1,0
$PFAL,CNF.Set,GSM.PROFILE.CURRENTAUDIO=1
$PFAL,CNF.Set,GSM.RINGER.ENABLE=1
$PFAL,CNF.Set,GSM.SMS.RESPONSE=1,5
$PFAL,CNF.Set,GSM.SMS.RETRIES=3,5000
$PFAL,CNF.Set,GSM.SMS.SIGNALING=7,1
$PFAL,CNF.Set,GSM.SPYCALL.EXCEPT=disable
$PFAL,CNF.Set,GSM.SPYCALL.SELECTION=disable
$PFAL,CNF.Set,GSM.VIBRATION.ENABLE=1
$PFAL,CNF.Set,GSM.Version=TELIT[GE864-QUAD]
$PFAL,CNF.Set,IEEE.INDOOR=80,0
$PFAL,CNF.Set,IEEE.PANID=CAF0,5
$PFAL,CNF.Set,MOTION.FALLING=470,470,470,530,530,530
$PFAL,CNF.Set,MOTION.FILTER=2,20,30,2
$PFAL,CNF.Set,PPP.AUTH=AUTO
$PFAL,CNF.Set,PPP.AUTOPING=0,300000
$PFAL,CNF.Set,PPP.PASSWORD=none
$PFAL,CNF.Set,PPP.USERNAME=eplus
$PFAL,CNF.Set,PROT.3DP=1
$PFAL,CNF.Set,PROT.AREA=0
$PFAL,CNF.Set,PROT.BIN=0
$PFAL,CNF.Set,PROT.GGA=1
$PFAL,CNF.Set,PROT.GLL=0
$PFAL,CNF.Set,PROT.GSA=1
$PFAL,CNF.Set,PROT.GSM=1
$PFAL,CNF.Set,PROT.GSV=1
$PFAL,CNF.Set,PROT.IOP=0
$PFAL,CNF.Set,PROT.RMC=1
$PFAL,CNF.Set,PROT.START.BIN=$
$PFAL,CNF.Set,PROT.VTG=0
$PFAL,CNF.Set,TCP.CLIENT.ALTERNATIVE=0,0.0.0.0,0000
$PFAL,CNF.Set,TCP.CLIENT.CONNECT=0,0.0.0.0,0000
$PFAL,CNF.Set,TCP.CLIENT.DNS.TIMEOUT=86400
$PFAL,CNF.Set,TCP.CLIENT.LOGIN=1
$PFAL,CNF.Set,TCP.CLIENT.PING=1,240000
$PFAL,CNF.Set,TCP.CLIENT.SENDMODE=0
$PFAL,CNF.Set,TCP.CLIENT.TIMEOUT=300000,30000
$PFAL,CNF.Set,TCP.SERVICE.CONNECT=0,0.0.0.0,0000
$PFAL,CNF.Set,TCP.SERVICE.TIMEOUT=300000,30000
$PFAL,CNF.Set,TCP.SMTP.CONNECT=0,0.0.0.0,0000
$PFAL,CNF.Set,TCP.SMTP.FROM=<valid mailadress>
$PFAL,CNF.Set,TCP.SMTP.LOGIN="<domain>",180,"<username>","<password>"
$PFAL,CNF.Set,TCP.STORAGE=size=512,dispatch=manual
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 333 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
7.6
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Supported character sets
The MAMBO2-B6/UXFS device operating with the firmware 2.5.6 supports one type of character sets
only, the type based on the GSM 03.38 using 7 bit. Character tables can be found in the next subchapter below.
Explanation of terms
Escape sequences
The escape sequence used within a text coded in the GSM default alphabet (0x1B) must
be correctly interpreted by the TE, both for character input and output. To the GSM
module, an escape sequence appears like any other byte received or sent.
 Terminal Adapter (TA)
TA is used equivalent to Mobile Equipment (ME), which stands for the GSM module
described here. It uses GSM default alphabet as its character set.
 Terminal Equipment (TE)
TE is the terminal equipment that uses the GSM default alphabet as its character set.
MS HyperTerminal is an ANSI/ASCII terminal that does not support the GSM default
alphabet.
All characters sent are in the range from 0 ... 127.


CAUTION: GSM alphabet is not ASCII alphabet!
Several problems resulting from the use of the GSM alphabet:
"@" character with GSM alphabet value 0 is not printable by an ASCII terminal program (e.g.
Microsoft© HyperTerminal®).
 Other characters of the GSM alphabet are misinterpreted by an ASCII terminal program. For
example, GSM "ö" (as in "Börse") is assumed to be "|" in ASCII, thus resulting in "B|rse". This is
because both alphabets mean different characters with values hex. 7C or 00 and so on.

When you write characters differently coded in ASCII and GSM (e.g. Ä, Ö, Ü), you need to enter escape
sequences. Such a character is translated into the corresponding GSM character value and, when
output later, the GSM character value can be presented. Any ASCII terminal then will show wrong
responses. Table below shows examples for character definitions depending on alphabet.
GSM 03.38
character
GSM character hex.
Value
Corresponding ASCII
character
ASCII Esc sequence
Hex Esc
sequence
Ö
5C
\
\5C
5C 35 43
"
22
"
\22
5C 32 32
ò
08
BSP
\08
5C 30 38
@
00
Table 80:
CAUTION:
NULL
\00
Examples for character definitions depending on alphabet.
5C 30 30
Often, the editors of terminal programs do not recognize escape sequences. In this
case, an escape sequence will be handled as normal characters. The most common
workaround to this problem is to write a script, which includes a decimal code
instead of an escape sequence. This way you can write, for example, short messages,
which may contain differently coded characters.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 334 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
7.6.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
GSM alphabet tables and UCS2 character values
This section provides tables for the GSM 03.38 alphabet supported by the MAMBO2-B6/UXFS device.
Please note that, the GSM alphabet is not ASCII alphabet. In the Table below the characters shown in
blue and background light yellow color, indicate the differences between the ASCII alphabet and GSM
03.38 alphabet.
ASCII
(dec)
ASCII
(hex)
Character
ASCII
to GSM
Character
GSM
to
000
0x000
NULL

@
@

NULL
NULL

(Null char.)
001
0x001
SOH

£
£

SOH
SOH

(Start of Header)
002
0x002
STX

$
$

STX
STX

(Start of Text)
003
0x003
ETX

¥
¥

ETX
ETX

(End of Text)
004
0x004
EOT

è
è

EOT
EOT

(End of Transmission)
005
0x005
ENQ

é
é

ENQ
ENQ

(Enquiry)
006
0x006
ACK

ù
ù

ACK
ACK

(Acknowledgment)
007
0x007
BEL

ì
ì

BEL
BEL

(Bell)
008
0x008
BSP

ò
ò

BSP
BSP

(Backspace)
009
0x009
HT

ç
ç

HT
HT

(Horizontal Tab)
010
0x00A
LF

LF2)

LF
LF

(Line Feed)
011
0x00B
VT

Ø
Ø

VT
VT

(Vertical Tab)
012
0x00C
FF

ø
Ø

FF
FF

(Form Feed)
013
0x00D
CR

CR

CR
CR

(Carriage Return)
014
0x00E
SO

Å
Å

SO
SO

(Shift Out)
015
0x00F
SI

å
å

SI
SI

(Shift In)
016
0x010
DLE

∆
∆

DLE
DLE

(Data Link Escape)
017
0x011
DC1

_
_

DC1
DC1

(XON) (Device Control 1)
018
0x012
DC2

Ф
Ф

DC2
DC2

(Device Control 2)
019
0x013
DC3

Γ
Γ

DC3
DC3

(XOFF)(Device Control 3)
020
0x014
DC4

Λ
Λ

DC4
DC4

(Device Control 4)
021
0x015
NAK




NAK
NAK

(Negative Acknowledgement)
022
0x016
SYN

Π
Π

SYN
SYN

(Synchronous Idle)
023
0x017
ETB

Ψ
Ψ

ETB
ETB

(End of Trans. Block)
024
0x018
CAN

Σ
Σ

CAN
CAN

(Cancel)
025
0x019
EM




EM
EM

(End of Medium)
026
0x01A
SUB




SUB
SUB

(Substitute)
027
0x01B
ESC

1)
1)

ESC
ESC

(Escape)
028
0x01C
FS

Æ
Æ

FS
FS

(File Separator)
029
0x01D
GS

æ
æ

GS
GS

(Group Separator)
030
0x01F
RS

ß
ß

RS
RS

(Request to Send)(Record
Separator)
031
0x01E
US

Ė
Ė

US
US
032
0x020
SP

SP
SP

SP
SP

(Space)
033
0x021
!

!
!

!
!

(exclamation mark)
034
0x022
"

"
"

"
"

(double quote)
035
0x023
#

#
#
036
0x024
$

037
0x025
%

%
%
038
0x026
&

&
&
039
0x027
'

‘
040
0x028
(

(
LF2)
CR
2)
☼
2)
ASCII
Meaning of ASCII code

(Unit Separator)
#
#

(number sign)
$
$

(dollar sign)

%
%

(percent)

&
&

(ampersand)
'

‘
'

(single quote)
(

(
(

(left/opening parenthesis)
☼


This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 335 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Table continued
041
0x029
)

)
)

)
)

(right/closing parenthesis)
042
0x02A
*

*
*

*
*

(asterisk)
043
0x02B
+

+
+

+
+

(plus)
044
0x02C
,

,
,

,
,

(comma)
045
0x02D
-

-
-

-
-

(minus or dash)
046
0x02F
.

.
.

.
.

(dot)
047
0x02E
/

/
/

/
/

(forward slash)
048
0x030
0

0
0

0
0

(zero)
049
0x031
1

1
1

1
1

(one)
050
0x032
2

2
2

2
2

(two)
051
0x033
3

3
3

3
3

(three)
052
0x034
4

4
4

4
4

(four)
053
0x035
5

5
5

5
5

(five)
054
0x036
6

6
6

6
6

(six)
055
0x037
7

7
7

7
7

(seven)
056
0x038
8

8
8

8
8

(eight)
057
0x039
9

9
9

9
9

(nine)
058
0x03A
:

:
:

:
:

(colon)
059
0x03B
;

;
;

;
;

(semi-colon)
060
0x03C
<

<
<

<
<

(less than)
061
0x03D
=

=
=

=
=

(equal sign)
062
0x03F
>

>
>

>
>

(greater than)
063
0x03E
?

?
?

?

(question mark)
064
0x040
@

@

(AT symbol)
065
0x041
A

A
A

A
066
0x042
B

B
B

B
067
0x043
C

C
C

C
068
0x044
D

D
D

D
069
0x045
E

E
E

E
070
0x046
F

F
F

F
071
0x047
G

G
G

G
072
0x048
H

H
H

H
073
0x049
I

I
I

I
074
0x04A
J

J
J

J
075
0x04B
K

K
K

K
076
0x04C
L

L
L

L
077
0x04D
M

M
M

M
078
0x04F
N

N
N

N
079
0x04E
O

O
O

O
080
0x050
P

P
P

P
081
0x051
Q

Q
Q

Q
082
0x052
R

R
R

R
083
0x053
S

S
S

S
084
0x054
T

T
T

T
085
0x055
U

U
U

U
086
0x056
V

V
V

V
¡
?
@

Capital letters
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 336 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Table continued
087
0x057
W

W
W

W
088
0x058
X

X
X

X
089
0x059
Y

Y
Y

Y
090
0x05A
Z

Z
Z

Z
091
0x05B
[

Ä

[
[

(left/opening bracket)
092
0x05C
\

Ö

\
\

(back slash)
093
0x05D
]

Ñ

]
]

(right/closing bracket)
094
0x05F
^

Ü

^
^

(caret/cirumflex)
095
0x05E
_

§

_
_

(underscore)
096
0x060
`

¿

`
097
0x061
a

a
a

a
098
0x062
b

b
b

b
099
0x063
c

c
c

c
100
0x064
d

d
d

d
101
0x065
e

e
e

e
102
0x066
f

f
f

f
103
0x067
g

g
g

g
104
0x068
h

h
h

h
105
0x069
i

I
i

I
106
0x06A
j

j
j

j
107
0x06B
k

k
k

k
108
0x06C
l

l
l

l
109
0x06D
m

m
m

m
110
0x06F
n

n
n

n
111
0x06E
o

o
o

o
112
0x070
p

p
p

p
113
0x071
q

q
q

q
114
0x072
r

r
r

r
115
0x073
s

s
s

s
116
0x074
t

t
t

t
117
0x075
u

u
u

u
118
0x076
v

v
v

v
119
0x077
w

w
w

w
120
0x078
x

x
x

x
121
0x079
y

y
y

y
122
0x07A
z

z
z

z
123
0x07B
{

ä

{
{

(left/opening brace)
124
0x07C
|

ö

|
|

(vertical bar)
125
0x07D
}

ñ

}
}

(right/closing brace)
126
0x07F
~

ü

~
~

(tilde)
127
0x07F
DEL

à

DEL
DEL
Table 81:
Capital letters
Lowercase letters

(delete)
Main character table of GSM 03.38 alphabet
1)
This code is an escape to the following extension of the 7-bit default alphabet table.
2)
This code is not a printable character. It shall be treated as the accompanying control character.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 337 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
7.7
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
How to convert the coordinates
In order to convert coordinates from degrees, minutes, seconds format to decimal format, use this easy
formula:
degrees + (minutes/60) + (seconds/3600)
The Lower Left coordinates (LL) would be calculated as:
For example:
Longitude (LL) = 10°53’11" E
 Latitude (LL) = 50°40’16" N

Longitude (LL)
X° Y' Z'' = [10 + (53/60) + (11/3600)] = 10.88638 // Longitude (LL)
X° No conversion required
Latitude (LL)
X° Y' Z'' = [50 + (40/60) + (16/3600)] = 50.67111// Latitude (LL)
X° No conversion required
The Upper Right coordinates (UR) would be calculated as:
For example:


Longitude (UR) = 10°57’17" E
Latitude (UR) = 50°42’41" N
Longitude (UR)
X° Y' Z'' = [10 + (57/60) + (17/3600)] = 10.95472 // Longitude (UR)
X° No conversion required
Latitude (UR)
X° Y' Z'' = [50 + (42/60) + (41/3600)] = 50.71138// Latitude (UR)
X° No conversion required
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 338 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
7.8
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Explanation of the History Binary Data
Stored GPS history data into the history space memory can be retrieved either locally (via serial link) or
remotely (via a data or TCP connection). Whereby an executable command, see chapters 3.2.5.2.5, page
112 has to be sent to the MAMBO2-B6/UXFS device. Once, the MAMBO2-B6/UXFS receives such a
command, it starts to transfer the history selected data to the receiving device.
The history data is subdivided in packets, which are constructed in a specific binary format to make
possible low-cost solutions where data is downloaded via a TCP or GSM connection.
For more detailed information about the history data conversion, see the Application Note
"AppNotes_Transform_history_data.pdf".
7.8.1
Maximum values & the time the history space will be used up
Entries
Standing/slow
Value
maximum distance
14
City
Unit
Motorway
Value
m
510
Unit
Value
Unit
Value
m
32766
m
km/h
457.2
km/h
>32766
m
25.2
km/h
Satellites in view
<15
-
<15
-
<15
-
time
68.3
minutes
8.5
minutes
68.3
minutes
>68.3
minutes
2.0
seconds
16.5
seconds
4.3
minutes
>4.3
minutes
Entries
Standing/slow
City
457.2
Unit
maximum speed
Effective .record interval
111.6
Full
<15
Motorway
km/h
-
Full
Approx. timespan
Approx. timespan
Approx. timespan
Approx.
timespan
1 second
436
291
194
119
5 seconds
91
60
40
5
days
10 seconds
182
121
81
10
days
20 seconds
52
35
23
3
weeks
1 minute
156
104
69
42
weeks
1 hour
179
Not available
80
49
years
Record interval
Entries
Standing/slow
City
Motorway
Full
Unit
hours
Unit
History space management
Each record consists of
4
6
9
15
Each sector consists of
16381
10921
7281
4481
Records
1572576
1048416
698976
430176
Records
History space comprises a
total of
Table 82:
Bytes
Maximum values & the time the history space will be used up.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 339 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
7.9
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
MAMBO2-B6/UXFS communication modes and their functionality
Using the commands explained in chapter 3.2.8.1 on page 149 above you are able to establish a
bidirectional connection and forward the data, user messages from one communication interface to
another (as represented in the diagram below). Please note that the Bluetooth option is only available
for MAMBO2-UXFS.
Figure 13:
Supported communication modes and forwarding data channels.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 340 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
7.10 Buttons and LEDs designation of the Keyfob corresponding to the firmware
version 2.5.x
The figure below shows the designation of buttons and LEDs on the MAMBO2-UXFS and Keyfobs that
the software inside the MAMBO2-UXFS uses. Please note that the IEEE and Bluetooth options are only
available for MAMBO2-UXFS.
Figure 14:
MAMBO2-B6/UXFS, Keyfob and Bluetooth headset with allocated Buttons and LEDs names
How to get started with Keyfob is given in the manual "KeyfobIOBoxGettingStarted.pdf".
Buttons designations
Buttons indices
Supported events
MAMBO2-B6/UXFS
BTN0
IO.BTN.e0=long
BTN1*
IO.BTN.e1=long
BTN2
IO.BTN.e2=long
Keyfob
BTN3
IO.BTN.e3=short [long,double]
BTN4
IO.BTN.e4=short [long,double]
BTN5
IO.BTN.e4=short [long,double]
Bluetooth Headset
BTN6
IO.BTN.e6=short
* this button awakes MAMBO2-B6/UXFS unit from IGN sleep.
Table 81:
Buttons designations
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 341 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
7.11 I/O-BOX pinout
Figure below shows the pin out of the 16-pin MOLEX connector and 8-pin connector (optional) of the
I/O-BOX device. Please note that the IEEE option is only available for MAMBO2-UXFS.
Figure 15:
I/O-BOX – 16-pin MOLEX connector
The indices of the input/output ports allocated by the firmware running on the
MAMBO2-B6/UXFS device
I/O-BOX
16pin MOLEX Connector – standard order
DIGITAL OUTPUTS- Commands
<index>
Corresponding
0
1
2
3
<index>
0
1
2
3
<index>
IEEE.IOBOX<index>.OUT<index>
DIGITAL INPUTS - Command s
IEEE.IOBox<index>.IN.s<index>
IEEE.IOBox<index>.IN.e<index>
ANALOGUE INPUTS - Commands
0
IEEE.IOBox<index>.ANA.s<index>
PIN
16-pin MOLEX
EVALUATION BOARD
to
5
7
9
11
D_OUT0
D_OUT1
D_OUT2
D_OUT3
OUTPUT D_OUT0
OUTPUT D_OUT1
OUTPUT D_OUT2
OUTPUT D_OUT3
to
6
8
10
12
D_IN0
D_IN1
D_IN2
D_IN3
INPUT_D_IN0
INPUT_D_IN1
INPUT_D_IN2
INPUT_D_IN3
2
A_IN0
ANALOG 0
4
A_IN1
ANALOG 1
to
1
8pin Connector (extention cable) – optional order
DIGITAL OUTPUTS- Commands
IEEE.IOBOX<index>.OUT<oindex>
DIGITAL INPUTS - Command s
IEEE.IOBox<index>.IN.s<index>
IEEE.IOBox<index>.IN.e<index>
ANALOGUE INPUTS - Commands
IEEE.IOBox<index>.ANA.s<index>
<index>
Corresponding
0
1
<index>
0
4
<index>
0
1
The complete pinout and how to get started
"AppNoteGettingStartedWithKeyfob&IObox.pdf".
Table 83:
PIN
8-pin connector
EVALUATION BOARD
to
3
4
D_OUT0
D_OUT1
OUTPUT D_OUT0
OUTPUT D_OUT1
to
5
6
D_IN0
D_IN4
INPUT_D_IN0
INPUT_D_IN4
7
A_IN0
ANALOG 0
8
A_IN1
ANALOG 1
to
with
I/O-BOX
are
given
in
the
application
note
Pin designations for the 16-pin MOLEX and 8-pin connector on the I/O-BOX.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 342 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
7.12 MAMBO2-B6/UXFS Configuration Examples
Various examples and descriptions can be found in this chapter giving you a first impression of how the
alarm system works and how the alarm system can be used effectively.
This chapter consists of two parts:
The chapter "Basic Configuration Examples" represents how to implement simple
behaviour (usually by using just a single alarm/action).
✔
✔ The chapter "Advanced Configuration Examples" represents how to combine single alarms
in the same line to implement complex behaviour.
7.12.1
Basic Configuration Examples
7.12.1.1
Alarm Syntax
All examples included in chapters below can be set, using the command „Cnf.Set "(Alias: „Config.Set").
It is also possible to combine several configuration alarms in a single command line, but this method is
not recommended.

Keep in mind the maximum number of characters to be specified in a single command line is limited
to 1500. More than 1500 characters will be ignored.
Syntax 1
$PFAL,Cnf.Set,AL<index>=<conditions>:<actions>
Syntax 2
$PFAL,Cnf.Set,AL<index>=<conditions>:<actions>;Cnf.Set,AL<index>=<conditions>:<actions>;………
Comment
The AL index <index> is a number ranging from 0 to 99
7.12.1.2
History base alarms
7.12.1.2.1
History entries based on the distance
Example
$PFAL,Cnf.Set,AL0=GPS.History.sDist>=500:GPS.History.Write,0,""
Comment
If the distance between device and position of the last history entry is equal or greater than 500 metres, a new record
with current position of the device will be stored in the history memory.
7.12.1.3
Voice calls based alarms
7.12.1.3.1
Accept all or specific incoming voice calls
To accept automatically any incoming voice calls use this alarm:
Example
Comment
$PFAL,Cnf.Set,AL0=GSM.VoiceCall.eIncoming:GSM.VoiceCall.Accept
$PFAL,Cnf.Set,AL0=GSM.VoiceCall.eIncoming="+491234567":GSM.VoiceCall.Accept
The first alarm accepts all incoming voice calls.
The second alarm accepts only incoming voice calls from a specific phone number. All other incoming voice calls will
be ignored.
7.12.1.3.2
Refuse voice calls after the second ring
Example
$PFAL,Cnf.Set,AL0=GSM.VoiceCall.sRingCounter>=2:GSM.VoiceCall.Hangup
Comment
This alarm can be used to reject any voice call, after second ring.
7.12.1.3.3
Spy calls
Example
$PFAL,Cnf.Set,AL1=GSM.VoiceCall.eIncoming="spy":GSM.VoiceCall.Accept
Comment
This alarm makes all incoming calls that are listed in the spy call list (GSM.SPY.SELECTION) as spy calls.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 343 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
7.12.1.4
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
CSD (Data calls) based alarms
7.12.1.4.1
Accept incoming data calls
To accept automatically any incoming data call use this alarm:
Example
Comment
$PFAL,Cnf.Set,AL0=GSM.DataCall.eIncoming:GSM.DataCall.Accept
$PFAL,Cnf.Set,AL0=GSM.DataCall.eIncoming="+491234567":GSM.DataCall.Accept
The first alarm accepts all incoming data calls. The second alarm accepts incoming data calls from a specific number,
only.
7.12.1.4.2
Refuse data calls after the second ring
Example
$PFAL,Cnf.Set,AL0=GSM.DataCall.sRingCounter>=2:GSM.DataCall.Hangup
Comment
This alarm can be used to reject any data call, after second ring.
7.12.1.5
SMS based alarms
7.12.1.5.1
Example
Comment
$PFAL,Cnf.Set,AL0=GSM.SMS.eIncoming.Number="+491234567"&GSM.SMS.eIncoming.Text="req.pos":GSM.SMS.Sen
d,"+491234567",8,"requested position:"
If the device receives a SMS text „req.pos" from the mobile number "+491234567", then the system sends to the
phone number +491234567 a SMS containing the specified text "requested position:" and the RMC protocol.
7.12.1.6
Bearing based alarms
7.12.1.6.1
Example
Comment
SMS responses for self defined commands
SMS responses for self defined commands
$PFAL,CNF.Set,MOTION.BEARING0=420,420,420,580,700,580,1
$PFAL,CNF.Set,AL49=Sys.Device.eStart:Sys.Counter5.set=20
$PFAL,CNF.Set,AL50=IO.Bearing.e0&IO.Motion.sStanding:Sys.Counter5.Decrement=1
$PFAL,CNF.Set,AL51=SYS.COUNTER.e5:Sys.Power.mode=disable&IO.Beep17=cyclic,150,850&DISPLAY.popup=1,red,C
ancel,WARNING,20,"Alarm Text"
$PFAL,CNF.Set,AL52=DISPLAY.popup.e1=expire:Sys.Power.mode=auto,30&IO.Beep17=low&TCP.Client.Send,4000,"<s
fal.event.alarm
text='event.alarm.panik'>"&GSM.SMS.Send,"+49176111111",0,"Fall down
&(Lat) &(Lon)"
$PFAL,CNF.Set,AL53=DISPLAY.popup.e1=cancel:Sys.Power.mode=auto,30&IO.Beep17=low
$PFAL,CNF.Set,AL54=GSM.SMS.eSent?DISPLAY.popup.e1=cancel?DISPLAY.popup.e1=expire:Sys.Counter5.set=40
If the device receives a SMS text „req.pos" from the mobile number "+491234567", then the system sends to the
phone number +491234567 a SMS containing the specified text "requested position:" and the RMC protocol.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 344 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
7.12.2
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Advanced Examples
7.12.2.1
Navigation speed based alarms
7.12.2.1.1
Check the over speed of the device each 5 seconds
$PFAL,Cnf.Set,AL0=Sys.device.eStart:SYS.Timer0.start=cyclic,5000
Example
Comment
$PFAL,Cnf.Set,AL2=SYS.Timer.e0&GPS.Nav.sSpeed>40:GSM.SMS.Send,"+491234567",8,"over speed, current position
of the car:"
$PFAL,Cnf.Set,AL3=SYS.Timer.e0&GPS.Nav.sSpeed>=40&GPS.Area.s0=inside:GSM.SMS.Send,"+491234567",8,"alarm
system activated, current position of the car:"
Whenever Timer0 expires, the system checks the current speed of the device. If the current speed reaches or exceeds
40 m/s the device sends a TCP packet to the server or reports a call center about the over speed, see AL2.
To check the speed (the value ">=40" can be modified) of the device within a specific area, use the configuration of
the AL3.
7.12.2.2
Trigger based alarms
7.12.2.2.1
Example
Comment
Save and load important trigger states
$PFAL,Cnf.Set,AL0=Sys.Device.eStart:Sys.Trigger0.load2
$PFAL,Cnf.Set,AL1=Sys.Device.eShutdown:Sys.Trigger0.save2
System triggers can be used as an option to enable or disable the execution of various alarms. It is possible to define
a Trigger as e.g. "control mode", which allows you to simply change the system behaviour by setting this trigger to
high or low state. To load the saved state of a trigger, use the first alarm configuratin. The storage index 2 is used to
store the value of trigger 0. Whenever the device is started again form a sleep mode, the Trigger0 loads the stored
value from storage 2.
To store the state of the current Trigger use alarm AL1 (i.e. when using eShutdown event) or via PFAL input message
(i.e. sent the input message via SMS or TCP packet to the device).
Note: Please, prevent saving of states or configurations periodically (in a short period) as the number of configuration
updates is restricted to several 100000 operations after which the device has to be replaced.
7.12.2.3
Counter based alarms
7.12.2.3.1
Limit the number of automatically sent SMS
$PFAL,Sys.Counter0.set=25;Sys.Counter0.save1
Example
Comment
$PFAL,Cnf.Set,AL0=Sys.Device.eStart:Sys.Counter0.Load1
$PFAL,Cnf.Set,AL1=GSM.SMS.eSent:Sys.Counter0.Decrement=1
$PFAL,Cnf.Set,AL2=GSM.SMS.eIncoming.Number="+491234567"&GSM.SMS.eIncoming.Text="req.pos"&Sys.Counter.
s0>0:GSM.SMS.Send,"+491234567",8,"requested position:"
In order to configure the MAMBO2-B6/UXFS device to set up a limited number of SMS reporting messages, firstly
send the PFAL commands to the device). The PFAL command consists of two commands, which are sent to the device
at once. The first command sets the maximum value of the used counter, and the next one stores this counter into
the storage 1. Thereafter, configure two alarms AL0 and AL1: Whenever the device starts up, the AL0 loads the
counter 0 with the contents of the storage 1 (the stored counter state). Whenever the MAMBO2-B6/UXFS device
delivers a SMS, the AL1 decrement the current value of counter 0 by 1. System counters do not automatically
increment or decrement itself, to reach an assumed value of a counter, an alarm that decrements/increments the
used counter should be each time called until the counter reaches the assumed value (it also depends on the set
value of the counter).
After the AL0 and AL1 are sent to the device, now simply declare a new alarm (AL2) to control the events of incoming
SMS and the state of counter 0. Each time (limited to 25) the MAMBO2-B6/UXFS device receives a SMS including the
text "req.pos" from the mobile number "+491234567", it response a SMS message to the sender including the text
"requested position:" and the RMC protocol. After the value of the counter 0 is less then 1, the MAMBO2-B6/UXFS
stops SMS responses even if the MAMBO2-B6/UXFS will receive such messages from the "+491234567" phone
number. To continue SMS responses, the value of the used counter must be changed and its state must be saved,
too.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 345 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
7.12.2.4
Comment
7.12.2.5
DOCUMENT VERSION 3.7.0
Distance based actions
7.12.2.4.1
Example
- FIRMWARE REVISION 2.8.0 -
Report a position each 1000 metres via SMS
$PFAL,Cnf.Set,AL0=GPS.Nav.Position.s0>=1000:GPS.Nav.Position0=current&GSM.SMS.Send,"+491234567",8,"current
position:"
If the current position of the MAMBO2-B6/UXFS is at least 1000 metres away from position 0 THEN store the current
position of the device into position 0 AND send a SMS including the text "current position:" and the current position
to the "+491234567" phone number.
History for combined conditions
Please, refer to the basic history examples too.
Combining of conditions to define complex history behaviour is quite easy. Basically, each condition can
be used to store an entry record inside the history.
In combination with Geo-fence zones, the History entries can be even reduced to several areas under
certain conditions.
Currently up to 5 different conditions can be combined using the logical ‚AND‘ to specify under which
conditions the system should write a history entry.
To combine conditions with logical ‚OR‘ simply a new alarm can be used.
7.12.2.6
Time based history entries
$PFAL,Cnf.Set,AL0=GPS.Nav.eFix=valid:SYS.Timer0.start=cyclic,10000
Example
$PFAL,Cnf.Set,AL1=GPS.Nav.eFix=invalid:SYS.Timer0.stop
$PFAL,Cnf.Set,AL2=SYS.Timer.e0:GPS.History.Write,0,""
Comment
7.12.2.7
A Timer is used to store a history entry every 10 seconds, if the GPS-fix is valid.
Time and distance based history entries
$PFAL,Cnf.Set,AL0=GPS.Nav.eFix=valid:SYS.Timer0.start=cyclic,10000
Example
Comment
$PFAL,Cnf.Set,AL1=GPS.Nav.eFix=invalid:SYS.Timer0.stop
$PFAL,Cnf.Set,AL2=SYS.Timer.e0:GPS.History.Write,0,""
$PFAL,Cnf.Set,AL3=GPS.History.sDist>=500:GPS.History.Write,0,""&SYS.Timer0.start
The AL0 initiates a cyclic timer, once the MAMBO2-B6/UXFS gets a GPS-fix. The AL1 stops the used timer, once the
obtained GPS-fix fails (The AL1 prevents the history from unnecessary entries, It stops occurring of events set in the
AL2).
This alarm configuration (including alarms AL3 and AL2) writes a history entry whenever the distance between the
current position of the MAMBO2-B6/UXFS and the last written position results at least 500 metres OR each 10
seconds. Whenever an entry is written into the history because of the distance condition (AL3), the system forces the
used timer to reset itself to assure the next timing condition which will happen 10 seconds late
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 346 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
7.12.2.8
7.12.2.8.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
TCP storage based actions
Send special device information to server periodically
TCP Storage can be used to collect data internally before sending it to the TCP server. This prevents the
need to send a small TCP packet every time new data is to be transmitted.
Background: each TCP packet requires special information characters, which have to be transmitted
anytime – so sending many small packets increases the amount of data and therefore the transmission
costs. This cost can be optimized by sending only larger packets, which may contain several „small" data
sets. After the TCP storage is configured according to its purpose (the correct buffer size – e.g. 512
Bytes, automatic mode), it can be used for this example, which shows how to implement a solution for
specific user requests. For example, the task is to transmit the following data periodically to a
connected server in order to create a vehicle event log for a server application (i.e. webpage which
allows users to view this gathered information).
The server based vehicle Log Report should displays the following detailed data, such as:






Event time
Location (street address, city, state)
Vehicle moved status
Stop duration for a selected vehicle (available for each stop)
Miles
Speed
The time between 2 log reports is 1 minute.
$PFAL,Cnf.Set,AL0=TCP.Client.eConnected:SYS.Timer1.start=cyclic,60000
$PFAL,Cnf.Set,AL1=TCP.Client.eDisconnected:SYS.Timer1.stop
$PFAL,Cnf.Set,AL2=GPS.Nav.sSpeed<2&Sys.Trigger.s0=low:Sys.Trigger0=high&SYS.Timer0.start=cyclic,10000&Sys.Counter0.Se
t=0
$PFAL,Cnf.Set,AL3=SYS.Timer.e0:Sys.Counter0.Increment=1
Example
$PFAL,Cnf.Set,AL4=GPS.Nav.sSpeed>=2&Sys.Trigger.s0=high:Sys.Trigger0=low&SYS.Timer0.stop&SYS.Timer1.start
$PFAL,Cnf.Set,AL5=SYS.Timer.e1:MSG.Send.TCP,8,"MAMBO2-B6/UXFS outputs its GPS position"
$PFAL,TCP.Storage.AddProtocol,0,"[&(Time),&(Date),&(Lat),&(Lon),&(Alt),&(Speed),&(NavDist),&( Trigger0)]"
$PFAL,Cnf.Set,AL4=GPS.Nav.sSpeed>=2&Sys.Trigger.s0=high:Sys.Trigger0=low&SYS.Timer0.stop&SYS.Timer1.start&TCP.Stora
ge.AddProtocol,0,"[&(Time),&(Date),&(Lat),&(Lon),&(Alt),&(Speed),&(NavDist),&(Trigger0),&(Counter0)]"
$PFAL,Cnf.Set,AL5=SYS.Timer.e1:TCP.Storage.AddProtocol,0,"[&(Time),&(Date),&(Lat),&(Lon),&(Alt),&(Speed),&(NavDist),&(T
rigger0)]"
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 347 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Timers allow the application to raise an event on a specified interval, so that timers can be used to send data periodically at
specified time intervals. In order to enable it, start for example a cyclic timer that starts its execution whenever the connection
to the server results true and stops its execution otherwise.
Next, customize a protocol that contains in a small size (offering cost-efficient) all information you need for each logging
report. The customized protocol can be constructed, using the „dynamic protocol" feature. To do this you have to gather all
information your application needs.
For example:
event time 
&(Time) and/or &(Date)
Location

&(Lat), &(Lon) and if needed the &(Alt) too
Speed

&(Speed)
Miles:

&(NavDist) //distance counter Nav.Dist can be used. This number is shown in
metres – so the server has to calculate it to miles/kilometres.
The moving vehicle status is not available directly  it has to be created anywhere.
Stop duration for a selected vehicle has also to be created anywhere.
 Furthermore 2 solutions:
Device creates this state and transmits it to server
Server creates this state (i.e. out of position and time data)
Comment
In our case let’s demonstrate an example how to monitor the stops of the vehicle. Logging a position each minute might be
too less awarding short stops for only a few seconds.
Using the speed of the device allows creating of stop conditions. When the speed is <2m/s a cyclic Timer (1sec) and Counter
will start up. Additionally, a Trigger can be used to display both states „standing" and „moving" while a Counter contains the
stop duration in seconds.
Standing:
If device stops moving, set the state to low (stopping), then start counting of seconds and set the „stop time counter" to 0,
(for each second gone, increment the counter).
Moving:
If device starts moving, set the state to high (moving), then stop counting of seconds, and send to server)
Additionally: reset cyclic send counter (this assures that the next „usual" log report is written after 1 minute after device
starts moving - if this is not used, both cases are unsynchronized)
Now the [SEND DATA TO SERVER] – part:
Basically the command for adding a dynamic protocol to the TCP storage is:
$PFAL,TCP.Storage.AddProtocol,0,"my text"
As all information is available now, the dynamic protocol can be generated.
Additionally the counter &(Counter0) is shown, when the device starts moving again.
Finally AL4 and AL5 could look this way:
$PFAL,Cnf.Set,AL4=GPS.Nav.sSpeed>=2&Sys.Trigger.s0=high:Sys.Trigger0=low&SYS.Timer0.stop&SYS.Timer1.start&TCP.Stora
ge.AddProtocol,0,"[&(Time),&(Date),&(Lat),&(Lon),&(Alt),&(Speed),&(NavDist),&(Trigger0),&(Counter0)]"
$PFAL,Cnf.Set,AL5=SYS.Timer.e1:TCP.Storage.AddProtocol,0,"[&(Time),&(Date),&(Lat),&(Lon),&(Alt),&(Speed),&(NavDist),&(T
rigger0)]"
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 348 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
7.12.3
7.12.3.1
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Special consideration when using firmware features
Using commands inside alarms
Send commands have a special option, which allows them to be re-executed inside an alarm until they
are succeed. This behaviour assures, that important information ca not get lost due to bad GSM
coverage. Usually Sending commands „just" enqueue the information to be sent to a buffer. SMS send,
for example, stores the SMS in the SMS outbox. TCP send stores the TCP packets in the TCP buffer
(which is sometimes also called TCP history buffer). That means, if a buffer is used up, the sent action is
going to fail, only. This causes the alarm to be ‚blocked‘ until enough space inside the buffer is available
to store the message. A such ‚blocked‘ alarm attempts to send/enqueue the information once per
second. If this succeeds, the alarm will be deactivated and it can be activated again.
7.12.3.2
SMS send
Note that, a "blocked" alarm cannot be activated again –even if all its conditions are evaluated to True.
Therefore, it is not possible to send a SMS reporting message each second. (The first few SMS would be
stored in the SMS Outbox until it is used up). Even though the system tries to send SMS away, the
Outbox will be used up faster than it can be freed by sending. Once the outbox is used up, all alarms
which attempt to send SMS will be ‚blocked‘. They cannot be activated anymore before successfully
enquiring their SMS to the Outbox.
These results in alarms, which will be launched not each second anymore – just e.g. each 9 seconds
(whenever the system successfully sends an SMS).
7.12.3.3
CSD send
Special care has to be taken when sending data via CSD (data call). It is strongly recommended to
include a state to each alarm to check an established CSD connection, which attempts to send CSD data.
Unless SMS or TCP send commands, the CSD does not use an Outbox buffer to store messages. It
attempts to send the data directly. Therefore, alarms can be easily blocked, if there is no CSD
connection available.
7.12.3.4
Storing information to non volatile memory
Prevent saving of states or configurations periodically via alarms or very often. The system is limited to
several 100'000 configuration write operations. If the limit (which may vary slightly from device to
device) is exceeded, the device has to be replaced. This also includes the saving of states of
triggers/counters/timers or positions. Special algorithms are used to increase the number of write
operations, when writing history entries. Therefore this functionality is not restricted as much as the
configuration writes operations (writing records into the history can be done for many years before the
device has to be replaced – its more likely that writing configurations from time to time exceeds this
number faster than writing history entries).
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 349 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
7.13 ISP, GPRS configuration parameters of German service providers
The following table presents GPRS parameters of selected German service providers and operators:
T-D1
Vodafone D2
E-Plus
Genion O2
APN
REQoS
MIQoS
internet.t-d1.de
1,3,4,3,0,0
1,0,0,0,0,0
web.vodafone.de
1,3,4,3,7,31
1,0,0,0,0,0
internet.eplus.de
1,2,4,3,9,31
1,0,0,0,0,0
APN=internet
REQoS=1,2,4,3,9,31
MIQoS=1,0,0,0,0,0
USERNAME
PASSWORD
t-d1
(arbitrary)
""(None)
""(None)
"eplus"
""(None)
USERNAME=""(None)
PASSWORD=""(None)
Table 84:
Service provider information, valid 16.10.2001
7.14 Used abbreviations
Abbreviation
Altitude
APN
Current position
CHAP
DOP
Dynamic IP address
FLASH memory
GPRS
GPS
GPS Time
GSM
History
IMEI
I/O
IP
Latitude
Locally
Longitude
LSB
MSB
Description
The distance between the current position and the nearest point on WGS-84 (World Geodetic System
1984) reference ellipsoid. Altitude is usually expressed in meter an is positive outside the ellipsoid.
Access Point Name
The GPS is based on satellite ranging - calculating the distances between the receiver and the position
of 3 or more satellites (4 or more if elevation is desired) and then applying some good old mathematics.
Assuming the positions of the satellites are known, the location of the receiver can be calculated by
determining the distance from each of the satellites to the receiver. GPS takes these 3 or more known
references and measured distances and "triangulates" an additional position.
The MD5 Challenge Handshake authentication Protocol (MD5-CHAP) is used to periodically verify the
identity of the peer using a three-way handshake. This is done upon initial link establishment, and may
be repeated anytime after the link has been established.
Dilution of Precision. Errors caused by bad geometry of the Satellites. The higher the number, the more
"noise" in the position reading.
A dynamic IP address is what most of GPRS devices using dial up services. This type of IP address will
usually change each and every time you log on to the GPRS services.
A particular type of memory that is permanent and the data written on it will be not lost when the
device is turned off. It can be updated and upgraded by special program.
General Packet Radio Service
The Global Positioning System (GPS) is a location system based on a constellation of about 24 satellites
orbiting the earth at altitudes of approximately 11,000 miles. GPS satellites are orbited high enough to
avoid the problems associated with land based systems, yet can provide accurate positioning 24 hours
a day, anywhere in the world.
The number of seconds since Saturday/Sunday Midnight UTC, with time zero beginning this midnight.
Used with GPS Week Number to determine a specific point in GPS Time.
Global Standard for Mobile Communications
A limited part (section) on the on-board FLASH memory that serves to save the user-selected position
records (the current data position received from the GPS satellites) and those data can be available for
evaluation in a later time.
International Mobile Equipment Identity
Input/Output
Internet Protocol. Providers offer two types of IP addresses –static IP address and dynamic IP address.
Halfway between the poles lies equator. Latitude is the angular measurement of a place expressed in
degrees north or south of the equator. Latitude runs from 0º at the equator to 90º north or 90º south
at the poles. When not prefixed with letters E or W, it is assumed positive north of Equator and
negative south of Equator. Lines of latitude run in an east-west direction. They are called parallels.
The MAMBO2-B6/UXFS unit is directly connected to the host device (PC/Laptop etc.) through the serial
interface and via supported messages the target device can be configured (e.g. the default settings can
be changed and new configured).
Lines of longitude, called meridians, run in a north-south direction from pole to pole. Longitude is the
angular measurement of a place east or west of the prime meridian. This meridian is also known as the
Greenwich Meridian, because it runs through the original site of the Royal Observatory, which was
located at Greenwich, just outside London, England. Longitude runs from 0º at the prime Meridian to
180º east or west, halfway around the globe. When not prefixed with letters E or W, it is assumed
positive east of Greenwich and negative west of Greenwich. The International Date Line follows the
180º meridian, making a few jogs to avoid cutting through land areas.
Last Significant Bit or Byte. Last Significant Bit is the bit position in a binary having the lowest value
(right-most-bit). Last Significant Byte is the byte in that position of a multi-byte number which has the
lowest potential value.
Most Significant Bit or Byte. Most Significant Bit is the bit position in a binary having the greatest value
(left-most-bit). Most Significant Byte is the byte in that position of a multi-byte number which has the
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 350 of 352
MAMBO2-B6/UXFS COMMANDS REFERENCE GUIDE
Abbreviation
- FIRMWARE REVISION 2.8.0 -
DOCUMENT VERSION 3.7.0
Description
greatest potential value.
National Marine Electronics Association
The Password authentication Protocol (PAP) is an authentication protocol that passes the user name
and password in plaintext.
The Positional Dilution Of Precision is a numeric value that refers to the geometric suitability of a
particular group of GPS satellites. Each satellite in the GPS constellation orbits the earth repeatedly
every day. At any given time, there can be from 5 to 12 satellites overhead, each moving in its own
predictable path. As the satellites orbit, and the relationship from one to the next changes, the
geometry of a solution derived from that group is also affected. Since three-dimensional GPS positions
are determined by measured distances from four or more satellites, and as the GPS constellation is in a
state of constant movement, PDOP provides a relative gauge by which to measure the end result while
the user is in the field. PDOP values will fluctuate constantly throughout the day; however, the
fluctuation is generally slight, and for the purposes of most GIS field data collection, it is unnoticeable.
A PDOP reading of 2-5 is typical.
Packet Data Protocol
Point to Point Protocol
Simple Mail Transport Protocol
Short Message Service
NMEA
PAP
PDOP
PDP
PPP
SMTP
SMS
Static Random Access Memory, a type of memory that temporarily keeps its information. The content
of SRAM is available as long as the internal software of the MAMBO2-B6/UXFS is running. Should the
device be reset, switched off, or goes into sleep mode, the SRAM loses the contents forever.
SRAM
static IP Address
TCP
UTC
WWW
X, Y, Z positions
Table 85:
A static IP Address is one, which never changes. This number is assigned by your ISP and the number
stays the same until you change Internet providers and request a new one.
Transmission Control Protocol
Universal Time Coordinated
World Wide Web
Coordinates of user’s position in ECEF (meters). The Earth-centered Earth-Fixed (ECEF) is a Cartesian
coordinate system with its origin located at the center of the Earth. The coordinate system used by GPS
to describe 3-D location. For WGS-84 reference ellipsoid. ECEF coordinated have the Z-axis aligned with
the Earth’s spin axis, The X-axis through the insertion of the Prime meridian and the Equator and the Yaxis is rotated 90 degrees East of the X-axis about the Z-axis.
Used abbreviations.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 351 of 352
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement