Whooping

The Fuso Szulc is now parked in the same location for almost 4 months.
In the dry river bed of Punta Boca del Salado, Baja California, Mexico near the rancho of the Gonzalez family and the Sea of Cortez.

For all those days the disk on the roof of the Fuso Szulc has been pointing to the SatMex 5 satellite using Motosat as a company to have access to the Internet.

This has been going very well.
Of course there is the FAP to take into consideration.
FAP stands for Fair Access Policy.
There is a limit to the usage of downloading and uploading Megabytes and if this is not respected, one is put on an access speed of a turtle for 24 hours.

But yesterday morning suddenly the Datastorm Satellite System failed totally.
No more connection to cyberspace and therefore the world.

These problems with the Datastorm Satellite System are not occurring for the first time.
Actually, as long as this system has been used, regularly there are problems.

By itself this is not too bad, but what is very inconvenient is that it is often very complicated to find out what exactly is wrong.

When the Datastorm Satellite System doesn’t work, user gets to see what is the problem.
Yesterday it said:
“RXCode 4, receiver locked to the wrong network”.
That was puzzling.
How could it be that suddenly user was locked to the wrong network while 6 hours ago the Datastorm Satellite System was working “no problema”?
It was also explained that it could be an administrative problem with Motosat.
Or that the satellite had been falling out of the sky.

Being without Internet has consequences.
Unable to publish the daily blog.
Unable to run the business.
Unable to make phone calls.
Unable to receive and send e-mails.
Unable to know what is going on the world.

Yesterday, most of the time was spend trying to solve the Datastorm Satellite System problem.
A trip was made to a small restaurant about half an hour from the Rancho where they also have Internet through a satellite connection.
Mail was sent and received, the blog published and the Service Desk of Motosat called by VOIP to hear a possible solution.
But the connection was too slow.

Later that afternoon a visit was made to the neighbours who also have a satellite connection.
And again from there a phone call was made to Motosat.
A bad connection again but at least it was heard that it could be a matter of the settings.
Not of the Rxcode 4…

Hence, this morning a new effort was made to try to solve the problem.
It turned out that in the settings one little piece of information had to be changed.
And next: wwwwhhhhhooooooppppssss, back on the Internet and in life and business.

Now the question is, how come that this happened?
That one small piece of information got changed?
We will ask Motosat.