# Laurel Panel Meter, Modbus RTU over TCP, FYI

**URL:** <https://forum.inductiveautomation.com/t/laurel-panel-meter-modbus-rtu-over-tcp-fyi/25037>\
**Category:** Ignition\
**Created:** [May 15, 2019, 4:58pm UTC](https://forum.inductiveautomation.com/t/laurel-panel-meter-modbus-rtu-over-tcp-fyi/25037 "2019-05-15T16:58:08Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dano38291](https://avatars.discourse-cdn.com/v4/letter/d/9d8465/32.png) [@dano38291](https://forum.inductiveautomation.com/u/dano38291)\
**Post date:** [May 15, 2019, 4:58pm UTC](https://forum.inductiveautomation.com/t/laurel-panel-meter-modbus-rtu-over-tcp-fyi/25037/1 "2019-05-15T16:58:08Z")

</div>

Hi Guys,

Here’s some Known Modbus RTU over TCP settings that work to talk to this Laurel device.  
[https://www.laurels.com/frequency.php](https://www.laurels.com/frequency.php)  
Its the only Rate Panel Meter I could find with On Board Ethernet plug/ Modbus TCP comms.

-Change Config of Laurel Device so Serial Protocol is Modbus RTU vs Custom ASCII(factory)  
-Set IP address of Meter/ Modbus TCP board.  
-Using Ignition Modbus RTU over TCP driver  
-Uncheck 1’s addressing for 0 addressing  
-Uncheck Span Gaps

Make sure your tag path uses UnitID of device, which is probably default 1.  
You have to read two Registers at a time or Read Fails, hence the second “I”  
[rate]1.IRI3

The Modbus TCP board has the IP address but the meter itself is at UnitID address of 1.  
I spun my wheels with Meter that it came with Custom ASCII protocol enabled, instead of RTU.