Changing User Tag

[plevtls]

Hi all

I have my SBS 1er set up in Registrions mode, so anything I require as a frame shows as Required, and any scrapes show as R Required. I want to change the user tag of R, to Reg if possible, and have edited all the R user tags in my SQB to Reg with no problem.

The bit I can't get working, is when a new Hex is added to my SQB which is required as a scrape, it will automatically appear as R. From the info I've read so far, it appears I may need to change something in my .ini file, so it will appear as Reg, but I'm not sure where, or what changes need to be made (or if it's even possible!).

Can anyone point me in the right direction?

Cheers

[Anmer]

As far as I understand, the User Tag is only a "free text" field.  In other words, to be used as one prefers.  The BaseStation software doesn't interact with this field or the data entered.  I could be wrong.

Can you post some screenshots showing how you currently use the User Tag field?

[plevtls]

Hi Amner

Yes from my Basestation screen you can see the side panel with seen, or blank (required), and also Reg (this is what I added manually), for scrapes.

When I pick up a new SQB through PB Link, if it is required as a scrape the user tag automatically populates as R, when ideally I'd like this to populate with Reg without having to manually change it.



[Attachment deleted by Admin to save file space]

[Anmer]

Thanks.

So this is to do with PB Link?  I don't use that software.  What's a "scrape"?

[plevtls]

Hi Amner

It's not driven by PB Link, as I've used other software, which has done the same thing.

A scrape is when you've seen an aircraft before, but with a different registration.

[Anmer]

I'm not sure I understand the underlying procedure?

I'm assuming you manually edit your sqb data to add "Required" to the User Tag field for aircraft you've not seen?  When seen, do you manually remove the "Required" data?

If the aircraft has been re-registered but seen prior to this, do you also manually edit the User Tag field and add "R Required"?

How is this bit happening?

"The bit I can't get working, is when a new Hex is added to my SQB which is required as a scrape, it will automatically appear as R."

How is the new Hex added and what "automatically" makes it add the R to the User Tag field?

[plevtls]

Everything is done automatically via the link software, which updates my SQB to reflect what's in my seen/required database, so there's no manual intervention by me at all.

This bit How is the new Hex added and what "automatically" makes it add the R to the User Tag field? I suspect is what I need to know.

[Anmer]

Thanks.

I may be wrong but it appears you are using PBlink to import data and set the User Tag field.

Are you using Planebase too?

Maybe someone who uses PBlink can help.  It's definitely not a BaseStation.ini file feature.

[plevtls]

Yes that's correct. No worries, thanks for the responses Amner.

[Triple7]

I use both PlaneBase and PBLink, but not in the same way as you do. I am struggling a little to follow what's happening.

You say you obtain a new SQB via PBLink but as I don't use that option, I'm not sure what happens to that DB, but does it somehow get updated from your existing SQB file, i.e. so it populates the fields with information about aircraft you have seen / require etc?

I viewed a single aircraft in PBLink - the screen grab is below. You can see in my case the user Tag is 'N' = needed this is being determined from the UserTag field in my SQB file. Therefore the 'R' in your case must also be coming from your SQB file. The question therefore is, did you specify somewhere for the file to be populated with an 'R' or is the new SQB importing data from your existing one?

Finally, you can edit the field in PBLink to whatever you like, but that is a manual operation. You could also run an SQL script in something like SQLite Expert to re-write all the "'R's" with "Reg" but that too is a manual operation.

Not sure if any of this helps but it would be good to get a bit more background on how your new 'Pre-populated SQB' file actually gets updated with data specific to you.

Tim



[Attachment deleted by Admin to save file space]

[plevtls]

Hi Tim, I'm not sure if yours would be set up for frames or registrations, but mine is similar to yours in that anything flagged as interested shows as needed, Because I'm on registrations, whenever my SQB updates a new Hex that is Required but as a Reg only, my User Tag populates as R, so the tag will then read R Required, rather than Required. Normally if the aircraft was required as a frame, my user tag stays unpopulated, but the display tag will show as required.

As I mentioned it's been set up this way for around ten years now (and I didn't set it up initially) so I'm unsure as to where the R detail is coming from. As you mentioned I have the option of a manual edit, so I think I'm just going to stick with that for simplicity.

Cheers

[IanH]

I'm assuming that the update to the SQB database is performed via PlaneBase.

That downloads additions to the database and then the "import log" function combines the new data with existing customisations. Works for me in that my "interested" stay like that.

The subtleties of "scrapes" versus "registrations" are a new concept - in the "old days", we had no idea what was going on. I'm sticking with "registrations".

These days a "scrape" is immediately apparent on the internet but why bother diferentiating?. An  example from recent observation is OO-SFT - two different aircraft of same type. I would have simply assumed it had come back from a sale/lease!

[s92driver]

plevtls, your sqb file is being updated by PBLink when you pick up a new ModeS code.  PBLink uses the data in Planebase to do this.

I don't use the User Tag field in my sqb, so cannot assist with your specific request i.e. how the "Personalise User Tag" option in PBLink works.

I suggest you ask your question on the Planebase forum :-)


Steve