Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - support

Pages: 1 [2] 3 4 ... 6
16
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.

17
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.

18
EchoHam / Re: Echoham preferences
« on: June 21, 2020, 10:08:29 pm »
Hi Roger,
while connected to the Echolink Servers Preferences are not available.
Disconnect from Echolink Servers by clicking the left most icon in the toolbar.
Once disconnected the Preferences symbol will become available.

19
EchoHam / Re: Please Help Osx 10.15.4
« on: June 21, 2020, 10:05:51 pm »
Please download latest EchoHam V2.10. It has been tested with macOS 10.15 Catalina

20
EchoHam / Re: EchoHam on macOS 10.15 (Catalina)
« on: June 21, 2020, 10:04:24 pm »
EchoHam 2.10 is tested and working under macOS 10.15 Catalina

21
EchoHam / Re: crash on Mac OS Catalina 10.15.3
« on: February 12, 2020, 02:05:12 pm »
How often doe this happen?
What is your callsign?
Did you submit the crash report to Apple?

22
EchoHam / Re: color coding
« on: February 11, 2020, 01:37:47 pm »
A station will appear with orange colour background when it reports its status as "Busy".

What makes a station appear as busy depends on the application used by the operator.
In EchoHam you can use the status icon in the Toolbar to change your own station status between Busy and Free.


23
EchoHam / Re: Connection Issues
« on: January 28, 2020, 10:54:01 pm »
A "REAL IP" is a prerequisite at this stage.
However, a proxy server solution is in the making.
Unfortunately I can't provide a release date at this point in time.

24
EchoHam / Re: EchoHam on macOS 10.15 (Catalina)
« on: November 28, 2019, 09:14:25 am »
Thanks James, that's a very detailed report. I'm still not ready to go to Catalina as I would loose a number of incompatible apps.

25
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.

26
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.   

27
EchoHam / Re: EchoHam microphone not working on Mojave
« on: June 29, 2019, 04:31:54 pm »
EchoHam V2.07 has improved Microphone access detection. It will provide a warning message to the operator if Microphone access is not available.

28
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

29
EchoHam / Re: Echo ham
« on: August 20, 2018, 08:39:31 am »
Hello Mark,
Echoham is available as a free download from the AppStore.
You can delete EchoHam by dragging it into the Bin.
You can download Echoham from the AppStore as often as you like.

I am not familiar with Echoic, can you please provide more details or a link.

30
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.

Pages: 1 [2] 3 4 ... 6