Iridium Configuration - Prototype units

SIM Logger Configuration (firmware SIM53 V1.10)

• see SIM Logger Command Set for Ver 1.xx Firmware

• In UOK setup, check Option 8 - Enter the Sample Interval:
  1. Sample Interval should be set for 5 minutes

FETSWBD2 Power Control/Regulator Board Ver1.xx (firmware FETSWBD45 V1.01)

• see FETSWBD2 Command Set for Ver 1.xx Firmware

• In UOK setup, check PWRUP and P[123]ON and P[123]OFF settings:
  1. PWRUP=5 sets power up ON time delay to 5 minutes
  2. P1ON=5 sets power switch 1 to 5 minutes ON time each cycle (Iridium modem 4.4VDC regulated power)
  3. P1OFF=235 sets power switch 1 to 235 minutes OFF time each cycle (a total 4 hour period)
  4. P2ON=5 sets power switch 2 to 5 minutes ON time each cycle (Cerfboard 10VDC regulated power)
  5. P2OFF=235 sets power switch 2 to 235 minutes OFF time each cycle (a total 4 hour period)
  6. P3ON=5 sets power switch 3 to 5 minutes ON time each cycle (unused)
  7. P3OFF=235 sets power switch 3 to 235 minutes OFF time each cycle

  8. save settings by exiting with WRTOK
  9. check settings with a STAT command

Comms Controller Configuration

Nothing to configure!

Note that the Iridium box console cable pinout is standard ASIMET type RS232. Procomm or equivalent should be set for 9600 N81. Currently, this console connector goes to the FETSWBD Power Control/Regulator RS232 console port.

NOTE that removing power from the Iridium comms controller at anytime should be OK - a Linux shutdown is not necessary, as all software resides in FLASH EPROM on the controller CPU board.

System Operation

1. Start SIM Logger as usual and confirm AOK; power is supplied via special console cable breakout (NOT from Comms Controller).

2. Connect Iridium Comms Controller box as follows (don't connect power control cable!):
   1. IMPORTANT! First Connect Antenna!
   2. Connect SIM Logger console to Comms Controller input
   3. Connect Comms Power (6-pin cable)
   4. this will initiate a complete acquisition and satellite transmission cycle

3. Once above is successful, you should get a message from the system in your Iridium mailbox within a minute or so, typically.

4. The comms controller is powered up every 4 hours for 5 minutes using the settings shown above. If you have ethernet access thru the open cover of the comms controller, you can ssh to the Cerfboard if you wish. This is not necessary to operation, however.

5. that's all......

System Test

The prototype system currently uses the Cerfboard serial console port (/dev/ttyS0) as the SIM Logger port. The other serial port available (/dev/ttyS2) is dedicated to the NAL Iridium modem. The console connector on the grey box is temporarily connected to the FETSWBD2 Power Control module board serial console.

System testing with the cover off the grey box is possible by using a laptop PC with a serial port connected to the FETSWBD2 console (using Procomm at 9600N81 - ASIMET style), and an ethernet connection from the ethernet port on the Cerfboard to the laptop PC. An ethernet crossover cable can be used directly to the laptop PC, or straight cables via an ethernet hub. Send a test command to the FETSWBD2 module to turn all power ON in the comms controller box. After about 30 seconds, you should be able to ssh into the Cerfboard at 128.128.21.45 (assuming your laptop is also set up for a WHOI IP address). All the operating stuff happens in the /root/iridium/ directory - you should see the current intermediate files here. The redundant (and ASCII, not binary as sent thru Iridium) data files are stored in the /media/cf1/ird/ subdirectory.

When done "playing", you must exit the FETSWBD2 'T' test command by sending an ESC character; you should see a "done!" message. Send a 'D' command to see the current ON/OFF status of the FETSWBD2. If in doubt, pull the main 6-pin power connector to the grey box to restart everything (this will initiate a transmission cycle so you can confirm all is working