Satsio Support

Obtaining Ephemeris Data in Future

When the S3satcom Ephemeris server is not available, a SATIO will “fall back” to the next available source of ephemeris data. This is normally Celestrak. The only noticeable effect of this is a few seconds delay while the request to the S3 server times out.

To remove this delay - In the Web browser interface:

  • Select the Maintenance Menu – it will default to the “ACU Config” page
  • Click the “Edit” button (if requested enter the admin password and then click “Edit” again) – the caption of the “Edit” button changes to “Cancel”
  • Change the contents of the “Sources for Geo.txt” box and remove lines containing either “” or “”
  • Ensure that there is a line 
  • Click the “Save Changes” button
  • Clicking the “Get Geo.txt” button will now retrieve the ephemeris data directly from Celestrak


The “ACU Config” page will then look something like this:

NOTE If you have made any special arrangements to obtain the ephemeris file and place it on a private internal network (e.g. for security reasons) then you will need to make sure your IT department use the 'celestrak' address as their source rather than “” or “”.

Password Issues with S3 embedded software

The major web browsers have recently changed the, default, way that they handle “cookies”, or more specifically third-party cookies. The S3 SATSIO, the S3 De-Ice controller, and the S3 Waveguide Switch controller all use cookies to manage password tokens and so when the web browser is updated passwords will fail to work.

This is specifically related to using dotted IP addresses for the SATSIO in the browser, when the browser treats all cookies as “third party” cookies.
A software update is available for the S3 products which fixes this problem – please contact the factory to obtain it using the options on the contact page. Note that S3 Satcom will need to know which product you need the update for and the current software versions (found on the About tab on the web browser interface – which will still work).

Updating the software will result in a permanent resolution of this issue but for an immediate fix, there are several work-arounds that will restore functionality. Each work-around has its own advantages and disadvantages and these are set out below - you should only need to apply one of these:

Add the equipment host name/address to the networks DNS server

• Fixes the problem for all browsers

• Not many sites run a DNS server!

Add a fake hostname to the Windows hosts file

• Fixes the problem for that PC

• Since the hosts file is a Hidden System file it is not easy for a casual user to change
• Has to be done on each PC used to access the S3 product

• Run Notepad.exe as an administrator (type Notepad.exe into the start menu, right click the entry that appears “notepad.exe” and select “Run as administrator”)
• Go to the “File” “Open” menu
• In the Filename box type “C:\Windows\System32\drivers\etc\hosts”
• Click “Open”
• Add a line similar to the following – replacing the IP address with the actual address, and replacing “” with the domain name you want to use (NOTE that this must be a syntactically correct URL, for example it must end .com, or etc)
• Save the file
• In the web browser navigate to (instead of

Totally disable all passwords in the S3 product

(This is still possible, as it uses a direct password check instead of a token stored in a cookie).

• Fixes the problem for all browsers

• Anyone with browser access can make changes to the unit

• In the S3 Web interface go to “Maintenance” and “Password Config”
• Tick both “Disabled” boxes
• Enter the current Admin password
• Click “OK”

Enable third party cookies in the browser

• Fixes the problem
• Allows password control over the equipment

• It is applied universally and not just for the S3 product
• Has to be done on each PC used to access the S3 product

© 2022