Menu

Troubleshooting Checklist

If you are running into trouble configuring and running RIC, use the following checklist to confirm everything is set up correctly.

Note: `~` is a shorthand that refers to your home directory.

Note: Examples use the MTP instrument as an example. You should replace that string with your instrument string as described in the first section.

~/.ric/Proxy.ini

  • Did you change the ProxyID near the top of the file to the string that you are using to start your UDP packets?
    • For example, if your UDP packet is “MTP,20260707T212900,99,99,99,99”, your ProxyID line should be 
      ProxyID=MTP
  • Did you change the last line of .ric/Proxy.ini to point to a .ini file with the name of your instrument? 
    InstrumentFile=MTP.ini

~/.ric/Instruments/SAMPLEINST.ini

  • Did you rename SAMPLEINST.ini in .ric/Instruments to the .ini filename created in step 1? 
    SAMPLEINST.ini -> MTP.ini
  • In the renamed .ini file, did you change InstName to the name of your instrument? eg InstName=MTP
  • Did you change the ID to the name of your instrument, eg 1\ID=MTP
  • Did you change UserIncomingPort and UserDestPort to the ports provided by the RAF SEs?

~/.ric/Certs

  • Do you have eol_ric.crt and a .key and .crt file that are named the same as your instrument ID? 
    homedir/.ric/  <- where homedir is /Users/<username> on a mac, or C:\Users\<username> on Windows
   Proxy.ini
   Certs/
       eol-ric.crt
       MTP.crt
       MTP.key
   Instruments/
       MTP.ini
  • Do the certificate files contain certificates? Confirm that the file sizes aren’t zero.

For you control software on the ground:

  • Are you sending to the correct port and listening on the correct port?
  • Are you sending your packet to 127.0.0.1 (localhost)

If you are using LabVIEW as your control software, do NOT send to the RIC port. Instead open any other port, eg port 0. Contact the RAF SEs if you would like a copy of a simple example LabVIEW 2018 program to test with.

For your software on the aircraft:

  • Are you sending packets to 192.168.84.2
  • Are you receiving at your assigned instrument IP address?
  • Are you sending to the correct port and listening on the correct port? (Opposite of on the ground)