Inntele

I've did. But I used Modbus instead of Iverter Protocol, because the first is more effective on time of request-responce than the second. Making this program I did read the abovemtioned document and based on it. The information in it is enough, but it's necessary to read it with great attention, because the information is very segmented(

RTFM. In FX series there is a special instruction for time addition. What PLC model are you using?

will not support programming instructions for Modbus comm, but can support programming implementation of Modbus protocol like non procedural.

This is an initial school arithmetic rule: Y=X**1.5=X**(1+0.5)=(X**1)*(X**0.5)=X*SQRT(X)

There is an instruction (D)PRUN [FNC 81], which copyring an octal set of bits to an octal set of bits. For example, PRUN K3X16 K3M16 will copy: X16 -> M16 X17 -> M17 X20 -> M20 X21 -> M21 X22 -> M22 X23 -> M23 X24 -> M24 X25 -> M25 X26 -> M26 X27 -> M27 X30 -> M30 X31 -> M31 https://dl.mitsubishielectric.com/dl/fa/document/manual/plc_fx/jy997d16601/jy997d16601q.pdf  , page 460  

X28 and X29 with FX3G LOL "This is the easiest way how I could explain the problem" you're facing.

LD X0 OUT M0 [END] where M0 is a desired signal of presence the pulse sequence at X0 input  

Hi, This module is not an intelligent, it's just a converter of bus connectors from FX5UC CPU to FX5U series modules. So this is not neccessary to configure it.

Hello, You can find a code sample in this topic:  http://forums.mrplc.com/index.php?/topic/36694-how-to-calculate-crc-gx-works-3-fx5/  

Look at the SPD instruction then scale its result to get a level value.

Dear panic mode, I'd like to take your attention to a one thing. A calculation using the traditional math equation will give a correct result only for limited range of integers (the subtraction of in_max/in_min and/or out_max/out_min should not give a result outside the range of -32768 - 32767). If it's necessary to operate with a full range of integer values (16-bit AD/DA analog modules), another integer arithmetics should be used, that requires more math operations.

Yes

Sorry for delay with answer, just finished a commissioning work with FX5 and full of new uncensored impressions, regarding to Mitsubishi docs/soft. The cooperation with Beijer was not a jift for Mitsubishi. Beijer did a lot for technical support of Mitsubishi products, while Mitsubishi did nothing for that. When several years ago Mitsu has quarelled with Beijer, offended Beijer has deleted all materials related to Mitsu products from own website. And it became a strong strike onto Misubishi ***.

1. You have not attached the screenshot of RS485 port settings . 2. You have not attached data (comm port settings, modbus address) for E5DC. 3. How the RST M0 command is related to ADPRW and Modbus comm??

FX3U is supplied with instruction for Modbus CRC16 calculation that's named CRC.

I spent for a one, A ONE WEEK, just to translate a program from L02CPU to FX5. No, its programmer did not use instructions that is supported by L02CPU, but does not supported by FX5... it's just impossibility to convert the old project to a new. It's a lack of software compatibility from the bottom to up. It's a big bullshit. A very stupid management, hired blunt performers.

Ron_S, it's nothing. I'm sitting at work for a month and a half, which, if Mitsubishi knew how to prepare properly a technical documentation, could be done in two weeks.

Check the length of Snd/Rcv buffers

FB = Function Block

For the second MB channel the FB can be used, that is available at ME FA website after registration there  https://gb3a.mitsubishielectric.com/fa/en/

Differences between Modbus CRC16 and XModem CRC16: Modbus: XOR the data byte with low byte of CRC Right shifting XModem XOR the data byte with high byte of CRC Left shifting  

The key problem is in this. At present you are processing only very short messages. When the length of messages will increase, the scan time will stretch, that may affect (will effect) to control processes. Despite on it's just a one of sources of input data for control process...

You have not read both manuals (to VFD & PLC Comm) carefully. In particular: - The Com-port settings will become actual since the next program scan. When its settings is performing, the Com-port must be empty. Thus, the Com-port should be adjusted (re-adjusted) one scan before the RS instruction activation. If you don't use several protocols at the same port, the Com-port settings might be done only once, in the first scan. - The array of message should be represented either in 16-bit, or in 8-bit mode form, but no as a mix. - The VFD ParamNum in Modbus message = VFD ParamNum - 40001 - The VFD ParamValue is represened in BCD, not BIN, format. etc. etc. All mentioned is written in manuals. So read the manuals with attention again. Related to the VFD parameters setting yet can not say exactly. Will check it next week.

Have looked at... All is wrong in your program...