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 ... 6
1
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

2
EchoHam / Re: Favorites?
« on: April 06, 2022, 10:00:38 pm »
This is on the feature list

3
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

4
Modbus Client (Pro) / Re: Unable to purchase Pro
« on: October 01, 2021, 07:55:54 am »
The pro version is no longer available and has been removed from the AppStore.
All features of the previously available in the PRO version are enabled in the standard version.

5
Serial Tools / Re: feature suggestion for serial tools
« on: September 21, 2021, 01:21:35 pm »
Hi dumpington,
thanks for the feedback.
you are not the first user to come up with this suggestion.
It is already on the feature request list and will be implemented eventually.

Unfortunately time is limited, but I will get to it eventually.

6
Modbus Client (Pro) / Re: How to set the port number to 502?
« on: April 24, 2021, 09:20:08 am »
Prior to macOS V10.14 (Mojave) all ports below 1023 require root privileges for full access. A workaround solution is explained in the ModbusClient Help section.
From 10.14 onwards this restriction has been removed and you can simply set the port number to 502.

7
Modbus Client (Pro) / Re: How to read MODBUS register
« on: April 24, 2021, 09:08:01 am »
0x0FFD = 4093
If that doesn't work try +1 and -1, i.e. 4092 and 4094

Register addresses can be 0 based or 1 based, depending on Modbus device, hence try the addresses either side of 4093

Hope this helps

8
EchoHam / Re: EchoHam 2.13 on Big Sur
« on: December 05, 2020, 06:56:12 am »
EchoHam has not been tested on Big Sur and I would expect it not to work.
Unfortunately the Audio interface on Big Sur has been completely changed and is no longer compatible.
All audio related code needs to be completely re-written for Big Sur.
I'm hoping the Christmas break will allow me time to tackle the rewrite.

9
EchoHam / Re: EchoHam 2.13 Connection Issues
« on: October 28, 2020, 08:45:20 am »
proxy connections are only partially implemented in V2.13. However, I have tested connection to public proxy servers and they do work.
You can find a list of public proxy server at https://www.echolink.org/proxylist.jsp
Find a suitable server and enter the details in Echolink.

10
EchoHam / Re: EchoHam 2.13 Connection Issues
« on: July 16, 2020, 05:33:53 pm »
Arandolp, what's your call sign?

11
EchoHam / Re: EchoHam 2.13 Connection Issues
« on: July 15, 2020, 07:57:03 am »
Hi Phil,
many thanks for sharing your solution.

I have removed "El Capitan" from the subject name as the problem wasn't really related to El Capitan but EyeConnect and hence your solution would be applicable to other macOS versions.

12
EchoHam / Re: EchoHam 2.13 Connection Issues
« on: July 14, 2020, 08:48:46 am »
Thanks Phil,
it may be El Capitan or something else which is installed on your computer.

It would be great to hear from other users if they have the same issue with El Capitan.

13
EchoHam / Re: EchoHam 2.13 Connection Issues
« on: July 13, 2020, 10:24:28 am »
Phil, I noticed about 4 hours and 40 minutes after your last post our system shows you as working for both incoming and outgoing calls:
http://echolink.rossw.net/index.html?callsign=m7phx
Note the times are in UTC

Can you please let us know what you did to get it working?

14
EchoHam / Re: EchoHam 2.13 Connection Issues
« on: July 10, 2020, 10:10:03 pm »
Hi Phil,
the console messages indicate that you have another application running which is hogging port 1900.
Do you have anything uPnP related installed?
Do you get the same console messages if run EchoHam straight after a reboot?
Any possibility that you have other software which could block EchoHam from port 1900?


15
EchoHam / Re: EchoHam 2.13 Connection Issues
« on: July 10, 2020, 08:55:32 am »
Hi Phil,
could you please advise your call sign so I can do some diagnostics from this end.

Thanks

Pages: [1] 2 3 ... 6