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
EchoHam / Re: EchoHam 2.02 (2357) and Mac Sierra
« on: August 29, 2017, 08:37:26 AM »
Did you submit the crash report to Apple?

EchoHam / Re: EchoHam ver. 2.00 (2255) doesn't work under macOS Sierra
« on: February 09, 2017, 11:43:39 AM »
Sergey, you are the first/only user to report this. I don't have Sierra to run a test so can't really confirm your diagnosis.
I would be very interested to hear from any other Sierra users if they have the same problem.

EchoHam / Re: EchoHam ver. 2.00 (2255) doesn't work under macOS Sierra
« on: February 09, 2017, 09:29:11 AM »
Sergey, could you please describe what happens.

EchoHam / Re: Connection help for complete noob
« on: June 29, 2016, 08:46:32 AM »
A static IP address is not necessary but a "public" IP is. Some of the ISP nowadays use private IP's for their customers and that makes it very difficult/impossible for old protocols such as EchoLink.

As a first step I would suggest that you need to find out the "public" IP address on the Super Hub 2, post the address here (blank out the last octet with XXX for security reasons) so we can find out it is really "public".

EchoHam / Re: EchoHam - Connection
« on: May 21, 2016, 08:06:14 AM »
EchoHam does not differentiate between repeaters, links and stations.
The communication is established to the partner IP address and at that level EchoHam is not even aware of what type of station it is.

If the other station is a mobile device (e.g. iPhone, Samsung, etc) you can not establish communication due to limitations in mobile phone networks which put these devices on a private IP address. However, that is not a limitation of EchoHam but of the network infrastructure.

If you can establish a connection to the echolink test server and your transmission is echoed back to you then you can be confident that your end is working OK.

EchoHam / Re: Connection Issues
« on: April 17, 2016, 04:29:49 AM »
your problem is not with EchoHam or EchoMac.
Google "port forwarding ZyXEL" and you will find some videos to show you how it's done.
You need to forward UDP on ports 5198 and 5199 to your MacBook Pro.
Also look at for more information on port forwarding.

If you have previously used EchoHam then port forwarding would still be in place, but for whichever computer you have previously used and not for your MacBook Pro.

Hope this helps.

EchoHam / Re: Connection Issues
« on: April 16, 2016, 06:48:13 AM »
K1CGZ, do you still have EchoMac installed? Does it connect?
It looks very much like a Firewall issue, can you post details on what router you are using and copy of your firewall permission.

EchoHam / Re: New version fo El Capitan?
« on: March 18, 2016, 10:03:37 AM »

EchoHam / Re: New version fo El Capitan?
« on: March 18, 2016, 07:59:06 AM »
.... What will be the price?

Free App, $0

EchoHam / Re: New version fo El Capitan?
« on: March 16, 2016, 12:37:36 PM »
Beta testing has now been completed and EchoHam V2.00 has been submitted to the App Store for review.
This process can take some weeks depending on how deep the reviewers want to dig.
I will post once the App is available for downloading.

General Discussion / Re: Echoham Callsigns
« on: March 16, 2016, 12:34:09 PM »
R = Repeater
L = Link

EchoHam / Re: EchoHam V2 bug reports
« on: March 09, 2016, 01:12:30 PM »
Thanks Mike,
maybe you could email a screenshot  to make sure I can reproduce the same problem.

EchoHam / Re: EchoHam V2 bug reports
« on: March 08, 2016, 01:24:58 PM »
All versions before build 2238 suffer form the following issue:

If EchoHam V1 was or is installed on the Mac, the V1 preferences file is incompatible with V2 and will cause a "Cannot create NSData from object" error (visible in Console).
The issue has been resolved in build 2238 by checking the preferences file on startup, upgrading it to V2 and then terminating EchoHam. Upon the next launch of EchoHam the upgraded preferences file will be used.

If EchoHam V1 was never installed this bug should not be an issue.

Thanks to Mike (KM0S) for his help in discovering this bug.

EchoHam / Re: EchoHam V2 bug reports
« on: March 08, 2016, 11:01:57 AM »
If possible, run the application to get the error and post all debug messages which were generated during the run. A screen shot of the application could also be handy.

EchoHam / Re: EchoHam V2 bug reports
« on: March 08, 2016, 10:11:29 AM »
To provide more information open Applications -> Utilities -> Console, select "All Messages" and enter "EchoHam" in the search field on the right hand side.
You will now see all debug messages from EchoHam. Post these messages to document any issues.

Pages: [1] 2 3 4