Search results

Take a look at the Fuji FRENIC Multi Instruction Manual, specifically pages 5-58 and 3-2 (excerpts shown below): https://www.fujielectric-europe.com/fileadmin/02_Products/01_Drives_and_Automation/01_07_discontinued_products/frenic_multi/instruction_manual_multi_en.pdf Some parameters, such as...

Thanks for the additional details. What you've done seems like the typical approach I've seen. Depending on the logic required, though, it may have been possible to do this with just a gateway that, in addition to protocol conversion, also supports PLC-style logic built-in, without needing the...

Can you explain a bit more? Was protocol conversion required, which is why you needed a gateway? Did the Daikin HVAC unit replace a unit from a different manufacturer (or different, incompatible model from the same manufacturer), and so it needed to appear to the BAS as if nothing had changed...

You may find it easier to use a different Modbus software tool that supports viewing and modifying values directly in ASCII or hexadecimal. I believe Modbus Poll allows you to view values as ASCII / Hex: https://www.modbustools.com/modbus_poll.html

If Simply Modbus does not allow you to enter values as hexadecimal, you will need to convert from hexadecimal to decimal. You can do this with a calculator, such as the following: https://www.rapidtables.com/convert/number/hex-to-decimal.html For example, the characters "AB" have a hexadecimal...

These are ASCII characters. https://www.asciitable.com/ Each Modbus (16-bit) register is comprised of two ASCII characters. It is perhaps easier to understand by looking at the hexadecimal encoding of the value, instead of the decimal encoding. Digits 0 - 9 use hexadecimal codes of 0x30 -...

Hello and welcome to the forum. I'm going to assume that "...but cannot get good values to register" means you are reading values, just not the values you expect. If this is the case, the issue is not a connection issue (since you must have successfully established a connection in order to read...

You're welcome. I'm happy to help. I completely understand about company policies for schematics, however, that's not actually what I was asking for. Any publicly available documents for your device(s), such as a user's manual, installation guide, wiring diagram, etc. would be sufficient to...

Hello and welcome to Control.com! One potential cause for the issues you are describing is a software bug or unhandled/unexpected fringe-case condition or timing condition that your Modbus driver does not handle correctly. However, these communication issues may actually be caused by lack of a...

There may be multiple tags at work here mapping to different Modbus registers. It is entirely possible, and somewhat common, to map the same data to multiple registers, coils, etc. in Modbus. One common example (though this is not what's being done here) is mapping digital outputs to both coils...

Thank you for the detailed explanation. I think I understand now. As mentioned previously, the VA is irrelevant to the Modbus client (ESP32 in your case). What is required by the Modbus client is the Base Address. Therefore, instead of having a user enter the specific type of unit and a VA...

I'm sorry, but I don't understand what it is you're trying to accomplish and therefore don't understand the problem you're trying to solve. Can you please provide a high-level description of your project or application? Is this for a one-time integration? Are you designing a new product that...

Hello and welcome to the forum! If I'm understanding your question correctly, you're confused about CoolMaster's Virtual Address concept. The following pages discuss this topic: https://support.coolautomation.com/hc/en-us/articles/4415361550737-CoolMaster-Virtual-Addresses...

#1 is odd and doesn't seem to be related to Modbus communications at all. It seems to be some issue/disconnect internal to the HMI between the graphics and the tag. Therefore, retries should not have any effect (perhaps seeing a positive effect was just a coincidence with a randomly occurring...

I recommend starting by simplifying the problem. Split it in half by using a Modbus Client simulator on your computer and trying to establish communications with the PLC, reading only a single Holding Register. After you've succeeded doing this, then use a Modbus Server simulator on your...

As I said I'm not familiar with the Schneider software, but to me it seems you may be reading data from the REX640 by reading coils (function code 0x01) in Modbus Poll, but in the Schneider software it seems you may be attempting to read data by reading registers (e.g. Holding Registers using...

A little more Google searching... In your Diagnostics Viewer screenshot, I noticed it shows a RequestStatus of "blocked". Here is what Schneider's troubleshooting guide...

You confirmed that the REX640 is setup correctly for Modbus communication by successfully communicating to it from Modbus Poll. Your issue most likely lies in the configuration of the Schneider Power Monitoring Expert software. I'm sorry, but I have never actually used this Schneider software...

Is anything useful shown under the "Communication Diagnostics" node in that tree?

In the StruxureWare Management Console, click on the Tools menu and select System > Diagnostics Viewer to find more information about why the status is marked as "Failure".