Linkr-MBT

1 - MBT Activation & Troubleshooting

Notes: If there is only power and ground or the data wires/protocol is not correct the unit will not let new devices pair and give a warning about doors locked.
If the unit is powered down LESS than ~10 seconds it may have issues re-connecting to app.
Tested current draw is 4.4ma with no active BT connections.

1.1 - Initial Test Activation

1.

a.

2.
#top

1.2 - User

1. User search function IS CaSe sensitive.
2.
#top ==1.3 - #top To be added
#top

2 - MBT Admin

2.1 - Dashboard

1. Displays Stats

a. System totals for each category

2.2 - Devices

1. Lists all devices registered in the system

a. UUID - Device serial number based off of Bluetooth ID number

b. Owner - Email address of registered owner, if one exists

c. Authorized User - Email address of any used authorized by the owner to use the device

d. Device Status - Shows current status (enabled/Disabled) of device. Gives admin ability to Disable/Transfer/Replace devices

2. Click on UUID field to get further details on device status and settings

a. Click any field (BLE Firmware/RS Product/RS Firmware/Owner/Auth User) to go to Firmware/Product/User page

b. Check box to enable/disable AUX functions. You must save after selecting and user MUST back out to home screen for settings to take effect

c. Click Disable/Enable, Save, Transfer, Replace, or Add Auth User to do the listed function.

d. Scroll thru features to see last known RS configuration. (Blue = Default / Red = Current selected option if not Default)

3. Click on Owner or Authorized User field to go to user settings (See 2.3 Users)
4. Click on Device enabled/disabled button to go to device settings (See 2)
5. Click on Disable button to disable device
6. Click on Transfer button to transfer the device to another registered user.

a. User must already be registered in the system before transfer is possible.

7. Click on Replace button to replace the old device with a different one.

a. Be sure the device you select is not already registered to another user.

2.3 - Users

1. Email - The email they used to login/register (what else would it be)
2. Name - What ever they put for there first and last name when registering
3. Role - The functions they are allowed to see or use within the admin and app

a. User - End user who can use the app, that's about it

b. Admin - Omega user who can use the app, and do everything in the website.

c. Technical Staff - Technical user who can use the app, and access to the website for technical troubleshooting and device testing. (can not edit user roles)

d. Manufacturer - Hardware manufacturer with access to Device Labeling only.

4. Owned devices - All devices owned by the user
5. Authorized devices - All devices this user is authorized to use
6. Firmware access - Displays firmware access level of user (see firmware for further info)

a. R - Release - Tested and verified firmware for use by the general public.

b. A - Alpha - Limited public accessibility intended for testing firmware and report any bugs or issues to the Dev team. Intended for VERY well known users who understand the potential of firmware flaws and will not get there panties in a bunch if the firmware is flawed.

c. B - Beta - More general but still limited public accessibility intended for testing firmware and report any bugs or issues to the Dev team. Intended for users who may have a particular scenario that needs firmware testing or a custom firmware.

d. I - Internal - Omega and industry ONLY users.

2.4 - Brands

1. Device Brands - You can only create or delete brands

2.5 - Products

1. Product creation - You can only create or delete products.
2. Information needed to create product.

a. Product Name - Model number. For Omega units use model number on case, for example AL-1670-B would be AL-XX70-B.

b. Product Brand - Must already be existing in the system (see 2.4).

c. Product UUID - Unique HEX value coded in the firmware to ID device. Assigned by Product Dev.

d. Boot UUID (not all products need) - Bootloader UUID needed by some devices.

2.6 - Firmware

1. View all available firmware.
2. Change firmware release stage.

a. Release - Tested and verified firmware for use by the general public.

b. Alpha - Limited public accessibility intended for testing firmware and report any bugs or issues to the Dev team. Intended for VERY well known users who understand the potential of firmware flaws and will not get there panties in a bunch if the firmware is flawed.

c. Beta - More general but still limited public accessibility intended for testing firmware and report any bugs or issues to the Dev team. Intended for users who ,ay have a particular scenario that needs firmware testing or a custom firmware.

d. Internal - Omega and industry ONLY users.

2.7 - Device Labelling

1. Used for production labeling. No support functions here (keep out)

2.8 - About

1. Website version history. (nothing to see here folks, keep moving)

3 - FSF File

This file defines the firmware banks, features, and options as displayed and used in the app. Banks, Features, and Options MUST match firmware EEPROM map

3.1 - Creating FSF file

1.
2. FSF file notes
Text in Banks tab under “Bank Read Only Message_EN” column display Error message box with text and will not allow user into bank
Text in Banks tab under “Bank Warning Message_EN” column display Warning message box with text and will allow user to choose to enter Bank
Text in Features tab under “Feature Read Only Message_EN” column display Notification message box with text and will not allow user into feature
Text in Features tab under “Feature Warning Message_EN” column display Warning message box with text and allow user to choose to enter feature
Text in Features tab under “Help Message_EN” column display “?” icon. When icon selected message box with feature name displays with text in field and user has to choose “ok” to clear
Text in Options tab under “Option Read Only Message_EN” column display Error message box with text and will not allow user to select that feature
If no Option Bank-Feature ID number is present for an option “N/A” will display in features list
Android uses "Yes/No" text, iOS uses "Proceed/Cancel" text when user has a choice to enter or exit option. Be sure message is written so both make sense to the end user.