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 ... 4 5 [6]
EchoHam / Re: EchoHam crashing on Connect
« on: October 05, 2014, 08:57:06 am »
I have found a bit of spare time, rewritten the networking components and totally restructured the EchoHam application.
EchoHam no longer uses subprocesses (echoaudio and echolink).

I am sure this will solve the crashing issue discussed in this topic.

The new EchoHam V1.10 is in the stages of final testing and will be available to beta testers shortly.

EchoHam / Re: EchoHam crashing on Connect
« on: July 05, 2014, 07:18:18 am »
Thanks n0mwu,
that solution is a reasonable temporary fix and gives you all the important the re-written code.

EchoHam / Re: EchoHam crashing on Connect
« on: July 04, 2014, 09:37:55 pm »
Thanks n0mwu,
did you save the original files? If you did, could you please try and replace only echolinux and leave everything else as per App Store download. Let us know of the result.

echoaudio has undergone a major re-write to make the audio system compliant with OS X 7 and higher. The old echoaudio contains a lot of code that can causes problems on the later versions of OS X.

EchoHam / Re: EchoHam crashing on Connect
« on: June 28, 2014, 07:01:48 am »
thanks for your offer to help.

I run 10.9.3 on a couple of machines connected wireless.
At work I run a 10.8 machine with wired connection.

EchoHam / Re: EchoHam crashing on Connect
« on: June 13, 2014, 09:35:49 am »
not fixed yet, haven't received any debug output files as yet.
Look forward to receiving debug files.

EchoHam / Re: EchoHam crashing on Connect
« on: June 09, 2014, 10:09:24 pm »
you may be able to help resolve this problem - please see for details.

EchoHam / Re: EchoHam crashing on Connect
« on: June 02, 2014, 02:43:52 pm »
BTW: you say you find crash reports helpful.  The one from just now doesn't fit inside the 20k character max length of the allowed forum message.  I have it in my paste buffer, but don't know how to get it to you.

As the first post in this thread states "please email me on

Now the router avatar is giving me flashing-amber, and the ASCII "double NAT" so when I went back in and set the trailing field back to 201, again the router took the edit with no problem (so what WAS the problem with the first submission?  Just leaving out the port-5200 TCP assignment??)

Not sure on that, a bit hard to diagnose from the other side of the world ???

EchoHam / Re: EchoHam crashing on Connect
« on: June 02, 2014, 02:04:43 pm »
When I clicked on Update, I got a diagnostic that an error had occurred …
 BTW, today I acceded to router firmware-version update, from 7.6.1 to 7.6.4.

Now that you have upgraded the Airport Extreme firmware, try again to add the port settings.

EchoHam / Re: EchoHam crashing on Connect
« on: June 01, 2014, 07:11:27 pm »
maybe the screenshot below helps with your router setup. It shows the port redirection required to run EchoHam.

EchoHam / Re: EchoHam crashing on Connect
« on: May 31, 2014, 07:22:43 am »
Hi Laird,
thanks for the additional information. It confirms my thoughts.

EchoHam uses a couple of subprocesses (echolinux and echoaudio), from the crash reports I can see that echolinux is the process that crashes. EchoHam detects the termination of echolinux and attempts to restart echolinux and that's why EchoHam uses up lots of CPU time when it continuously restarts the echolinux process. That's also why you see multiple echolinux processes where all but the last one have actually crashed.

The puzzle for me is why does echolinux crash on some systems?

The free version of Modbus Server (3.1) does not work on Mavericks 10.9.
At this stage there is no timeline to make the free version available for Mavericks.

The latest version of Modbus Server Pro has been compiled to run under Mavericks.

EchoHam / EchoHam crashing on Connect
« on: May 30, 2014, 04:32:45 pm »
Some users have reported EchoHam crashing on "Connect".
I am unable to reproduce this problem on my iMac(s) / MacBookPro.

I am still looking for someone who can edit files in terminal to enable additional debugging and then email me the log files to determine which part of the code causes the crash.

If you can help please email me on

Pages: 1 ... 4 5 [6]