Weekly Newsletter - July 13, 2025

Highlights

General

• G4lile0 announced the new dynamic satellite map at tinygs.com, highlighting its real-time telemetry data, interactive satellite selection, enhanced sound experience, and full-screen mode. 🔗
  
  
• punarinta shared the /weblogin command. 🔗
• Eduardo asked about accessing the node’s logger, noting only an HTTP port and no telnet or SSH. Later, clarified the question, focusing on accessing MQTT packets, particularly the JSON file containing information like vbat, mem, and RSSI. Connected to the TinyGS MQTT server using MQTT Explorer and the certificate found in the source code after initially facing TLS errors. 🔗
• Helmi clarified that there isn’t a special logger on the board, but rather a MQTT server operated by TinyGS that holds all received packets. 🔗
• ubabematrix asked about alternatives to Telegram accounts for MQTT login, as they are planning a TinyGS node workshop for kids and cannot ask them to create Telegram accounts. Stefan/OE6ISP suggested registering a Telegram account for themselves and assigning the kids’ stations to it, and mentioned having linked 10+ stations to a single account. G4lile0 mentioned that a new non-Telegram registration is ready and will provide details via DM. 🔗
• G4lile0 informed that the new non-Telegram registration is ready and that they will send a DM with the process to register by e-mail. 🔗

Technical Problems

• Stefan/OE6ISP reported that some Connectas are missing from the supported list, noting packets received from #8 which wasn’t listed. 🔗
• Phil asked if it is possible to receive Starlink signals and how. 🔗
• rj45jack raised a question about why their TinyGS station seems to ignore satellites passing directly overhead, while actively listening for satellites that are much further away. As an example, Tianqi-20 passed directly over their station while it was listening for FossaSat-2E19, which was still 2-3 orbits away. They confirmed that the timezone and lat/long are correctly configured and mentioned their station is fundygs_433, suspecting a delay in the web-portal data compared to the local web-gui for the GS. 🔗
• Stephen reported issues with the TinyGS website, specifically not being able to see their GSDurango and encountering an “Error loading packets” message. 🔗
• CT1DHM_CR5M asked G4lile0 for help, asking what to do. 🔗
• G4lile0 mentioned that after 48 hours of disconnecting an old board, a new one with the same name can be added to automatically transfer all statistics. 🔗
• Manny mentioned having a station up for four years but potentially losing access to the registered email and asked for advice. 🔗
• ipeeoften stated having the MQTT username and password but not knowing how to link it to the Telegram account, and confirmed being able to access the local page but unable to manage the station online. 🔗
• G4lile0 addressed account access issues, advising against requesting web login through the Telegram bot for those who have lost access to their old accounts. Instead, suggested requesting web login directly within the Local dashboard to link their email address. If the old credentials are still available, they can be used; otherwise, the station name should be provided to update the total amount of received packets. 🔗
• Nypon reported being logged in with old MQTT credentials and having stations online, but needing guidance on using the local dashboard and reported issues with the !w command, receiving a message that the command is not supported in the web serial console. Later, after updating the firmware, the user encountered a problem where the weblogin page displayed incorrect stations and user IDs. 🔗
• G4lile0 provided assistance to users experiencing issues with web login, explained that for TinyGS updated to this year’s firmware, users can type !w to receive the weblogin. Advised the user to request the weblogin directly in their TinyGS local dashboard, shared photos to guide the user, offered to send the latest firmware that supports the command, and instructed to use the “Upload new version” option. 🔗
  
  
  
• ipeeoften asked about obtaining a weblogin and reassociating a station with the Telegram Chat bot. G4lile0 responded that after requesting the weblogin, users should add their email to request the weblogin using it, since there isn’t a feature yet to change the Telegram ID. 🔗

Beta Firmware Testing

• Stefan/OE6ISP reported amazing FSK conditions with over 1200 packets received on his FSK-only station using beta-firmware. 🔗
  
• Notsure7 explained that a .bin file wouldn’t be useful because the firmware is customized manually for the offset and suggested building from source to modify and contribute back. Later mentioned having to revert some changes to get it working on the C3. 🔗
• Stefan/OE6ISP clarified that the latest builds now use synchronization to NORBY-frequency, eliminating the need for hardware-specific calibration and incorporating an improved tracking algorithm. 🔗

Antenna Building

• Notsure7 shared a photo of a dual-band QFH antenna, noting it’s almost done and easily modified back into 137/144 only. 🔗
  
• Stefan/OE6ISP mentioned that it’s LHCP, but this doesn’t matter as long as you don’t need to receive RHCP, noting that tianqi beacons are LHCP, and most other birds are linear. 🔗
• Notsure7 stated that tianquis are already too strong and probably will end up taking the UHF part out. Later, added that one can tune each loop separately, one resonates just above the intended freq, the other just below, but haven’t got there yet. Shared a photo of antenna and mentioned have a lot to tune yet, too low. Then, thought i should tune the small to 135, and large loop to 139/140. Added that the picture was like that, both. And Later I’ll try some more, not cutting, just adjusting the nuts and skipping a hole on the metal strip, so everything is reversible. 🔗
  
• Notsure7 shared a photo of an antenna setup and mentioned it was the best result achieved. Further discussion involved resonance points, tuning for wider bandwidth, and impedance considerations. A later message included another photo showing the results of adjustments. 🔗
  
  
• Stefan/OE6ISP commented on impedance and resonance frequency, suggesting designing the antenna to be resistive at resonance and using a λ/4 transformer. Later, Stefan/OE6ISP added that there might be two transitions, like a two-stage helical, tuned for wider bandwidth, with the target frequency somewhere in between and impedance not at 50Ohms. Stefan/OE6ISP also mentioned that phase should not have wild changes within the Lora signal bandwidth, noting that this is more of a problem with cheap SAW filters. 🔗
• Notsure7 shared a photo of an antenna build, noting it’s of similar shape to another QFH antenna for 1.6GHz. 🔗
  

Share your setup

• salvacybersec asked for documentation or instructions to help set up an environment in Turkey and mentioned difficulty finding necessary equipment. 🔗
• Michel aka Chelmi is using the same type of LNA for balloon reception on 400 MHz, which adds a significant 15 dB, and for the price it’s unbeatable. For the moment, using it without a filter, but have a rather quiet radio environment. Nevertheless, planning to add a band filter, if it’s possible to gain a little in noise floor. 🔗
• Notsure7 has burnt one LNA and put a pga103+ in it’s place, even better but it cost more than the module. Remember to use fuses, these LNA when they go, they suck up amps, and modern usb adapters can deliver them, fire hazard 🔗
• Wo reported that the tinyGS website has been down since this morning and can’t see the user count or the status of my GS station. Shared two photos of setup 🔗
  
  
• alias mentioned that there is a technical problems section for technical issues, and that this section is for sharing setups. 🔗

Where to buy

• salvacybersec asked for documentation or instructions to help set up an environment in Turkey and mentioned difficulty finding necessary equipment. 🔗
• Helmi suggested looking for a Heltec Lora32 V3 433MHz board on eBay, Amazon, or Ali, and recommended DIY antennas, specifically ground plane antennas, along with a good RF cable. 🔗

Announcements

• G4lile0 announced the new dynamic satellite map at tinygs.com, highlighting its real-time telemetry data, interactive satellite selection, enhanced sound experience, and full-screen mode. 🔗
  
  

Featured Conversations

• The TinyGS community is buzzing about the new dynamic satellite map at tinygs.com, featuring real-time telemetry data, interactive satellite selection, and an enhanced user interface. Users are encouraged to explore the map and share their feedback.
• Stefan/OE6ISP reported impressive FSK conditions with over 1200 packets received using beta firmware and highlighted the latest builds synchronize to NORBY-frequency, simplifying calibration. This update has prompted users to rebuild their setups for optimal performance.
• The TinyGS project is expanding its accessibility by developing a non-Telegram registration option to facilitate workshops for kids and users who prefer not to use Telegram. This initiative aims to broaden participation and make the project more inclusive.
• The community is actively assisting users with technical issues related to web logins and account management. G4lile0 is providing direct support, offering firmware updates and detailed instructions to resolve login problems and ensure users can properly access their stations.
• Antenna tuning strategies were discussed, with users sharing their experiences and methods for optimizing QFH antennas, including separate tuning of loops and the use of VNAs. Experienced users, such as Stefan/OE6ISP, shared their insights on advanced antenna design techniques.

What’s next

Explore the new dynamic satellite map at tinygs.com and share your feedback! Join the TinyGS community to contribute your knowledge and help expand the project.