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

More
06 Feb 2026 16:14 - 06 Feb 2026 16:17 #342555 by Stephan@work
How can i Check this fault status ?
this way ?
Attachments:
Last edit: 06 Feb 2026 16:17 by Stephan@work.

Please Log in or Create an account to join the conversation.

More
06 Feb 2026 19:51 #342562 by PCW
No fault but seems like something very basic is missing/wrong
maybe in the hal file?
 

Please Log in or Create an account to join the conversation.

More
07 Feb 2026 08:41 #342589 by Stephan@work
I will measure the Mesa output signal again and compare them with the running USB-Dongle signals.
Maybe there is something wrong with these PullUp/Down resistors.

If there is any output, it could be the wrong configuration.
If not, maybe something is wrong in my .hal
Is there any chance to see the pktuart output in terminal ?
Like wireshark or candump ?

Thank you!

Please Log in or Create an account to join the conversation.

More
07 Feb 2026 15:25 #342606 by PCW
Is there any communication happening?

That is, do you get a fault if the VFD is not connected?
 

Please Log in or Create an account to join the conversation.

More
07 Feb 2026 18:23 #342615 by Stephan@work
Hey Guys,
bad luck. The communication seems to run between mesa and Vfd. 
Now i measured (in parallel) the connected Mesaoutput with Vfd Input. (mesa_modbus.png)
Compare to the connected USB-Dongle output and Vdf Input (USB_Modbus.png)
Signal Quality looks pretty good. (pktuart seems to work)

I figured out by using the USB-Dongle, that i have to set some Frequency to get this RUN-LED flashing on my OmronMX2 Vdf.
So I implemented all the other necessary Hal Pins to .hal file to check this with the Mesa <--> Vdf communication.
Know, if i click the CW AXIS GUI Button, Iḿ getting the same Error at my Vdf ( E12.1 like a few days ago).

From my point of view, there must be something wrong with the run, reverse or cmd-freq command.
Or still some wrong configuration somewhere.
Iḿ still getting no Vdf temperature out of the Vdf.

so write or read is not Working, 
my current .mbccs:
<mesamodbus baudrate="9600" parity="N" interval="1000" stopbits="1" duplex="half"> 
  <devices>
    <device name="omronmx2" address="0x01"/>
  </devices>
  <initlist>
    <command device="omronmx2" address="0x0001" function="W_COIL">
      <description>Zero Operation</description>
      <data value="0"/>
    </command>
    <command device="omronmx2" address="0x0002" function="W_COIL">
      <description>Reverse Operation</description>
      <data value="0"/>
    </command>
    <command device="omronmx2" address="0x0001" function="W_REGISTERS">
      <description>Frequency</description>
      <data value="0"/>
    </command>

  </initlist>
  
  <commands>
      <command device="omronmx2" address="0x0001" function="W_COIL"       name="run"/>
      <command device="omronmx2" address="0x0002" function="W_COIL"       name="reverse"/>
      <command device="omronmx2" address="0x0001" function="W_REGISTERS"  name="cmd-freq"       haltype="HAL_FLOAT" modbustype="U_AB" count="1"/>
      <command device="omronmx2" address="0x0014" function="R_COILS"      name="is-at-speed"    count="1"/>
      <command device="omronmx2" address="0x0018" function="R_COILS"      name="watchdog-out"   count="1"/>
      <command device="omronmx2" address="0x0013" function="R_COILS"      name="is-running"     count="1"/>
      <command device="omronmx2" address="0x1003" function="R_REGISTERS"  name="motor-current"  haltype="HAL_FLOAT" modbustype="U_AB" count="1"/>
      <command device="omronmx2" address="0x1019" function="R_REGISTERS"  name="heatsink-temp"  haltype="HAL_FLOAT" modbustype="U_AB" count="1"/>
  </commands>
</mesamodbus>

Can someone explain these
<data value="0"/>
?

Once, i had one PDU Error. But i guess it was only a wrong configuration.
Iḿ loosing my motivation, i wasted 3 weeks now 3h a day :(

 
Attachments:

Please Log in or Create an account to join the conversation.

More
07 Feb 2026 19:15 #342617 by PCW
<data value="0"/>

Is register initialization data for the init section of the mbccs file
(since the data is initialization data, not data from hal like the command
section)

What does the last error show? (theres a modbus pin for the last reported error)

This is a really strange error since it seems like CRC checked communication
is happening but no data is being transferred.

Please Log in or Create an account to join the conversation.

More
08 Feb 2026 08:40 #342634 by Stephan@work
this hm2_modbus.0.last-error-code ?
it looks like:
• 110, 0x6e (ETIMEDOUT): The command received no reply and timed out.

But I 'm not sure if this was some consequential error.
I compared the running wj200.comp example of my USB-Dongle
but i can´t see any difference. Do I need some delay somewhere .
I added some interval="1000" like you did in your gs10. but no success.

Please Log in or Create an account to join the conversation.

More
08 Feb 2026 15:37 #342655 by PCW
You might try increasing the interval (it's in microseconds so 1000 is just one ms)
And that may be too fast for the Omron

I will look into getting a MX2 to try to have some way of duplicating the issue.
The GS10 setup was straightforword
 

Please Log in or Create an account to join the conversation.

More
09 Feb 2026 06:18 #342697 by Stephan@work
Thank you Peter, thank you Tom.
I will try to increase the interval.
No pressure with these MX2. I have a running solution with the USB-Dongle.

Thank you !
The following user(s) said Thank You: COFHAL

Please Log in or Create an account to join the conversation.

More
17 Feb 2026 18:16 #343099 by Stephan@work
I'm back !
With some good new !
I figured out my Problem. (read the fvck!ng manual :D )
For some reasons, you have to decrement the Register address by one for "run" and "reverse".

Now I'm struggling with the command-frequency.
I can run the Vdf using the Mesa pktuart. But I there is still a scaling of 2.56
If i send 10Hz to the Vdf, the displayed frequency on my OmronMx2 show me 25.6Hz
same as 100Hz. Vdf - 256 Hz

I checked all combinations of U_AB, U_BA, S_AB, S_BA, F_AB, F_BA.
Did i miss something or choose the wrong LSB/MSB ?

Same as Motor Current.
Heatsink-temperature works pretty well.
<mesamodbus baudrate="9600" parity="N" interval="10000" stopbits="1" duplex="half"> 
  <devices>
    <device name="omronmx2" address="0x01"/>
  </devices>
  <initlist>
    <command device="omronmx2" address="0x0000" function="W_COIL">
      <description>Zero Operation</description>
      <data value="0"/>
    </command>
    <command device="omronmx2" address="0x0001" function="W_COIL">
      <description>Reverse Operation</description>
      <data value="0"/>
    </command>
  </initlist>
  
  <commands>
      <command device="omronmx2" address="0x0000" function="W_COIL"       name="run"/>
      <command device="omronmx2" address="0x0001" function="W_COIL"       name="reverse"/>
      <command device="omronmx2" address="0x0001" function="W_REGISTER"   name="cmd-freq"       haltype="HAL_FLOAT" modbustype="U_BA"/>
      <command device="omronmx2" address="0x0018" function="R_COILS"      name="is-at-speed"    count="1"/>
      <command device="omronmx2" address="0x0017" function="R_COILS"      name="watchdog-out"   count="1"/>
      <command device="omronmx2" address="0x0012" function="R_COILS"      name="is-running"     count="1"/>
      <command device="omronmx2" address="0x1002" function="R_REGISTERS"  name="motor-current"  haltype="HAL_FLOAT" modbustype="S_AB" count="1"/>
      <command device="omronmx2" address="0x1018" function="R_REGISTERS"  name="heatsink-temp"  haltype="HAL_FLOAT" modbustype="F_BA" count="2"/>
  </commands>
</mesamodbus>
Attachments:

Please Log in or Create an account to join the conversation.

Time to create page: 0.129 seconds
Powered by Kunena Forum