Advanced Search

Maybe something with the addf order?

hm2_7i96s.0.encoder.sample-frequency
is a pin, not a parameter

Note that you cannot change the update rate dynamically
if it has ever been set to 0

Here is my list of known mesa-modbus bugs:

    Current Mesa Modbus issues:

    
    BUGS:
    At startup there can be "call/response function number missmatch"
    error popups or sig11 (segv)s due to the fact that the PKTUART is
    not cleared at startup, so random numbers of garbage characters
    may be present in the RX FIFOs, leftover from the last LinuxCNC run.
    
    A temporary workaround is to run this before launching linuxcnc:
    
    mesaflash --device cardname --addr ipaddr --wpo 0x6800=0x00010000
    
    (writing 0x10000 to 0x6800=pktuartr_mode_reg clears the RX FIFOs)

    If you ever set the update rate to 0 (maximum), changing to a
    non-zero rate will not work (communication stops)
    
    There is a check for TX overflow in the PKTUART code that's
    in the wrong location (TX section) so will print bogus error
    messages with particular outgoing messages.
    
    FEATURES:
    
    Channel setting should not be global but in the .mod file
    to support more than one device.
    
    It would be good to have the error timeout/recovery
    time programmable.
    
    For multiple reads/writes it would be good to have the
    possibility of mixed types,
    This means for modbus devices that support table reads,
    all I/O for a device could be done in a single read and a single
    write.



 

PCW post=301477 userid=481Is it possibly just noise related?
that is, what happens if you set:

setp hm2_7i96s.0.encoder.00.filter true
setp hm2_7i96s.0.encoder.sample-frequency 100000

I don't have a .sample-frequency in my parameters, just counter-mode, filter, index-invert, index-mask, index-mask-invert, scale and vel-timeout.

A little bit of playing around with filter on/off didn't seem to make a difference.

Actually I think found a fix for our problem.

Putting the setp for the update-hz after the loadrt scale count=2 makes it work. Moving it up one line so it's right before it makes it break.

I re-enabled the mesa_modbus component.
The encoder seems to jump on every update. update-rate 1 Hz will jump every second, 0.5 once every two seconds, etc...

If I set the update-hz in the HAL to anything but 0, it will jump around. Changing it in halshow to 0 or a different value doesn't help, it will change the rate at which it's jumping but it will never stop.

If I set the update-hz in the HAL to 0 or leave it unset, it jumps around at first, but I can set it to something else and it won't jump around. Setting it back to 0 makes it jump again.

Thank you, but it seems Q2A does not accept Modbus function code 0x06, I always get modbus error 134.
Is there possible somehow to send 0x10 function code?
Thank you.

Hi,

The PC boots fine, the controller turns on (I hear the/a motors energise) I have no movement but the config files have not been configured, its an up to date Linux CNC.

between Inkscape and blender i am making myself crazy i am looking to explore the more creative side of things i can do on this machine but figuring out how to do a Z axis height map from a 2d image is out of the normal box for me and proving to be a bit of a challenge for me  

Could you share how I achieved it?

Awesome. It works flawlessly now. And I have what I always wanted. I have to home only once after starting LinuxCNC and now when I push power button, the servos are disabled, but LinuxCNC keeps the position of all the axes. So when I press power again, I don’t have to re-home!!

Yes, you are right .  I saw your video on YouTube.  You made amazing parts with the lathe.  Well done! 
 I turned on the display today.  Now I will play with the configuration.

 

There reason I suspected electrical interference/ too fast encoder filter settings
is that you said the MPG missed counts and that the encoder appears to count,

 (a memory overlap would not be likely to count (slew) but rather have crazy numbers)
 

Well this will not work Flex GUI is PyQt6 and all of lcnc is pyqt5... and QGLWidget is not in Qt6 it's been removed.

JT

Thanks for the quick reply! Will test and report back but enabling/disabling the mesa_modbus was the only thing we changed, nothing else. Wiring stayed the same.

I also tried the following


And got this error


So something is working up to a point.
JT

You must use encoder index enable with encoder feedback
 (and use stepgen index enable if you use stepgen feedback)