Changes

Line 14: Line 14:  
Profile 3 is default profile for {{{model|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 (although device remembers which profile it used after that).  
 
Profile 3 is default profile for {{{model|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 (although device remembers which profile it used after that).  
   −
* '''Profile Switching dependence on GSM Operator'''
+
*'''Profile Switching dependence on GSM Operator'''
    
GSM Operator code profile switching is mostly used in roaming applications, when the purpose is to have information from module both from Home and Roaming operator network for a reasonable price. This method allows you to define different module behaviour in Home network, Roaming network and unknown operator areas.  
 
GSM Operator code profile switching is mostly used in roaming applications, when the purpose is to have information from module both from Home and Roaming operator network for a reasonable price. This method allows you to define different module behaviour in Home network, Roaming network and unknown operator areas.  
Line 25: Line 25:  
{| class="wikitable"
 
{| class="wikitable"
 
|+
 
|+
! style="background: black; color: white;"|[[Image:alert.png]]
+
! style="background: black; color: white;" |[[Image:alert.png]]
! style="background: black; width: 800px; color: white;"|Operator search is performed every 15 minutes. If no operators are entered in any profile it can have influence on GPRS sessions. IF GPRS sessions are attaching/detaching every 15 minutes it means configuration of {{{model|FMB630}}} is performed incorrectly.
+
! style="background: black; width: 800px; color: white;" |Operator search is performed every 15 minutes. If no operators are entered in any profile it can have influence on GPRS sessions. IF GPRS sessions are attaching/detaching every 15 minutes it means configuration of {{{model|FMB630}}} is performed incorrectly.
 
|}
 
|}
   Line 32: Line 32:  
[[Image:fmb630_profiles_algo.png|none]]
 
[[Image:fmb630_profiles_algo.png|none]]
   −
* '''Profile switching dependence on I/O event'''
+
*'''Profile switching dependence on I/O event'''
    
Another profile switch method is based on I/O event. Events happen when the value of enabled I/O intersects thresholds (enter, exit, on both, hysteresis) predefined by High and Low level thresholds. SW21, SW22, SW23, SW24 stands for “Switch to profile no. X”. After an event happens, {{{model|FMB630}}} switches to a defined profile. Using profile switching you can create smart applications. SW2X actions can be performed only if “Profile change on event” is enabled in Global parameters.  Pictures below illustrate profile switching depending on digital events:  
 
Another profile switch method is based on I/O event. Events happen when the value of enabled I/O intersects thresholds (enter, exit, on both, hysteresis) predefined by High and Low level thresholds. SW21, SW22, SW23, SW24 stands for “Switch to profile no. X”. After an event happens, {{{model|FMB630}}} switches to a defined profile. Using profile switching you can create smart applications. SW2X actions can be performed only if “Profile change on event” is enabled in Global parameters.  Pictures below illustrate profile switching depending on digital events:  
Line 40: Line 40:  
<br>
 
<br>
 
Configuration of Profile1 to switch to Profile2 on DIN1 value change from 0 to 1:
 
Configuration of Profile1 to switch to Profile2 on DIN1 value change from 0 to 1:
[[File:Exampleprofileswitch1.PNG|none]]
+
 
 +
[[File:Profile1 to 2.PNG]]
 +
 
 
<br>
 
<br>
 
<br>
 
<br>
 
Configuration of Profile2 to switch to Profile1 on DIN1 value change from 1 to 0:
 
Configuration of Profile2 to switch to Profile1 on DIN1 value change from 1 to 0:
[[File:Exampleprofileswitch2.PNG|none]]
+
 
 +
[[File:Profile2 to 1.PNG]]