Configure Mesa 7i96s and pktuart with Omron MX2 (wj200)

Hey Guys,
this is Stephan from Germany. A 39 years old HW/SW Engineer without any clue about LinuxCNC.
I retrofitted my old Gravorgraph VX92 with a Mesa 7i96s and a Vdf Omron MX2 ( similar to Hitachi WJ200).
LinuxCNC was working with some USB/RJ485 Dongle, and i was able to run my Vdf without any issues.
Thank you for all these comments in this message board. Without your help with other peopleś issues, I would still have to operate my milling machine by hand.

I tried to connect my Vdf without these ModBus USB-Dongle and connected it to the Vdf.
After wasting days to get it running, i decided to write my first question in a forum.

I took my oscilloscope to measure the output of the mesa 7i96s (modbus_mesa.png, not connected with the Vdf this time).
The signal looks pretty fine, but compare to the USB/RJ485 Dongle signal (modbus_USB.png),
I saw only a few packages every 20 seconds.
The Signal of my USB/RJ485 was running every ~10ms (not connected with the Vdf either).

HAL:
#

---

SPINDLE <--->  MODBUS <---> MESACard
loadrt   wj200-vfd ports=hm2_7i96s.0.pktuart.0
addf     wj200-vfd.00 servo-thread

setp     wj200-vfd.00.address                  1
setp     wj200-vfd.00.baudrate                9600
setp     wj200-vfd.00.parity                      0
setp     wj200-vfd.00.update-hz               0.1
[...]

mod file:
/*
The format of the channel descriptors is:

{TYPE, FUNC, ADDR, COUNT, pin_name}

TYPE is one of HAL_BIT, HAL_FLOAT, HAL_S32, HAL_U32
FUNC = 1, 2, 3, 4, 5, 6, 15, 16 - Modbus commands
COUNT = number of coils/registers to read
*/

#define MAX_MSG_LEN 16   // may be increased if necessary to max 251

static const hm2_modbus_chan_descriptor_t channels[] = {
/*  {TYPE,     FUNC, ADDR,   COUNT, pin_name} */

    {HAL_BIT,   5,   0x0001,    1,  "run"},
    {HAL_BIT,   5,   0x0002,    1,  "reverse"},
    {HAL_BIT,   1,   0x0014,    1,  "is-at-speed"},
    {HAL_BIT,   1,   0x000F,    1,  "is-running"},
    {HAL_BIT,   1,   0x0018,    1,  "watchdog-out"},
    {HAL_FLOAT, 3,   0x1003,    1,  "motor-current"},
    {HAL_FLOAT, 3,   0x1019,    1,  "heatsink-temp"},
    {HAL_FLOAT, 6,   0x0001,    1,  "commanded-frequency"},
};




Does anyone knows these issue ?
Thank you so much !

Best Regards, 
Stephan
 

setp     wj200-vfd.00.update-hz               0.1

Means you would  get 1 packet every 10 seconds
(so a 2 in 20 seconds)
 

I removed
setp     wj200-vfd.00.update-hz               0.1
from .hal
Linuxcnc starts without any error, but still no Temperature from VDF (my indicator that it should work).
But if click the Spindle CW Button , my Vdf switched immediately into some E 12.1 Error Code (image):
If I click the ccw button, Linux CNC will close suddenly and create some error log about weird Modbus data. (modbus_error.png).

Itś hard to debug, my Workshop is 75m long walk, it is currently -5°C inside, so i bought a 75m ethernet cable to extend my Wifi for RemoteDesktop.
But i have to reset my Vdf by Hand every  E12.1 Error ( good excercise )
 

Actually I would move to the new and better supported hm2-modbus
as there are some long-standing bugs in mesa-modbus
(the call response  mismatch is a known one)

Hey PCW,
thank you. I updated LCNC from 2.9.4 to 2.9.8 to use mesambccc.
I saw some comment of your gs10 vdf and tried to edit this.
I created a mbccs file only with "run" and "heatsink-temperature" to test

My first question:
in my Omron_MX2.mbccs file. there is some device name. I tried to use a different name like "OmronMX2" but it seems, only gs10 or wj200 should work. [/code][/code]

[/code][/code][/code][/code]
[/code][/code][/code]


[/code][/code][/code][/code][/code][/code]

The device name can be anything but must be consistent within the source file

Not sure about the addf issue, I will take a look at a working gs10- hal file later today

You have this line
addf hm2_7i96s.0.read servo-thread
twice inside the hal file, so that will obviously not work, and i assume the same thing will happen with
addf hm2_7i96s.0.write servo-thread
after you delete the fist offending line.
You have to add this line
addf hm2_modbus.0.process servo-thread
between the already existing READ and WRITE lines, and add
loadrt hm2_modbus ports=hm2_7i96s.0.pktuart.0 mbccbs="Omron_MX2.mbccb"
before those read and write lines.

ohh yes,
I was searching for hm2_7i96s.0.*
But I used addf [HMOT](CARD0).read of my .ini variables in the beginning of my .hal file.
I will check it before work

Hey Guys,
a few hours later, i compile a new mbccs file and implemented these pin names in my .hal file.
I can toggle the pin in LinuxCNC but still no reaction on my Vdf.
There is a little RUN LED on top of the VDF to indicate, if I successfully send the "run" command.
(It worked with the USB-Dongle pretty well)
Can you see any kind of mistakes anywhere ?
I am close to the finishline but getting more and more frustrated

Thank you for any hint

What is the omronmx2 fault status?