Recent Posts

Pages: [1] 2 3 ... 10
EchoHam / Re: EchoHam on macOS 10.15 (Catalina)
« Last post by support 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.
EchoHam / Re: EchoHam on macOS 10.15 (Catalina)
« Last post by N7JHK on October 21, 2019, 12:05:00 AM »
It took me some time to get EchoHam to work on my my MacBook Pro with OSX Mojave, but this was due to port forwarding issues with my Apple Time Capsule and my AT&T router. However, I finally got everything configured per all the guidance videos that I could find and EchoHam became operational. I did have to uncheck the box in the option tab as it kept telling me I was not correctly configured, but everything seemed to work extremely well. However, after I loaded Catalina, EchoHam stopped working. Everything appears normal, but the issue is it wonít transmit. I can locate stations and hear normally and the S-Meter is also indicating. When, I tap TX, I get the red TX display, I then start talking and again the S-Meter tells me Iím modulating. I do have EchoHam microphone check in the Privacy settings and can confirm the microphone is working in sound settings. I then noticed that after I connect to a station/repeater, I get the audible connected sound along with the station/repeater ID, but my Callsign ID is not displayed. In the past week, I have left EchoHam running on my MacBook while I work and listen to people chatting on a local repeater and on two occasions, I have seen my callsign appear. I did a radio check and all normal. However, 99% of the time my callsign does not indicate and I canít TX. Again connection and RX works perfectly. I have double checked my modem and router settings, deleted and reloaded EchoHam, but issue continues. I hope this helps, but let me know if you have questions or you need my try something. 73s, James-N7JHK

21OCT2019 Update: I am currently listening to a local repeater (K4YTZ-L) in Rock Hill, SC and my name is NOT listed under the Station ID, however, I heard another HAM call out, so I responded. He heard me and reported I was loud and clear. As you can see from attachment, my name is NOT listed below the Station ID info.
EchoHam / EchoHam on macOS 10.15 (Catalina)
« Last post by support 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.
EchoHam / What is EchoHam "Port Check"
« Last post by support 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.   
EchoHam / Re: EchoHam microphone not working on Mojave
« Last post by support 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.
EchoHam / EchoHam microphone not working on Mojave
« Last post by support 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:
EchoHam / Re: Echo ham
« Last post by N5XRW on March 22, 2019, 03:09:38 PM »
Downloaded 2.05 from the app store.  I have used echolink on windows device, but first time using on mac os.
EchoHam / Re: Echo ham
« Last post by support 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.
EchoHam / Echo ham
« Last post by KE0MQQ on August 19, 2018, 11:29:57 PM »
Hello community, I am an Echoham user. When using the app. I experience a warbled audio playback of my voice on the Echotest server and conference servers. I have tried uninstalling, then reinstalling, but the issue is present with every reinstall. I downloaded Echoham, and it works fine. I would much rather run Echoham, as opposed to Echoic. Does anyone have any idea how to download a fresh copy of Echoham? Or, have a solution to the issue? Thank you, Mark D. Miller KE0MQQ.
EchoHam / EchoHam crashing - what to do ....
« Last post by support 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 ... 10