29
The easiest way to understand what is a profile is to compare it to a list of instructions that are
written for different cases. You are allowed to setup up to 4 different module behaviours. Global
parameters contain settings that are common for all 4 profiles. This means that if FMB630 is set
to call to predefined number, you will be able to call it while using any profile.
Profile 3 is default profile for FMB630. It is always loaded on the very first start-up and
further profile switching is proceeded after operator scan or I/O element changes.
Switching between profiles (changing behaviour) can be performed by GSM Operator
(mostly used for roaming applications), or by Profile switching depending on I/O Event (on I/O
value changing). More information about Profile switching functionalities can be found in
chapters 7.1 (Switching by GSM Operator) and 7.2 (Switching by I/O Element).
5.6
Features
Using available features can greatly increase FMB630 usability options.
5.6.1
Scenarios
Seven scenarios are available on FMB630 device:
Any Digital Output can be used by scenarios: Authorized Driving/Immobilizer, iButton
notification, ECO driving/Green driving, Overspeeding and Jamming detection.
Excessive idling and crash detection don’t use Digital Output.
5.6.1.1
ECO driving or Green driving Scenario.
Gives the ability to periodically monitor drivings characteristics and warn the driver against
over accelerating, braking or cornering. More about ECO driving/Green driving read in chapter
13.1
5.6.1.2
Over Speeding Scenario.
Helps to prevent from exceeding fixed speed and inspects driver if needed. Any DOUT
(which is configured) is controlled by scenario for user needs, to manage buzzer, LED etc.
5.6.1.3
Authorized Driving and Immobilizer Scenario.
Gives ability to use vehicle for 500 specific iButton owners (specified in iButton list). Any
DOUT (which is configured) is controlled by scenario for user needs, to manage buzzer, LED etc.
Vehicle can be used only if iButton is connected. In this scenario iButton list is not used -
connect any iButton to pass Immobilizer security. Any DOUT (which is configured) is controlled
by scenario for user needs. DOUTX is continuously OFF. DOUTX turns ON if Ignition turns ON
(Din1=1). After iButton ID is read (any iButton is attached), DOUTX turns OFF. After iButton
identification DIN1 (ignition) can be turned OFF (Din1=0) for no longer than 30 seconds,
otherwise immobilizer must be repeated.
5.6.1.4
iButton notification.
Scenario is introduced. If scenario is enabled, when iButton is attached and is successfully
read, configured DOUT goes ON for configurable amount of time (min: 0.1 s; max: 10.00 s;
default: 0.5 s). If Immobilizer scenario is enabled and iButton’s indication scenario is enabled and
the same DOUT controls are chosen then in case iButton is attached DOUT is not affected.
IButton’s event generation works as a standard IO event generation
