On Thursday 05 November 2020 23:20:48 Johannes Fassotte wrote:
> Gene , I use my labview based network interfaces for all my remote
> work into linuxcnc. I put most of my info in the regular forum at:
> https://forum.linuxcnc.org/41-guis/36920-labview-ui-project-for-linuxc
>nc
So labview, which I
Gene , I use my labview based network interfaces for all my remote work
into linuxcnc. I put most of my info in the regular forum at:
https://forum.linuxcnc.org/41-guis/36920-labview-ui-project-for-linuxcnc
I'm not familiar with the tool you are using so can't comment on that
but I'm sure that
On Thursday 05 November 2020 09:01:53 andy pugh wrote:
> On Thu, 5 Nov 2020 at 04:34, Johannes Fassotte
>
> wrote:
> > It seems to me that a regular file or small database is more than
> > sufficient for a tool table with a choice depending on if pictures
> > are wanted or not. I see absolutely
On Thu, 5 Nov 2020 at 04:34, Johannes Fassotte
wrote:
> It seems to me that a regular file or small database is more than
> sufficient for a tool table with a choice depending on if pictures are
> wanted or not. I see absolutely no valid reason for messing around with
> NML buffer sizes to handl
On Wednesday 04 November 2020 23:33:51 Johannes Fassotte wrote:
> I wanted to post a update on this since I have isolated the source of
> unknown data being intermixed with my status requests data sent via
> the tcp buffer to my remote. This unknown and not requested data
> completely disrupts the
I wanted to post a update on this since I have isolated the source of
unknown data being intermixed with my status requests data sent via the
tcp buffer to my remote. This unknown and not requested data completely
disrupts the normal flow of status data at 6 times in a row and this
sequence rep
On Mon, 26 Oct 2020 at 07:09, Johannes Fassotte
wrote:
> My tests seem to show that there is no data in these transfers that do
> not have 20 as a before value, they are just a whole lot of zero's..
> Is there any info available how best the disable these data transfer so
> I can continue on othe
This is what is happening in relation to the actual traditional
emcStatus sync word location, .
This list was automatically generated by looking for the locations of
the sync word in the data received from LinuxCNC and splitting the
received data into before and aft
I wanted to follow up a bit on my last msg regarding this with some
debug and a bit more additional info.
The below are the typical responses I get from LinuxCNC when status
requests are made from my remote UI.
I added some ( ) comments to some lines for additional clarity along
with some spac
On Sun, 25 Oct 2020 at 03:34, Johannes Fassotte
wrote:
> Such a large change in file size indicates a major change in the method
> of how some data is handled.
It is at least partly the increase in the tool table size.
https://github.com/LinuxCNC/linuxcnc/commit/b51ef8cc3c560b6c44d095814988a3f9
John,
Some of the increase will be due to the addition of state tags data
structure to emcmot_status_t;
See https://github.com/LinuxCNC/linuxcnc/blob/master/src/emc/motion/motion.h
and
https://github.com/LinuxCNC/linuxcnc/blob/master/src/emc/motion/state_tag.h
Also I think the number of entries i
There are changes to the NML configuration file Master that concerns me
a lot.
From the NML configuration file at the start of 2.9 pre0
B emcStatus SHMEM localhost 16384 0 0 2 16 1002 TCP=5005 xdr
B toolSts SHMEM localhost 8192 0 0 5 16 1005 TCP=5005 xdr
Present 2.9 pre0 I use
B emcS
12 matches
Mail list logo
