Lars, If you have another user interface running, the first interface to see the error is going to swallow it. Since a local interface generally updates faster that one over a network, the odds are that the local interface will see it first.
This is a known limitation of that interface. I believe linuxcncsvr (5005) is for nml, which is why halrmt is by default on 5006 and linuxcncrsh on 5007. Regards, Eric Sent from my ASUS Pad Lars Andersson <l...@larsandersson.com> wrote: >Hi list, >got inspired by recent threads and decided to try a remote display app >for LinuxCNC using linuxcncrsh. >I started in C# as this is the windows thing that usually works for me, >was promising to start with. > >One serious problem now. I can't get error reporting to work. If I issue >a command like "set mdi g0x0y0" and the AXIS display shows an error >"must be in MDI mode to issue MDI command" then I issue a "get error" >which returns "ERROR OK". > >How should I do this correctly? My plan was to follow each command with >a "get error", I cannot find any other way of error feedback. > >(By the way, what is linuxcncsvr on port 5005 doing? Wasn't able to find >anything in the docs) > > > >------------------------------------------------------------------------------ >Everyone hates slow websites. So do we. >Make your web apps faster with AppDynamics >Download AppDynamics Lite for free today: >http://p.sf.net/sfu/appdyn_d2d_mar >_______________________________________________ >Emc-users mailing list >Emc-users@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/emc-users > ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
