Topics

1

EchoHam / EchoHam 2.28 released

« on: March 17, 2023, 09:16:28 am »

EchoHam 2.28 is now released.
A number of modules have been re-written in Swift.
Please report any issues to me via email support@apphugs.com

2

EchoHam / New EchoHam version 2.25

« on: January 29, 2023, 03:37:58 pm »

The last 3 releases included many code improvements with some of the old Objective-C modules completely re-written in Swift.
V2.25 provides the ability to set specific audio devices for use with EchoHam via the preferences window.

Since some audio devices can be temporary (e.g. bluetooth earphones getting disconnected), EchoHam will not complain when a pre-set audio device is not available, instead, it will revert to the default device specified in system preferences.

To always use the audio settings from system preferences you can set the audio devices to "Default" in EchoHam.
Using default devices has the advantage of devices automatically changing as required by the system.

3

EchoHam / New EchoHam V2.20/21 - with proxy support

« on: December 29, 2022, 06:38:02 pm »

V2.21 has been submitted to the AppStore for approval and should be available for download in the next few days.
It took a while to implement proxy server support in the code but hopefully this will fix the most common user problem reported over the years, which is the port forwarding setup on routers.

Here is an explanation and demonstration of the proxy server support feature:
https://youtu.be/pkrYBUvLCXE

I would expect some bugs to show up as the proxy server code required modifications in most of the code modules.
I ask for your assistance in resolving the bugs.
Before reporting a bug please make sure it is repeatable and that you record the exact steps which lead to the bug so I can re-create the bug and try to resolve it in the next version.
You can email all bug reports to me: support AT gmail DOT com

4

Modbus Server / New Modbus Server(TCP) and Slave(RTU) application

« on: September 08, 2022, 12:05:14 pm »

Modbus Server has been completely re-written using the latest Apple SDK and Network Framework.
Unfortunately it was not feasible to accommodate the new features in the old version so we have now created two new applications:

• Modbus TCP Server
• Modbus RTU Slave (to be published soon)

Splitting the RTU and TCP functionality has come as a result customer confusion with the server/client (TCP) and master/slave (RTU) terminology. We re hoping the new terminology leaves no room for confusion.

Link to Modbus TCP Server: https://apps.apple.com/us/app/modbus-tcp-server/id1640384900

5

Modbus TCP Client and RTU Master / V1.00 Released

« on: July 13, 2022, 08:37:08 am »

V1.00 is now available in the AppStore:
Modbus TCP Client
Modbus RTU Master


Demonstration video:
TCP Client: https://youtu.be/F7hcCfoS1xo
RTU Master: https://youtu.be/aXNQNeaJCtw


Please post any support questions in this forum.

6

NavPredict / V1.00 release

« on: May 12, 2022, 04:04:22 pm »

V1.00 is now released in the Appstore
Appstore link:https://apps.apple.com/app/id1623759179
Introduction Video: https://youtu.be/xxiUDOwUx0A

7

Ham Rotator / V1.0 released

« on: April 01, 2022, 06:15:35 am »

V1.0 is now available in the App Store.
Supported Protocols: SPID ROT2, Yaesu, Easycomm, DCU1.
Please contact support@apphugs.com if you would like to see another rotator protocol.
Short video introduction: https://youtu.be/JzPTOmgqKVk

8

EchoHam / EchoHam V2.13 released

« on: June 29, 2020, 11:00:52 am »

A few more improvements to make network debugging easier.
The port checking facility now tests for two different scenarios:
1) EchoHam connecting to another station (Outgoing Connection)
2) Another station connecting to EchoHam (Incoming connection)
Most modern routers will support outgoing connections without any special requirements.
Incoming connection pose more of a challenge and need port forwarding to be functioning correctly.

As of V2.13 the Port Check user alert will report separately on Incoming and Outgoing connections to enable better network diagnostics. 

9

EchoHam / EchoHam V2.12 released

« on: June 25, 2020, 09:22:14 am »

V2.12 is now in the AppStore
the main improvement is the addition of NAT-PMP protocol to establish port forwarding.
NAT-PMP is very popular in Apple devices.

10

EchoHam / EchoHam V2.10 / V2.11 released

« on: June 21, 2020, 10:18:46 pm »

V2.10 improvements:
- uPnP based automatic port forwarding
- tested on macOS 10.15 Catalina
- station connection progress indicator
- reliability improvements and bug fixes

Unfortunately a bug crashed EchoHam when the user connects to another station.
V2.11 was released within 24hrs to fix this bug.

11

EchoHam / EchoHam port forwarding update

« on: June 21, 2020, 10:15:35 pm »

As of V2.10 EchoHam uses uPnP (Universal Plug N Play) to automatically establish port forwarding on routers.
I hope this improvement makes it easier for everyone to get the right ports forwarded to correct IP address.
It also allows for multiple computers on the same network to have EchoHam installed as long as only one is running EchoHam at any time.
As of V2.12 EchoHam also utilises NAT-PMP for port forwarding. This feature is very popular on Apple devices.

12

EchoHam / EchoHam on macOS 10.15 (Catalina)

« on: October 17, 2019, 11:28:14 am »

With the release of macOS 10.15 Apple have made a lot of major changes some of which may affect EchoHam.
I have received one report of connection issues under Catalina, however, I'm unable to confirm this or run tests myself since I won't upgrade [to 10.15] until after the first bunch of bug fixes are released.
If anyone can provide reports of EchoHam working (or not) under Catalina I would appreciate it.

13

EchoHam / What is EchoHam "Port Check"

« on: June 30, 2019, 09:11:24 am »

EchoHam V2.07 has automatic port checking.
This check is carried out once when the program starts, it sends a UDP data packet to an echo server (over the internet) and expected the same data packet to be received back on port 5198 and 5199. With a correctly configured router and firewall, these return packets will arrive at the Application without much delay.
However, if the packets are not getting back within 10 seconds the user will be presented with an warning window outlining that an Echolink connection is not possible.

If you experience this scenario please check your router and firewall configuration, it is the most likely culprit causing the type of problem.   

14

EchoHam / EchoHam microphone not working on Mojave

« on: June 26, 2019, 09:12:13 am »

For anyone who has found the microphone input is not working:

macOS Mojave (10.14) has introduced new features under System Preferences -> Security & Privacy -> Privacy tab where microphone access permission can be given to each application individually. However, EchoHam actually needs to request microphone permission and this request was first included in V2.06 released 26 June 2019.

So, if you experience the microphone problem, make sure you are running EchoHam 2.06 or later and that EchoHam is ticked in the Privacy tab.

Further reading in this apple article: https://support.apple.com/en-au/HT209175

15

EchoHam / EchoHam crashing - what to do ....

« on: March 15, 2018, 02:57:55 pm »

EchoHam is a hobby project for me, it's non-commercial and is provided free for all Mac users to enjoy.

As I also have a paid job (to finance my Ham Radios), the time I spend on EchoHam coding is limited.
It is beyond my capacity to provide one-on-one support to EchoHam users, however, I still endeavour to provide an error-free application for all Ham's to enjoy.

If you experience an application crash in EchoHam, and you are on macOS 10.10 (Yosemite) or later, the operating system will present a window where you have the opportunity to submit a crash report to Apple.
Please, please, please allow the crash report to be submitted. This is the best contribution you can make to resolving the crash issue.

The crash information is available to me in the development platform (XCode) and in most cases I can jump straight to the code line which caused the crash.

The Apple crash reporter also gives me an accurate idea on how many crashes occur, in which version, and groups same crashes together.

Your privacy is totally protected by Apple, I can't see any information on the user, the computer or anything else, just where my code crashed.

If you don't submit the crash report I may never find the code which has caused the problem.

Thanks for your help in improving this software.