# Process Control Gravimetric Blender Modbus Device Trouble **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective\ **Created:** [March 28, 2023, 8:02pm UTC](https://forum.inductiveautomation.com/t/process-control-gravimetric-blender-modbus-device-trouble/71729 "2023-03-28T20:02:09Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![hhbauss](https://avatars.discourse-cdn.com/v4/letter/h/ecae2f/32.png) [@hhbauss](https://forum.inductiveautomation.com/u/hhbauss)\ **Post date:** [March 28, 2023, 8:02pm UTC](https://forum.inductiveautomation.com/t/process-control-gravimetric-blender-modbus-device-trouble/71729/1 "2023-03-28T20:02:09Z")
Has anyone had to connect to a PCC Gravimetric blender system before with Ignition? I am upgrading from an old iFix 4.0 line using the iFix MBE driver and am running into tag config issues. I can successfully connect to the blender controller in the Gateway, but the translation between the iFix address and a standard Modbus address is evading me. Example: The modbus address for 'Setpoint A' is 601049? I know they use an extended registers, but I have never run into a holding register that starts with the '6' instead of a '4' for the holding register. I know it is talking because I can see values with the Schneider Modbus tester app...but not using the addresses that the MBE driver lists (and the manufacturer documentation). So....coming here to see if anyone has ever run into this addressing type before? Thanks! ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [March 28, 2023, 8:06pm UTC](https://forum.inductiveautomation.com/t/process-control-gravimetric-blender-modbus-device-trouble/71729/2 "2023-03-28T20:06:48Z")
> [@hhbauss](#): > > The modbus address for 'Setpoint A' is 601049? That's an extended register address (AKA File Record address). IA's driver doesn't support the function codes for those. You need my [Advanced Modbus driver module](https://inductiveautomation.com/moduleshowcase/module/automation-professionals-llc-advanced-modbus). That address would become something like `1.XR1049` in my driver, or possibly `1.XR1048`. (These are not holding registers.) ---
**Author:** ![hhbauss](https://avatars.discourse-cdn.com/v4/letter/h/ecae2f/32.png) [@hhbauss](https://forum.inductiveautomation.com/u/hhbauss)\ **Post date:** [March 28, 2023, 8:10pm UTC](https://forum.inductiveautomation.com/t/process-control-gravimetric-blender-modbus-device-trouble/71729/3 "2023-03-28T20:10:43Z")
I'm going to give that module a whirl! Does it have the 2 hour trial that I can use for testing? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [March 28, 2023, 8:11pm UTC](https://forum.inductiveautomation.com/t/process-control-gravimetric-blender-modbus-device-trouble/71729/4 "2023-03-28T20:11:54Z")
Yes, it honors the 2-hour trial mode like most modules around here. ---
**Author:** ![Hans\_Bauss](https://avatars.discourse-cdn.com/v4/letter/h/7ea924/32.png) [@Hans\_Bauss](https://forum.inductiveautomation.com/u/Hans_Bauss)\ **Post date:** [December 31, 2024, 12:53am UTC](https://forum.inductiveautomation.com/t/process-control-gravimetric-blender-modbus-device-trouble/71729/5 "2024-12-31T00:53:11Z")
What is the trick to writing to a Wonderware tag address that was "664599 L". I have successfully written and read from most other tags, but this Start/Stop buttons are causing issues. Why would the INT32 ( I assume from the manuals that is what I am looking at) cause an issue. Tag in Ignition is written as '0.XRF64599'. I have tried to have it as an INT type(XRI64599) as well as float. Any suggestions using your driver to help with this? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [December 31, 2024, 1:00am UTC](https://forum.inductiveautomation.com/t/process-control-gravimetric-blender-modbus-device-trouble/71729/6 "2024-12-31T01:00:00Z")
> [@Hans\_Bauss](#): > > '0.XRF64599'. This is only valid syntax in Phil's Modbus driver, not IA's. Are you using his driver? edit: oops, looks like you might be upon reading your post more carefully. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [December 31, 2024, 1:26pm UTC](https://forum.inductiveautomation.com/t/process-control-gravimetric-blender-modbus-device-trouble/71729/7 "2024-12-31T13:26:28Z")
> [@Hans\_Bauss](#): > > Start/Stop buttons are causing issues Do note that File Record addresses do not support bit-level writes. But anyways, my driver is always zero-based, so you may need `1.HRI64598`. If you can get me a wireshark capture of what WW is doing, I can be more precise. ---
**Author:** ![hhbauss](https://avatars.discourse-cdn.com/v4/letter/h/ecae2f/32.png) [@hhbauss](https://forum.inductiveautomation.com/u/hhbauss)\ **Post date:** [December 31, 2024, 2:08pm UTC](https://forum.inductiveautomation.com/t/process-control-gravimetric-blender-modbus-device-trouble/71729/8 "2024-12-31T14:08:37Z")
Thanks Phil. I am working on this this morning. It seems that the Long Integers on this blender system are the only addresses that I am having issues with. The read/writes on the other tags with the current settings work great (thanks!)… I am active today for awhile, so I will try and get you a Wireshark dump. Thanks again for your support! ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [December 31, 2024, 2:22pm UTC](https://forum.inductiveautomation.com/t/process-control-gravimetric-blender-modbus-device-trouble/71729/9 "2024-12-31T14:22:18Z")
You are welcome. (But note that I am just dabbling today--working from home on some home office infrastructure. Response time will vary.) Part of the reason I want a capture is I suspect, from that address so close to 65535, that this device is breaking the File Records specification. By using 0-65535 per file instead of 0-9999. If so, then it will not work with my driver, which strictly follows the spec. ---
**Author:** ![hhbauss](https://avatars.discourse-cdn.com/v4/letter/h/ecae2f/32.png) [@hhbauss](https://forum.inductiveautomation.com/u/hhbauss)\ **Post date:** [December 31, 2024, 2:45pm UTC](https://forum.inductiveautomation.com/t/process-control-gravimetric-blender-modbus-device-trouble/71729/10 "2024-12-31T14:45:25Z")
I understand. I was not supposed to work also today. Working with these old PCC blenders is….interesting, to say the least. All things being the same with the driver, I am able to communicate just fine with all the other registers with how the driver is set up (read/write), but these: ![](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/1/4121a0b69fc4bc5150b4ab600e36425984ebeeb4.png)