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 5 6
EchoHam / EchoHam 2.04 now in AppStore
« on: March 15, 2018, 02:34:37 pm »
Thanks you to all those users who have submitted crash reports via the Apple Crash report system.
I have undertaken an extensive code review which should have most of the issues sorted out soon.

V2.04 is now available in the AppStore as a free purchase.

Any feedback welcome via this forum.

Modbus Client (Pro) / Modbus Client Pro Demo video
« on: March 09, 2018, 04:32:39 pm »
Modbus Client Pro Features have been released and will be available as an In-App purchase shortly.
You can watch the introduction video here:

EchoHam / Re: EchoHam 2.02 (2357) and Mac Sierra
« on: March 05, 2018, 10:14:39 am »
Yes, it is the best way to get crash information to the developer.
When developers look at the crash info collected by Apple we can easily see how many crashes are occurring and the details on which part of the application is crashing.
Many crashes in the the same area of code will point out weakness in my code and allow me to fix it.

Modbus Client (Pro) / ModbusClient 2.0 - demo video
« on: March 02, 2018, 02:45:27 pm »
ModbusClient V2.0 has been release.
see a demonstration video here:
AppStore link:

Serial Tools / Re: Ability to sense additional control signals?
« on: February 05, 2018, 10:34:58 am »
It is certainly possible. I will add this item to the feature request list.

EchoHam / Re: EchoHam 2.02 (2357) and Mac Sierra
« on: January 09, 2018, 09:38:45 am »
The crash report gets stored on Apple's server and the developer will see the crash report and get an idea how may crashes of this type occur. If there are lots of crashes of the same type the developer will address these issues.
Please send ALL crash reports to Apple.

Serial Tools / Re: Suggestion: new cr/lf option
« on: January 09, 2018, 09:26:55 am »
Thank you for your suggestion, it has been added to the feature wish list.

I'm afraid it may not be possible to differentiate between the different ports as the port name is provided by the underlying OS. Maybe there is an additional interface parameter provided in Sierra which I didn't implemented in SerialTools, but that's going to be really hard to simulate without the adapter hardware.
Could you please post diagnostic information from "About This Mac" -> "System Report" -> "USB", showing details of the two GUC232A adapters.

Just as a side note, I have previous experience with some of the cheaper adapters (mostly PL based) which appear to be indistinguishable. I solved the problem by getting a couple of FTDI based adapters which don't suffer from this issue.

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.

Pages: 1 2 [3] 4 5 6