| Quick recap | |
| The team discussed the WPSD software, which is ideal for single board computers like the Pi Star or Raspberry Pi. Rick highlighted the software’s advantages and disadvantages and recommended an arm quad-core processor for optimal performance. The team also delved into the installation process, Wi-fi settings, and the setup process for a system with default username and password. They also discussed issues related to their hotspots, the importance of using different frequencies for multiple hotspots, and the process of accessing the TGF network. The team also emphasized the importance of shutting down the network properly and the process of changing the duration tier, backing up and restoring the configuration, and checking for updates manually. The conversation ended with the integration of the brandmeister API code into their system and the documentation process. | |
| Next steps | |
| • Rick will provide the link to the WPSD manual in the chat. | |
| Summary | |
| DMR Technet TV Episode 2: WPSD Software Discussion | |
| Dana and Rick discussed the second episode of Dmr Technet TV, focusing on WPSD, a software that runs on single board computers like the Pi Star or Raspberry Pi. Rick detailed the software’s capabilities, including its support for various digital modes and its ability to run on multiple boards and hotspots. Rick also highlighted the software’s advantage of automatic updates and its disadvantage of requiring a more powerful computer compared to Pi Star. The discussion concluded with Rick recommending an arm quad-core processor for running the software. | |
| WPSD Installation and Wi-Fi Configuration | |
| Rick encouraged attendees to read the Wps d documentation and download the disk image using a specific software. He advised purchasing multiple microSD cards due to their affordability and potential usefulness. BradF demonstrated the process of downloading the Wpsd information using the Raspberry Pi Imager, emphasizing the importance of selecting the correct platform for installation. Dana and Lucille shared their experiences with the software, with Dana mentioning a defective microSD card and Lucille inquiring about the firmware’s upgradability. BradF then provided a detailed walkthrough on how to install software and configure Wi-fi settings on a device, emphasizing the importance of selecting the correct Wi-fi standard for the user’s country. Rick asked about an advanced setting for Wi-fi info in the Raspberry Pi imager, to which BradF clarified that the configuration generator must be used instead. | |
| Wi-Fi Connectivity and WPSD Support Discussion | |
| BradF discussed his experience with a technical issue related to a code’s instruction, which he suggested was causing Wi-fi connectivity problems. He recommended a solution that wasn’t universally applicable but was the best option in their specific case. BradF also highlighted the robust support available for the WPSD configuration via its Discord server, sharing his personal experience of swift responses to his inquiries. Dana and Norm confirmed their positive experiences with the support. The conversation ended with a discussion about who was using the WPSD and a brief demonstration of writing a disk image, which took a considerable amount of time. | |
| System Setup and Frequency Settings Discussion | |
| BradF, Rick, Dana, Norm, James, and Thomas’s discussed the setup process for a system using default username and password, ‘pi star’ and ‘raspberry’. They emphasized the importance of noting down the IP address and the hostname, ‘pi star’, which can be accessed through ‘http colon forward slash board slash hostname’. The team also discussed the selection of radio modem and the importance of capturing the old system information. BradF suggested enabling notifications for system updates. Various methods to find latitude and longitude were also discussed, including using Google Maps and checking GPS info. The team also discussed the selection of frequency settings for their devices, with BradF confirming that the entire 70 cm bandwidth was allocated for data, but suggesting using one of the specified addresses for best practice. Thomas’s explained that a simplex or duplex designation refers to radio-to-radio communication, not to a remote control device. | |
| Hotspots Performance and Configuration Discussion | |
| The team discussed issues and solutions related to their hotspots. Dana shared feedback on Wpsd’s performance, suggesting avoiding complex passwords and upgrading the pi 0 version to a Pi 0 2 watt. BradF advised using a good memory card for better longevity and discussed setting up DM board modes. Rick emphasized remembering to turn on DMR. The team also discussed the configuration of different settings for their hotspots, including display type, port, and layout. The importance of using a brand Meister API key was also discussed, but the conversation ended before this topic was fully addressed. | |
| Hotspot Frequencies and Programming Code Plugs | |
| BradF explained the importance of using different frequencies for multiple hotspots to avoid interference and transmission loops, a situation that could lead to network bans. He also detailed the process of programming code plugs, emphasizing the requirement of an 8 prefix followed by 7 digits to match the talk group. Dana, AC2UL, and others discussed the recommendation of using the master server closest to them, with a focus on the Chicago, Texas, and California servers. BradF confirmed the necessity of setting the SSID on all hotspots for each network they’re part of. | |
| Network Access and Shutdown Procedure Discussion | |
| BradF explained the process of accessing the TGF network and registering or signing in. He also discussed how to input talk group prefixes and use advanced features like full editors and RF remote commands. Steve and Dana discussed the use of reboot and shutdown commands, and Norm asked about the quick PTT feature. BradF concluded by explaining the importance of shutting down the network properly, especially when transporting it, and emphasized that each mode has its own shutdown commands. | |
| Software Platform Features Discussion | |
| The team discussed various features of a software platform. Dana and BradF explored appearance settings and manual updating, while BradF also presented the dashboard features. Rick brought up the bit error rate and an issue not covered in the manual, which BradF helped resolve. The team also discussed the dashboard toggles for group names, caller details, and hiding kerun chunks. | |
| WPSD Configuration and Update Process | |
| BradF explained the process of changing the duration tier, backing up and restoring the configuration of the WPSD, and checking for updates manually. Allan emphasized the importance of doing another backup after an update. Thomas’s inquired about the version of Piestar they were using, to which BradF clarified that they were using 4.2.1, the latest version. The team also discussed their experiences with WPSD updates and the importance of reporting any issues. Dana shared the Telegram group for Pi Star support. | |
| Integration of Brandmeister API and WPSD Discussion | |
| The team discussed the integration of the brandmeister API code into their system, with Rick guiding on the input of the API key. The documentation process was also mentioned, with clarification that it’s managed by a core development team. The WPSD project and its use in Discord for constant monitoring and question answering was brought up. The team ended the conversation by clarifying the meaning of WPSD, with Dana explaining it as an acronym for W. 0, CHP Star, dashboard. Rick suggested those interested in modifying or adding features to their code should get a copy from Github and develop it there. The conversation ended with Steve suggesting a challenge for the team to add an additional feature for WPSD, with the next meeting set for April 16th. | |