Mesa modbus and pktUart

That's weird, I'll have to try and duplicate this tomorrow.

Have you considered posting an issue on the LinuxCNC github?
I can do this if I can duplicate the fault.

Is this with spindle synchronized motion?

I tried to duplicate this but found no issues with following errors
either with stepgen or encoder feedback and mesa_modbus
running and switching a relay module.

I wonder if  this is related to your sigv

Can you post your .mod file?

itsme wrote:

rodw wrote:

...
A better approach might be to attract Andy's attention and work with his shiny new component. I'm sure he'll help as that was his intended use.
​​​​
It seems I missed Andy's new component, can you please help me finding it? Thanks!
 

I think rodw was referring to this: forum.linuxcnc.org/29-forum-announcement...river-for-mesa-cards
 

Apologies for the delay. I'm adding a rotary axis to my machine. Anyway, I attached the .mod file and the component I need in front of it. The architecture is shown in the attached pdf file. I see no way to use the mesa_modbus component otherwise because the motor on/off and speed commands must be converted to a specific format for the Huanyang GT series VFD.
Jim
(remove .txt from .mod file, extension not allowed)

EDIT: What's a sigv?
 

Sorry is was not sigv it was sig8 = floating point error.
I think these the are likely caused by a divide by zero.

There are some divide by zero possibilities in your component, for example
what happens if max-speed and speed-in are both  0?

Also why did you comment out the MAX_MSG_LENGTH definition?
I would set this quite high based on what I reported about serial noise/
garbage possible exceeding this threshold and causing a crash
(at least until mesa_modbus has some protection against too-long
input data)

Good point on the divide by zeros. Will take care of that.
The mesa_modbus template has this line commented out and since I had no clue otherwise, I just left it. I'll set it to a high number and try it out again. 
Jim
EDIT: Now that I think of it, that explains why the sig8 error disappears if I set the parameters first and then addf the component. After that, there is no possibility of divide by zero as long as I don't intentionally set max_speed to 0.
EDIT again: In fact, I'll do the same to the mesa_modbus component, ie. params first, then addf.