Packets yes. Beacons?? Not sure.

[BSDGuyShawn]

I am getting interesting data from what I believe is one of the VR3X satellites. I am currently monitoring B & C using TinyGS.

The packets below are from my station monitoring VR3X-B. Packets for this ground station should be visible here as well:

VR3X-B:

• https://tinygs.com/station/BSDGuy02@798793531

VR3X-C

• https://tinygs.com/station/BSDGuy02@798793531

Any help is appreciated:

Date is March 4th, times are in PST: 17:11:46 Packet (198 bytes): 17:11:46 70617e101ee346cf3c3a064b9c414e94cb0a5a3a61a5e67494167aad7b10c8788b613d075ce24e4273d6db8561d7d39cfdabac6d02083986734ae57594fe09b5af0dd9184343ab0506ad32b0fef311bed57992ef7ed8adc19c036e7c4ea3a958eb179db6abb8ac3ba69b43fba8523de93a7fc4338d2a2a4150d576be0c0bb20 17:11:46 [SX12x8] RSSI: -131.750000 dBm

18:46:47 Packet (47 bytes): 18:46:47 331ca0f2d3e5b23857e0153ea7d2910020b9164c77b7f880cbc12398b2c7744635969024cee5f21a9612bf3355af4e 18:46:47 [SX12x8] RSSI: -135.000000 dBm

18:49:06 Packet (24 bytes): 18:49:06 f98f385641fa0979fe8c3a6981d7802ec3ed1aebe8e6e532 18:49:06 [SX12x8] RSSI: -135.250000 dBm

19:38:57 Packet (148 bytes): 19:38:57 ad8fc8bb2bccc0c63ef472736e530687dfcd5e9ca53210f0b828aa934cd7bc48b83c6c02bfc0b00a126095ea9d709741832f8371d0eb9d3eb07b82d2c20a7bad9a179e04587988b0c294bdfb80541187943f769c24c6ce43fc5add1790c092892779561e43797325e3c6246e66afdbf0dde146f3bfc8bd03e55b415e99c69d4 19:38:57 [SX12x8] RSSI: -135.000000 dBm

20:45:55 Packet (44 bytes): 20:45:55 ca1f39f06de88fdffa2c14f3fb588197e6be1710044b9d7bfef1def7a29ae35142dab57a449124356e6510d3 20:45:55 [SX12x8] RSSI: -134.750000 dBm

[maholli]

@BSDGuyShawn first off, thank you for listening for VR3X. VERY appreciated :)

Looking at your packets, they appear to be bogus decodes. I've seen this happen more often on radio modules with 70cm front-end filtering (like modules designed for the 433 MHz band, for example) being used at 915 MHz for VR3X. The RSSI values also support this theory.

That being said, your packet at 18:46:47 is ALMOST a valid VR3X packet... So I will investigate this more and let you know.

Thanks again!

[patrick-rt]

I think I also have corrupted data from VR3X-A.

Station: https://tinygs.com/station/DE_RT_Hohbuch@681171952

Data: 6e7a4f3eebce5acf1b6ca2dcef3f92f865b0ac1e0a3900e653f164f9100e0795a63905e590ae940852d5a61bc5304dfefa533b096adbeb1ac87fac40286fa3918625d0166ea469f5a6021b876523f5058f30c824ee6512cb620d49c4be9cc68e17363b81c816becab369e20c25a98f9db3b64c8fd5cad18626e5159caef802a5b85cdb7872de6504ad082bbb428705c2c6b9f32a1058bda3f81b81985289183ed43203ae10

As far as I understood the python code, the '7a' part is the problem (should be '3A').

Hardware: TTGO T-Beam with LoRa32 868/915MHz and cheap antenna

[maholli]

@patrick-rt thanks for listening for VR3X! I too have been receiving at least one corrupted data packet during (and only during) VR3X passes. I'm investigating now and will let you know if I find anything.