On Friday 23 October 2020 01:08:23 Thomas J Powderly wrote:
> Hello
>
> Comparing 2 scope traces could be handy.
>
>
> I had a few techs working for me in a cnc repair situation.
>
> We all used tek scopes and had 'screen savers' that actually saved the
> source code to recreate screen
>
> These
Hello
Comparing 2 scope traces could be handy.
I had a few techs working for me in a cnc repair situation.
We all used tek scopes and had 'screen savers' that actually saved the
source code to recreate screen
These 'screenshots' could be reloaded on a 'channel' and compared to a
real
Andy,
Try this branch here:
https://github.com/LinuxCNC/linuxcnc/tree/rellenberg/halscope
It adds native CSV-saving capability to halscope (if you specify a .csv
file in the save dialog). It's much easier to parse in something like
octave (and also much faster). It won't do much for the
On Thu, 22 Oct 2020 at 16:50, Nicklas SB Karlsson wrote:
>
> Did not read very carefully, if you need maybe I could spend a few other
> try to get the halscope log file into Octave.
I would be much more interested in getting a halcope log back in to halscope.
--
atp
"A motorcycle is a bicycle
Did not read very carefully, if you need maybe I could spend a few other
try to get the halscope log file into Octave.
Den 2020-10-21 kl. 20:36, skrev andy pugh:
Does anyone have any investment in a tool to read the halscope log file format?
I am thinking that it is a bit unhelpful at the
I found although not perfect .csv is relatively easy to generate and
read. It might be a good idea to use ; as separator instead of , because
at least in Sweden this is used as a decimal separator.
Octave might be a rather good solution for visualization. It is
relatively easy to produce
Does anyone have any investment in a tool to read the halscope log file format?
I am thinking that it is a bit unhelpful at the moment and a plain CSV
or similar would be much easier to work with in external tools. But it
would be unfortunate if doing that broke existing tools.
(And it would be
