# Advanced Modbus Module - Scripting Device Creation

**URL:** <https://forum.inductiveautomation.com/t/advanced-modbus-module-scripting-device-creation/98714>\
**Category:** 3rd Party Modules\
**Tags:** scripting\
**Created:** [November 17, 2024, 3:32pm UTC](https://forum.inductiveautomation.com/t/advanced-modbus-module-scripting-device-creation/98714 "2024-11-17T15:32:55Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**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:** [November 17, 2024, 5:39pm UTC](https://forum.inductiveautomation.com/t/advanced-modbus-module-scripting-device-creation/98714/3 "2024-11-17T17:39:20Z")

</div>

As it happens, I've been improving this functionality, but not yet documented or tested. Feel free to try the following with the very latest driver version:

1. The `deviceType` argument is "ModbusClient". The following keys are supported in `deviceProps`: `framing`, `hostname`, `althost`, `backuphost`, `altbackuphost`, `maxoutstanding`, `exectimeout`, `tframeplus`, `shortbrowse`, `txidlimit`, and `unitscsv`.

2. Supply the complete configuration CSV for your slave units as a multiline string for the `unitscsv` device property.

Only `hostname` is required. All others have sane defaults.

{ I consider the `unitscsv` device prop to still be BETA quality. Bug reports welcome, but functionality is not officially supported. Prior versions use a binary encoded prop that doesn't play well with v8.3. So migration through my last v8.1 version will be required. }

---

_[View the full topic](https://forum.inductiveautomation.com/t/advanced-modbus-module-scripting-device-creation/98714)._