how to use motion-logger?

Hi,

rebuild of LC finished. Output of motion-logger is a bit more than at first try, but stil far from (my) expectations. But I admit, that my expectations may be wrong.

So I recorded 2 variants:
Rec1 shows, how I first start LC and then motion-logger with its output.
Rec2 shows the opposite, first start motion-logger and then LC.
Please note how LC fails in the second recording.

Hi,

no solution found yet.

So - did I run into some trivial situation, I should know about?

I think, motion-logger should have some output that is in sync with gremlin output, right?
So when I start gcode processing with motion-logger active and gremlin does not work any more, than something must be wrong, isn't it?

Any advices, how to proceed?

Just verified, that my app works fine together with axis - and yes, it runs in sync with axis gremlin and gcode-lister.

So what does motion-logger different, in that it clobbers axis state and functionality?

You probably need to inquire on the dev list or IRC.
The devs that would know the most about motion logger don't look at the forum.
Well actually, they hardly involved in linuxcnc anymore.

Chris

Well actually, they hardly involved in linuxcnc anymore.

Not sure, if I understand it right.
Does it mean, that lc lost its developer?

I follow the changes on master repository and it looks to me, that only plasma and qt is of interest.
So no one is working on python migration and core?
What a mess!

Most of the active developers of the past are busy with other things these days.
There are really quite few of active devs with push rights.
So most work is done outside of linuxcnc and its hard to get included in a timely fashion.
There was work on python 3, not sure if it got pushed to linuxcnc test branch or not.
Hopefully things will change for the better.

Chris

Hi Chris,

sad to hear that! But ...

... you said, what I already suspected from the changes at master.
So if the core developers have dedicated themselfs to other doings, the knowledge of core has disappeared with them.

And LC is really very big to get into it

Oh they are not all completely gone. Ask your question in the IRC yo may get answer.
It's just time to recruit some more interested people and get away from everyone working on outside projects that are all similar and never getting them incorporated We need a leader to start the ball rolling (IMHO)

Chris

... get away from everyone working on outside projects that are all similar and never getting them incorporated

Yes, its a shame - but plenty of them fork by an idea and died without having a leader or at least passion.
.

We need a leader to start the ball rolling (IMHO)

Yes, I agree completely.
I saw it in many many projects that claim: we don't want a leader, we don't need a leader ...
They never succeed.

A quick look in the run tests (I have to fix one with an update I'm working on), I would bet motion-logger was never meant to run beside the motion component.
both would be trying to be connected to task using shared memory.

They may both use the same shared memory key, or when one connects it locks out the other.

I'm just guesstimating ...

Chris