emcrsh: server part locks up

Hi!
I try to control Emc2 software via 'emcrsh', because i read about this is recommended way to do some non-trivial tasks like SMT Pick and place machine, and other types of external control.
I'm configure my system in standard way so i able milling well. Then, only i change is add 'loadusr emcrsh' in .hal file.
I not find any working example (command sequence) for emcrsh, so i try to write from scratch.
Here is my terminal log:
...but in places shown as (x), i not receive anything, and all stops until i disconnect telnet, and connect again (and 'hello' again, etc) - then 'set machine on' command, which first time always stop telnet server, second time always work. I reproduce it multiple times, and i reproduce it not only in hand mode, but also in simple C code which work in raw string send/receive mode, like telnet.
Where i am wrong? Probably command order?..
Thanks!

I just found topic which describes exactly same problem:
www.linuxcnc.org/component/option,com_ku...ew/catid,10/id,1633/
But it still not has a solution.

Hi!
Still no luck. I also check jitter and try increase Base_period, but it is not helpful.
Any chances to turn it to work?..
Please give me the direction where to search about fixing Emcrsh. Any success stories about using Emcrsh exist?.. Or, maybe another way to control Emc2 from my software, is exist?
Many thanks!

jpka wrote:

set update auto
SET UPDATE ACK
set machine on (x)

Hi

There has been a bit of discussion on emcrsh both here and on the user list, so I thought that I would try it.

The command sequence you posted does produce the result you specified, ie emcrsh seems to lock up and does not respond until restarted on 2.4.5

However, I did not try your sequence to start with and because update defaults to auto anyway, I just did the sequence below.

It worked perfectly, homed the axes then moved to the given co-ordinates.
I did not do extensive testing, just wanted to home and test axis movement, which were the major control items.

I will dig through the emcrsh code later to see if anything leaps out at me as to why and whether this tallies with the bugfix that Andy highlighted.

For now appears the factor which caused the lock-up was the set update auto command.
Seems to work OK if you don't use it.

regards