The messages themselfs only contain Ground Station ID's, not names. PC-HFDL shows a new Ground Station as "Unknown" The latest System Table as well as a readable version of it can be found in the FIles section. In between updates you can find that an aircraft is requesting the Ground Station to send the System Table. When a new system table becomes available the ground stations will transmit this new table and PC-HFDL as well as MultiPSK will capture and store this new table. Do not open the pchfdl.dat file! The "DB = 51" in above message indicates that the ground station is using system table version 51 (hex 33). The System Table is stored in a coded format the pchfdl.dat file in the PC-HFDL/Configs directory. The messages only contain numbers, not frequencies so PC-HFDL as well as MultiPSK use the system table to translate this number to a frequency. Then your program is not using the correct system table. GND 10:02:44 UTC SHANNON - IRELAND DB = 51 SV = 0 GS UP HEAVY OFFSET 2 SHANNON - IRELAND UTC LOCKED Active freqs (Hz) 100 KHz SANTA CRUZ - BOLIVIA UTC LOCKED Active freqs (Hz) 113 KHz KRASNOYARSK - RUSSIA UTC LOCKED Active freqs (Hz) 8886 KHz GND 10:02:44 UTC SHANNON - IRELAND DB = 51 SV = 0 GS UP HEAVY OFFSET 2 SHANNON - IRELAND UTC LOCKED Active freqs (Hz) 4 2 SANTA CRUZ - BOLIVIA UTC LOCKED Active freqs (Hz) 6 3 KRASNOYARSK - RUSSIA UTC LOCKED Active freqs (Hz) 3 PC-HFDL shows numbers instead of frequencies You can do that after the program is started, but it is much easier to start the program using a command or batch file which contains the following line: start "" /affinity 1 "PCHFDL.exe" This will start PC-HFDL and assing it to core 0. This can easily be fixed by assigning only one core to the program.
Planeplotter timeout Pc#
When running on a multi-core PC the logfile can/will contain corrupted data. Examples: and after 9 days without squitters: PC-HFDL Logfile contains corrupted data This also means that when you don't receive Squitters after midnight UTC the clock will continue. Every Squitter message will correct the PC-HFDL clock, but NOT the PC clock. After starting PC-HFDL the first correctly decoded Squitter message will set the clock in PC-HFDL. The message time is based on Squitter messages from the ground station. PC-HFDL Message time is 00:00:00 or greater then 24:00:00 When the frequency is off by 90 Hz it will not decode. You are probably not exactly tuned to the frequency. PC-HFDL showing data burst in the spectrum but no decodes Planeplotter shows a new Ground Station as "Unknown".PC-HFDL shows a new Ground Station as "Unknown".PC-HFDL shows numbers instead of frequencies.PC-HFDL Logfile contains corrupted data.PC-HFDL Message time is 00:00:00 or greater then 24:00:00.PC-HFDL showing data burst in the spectrum but no decodes.
Planeplotter timeout license#
If other people are interested, I will go through the trouble of packaging it and accommodating the license requirements of the various libraries. I am testing it out to make sure that there aren’t any major crashes with it.
Planeplotter timeout windows#
I seem to have been successful in creating a windows build of the latest dump1090-mutability. This is what I currently use, but I was interested in benefiting from the enhancements that obj has added to dump1090-mutability. In my initial searching for a windows version of dump1090, I found a relatively old build that runs on Windows (i.e. This is then fed to a VM running piaware/dump1090-mutability. I may be a special minority, but my main dongle is attached to a windows computer. I have been running this version to feed to flightaware for a few weeks and saw an immediate increase in messages and planes.įor those that are interested, the majority of the effort required to compile dump1090-mutability on windows was put into finding windows libraries that would provide the timing functions typically used in linux. This version has all of the features that have been added to dump1090-mutability: -phase-enhance, -oversample, etc. Edit: For those that are interested, my windows compile of obj’s dump1090-mutability is here:
0 kommentar(er)
