# Modbus tcp IP HOST from msg

**URL:** <https://discourse.nodered.org/t/modbus-tcp-ip-host-from-msg/53436>\
**Category:** General\
**Created:** [9 November 2021 08:23 UTC](https://discourse.nodered.org/t/modbus-tcp-ip-host-from-msg/53436 "2021-11-09T08:23:08Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![UnborN](https://avatars.discourse-cdn.com/v4/letter/u/4491bb/32.png) [@UnborN](https://discourse.nodered.org/u/UnborN)\
**Post date:** [18 November 2021 18:38 UTC](https://discourse.nodered.org/t/modbus-tcp-ip-host-from-msg/53436/4 "2021-11-18T18:38:32Z")

</div>

Try this if it helps

> [@IP Address as a variable](https://discourse.nodered.org/t/ip-address-as-a-variable/53225/7):
>
> Maybe this is possible to change the modbus config settings with a node in the collection called Modbus Flex Connector I havent used it in a real world example but i did some tests with a modbus software simulator and seems to work. Here is the flow that sets, as an example, a different port for that modbus config. Flow: [{"id":"c312db7a02c1f4dd","type":"modbus-flex-sequencer","z":"5847b7aa62131d37","name":"","sequences":[{"name":"1","unitid":"1","fc":"FC1","address":"1","quantity":"1"}],…

---

_[View the full topic](https://discourse.nodered.org/t/modbus-tcp-ip-host-from-msg/53436)._