# Connecting to a DESPATCH protocol 3 using Modbus

**URL:** <https://forum.inductiveautomation.com/t/connecting-to-a-despatch-protocol-3-using-modbus/7955>\
**Category:** Archived Topics\
**Created:** [February 4, 2014, 10:49pm UTC](https://forum.inductiveautomation.com/t/connecting-to-a-despatch-protocol-3-using-modbus/7955 "2014-02-04T22:49:00Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![plarochelle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/plarochelle/32/29608_2.png) [@plarochelle](https://forum.inductiveautomation.com/u/plarochelle)\
**Post date:** [October 3, 2022, 2:14pm UTC](https://forum.inductiveautomation.com/t/connecting-to-a-despatch-protocol-3-using-modbus/7955/10 "2022-10-03T14:14:11Z")

</div>

Phil - you unknowingly replied to a topic about a Despatch oven about a year ago: [Automation Professionals' Advanced Modbus Driver - #22 by pturmel](https://forum.inductiveautomation.com/t/automation-professionals-advanced-modbus-driver/41312/22)

The issue we found with the Protocol 3 is that it uses Function code 23 to edit profiles - I believe you added functionality in your Modbus module.

We ended up specifying Watlow F4T controllers on new Despatch ovens. The costs are a bit more than the Protocol 3 but the engineering hours saved in working with the Modbus protocol is definitely worth it.

---

_[View the full topic](https://forum.inductiveautomation.com/t/connecting-to-a-despatch-protocol-3-using-modbus/7955)._