Symptom

The user is presented with an “invalid receiver” message in the JET Device Configuration dialog after successfully finding the JET receiver.  The user is not able to continue with the configuration.

Cause

This issue is caused by corrupt information in the Bluetooth.cfg and/or rc.local files.  These configuration files are used at device startup and, if the proper information is not present, the device will not function as expected.

Resolution

Depending on what information is missing or corrupted, several options exist to correct the issue.  To determine what information needs addressed, log into the JET receiver using the Wrapfinder.exe application (attached).

1. With the JET receiver connected to the PC, launch the Wrap Access Server Finder (wrapfinder.exe).
2. You may be prompted by Windows to unblock the port in order to continue.
3. Ensure the desired Receiver (Wrap) is shown in the list of Wraps. If not, communication must be established before moving forward.

4. Click the desired Wrap’s serial number, then click the Connect button.
   The WRAP Access Server page should launch.

5. Click Setup to log into the web server with the following credentials:
   1. User name: root  
   2. Password: buffy   
6. Click OK to continue, if prompted.
   The Access Server - Setup page should appear.

7. Click iWRAP settings.
   The Access Server - Setup - iWRAP page should appear.

8. Click Edit startup script.
   The Access Server - Setup - iWRAP - Edit startup script page should appear.

9. Take a print screen of all the text that is listed and email this information to Support. Note that you will need to use the scroll bar on the right hand side of the menu to capture all text.

Resolution Option 1

It is recommended to send the receiver back to the factory to be reprogrammed if the “Invalid receiver” message is posted.  This is the only option guaranteed to produce a properly functioning unit.  However, if circumstances exist where the device cannot be sent back immediately to be reprogrammed, the option to reenter the correct startup script is available.

1. In the Access Server - Setup - iWRAP - Edit startup script page from above, scroll down in the text and locate SET BLUETOOTH NAME "DSI_x…” where x represents a unique device ID.
   
   NOTE: Two entries may be listed as SET BLUETOOTH NAME "x…”. One entry must contain “DSI” and the unique alpha-numerical ID string associated with that wrap (example, SET BLUETOOTH NAME "DSI_2382302892_$P”).

2. If SET BLUETOOTH NAME "DSI_2382302892_$P” (example ID) exists, delete all of the information above this entry and copy the following information above SET BLUETOOTH NAME “DSI_x…”.
   
   # iWRAP settings

    

   SET CONTROL PASSWORD "$1$df3cad76$.OzEgoX.rbF6lMZDww4ad0" --LOCAL

   SET BLUETOOTH LINK 4

   SET BLUETOOTH ROLE 1

   SET BLUETOOTH PAGEMODE 3

   SET BLUETOOTH READABLE 1

   SET PPP CHANNEL 0

   SET PPP AUTH

   10101 SET PPP IP 192.168.160.0/26

   10102 SET PPP IP 192.168.160.64/26

   10103 SET PPP IP 192.168.160.128/26

   10104 SET PPP IP 192.168.160.192/26

   SET PAN ENABLE 0

   SET BLUETOOTH CLASS 100108

   SDP ADD PNPINFORMATION 0 "Bluegiga Access Server"

   SET BLUETOOTH NAME "W$S_$p"

   SET BLUETOOTH AUTH * ""

   SET PPP DEFAULTROUTE "0"

    

   # set unique DSI name

3. Next, delete all the text below SET BLUETOOTH NAME “DSI_x…” and replace it with the following.
   
   # divide the rf spectrum among radios

   10101{

   hci 3f0c0a55555555005555555500

   }

   10102{

   hci 3f0c0a00000000FF0000000000

   }

   10103{

   hci 3f0c0aAAAAAAAA00AAAAAAAA00

   }

    

   # reduce supervisior timeout

   SET BLUETOOTH ROLE "1" "F" "1F40"

    

   SDP ADD OBJP 3 "Object Push"

   SET BLUETOOTH LISTEN 3 "/usr/sbin/obexserver --bdaddr $b --prefix $b-$P-" 256 5

   SDP ADD FTP 3 "File Transfer"
   
   
4. Click Save to save the updated text and return to the Access Server-Setup menu.
5. Click Advanced settings.
   The Access Server - Setup - Advanced page should appear.

6. Click System startup script (/etc/rc.d/rc.local).
   The Access Server-Setup-Advanced-System startup script page should appear.

7. Delete the text in the rc.local file and replace all text with the following:
   
   

   #!/bin/sh

    

   # This script will be executed *after* all the other init scripts.

   # You can put your own initialization stuff in here if you don't

   # want to do the full Sys V style init stuff.

    

   # set power down from 100m to 10m

   b2b_class2

    

   # turn off leds

   echo abcde > /dev/led
   
   

Resolution Option 2

It is recommended to send the receiver back to the factory to be reprogrammed if the “Invalid receiver” message is posted.  This is the only option guaranteed to produce a properly functioning unit. 

1. In the Access Server - Setup - iWRAP - Edit startup script page from above, scroll down in the text and locate SET BLUETOOTH NAME "DSI_x…” where x represents a unique device ID.
   
   NOTE: Two entries may be listed as SET BLUETOOTH NAME "x…”. One entry must contain “DSI” and the unique alpha-numerical ID string associated with that wrap (example, SET BLUETOOTH NAME "DSI_2382302892_$P”).
   
   
2. If SET BLUETOOTH NAME "DSI_2382302892_$P” (example ID) does not exist, the unit must be reprogrammed as this ID is unique to each receiver and is a calculated value.