Thanks Jeff.

so I can modify linuxcnc.nml (37-38-39 row) in these manner:

P myUI          emcCommand      LOCAL   localhost       W       0
10.0    0       10
P myUI          emcStatus           LOCAL   localhost       R       0
10.0    0       10
P myUI          emcError              LOCAL   localhost       R
0       10.0    0       10

than use the parameter in these way?

>     RCS_STAT_CHANNEL *c =
>         new RCS_STAT_CHANNEL(emcFormat, "emcStatus", "myUI", file)

Anyway, if I wanted to send a stat/cmd/err signal to a remote server, would
it be correct to add these three lines to the linuxcnc.nml file?

P myUI          emcCommand      REMOTE   192.105.0.5       W       0
10.0    0       10
P myUI          emcStatus           REMOTE   192.105.0.5       R
0       10.0    0       10
P myUI          emcError             REMOTE   192.105.0.5       R
0       10.0    0       10

and if I add a rt-ethernet line can you share between the two pc SHMEM in
some way (ex. using reflective memory)?
The purpose is to have rt copy of the messages so that they have exact copy
of the results on an external pc .... for example to replicate the graphic
portion of vismac on multiple pc at the same time .... or to send and
receive rt signals from Multiple workstations at the same time. The idea of
​​sharing SHMEM is because I think it's quicker to have data in this way
... but it might also be a bad idea for latency times.

Correct me if I'm wrong but my configuration example with REMOTE host sends
the signals in user-space, not in rt-space. Did I understand correctly or
incorrectly?

bkt

2017-06-07 13:54 GMT+02:00 Jeff Epler <[email protected]>:

> >     RCS_STAT_CHANNEL *c =
> >         new RCS_STAT_CHANNEL(emcFormat, "emcStatus", "xemc", file);
>
> The parameter "xemc" here is a mostly-meaningless string that needs
> to match the "name" column of an "emcStatus" line in the
> linuxcnc.nml file.  You can think of it as just meaning "the
> standard name for a UI process".
>
> Jeff
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Emc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/emc-users
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to