Difference between revisions of "Information Systems:RF Gun Administration"

From uniWIKI
Jump to navigation Jump to search
 
m
 
(62 intermediate revisions by 2 users not shown)
Line 1: Line 1:
  +
=Overview=
−
=Sending in a gun for repair=
  
  +
This article discusses administration of the RF guns. It is meant to contain only procedures and instructions, while background and in-depth technical information can be found [[Information Systems: Workabout Pro G2 7527C|'''in this accompanying article''']]. Also, refer to the [[:Category: RF Guns |'''RF Guns''']] category for more articles related to this topic.
   
  +
=Management and administration of RF guns=
−
Tags: gun repair, RF gun, Zebra, Mexico
  
   
  +
===Storage and inventory===
−
==Managing the device in MobiControl==
  
  +
RF guns that are in production are kept in 3 main areas. Their location and the number of guns recommended to be kept there are as follows:
−
''This step is not essential for getting the guns repaired, but is rather for accountability and asset management purposes. Skip ahead to RMA process if there is some urgency to sending the guns in for repair.''
  
   
  +
* Cupboard in the 'dumps' area: 20 units
−
There is a group in MobiControl named 'Out for Repair'. Read about the groups here (link to be included). Devices sent out for repair can be dragged to this group. You can also leave notes for each device in MobiControl. More details later.
  
  +
* Receiving: 5-6 units
  +
* Narcotics cage: 2 units
   
  +
The rest should be kept as spares '''outside Norwin's office''' for ease-of-access. At any given time, there are almost always a few that are marked to be shipped for repair (if they're not already under repair at TRG). '''These units should be kept in the I.T. cage.'''
−
==RMA process==
  
   
  +
===Hardware maintenance and repair===
−
When an RF gun needs to be sent in for repair, there are two methods of creating an RMA with Zebra Psion Solutions:
  
  +
Devices that are reported broken by warehouse staff can be sent to TRG for repair. Usually, warehouse supervisors call or email the IT Group that an RF gun has malfunctioned and either bring you the device or specify where they will leave it.
   
  +
The RF guns are under maintenance contract with TRG (Technology Recovery Group).
−
===Phone===
  
  +
Use the web portal to generate and submit RMAs. Credentials are as follows:
−
Number: 1-800-387-8898
  
  +
'''TRG Web Portal'''
−
Site ID: 6060011626
  
  +
'''Site''': [http://portal.trgrepair.com/home.asp TRG ServiceHub]
  +
'''Username''': norwin
  +
'''Password''': visionit
   
  +
As there are at least 5-6 spares in inventory at any given time (if none are already out for repair), it is recommended to hold devices for repair until there are 3-4 to be sent in, as shipping is charged both ways. ''However, best judgment is left to the administrator as some users have a strong preference for certain devices There is indeed enough variation between the guns to warrant this, despite all technically being the same model i.e. it's not just a placebo effect. Besides if it helps them work faster and happier, why not accommodate....-[[User:Norwinu|norwizzle]] ([[User talk:Norwinu|talk]])''
−
Call, provide the serial numbers, describe the problem for each unit and wait for an emailed packing slip. Pack up the guns, include the packing slip inside, and send via DHL/Loomis. Use either Ground (3-5) or Air 18:00 Express service at your discretion. You may also give the box to DC supervisor (Gordon or Gerald) and they will generate the label and ship the box for you.
  
   
  +
====Protocol for sending a device in for repair====
−
===Website===
  
  +
The process of sending guns in for repair is straightforward:
−
https://enterpriserepair.motorolasolutions.com/sym/servlet/PortalStart?portalLayout=yes
  
−
Login: norwinu@unipharm.com
  
−
Password: Our '''new''' favorite password + '2014'
  
   
  +
# Log in to TRG ServiceHub.
−
The preferred method of submitting RMAs is through the website, since it makes it possible to submit a more detailed and accurate description of the problem. The support agents over the phone go through teh exact same process anyways, so the website eliminates the middle man.
  
  +
# Start a ticket ("Submit Repairs" button), adding devices by serial number (located on a sticker at the back of the device, after removing the battery door), and describing the problem. Though not necessary, enter the gun number in the '''Ref.''' field (e.g. '''RF 33''') for reporting purposes.
  +
# Submit the ticket.
  +
# Print the packing slip.
  +
# Set the unit aside with the packing slip in the IT cage. If there are enough units to be sent for repair:
  +
:# Pack the devices in a box and include the packing slip/RMA inside.
  +
:# Give the box to one of the shippers and request for them to ship it to TRG (in Mississauga), or generate a label yourself, as TRG is already in the address book. I usually ship by Ground, but Air can be used for higher-priority situations.
   
−
====Steps====
 +
===Software administration===
  +
''Software administration is done via MobiControl. It will be discussed in a separate article.''
   
  +
===Serial numbers===
−
* Request an RMA
  
  +
Serial numbers are visible in MobiControl. They were manually entered in as a custom attribute, so it is conveniently displayed as a column.
−
* Enter serial number, and click 'Add to Shipment'. ''Note: The serial number is validated and the next page should confirm that it is under contract.''
  
−
* Select the 'Primary Sympton'
  
−
* Enter a detailed description in a way that makes it easy for the repair agent to identify the problem. Suggest a fix if possible. Insist on a fix if this is a repeat RMA for the same unit sent back as 'No Problem Found' the first time.
  
−
* (Optional) Enter the gun number in 'Your Ref. No.'
  
   
  +
===TRG Contact Information===
−
==Serial numbers==
  
  +
Melanie Drabiak is the main contact and can help with many things, from quotes on parts or general consultation. She is the first point of contact.
−
Gun 12 - 8277g005508
  
  +
  +
Contact: Melanie Drabiak
  +
Phone number: 440-471-8267
  +
Email: MDrabiak@TRGRepair.com
  +
  +
===Returning a gun to inventory===
  +
When the gun arrives there is no need to vet the repairs, and no configuration should be needed (unless the OS is wiped clean, in which case follow '''these instructions TBD''').
  +
* Make sure that the gun loads TekTerm and a session profile is defined. If there is no session defined, follow these steps.
  +
====Defining a connection/session in TekTerm====
  +
There are drop downs to fill out :
  +
* Session name: Bart
  +
* Protocol: TekTerm Emulation (TESS)
  +
* TekTerm Server should be greyed out
  +
* Connection type: Direct TCP
  +
* Server/host: 172.30.18.115 (this is the TekTerm server a.k.a lucy.unipharm.local)
  +
* Terminal number: Gun number (this is very important - it does not necessarily have to match the gun number but must be unique across all active session, which is why the gun number is convenient to use).
  +
  +
=Common Problems=
  +
===Sticky keys===
  +
* Particularly the Enter button.
  +
===Device powers off during use===
  +
This can be due to many factors, but some common ones include:
  +
* Loose battery door: The battery door has a foot that clamps down on a spring to signal to the device that it is installed, and allowing it to power on. A loose battery door (e.g. bad fit or missing twist-locks) or a stumped (broken) spring can lead to the device powering off abruptly.
  +
===Connectivity issues: Lock-H and Lock-B===
  +
Lock-H (yellow bar across bottom of TekTerm screen) and Lock-B (red bar) are normal if they last <1 second. However, if TekTerm is stuck on Lock-H or Lock-B, then investigate the following:
  +
* Lock-B is a communication problem between the gun (TekTerm application) and the base (wireless access point).
  +
:* Check the wireless client administration utility, SCU (Summit Client Utility, found in Start-->Programs), for the current wireless configuration
  +
:* Check the current connectivity state by checking the Network utility in Control Panel, or clicking the WiFi icon in the Notification Tray.
  +
* Lock-H is a communication problem between the gun and the server.
  +
:* Check that TekTerm server on Lucy is up
  +
:* Check that Telnet is up on Bart.
  +
:* Trace the network path from the access point to Bart.
  +
:* Check the access point cluster for any issues. Usually, Lock-H means the gun has wireless connectivity (e.g. you might even be able to remote into it using MobiControl), but the communication of data to and from the server is failing e.g. problematic roaming between access points. Since the wireless upgrade of August 2017, wireless issues are no longer expected to cause Lock-H.
  +
===Scanner does not produce a laser===
  +
* Cold boot the device, this sometimes fixes the problem
  +
* Refer to the article specifically discussing the WORKABOUT PRO G2 for comments about scanner module reliability.
  +
===User scans invalid barcode, screen stuck===
  +
* Log in to [http://lucy1.unipharm.local:8008/ TekTerm server].
  +
* Go to the Debug section. If this button is greyed out, use another browser (IE does not support this function).
  +
* Find the terminal session number that is experiencing the issue. In our environment, this is the same as the RF gun number, so check the sticker located on the handle of the gun.
  +
* Locate the section marked "Kill Session" and fill in the field with the terminal session number. Hit button.
  +
* TekTerm client on the mobile device should reset and the user may try to sign in again.
  +
=====Explanation=====
  +
* Sometimes, user activity - mostly involving scanning a bad barcode - can lock up the terminal session/screen. Since these sessions are persistent between TekTerm server and the IBM i, resetting the device and the client software (which job is only to trunk into said session) has no effect on this connection. Therefore, the actual session must be reset at the server.
  +
===Terminal session stuck===
  +
* First try to kill the TekTerm session (the session between the RF gun and TekTerm server) on lucy. Log in to the TekTerm Server web interface, go to Debug, enter the terminal number and press 'Kill Session'
  +
* If this doesn't work, or if TekTerm on the RF gun is now complaining about not the terminal ID being in use, then on a green-screen command line, issue a 'WRKACTJOB SBS(DCRF)', locate the job correlating to the TekTerm terminal (e.g. RFTER0001). Validate that it is consuming a high amount of CPU, meaning the jjob is a runaway process and therefore needs to be ended (enter 4 beside the terminal/job, and enter to end). This can take a few minutes, after which TekTerm on the gun will beep to indicate it is able to start/claim the terminal job again.
  +
  +
=Other notes / Archive=
  +
===9510 controller maintenance (Zebra)===
  +
Note: (12/16): We have migrated to the software version of TekTerm Server. See [[Information_Systems:TekTerm_and_TekTerm_Server_-_RF_gun_terminal_emulation_software| this page]] for more information regarding the software controllers.
  +
  +
While the RF guns are now covered under TRG, the (2) 9510 controllers are still under official Zebra support, until December 2017. The contact information is as follows:
  +
  +
: '''Number:''' 1-800-387-8898
  +
: '''Site ID:''' 6060011626
  +
  +
Call to generate an RMA, or use the credentials below to do it via their web portal (recommended). The rest of the process is similar to TRG RMAs.
  +
  +
: '''Site:''' [https://enterpriserepair.motorolasolutions.com/sym/servlet/PortalStart?portalLayout=yes Enterprise Repair]]
  +
: '''Login:''' norwinu@unipharm.com
  +
: '''Password:''' Our ''new'' favorite password + '2014'
  +
  +
===Reinstalling the OS (old way)===
  +
Note: The method described below is actually for upgrading the OS from an older to a newer version. It effectively wiped all data, which is why it was used prior for this purpose. Since we are at the most current version, and since the new version no longer allows a re-flash of the same OS image, this procedure will no longer work as a means of reinstalling and wiping the OS. It is left here for reference purposes.
  +
  +
This procedure should not be done unless upgrading the version of the OS, or to start absolutely from scratch with a device. If the device is returned from having just been repaired by Zebra/Motorola, this process is usually '''NOT''' required, as hardware technicians will leave the software in tact and MobiControl takes care of the rest. If you see the green uniPHARM wallpaper, the device is configured properly.
  +
  +
The Windows CE OS image used on the the 37 RF guns is located in {{unc | \\superserver.unipharm.local\tech\common\RF Guns\WindowsCE 5.0 OS Files\ | this folder}}, called "7527OS.img". The bootloader recognizes this exact filename so the file cannot be renamed. This is sourced from Psion/Motorola Solutions and is the most recent and likely last version of Windows CE for the 7527C. To perform a fresh install (wipe OS and format the persistent storage (flash disk)), follow these instructions:
  +
  +
# Hold Fn + Enter + any trigger button until the device reboots into BooST mode (similar to BIOS mode for computers).
  +
# Dock the device and connect via USB. Docking while in BooST mode makes the device appear as a "Removable Disk" drive to Windows.
  +
# Drag and drop 7527OS.img into the drive.
  +
# Undock the device. Loading of the image should commence and boot-up into the stock OS should follow thereafter. You should see a running progress meter (waterfall display) i.e. "Loading 8%".
  +
  +
Pay attention to any error messages. OS images are "signed", meaning the flashing process does not allow downgrading to lower versions (most lower versions), or using an image not intended for the device.
  +
  +
From this stage, the next step towards a production-ready device is to load the MobiControl agent. Dock the device while it's booted into Windows CE, and run "Configure RF.exe" in {{unc | \\superserver.unipharm.local\Tech\common\RF Guns\ | this folder}}. All the magic should happen soon thereafter, and the device will show up in MobiControl. Consult the [[:Category: MobiControl | MobiControl pages]] for more information regarding additional configuration.
  +
  +
===Marking the device for repair in MobiControl===
  +
  +
Note: The TRG portal has pretty good reporting tools, so the process below to track problems at the device level is no longer being used.
  +
  +
I have established a convention of leaving device notes in MobiControl when guns are sent for repair and when they are returned. Click on any device, and check the 'Notes' tab in the right panel to see any previous notes. Use them as reference for making new notes.
  +
  +
Also, there is a device group in MobiControl named 'Out for Repair'. Read about MobiControl groups here (link to be included). Devices sent out for repair can simply be dragged to this group for visibility into which devices are shipped out. Move the device back out to the appropriate group when it is returned from repair. More details later.
  +
  +
[[Category: Warehouse I.T.]]
  +
[[Category: RF Guns]]
  +
[[Category: Pages with Contact Information]]
  +
  +
  +
===RF Battery Control Table===
  +
{| class="wikitable"
  +
|-
  +
! Battery number !! In Service !! notes
  +
|-
  +
| 01 || Example || Example
  +
|-
  +
| 02 || Example || Example
  +
|-
  +
| 03|| Example || Example
  +
|-
  +
| 04|| Example || Example
  +
|-
  +
| 05|| Example || Example
  +
|-
  +
| 06|| Example || Example
  +
|-
  +
| 07|| Example || Example
  +
|-
  +
| 08|| Example || Example
  +
|-
  +
| 09|| Example || Example
  +
|-
  +
| 10|| Example || Example
  +
|-
  +
| 11|| Example || Example
  +
|-
  +
| 12|| Example || Example
  +
|-
  +
| 13|| Example || Example
  +
|-
  +
| 14|| Example || Example
  +
|-
  +
| 15|| Example || Example
  +
|-
  +
| 16|| Example || Example
  +
|-
  +
| 17|| Example || Example
  +
|-
  +
| 18|| Example || Example
  +
|-
  +
| 19|| Example || Example
  +
|-
  +
| 20|| Example || Example
  +
|-
  +
| 21|| Example || Example
  +
|-
  +
| 22|| Example || Example
  +
|-
  +
| 23|| Example || Example
  +
|-
  +
| 24|| Example || Example
  +
|-
  +
| 25|| Example || Example
  +
|-
  +
| 26|| Example || Example
  +
|-
  +
| 27|| Example || Example
  +
|-
  +
| 28|| Example || Example
  +
|-
  +
| 29|| Example || Example
  +
|-
  +
| 30|| Example || Example
  +
|-
  +
| 31|| Example || Example
  +
|-
  +
| 32|| Example || Example
  +
|-
  +
| 33|| Example || Example
  +
|-
  +
| 34|| Example || Example
  +
|-
  +
| 35|| Example || Example
  +
|}

Latest revision as of 23:42, 18 December 2020

Overview

This article discusses administration of the RF guns. It is meant to contain only procedures and instructions, while background and in-depth technical information can be found in this accompanying article. Also, refer to the RF Guns category for more articles related to this topic.

Management and administration of RF guns

Storage and inventory

RF guns that are in production are kept in 3 main areas. Their location and the number of guns recommended to be kept there are as follows:

  • Cupboard in the 'dumps' area: 20 units
  • Receiving: 5-6 units
  • Narcotics cage: 2 units

The rest should be kept as spares outside Norwin's office for ease-of-access. At any given time, there are almost always a few that are marked to be shipped for repair (if they're not already under repair at TRG). These units should be kept in the I.T. cage.

Hardware maintenance and repair

Devices that are reported broken by warehouse staff can be sent to TRG for repair. Usually, warehouse supervisors call or email the IT Group that an RF gun has malfunctioned and either bring you the device or specify where they will leave it.

The RF guns are under maintenance contract with TRG (Technology Recovery Group). Use the web portal to generate and submit RMAs. Credentials are as follows: 

TRG Web Portal
 Site: TRG ServiceHub
 Username: norwin
 Password: visionit

As there are at least 5-6 spares in inventory at any given time (if none are already out for repair), it is recommended to hold devices for repair until there are 3-4 to be sent in, as shipping is charged both ways. However, best judgment is left to the administrator as some users have a strong preference for certain devices There is indeed enough variation between the guns to warrant this, despite all technically being the same model i.e. it's not just a placebo effect. Besides if it helps them work faster and happier, why not accommodate....-norwizzle (talk)

Protocol for sending a device in for repair

The process of sending guns in for repair is straightforward:

  1. Log in to TRG ServiceHub.
  2. Start a ticket ("Submit Repairs" button), adding devices by serial number (located on a sticker at the back of the device, after removing the battery door), and describing the problem. Though not necessary, enter the gun number in the Ref. field (e.g. RF 33) for reporting purposes.
  3. Submit the ticket.
  4. Print the packing slip.
  5. Set the unit aside with the packing slip in the IT cage. If there are enough units to be sent for repair:
  1. Pack the devices in a box and include the packing slip/RMA inside.
  2. Give the box to one of the shippers and request for them to ship it to TRG (in Mississauga), or generate a label yourself, as TRG is already in the address book. I usually ship by Ground, but Air can be used for higher-priority situations.

Software administration

Software administration is done via MobiControl. It will be discussed in a separate article.

Serial numbers

Serial numbers are visible in MobiControl. They were manually entered in as a custom attribute, so it is conveniently displayed as a column.

TRG Contact Information

Melanie Drabiak is the main contact and can help with many things, from quotes on parts or general consultation. She is the first point of contact. 

Contact: Melanie Drabiak
Phone number: 440-471-8267
Email: MDrabiak@TRGRepair.com

Returning a gun to inventory

When the gun arrives there is no need to vet the repairs, and no configuration should be needed (unless the OS is wiped clean, in which case follow these instructions TBD).

  • Make sure that the gun loads TekTerm and a session profile is defined. If there is no session defined, follow these steps.

Defining a connection/session in TekTerm

There are drop downs to fill out :

  • Session name: Bart
  • Protocol: TekTerm Emulation (TESS)
  • TekTerm Server should be greyed out
  • Connection type: Direct TCP
  • Server/host: 172.30.18.115 (this is the TekTerm server a.k.a lucy.unipharm.local)
  • Terminal number: Gun number (this is very important - it does not necessarily have to match the gun number but must be unique across all active session, which is why the gun number is convenient to use).

Common Problems

Sticky keys

  • Particularly the Enter button.

Device powers off during use

This can be due to many factors, but some common ones include:

  • Loose battery door: The battery door has a foot that clamps down on a spring to signal to the device that it is installed, and allowing it to power on. A loose battery door (e.g. bad fit or missing twist-locks) or a stumped (broken) spring can lead to the device powering off abruptly.

Connectivity issues: Lock-H and Lock-B

Lock-H (yellow bar across bottom of TekTerm screen) and Lock-B (red bar) are normal if they last <1 second. However, if TekTerm is stuck on Lock-H or Lock-B, then investigate the following:

  • Lock-B is a communication problem between the gun (TekTerm application) and the base (wireless access point).
  • Check the wireless client administration utility, SCU (Summit Client Utility, found in Start-->Programs), for the current wireless configuration
  • Check the current connectivity state by checking the Network utility in Control Panel, or clicking the WiFi icon in the Notification Tray.
  • Lock-H is a communication problem between the gun and the server.
  • Check that TekTerm server on Lucy is up
  • Check that Telnet is up on Bart.
  • Trace the network path from the access point to Bart.
  • Check the access point cluster for any issues. Usually, Lock-H means the gun has wireless connectivity (e.g. you might even be able to remote into it using MobiControl), but the communication of data to and from the server is failing e.g. problematic roaming between access points. Since the wireless upgrade of August 2017, wireless issues are no longer expected to cause Lock-H.

Scanner does not produce a laser

  • Cold boot the device, this sometimes fixes the problem
  • Refer to the article specifically discussing the WORKABOUT PRO G2 for comments about scanner module reliability.

User scans invalid barcode, screen stuck

  • Log in to TekTerm server.
  • Go to the Debug section. If this button is greyed out, use another browser (IE does not support this function).
  • Find the terminal session number that is experiencing the issue. In our environment, this is the same as the RF gun number, so check the sticker located on the handle of the gun.
  • Locate the section marked "Kill Session" and fill in the field with the terminal session number. Hit button.
  • TekTerm client on the mobile device should reset and the user may try to sign in again.
Explanation
  • Sometimes, user activity - mostly involving scanning a bad barcode - can lock up the terminal session/screen. Since these sessions are persistent between TekTerm server and the IBM i, resetting the device and the client software (which job is only to trunk into said session) has no effect on this connection. Therefore, the actual session must be reset at the server.

Terminal session stuck

  • First try to kill the TekTerm session (the session between the RF gun and TekTerm server) on lucy. Log in to the TekTerm Server web interface, go to Debug, enter the terminal number and press 'Kill Session'
  • If this doesn't work, or if TekTerm on the RF gun is now complaining about not the terminal ID being in use, then on a green-screen command line, issue a 'WRKACTJOB SBS(DCRF)', locate the job correlating to the TekTerm terminal (e.g. RFTER0001). Validate that it is consuming a high amount of CPU, meaning the jjob is a runaway process and therefore needs to be ended (enter 4 beside the terminal/job, and enter to end). This can take a few minutes, after which TekTerm on the gun will beep to indicate it is able to start/claim the terminal job again.

Other notes / Archive

9510 controller maintenance (Zebra)

Note: (12/16): We have migrated to the software version of TekTerm Server. See  this page for more information regarding the software controllers.

While the RF guns are now covered under TRG, the (2) 9510 controllers are still under official Zebra support, until December 2017. The contact information is as follows:

Number: 1-800-387-8898
Site ID: 6060011626

Call to generate an RMA, or use the credentials below to do it via their web portal (recommended). The rest of the process is similar to TRG RMAs.

Site: Enterprise Repair]
Login: norwinu@unipharm.com
Password: Our new favorite password + '2014'

Reinstalling the OS (old way)

Note: The method described below is actually for upgrading the OS from an older to a newer version. It effectively wiped all data, which is why it was used prior for this purpose. Since we are at the most current version, and since the new version no longer allows a re-flash of the same OS image, this procedure will no longer work as a means of reinstalling and wiping the OS. It is left here for reference purposes.

This procedure should not be done unless upgrading the version of the OS, or to start absolutely from scratch with a device. If the device is returned from having just been repaired by Zebra/Motorola, this process is usually NOT required, as hardware technicians will leave the software in tact and MobiControl takes care of the rest. If you see the green uniPHARM wallpaper, the device is configured properly.

The Windows CE OS image used on the the 37 RF guns is located in this folder, called "7527OS.img". The bootloader recognizes this exact filename so the file cannot be renamed. This is sourced from Psion/Motorola Solutions and is the most recent and likely last version of Windows CE for the 7527C. To perform a fresh install (wipe OS and format the persistent storage (flash disk)), follow these instructions:

  1. Hold Fn + Enter + any trigger button until the device reboots into BooST mode (similar to BIOS mode for computers).
  2. Dock the device and connect via USB. Docking while in BooST mode makes the device appear as a "Removable Disk" drive to Windows.
  3. Drag and drop 7527OS.img into the drive.
  4. Undock the device. Loading of the image should commence and boot-up into the stock OS should follow thereafter. You should see a running progress meter (waterfall display) i.e. "Loading 8%".

Pay attention to any error messages. OS images are "signed", meaning the flashing process does not allow downgrading to lower versions (most lower versions), or using an image not intended for the device.

From this stage, the next step towards a production-ready device is to load the MobiControl agent. Dock the device while it's booted into Windows CE, and run "Configure RF.exe" in this folder. All the magic should happen soon thereafter, and the device will show up in MobiControl. Consult the MobiControl pages for more information regarding additional configuration.

Marking the device for repair in MobiControl

Note: The TRG portal has pretty good reporting tools, so the process below to track problems at the device level is no longer being used.

I have established a convention of leaving device notes in MobiControl when guns are sent for repair and when they are returned. Click on any device, and check the 'Notes' tab in the right panel to see any previous notes. Use them as reference for making new notes.

Also, there is a device group in MobiControl named 'Out for Repair'. Read about MobiControl groups here (link to be included). Devices sent out for repair can simply be dragged to this group for visibility into which devices are shipped out. Move the device back out to the appropriate group when it is returned from repair. More details later.


RF Battery Control Table

Battery number In Service notes
01 Example Example
02 Example Example
03 Example Example
04 Example Example
05 Example Example
06 Example Example
07 Example Example
08 Example Example
09 Example Example
10 Example Example
11 Example Example
12 Example Example
13 Example Example
14 Example Example
15 Example Example
16 Example Example
17 Example Example
18 Example Example
19 Example Example
20 Example Example
21 Example Example
22 Example Example
23 Example Example
24 Example Example
25 Example Example
26 Example Example
27 Example Example
28 Example Example
29 Example Example
30 Example Example
31 Example Example
32 Example Example
33 Example Example
34 Example Example
35 Example Example
Retrieved from "https://owl.unipharm.com/mediawiki/index.php?title=Information_Systems:RF_Gun_Administration&oldid=13304"