ANNOUNCING: FreqEZ2 Band Decoder software v2.1.2 release to general availability on the new website at www.freqez.com ( yes, we skipped over version 2.1.1 but that version was installed in some testers' sites. ;-) NEW FEATURES IP Address auto-discovery: To simplify FreqEZ configuration, the Raspberry Pi Controllers will send broadcast beacons on the LAN, announcing their network name, IP address, MAC address and software version. Those packets will be displayed in the FreqEZ packet window as "Action Required" statements, allowing the user to >Setup FreqEZ without having to separately connect to the Raspberry Pi for its IP Address. The auto-discovery feature was primarily intended to help with new installations, but will also assist in those instances when you cannot connect to the Controller because your router has changed the RPi's IP Address. Version Control visibility and tracking: Software versions are passed between Windows Consoles and RPi Controllers, and saved in the FreqEZSettings.xml. The RPi versions are displayed in the Windows Console >Setup window. A red "*" (asterisk) will appear when the Console version does not match the Controller version. These IP Address auto-discovery and version control features are the foundation of automated RPi Controller management, where - in a future FreqEZ version - the Windows Console will control software updates on the Raspberry Pi without the user needing to separately connect to the RPi. The goal is plug&pray headless Raspberry Pi operation. BUG FIXES - The XML XML_ERROR_STATION_NAME ELEMENT error - The packet CheckSumMD5 error - Directory/Path errors with config XML and help PDF files - RPi rc.local auto-start (see the help pdf file or groups.io email "Unable to get the freqezrpi to launch automatically" for this fix) Existing FreqEZ v2.x.x users: When updating, you can safely overlay existing files on both the Windows and the Raspberry Pi platforms You will not need to make any hardware changes to your physical layout or cable configurations. FreqEZ2 is all about software You will not need to change your settings, v2.x.x FreqEZConfig.xml and FreqEZSettings.xml files are compatible - although making a backup copy "just-in-case" is always a good idea You must update both the Windows and Raspberry Pi programs The newest FreqEZ2Help.pdf file with the latest documentation is included in the Windows Setup program The Setup programs will install to the default /FreqEZ2 directories

ANNOUNCING: FreqEZ2 Band Decoder software v2.1.0 release to general availability on the new website at www.freqez.com FreqEZ2 v2.1.0 is a major release and requires replacing the Windows FreqEZ Console program and the Raspberry Pi Controller program. Changes from v2.0.x to v2.1.0 New* ManualPlus Source activation of multiple outputs with single mouse click (OK1ALX) Enhanced SO2R and Networking operation (AA4VT) Modified FreqEZ Console settings to support 8 and 16 output HAT boards Improved packet integrity checksum based on MD5 Replaced packet descriptions with unambiguous terms - “request,” “assign,” “keep-alive,” "confirm," “notify” Added <PacketType> to UDP packets between Windows Console and Raspberry Pi Controller Reduced network packet traffic by 90% with elimination of redundant messages Existing FreqEZ v2.0.x users: When updating, you can safely overlay existing files on both the Windows and the Raspberry Pi platforms You will not need to make any hardware changes to your physical layout or cable configurations. FreqEZ2 is all about software You will not need to change your settings, v2.0.x FreqEZConfig.xml and FreqEZSettings.xml files are compatible - although making a backup copy "just-in-case" is always a good idea You must update both the Windows v2.0.x and Raspberry Pi v2.0.x programs The newest FreqEZ2Help.pdf file with the latest documentation is included in the Windows Setup program The Setup programs will install to the default /FreqEZ2 directories Despite the efforts of volunteer beta testers (THANK YOU!), bugs always manage to survive into an update containing as many changes as v2.1.0. Please report any issues you encounter here in https://groups.io/g/FreqEZ so that the FreqEZ community benefits from information sharing. Oh, and replace your browser links to the new URL www.freqez.com -larry (K8UT)

*Announcing a new FreqEZ interface board. The HAT8 board is designed and priced for Little Pistol Stations that only need 8 outputs, but may be suitable for Big Gun stations that don't need 16 outputs at all locations.* The board is intended for the inexpensive Raspberry Pi Zero 2W board. But like all Raspberry Pi products these days, the Pi Zero is very difficult to purchase at the organization's suggested retail price of $15 and can only be found in ridiculous scalper bundles. However the HAT8 board will mount on other Raspberry Pi models 3 and 4 if you can manage to get one of those (see documentation for special mounting considerations). Note that the Pi Zero 2W is WiFi only, you'll need a hardwired dongle for ethernet connectivity. We have a small initial inventory of HAT8 boards selling at an introductory price of $25. That price will likely increase with subsequent batches of boards from the manufacturer. Details: * Standard 64mm x 30mm RPi Zero HAT dimensions. Aligns perfectly with Pi Zero but can be installed on Pi 3/4 platforms (read documentation) * 8 high-speed solid-state opto-isolated outputs, MOSFETs rated 500ma, AC or DC, at 60 volts, but on-board clamping MOV's will activate on pulses greater than 28 volts. (protection from remote relay coil spikes) * 8 output indicator LEDs, one power LED * 8 screw terminals for remote connections (optional male SIP connectors by request) * PTT inhibit input (1 screw terminal) * BCD input (4 screw terminals) The FreqEZ HAT8 is fully compatible with existing FreqEZ installations and configurations. The only adjustment is in the Windows FreqEZ v2.1.0 Console: *More information on the new FreqEZ website www.freqez.com ( http://www.freqez.com )* -larry (K8UT)

The purpose of this group is to serve as the main support channel and discussion group for hams building and using the FreqEZ Band Decoder. You need to join the group in order to post messages. Include your callsign in requests to join. Be proud of your callsign and put it in every post. The first posting from you as a new user must be approved by the moderators - thus there may be a delay between the time of your original post and its arrival in groups.io. Don't spam. This is not a list for posting items for sale, for announcing contests or events, for discussing amateur politics or for other off topic posts. It is also not the place for personal attacks. Repeated or egregious violations will result in loss of posting privileges. If the volume of email from the group is too much, you can set your delivery to digests or no email, by signing in to the groups.io web site and selecting "Your Groups > Manage My Subscriptions". You can also change your account preferences by clicking on your account name at the top right. You can change your email address or add an email alias address from the same place. You can view messages on the web site either in chronological order or by topic. Attachments are not conveyed in messages, but the web site also has a Files area to which files and screen shots may be uploaded. Try to make the subject line of your postings meaningful and descriptive. If you are starting a new topic, don't post it as a follow-up to a different thread; start a new thread with a title appropriate to the new topic. Topic titles such as "Help needed" or "Question" or "New user" are uninformative. Put enough key words in you titles so the reader can decide whether they want to read your message... or not. Read all the posts in a topic before posting a response. If a post already says what you were going to say, don't clutter up the list with a "me too" post. When posting a response, it is a good idea to include just enough of the previous discussion to identify the context, and no more. There is no need to quote the entire past history of the thread in every response. After posting a problem, check back for responses. It is rude to post a problem then disappear. Likewise, please do not ask for off-list responses. If your post was important enough to ask everybody to read it, you owe it to them to let them see the responses. If the responses solve your problem, let the group know how your problem was solved; that may help someone else down the road. Please do not think of this group as only a place for you to get answers to your problems, but also as a place where you can help others with their problems. If someone else has a problem that you know how to fix, feel free to respond and provide the solution. The success of the group depends on more than just responses from the Mortty developers. However, when you do not know the answer, don't waste everybody's time with meaningless responses like "gee, that's a tough one. I have no idea." Above all, think before posting. If you want help, demonstrate your willingness to do your part of the work. Be polite. Larry (K8UT)

Here's a post where you can lodge any errors, corrections, or omissions you find in the documentation. When you respond to this post, please don't change the Subject Field as it may confuse the groups.io mail handler and create a separate post. -larry (K8UT)