890 modbus map

Hello stormpapa135,

Are you talking about Modbus/RTU via the RS485 option card or the Ethernet card and so Modbus/TCP?  There is a difference in terms of how the Modbus mapping is set up, though the general answer is it depends on how you map your data, there isn't a 'fixed' mapping per se.

For Modbus/TCP, the Ethernet block (which you add to your DSELite project) - under the Block -> 890 Comms menu) is where the 'mapping' is done. 

First you add the individual Value Inputs or Value Outputs available under the BLock -> 890 Comms menu to your project, tying them to whatever input or output values in the configuration you want to exchange via  Modbus. 

Then when you go into the EN block (ethernet block) and configure for Modbus, you add Inputs or Outputs and point those individually to the Value Input and Value Outputs you've already added in your configuration.

The details of this are available in the particular option user guide.  The Modbus/RTU uses a different block than the Ethernet (EN) block but similar type of concept.  The particular option user guide you need is available from the 890 product page.  Link here:

AC Variable Frequency Drives, kW Rated - AC890 Series | Parker NA

From this user guide, this page shows the address offsets for Input versus Output data and how many registers are supported if you add that many to your project.  Also shows the function codes supported.  Modbus/RTU will be slightly different, but again, the details are in the RS485 option user guide.

Rough example of Modbus/TCP project shown below.  The 'addresses' shown are more for reference as the actual Input or Output name is arbitrary.

Sincerely,

Gannon

https://www.parker.com/Literature/Electromechanical%20Europe/User%20Guides/HA469261U001.pdf

Specifically, see page 12.

Sincerely,

Gannon

Thanks saved me a bunch of time!

Tree Loppers Frankston