Virtual Radar Server Forums

agw wrote: ↑

Fri Nov 09, 2018 5:46 pm

I'll retire the airline and that should break the chain.

Is this done? Still have the problem with the APF routes.

/M

ModeSmixer 2 has auto-sense on inputs, but afaik it does not understand CompressedVRS. But, you are not feeding it Compressed VRS, you are connecting to 33033 where it should find Basestation format? And you are also connecting to 192.168.0.18:30002 where it seems to find something in BEAST format, ...

Ongoing problem confirmed by other users.

At 2019-02-03 14:27 it deleted the OP code and Registered Owner of 4AAA12.

Since 2017, 3 out of 7 helicopters from the same owner (Swedish Police) has had the Reg Owner reset to something coming from the main database.

Please try to find the problem.

/M

Could your ISP have started using CGN so you are no longer getting a real IP from them?

Check WAN IP in router and see if it matches what you see on whatsmyip.com

/M

Hi Hans, First, check that your friend hasn't ticked "Hide from Website" or "Merge only" in the Receiver setup. Second, you write that both sides has the other ones IP address. That is not how it should work (unless you are talking about "Access control", but disable that for start. One side connect...

OK!

While duplicates seem to be allowed with special limitations, IATA currently only list Amapola under HP, that is why I couldn't find the connection.

(AWE seems to have aquired HP from Hawaiian Pacific way back in time, according to Google.)

The route lookup finds AWE routes (US Airways) when no suitable APF route is found.

APF = Amapola Flyg (IATA code HP)

AWE = US Airways (IATA code US)

I can't see why, they have nothing to do with each other.

/M

It would be great to be able to send "Trt", transponder type in the JSON receiver.

I also propose new definitions of transponder types;

7: APRS/FLARM/Pilotaware
8: JAERO/Satcom
9: AIS


in addition to current

1=Mode-S, 2=ADS-B (unknown version), 3=ADS-B 0, 4=ADS-B 1, 5=ADS-B 2

Please don't bump threads. This has been fixed in the latest preview. Excellent thanks. Sorry for the bump, but if You please acknowledge that there in fact is a bug, then I will happily wait for a fix. But when we don't seem to agree of it's existance, its not easy to know if it's on the "fix list...

Ongoing problem.

Op codes disappear, Operator names gets changed back to outdated info.

/M