Welcome to Radarspotting. Please login or sign up.

February 16, 2025, 11:31:32 AM

Login with username, password and session length

New Members

New Members

You should get an activation email when you join.  If not, please use the Contact option.

Basestation issues

Started by CloudWarrior, July 05, 2022, 05:55:57 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

CloudWarrior

Good Evening
I have a number of issues which I think are probably related.

1. When i open basestation reporter it is completely empty.

2. Every so often an error message pops up basically saying 'Write to debug memo' with the last hexcode


3. I populate my SQB via Planebase PBLink, this now shows an error message
'upunker 0 position A3b()'  and fails to update any new hexcodes to the SQB

Any ideas?

Ospreyv22

Hi,

Type in your search box at the bottom of your monitor and type TASK MANAGER if your running W10, a box will open and scroll down till you see planebase or pblink,
Highlight it by clicking on it once, then at the bottom right of the box you will see END TASK, THAT WILL CLOSE planebase or pblink, and should get rid of that unpunker notice.

Ina

CloudWarrior

Cheers, that doesnt solve my problem of PBLink not being able to update my SQB. I have a feeling it may have an error in the SQB.

Anmer

You could try running an Integrity Check and Vacuum on the sqb file using an SQL editor such as SQLite Personal.

Take a backup of the file beforehand.
Here to Help.

CloudWarrior

#4
Thanks Anmer,
I downloaded SQLite personal and ran the checks
The integrity check came up with quite a few messages.
Mainly RowIDs out of order
The vacuum check came up with the message 'database disk image is malformed'
I should add the SQB file was on a USB stick
Can I repair the SQB?

Anmer

Quote from: CloudWarrior on July 13, 2022, 07:31:27 PM
Can I repair the SQB?

Not easily, if at all.

Do you have a backup sqb file prior to the errors?  How important is the existing sqb file?  Can you start afresh or do you want to retain anything?
Here to Help.

CloudWarrior

I usually back up every week, but the backed up SQB has the errors.
I dont have an earlier one. I can generate a new SQB from PlaneBase, but gutted if i will lose the original one.
I need to install a new SQB to make sure thats the problem.
As always thanks for the info.

rikgale

I'm no expert, but as long as you are not too attached to your flight logs you should be able to export the Aircraft table from the broken SQB and insert it into a completely blank Basestation.sqb.... I think. I've done that with my SQB when power has failed on my VRS Pi - rubbishes up the bottom Flight table, but I have not had a problem with the Aircraft table.

Auto updated daily ZIP files on GitHub

egnx


I have used this method to recover a corrupt BaseStation.sqb. Make sure you have a seperate copy and try the following, which is also detailed here:-

https://stackoverflow.com/questions/18259692/how-to-recover-a-corrupt-sqlite3-database/18260642



The "BaseStation.sqb" and "sqlite3.exe" need to be in the same folder, and then from the DOS (command prompt):-


This worked, but did not recover beyond the corrupt record:-

   sqlite3 BaseStation.sqb ".dump" | sqlite3  BaseStation_new.sqb


and trying this, it works with the new version of sqlite3 (beyond 3.29)

   sqlite3  BaseStation.sqb ".recover" | sqlite3  BaseStation_new.sqb

but did not recover any more rows than the ".dump" version.


Cheers
egnx

mhm

When i back up my sqb i keep the old ones with a month number. That way i can go back without starting from scratch. Found out the hard way once.
Mike
Colon Cancer Survivor for the Time Being

CloudWarrior

Thanks for your replies.
Not being IT savvy the process of repairing the sqb sounds way beyond my 'cut & paste' abilities.
I normally back up my SQB onto a USB stick every week, that way if my hard drive packs in I will have it stored externally. Ive no idea at which point the SQB failed.
Anyways while rooting around the Basestation programme I found the last time I used the back up was in 2019.
So now instead of losing a whole 15ish years of data and the personalised bits, Ive only lost 3. I can live with that.
Thanks once again.