issue: Skydel instance crashes Most probable reason: If RINEX GLONASS navigational messages file was imported into your configuration Skydel crashes with 100% repeatability 1 hour before last record in that RINEX GLONASS navigational file
Steps to reproduce:
start Skydel
create completely New Configuration
add GLONASS G1 signal in Output 1 settings
GLONASS - > General
Import RINEX Navigation Message file “glonass_ephemeris_21.3.txt” from /Documents/Skydel-SDX/Templates
Start time of Scenario will be changed to cover Date in RINEX file (31.03.2020)
As cherry on the cake:
if you have created a new Configuration and Imported Rinex GLONASS navigation file you cannot delete it from your configuration.
Clear button is not working here!!
Thank you for the detailed bug report, I was able to reproduce the issues and created two tickets on our side.
I will notify you when the bug fixes are available in a Skydel release.
I was trying to simulate live sky in the skydel, unfortunately, I was not able to run GLONASS Rinex file based on the current UTC time. Which means, when I upload the recent Rinex which I have downloaded from the CDIS website, Skydel will show the below error.
Since I need to run the simulation in the current time, I was unable to run the same. Because the error says "Check simulation start date matches the RINEX File, also the simulation time must be after the record and 1h 15 before the last record. Typically, start time in UTC should be in the interval (00:15…22:30).
I tried editing the RINEX file to the current time, still the Skydel is not accepting the same.
I am trying to simulate the live sky constellations for GLONASS using the RINEX file that is available from the CDIS. When I use the file for GPS and Gallileo it works fine. But when I use the RINEX file for GLONASS I am unable to start the simulation at current time. As soon as I upload the file, the time will be automatically changed and also I can only put a time 1:15 before the last record.
Right now we have some limitations with GLONASS which come from the fact that GLONASS ephemeris are not Keplerian. We have work in our backlog to improve these limitations, but I can’t give a date as when it will be available.
The best you can probably do today is import the most recent GLONASS almanac and we will generate the ephemeris data during the simulation based on this almanac (don’t import any ephemeris for GLONASS). It should be quite close to the real ephemeris for short simulations.
Thank you for your response. Could you provide any link for downloading the almanac for GLONASS, every time I search for the same, I find an FTP link which cannot be accessible and I tried to manually edit the almanac file with the values from ([https://glonass-iac.ru/en/ephemeris/]) and it is not working as well.
Thank you for your valuable support. I have installed the same and downloaded the agl file. Unfortunately, when I run the Skydel simulation at current UTC time, the constellations are different.
I just tested myself for your date and time, with Skydel’s default location as well as the almanac for that day downloaded from Studio View. I then compared with the Trimble website, the sky plot were identical:
As per your questions please find the below answers.
Skydel version - 23.5.4
I am using ublox receiver EVK-M8L and I have compared the Glonass constellations with the live sky from this receiver
When I tested I used the file named MCCT_231010.agl
Today I tried the experiment again with the Trimble’s skyplot, however the receiver live sky polt and Trimble’s sky plot almost matches and the Glonass constellation in the Skydel doesn’t match with them. The file name of Glonass almanac for the simulation is MCCT_231015.agl
The file MCCT_231015.agl is for the 15 October 2023, not for 15 November 2023.
Make sure you download the file for November by validating it starts with MCCT_2311.
