Hi Chris,
I had the time to get a closer look to your work.
I was very astonished on executing the testcase for the failure.
Looking at your work, it seems to me, as if the newly introduced fcode-
variable is unrelated to the rest of motion stuff and I doubt, whether this is
the right way.
Hi,
thank you for your attention.
> > I wanted to check other non motion commands and wrote a little gcode file,
> > which I put in the tests/motion-logger/basics directory.
>
> You want to log motion then g-code program is run?
When I discovered motion-logger, I had a misunderstanding and
Ok thanks. Once I get things working and know the register layout of the
finished module I will get some advice as to a final proper address
location.
On Mon, Mar 30, 2020 at 5:01 PM Peter C. Wallace wrote:
> On Mon, 30 Mar 2020, Curtis Dutton wrote:
>
> > Date: Mon, 30 Mar 2020 16:33:13 -0400
On Mon, 30 Mar 2020, Curtis Dutton wrote:
Date: Mon, 30 Mar 2020 16:33:13 -0400
From: Curtis Dutton
Reply-To: EMC developers
To: EMC developers
Subject: [Emc-developers] Mesa Sigma5ABS module
Hi all,
I'm working out the design for the Yaskawa Sigma V absolute encoders.
Within
Hi all,
I'm working out the design for the Yaskawa Sigma V absolute encoders.
Within hostmot2-firmware,
I've been studying the code and I'm not sure of the exact interface between
the mesa pci cards and linuxcnc.
It seems that the pci card is mapping registers into memory and that each
module
> Hi,
>
> I wanted to check other non motion commands and wrote a little gcode file,
> which I put in the tests/motion-logger/basics directory.
You want to log motion then g-code program is run?
___
Emc-developers mailing list
On Mon, 30 Mar 2020 at 01:28, Phill Carter wrote:
>
> I cannot access the discs directory nor the waterfall
I can get to the waterfall (and other results) but not /dists
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses,
Hi,
I wanted to check other non motion commands and wrote a little gcode file,
which I put in the tests/motion-logger/basics directory.
Then I started test.sh, but it blocks.
After adding a log message to test-ui.py I realized, that the new test is
started.
I thought, may be toolchange is the
