# TCP Driver device field delimiter **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [July 14, 2025, 1:46pm UTC](https://forum.inductiveautomation.com/t/tcp-driver-device-field-delimiter/108430 "2025-07-14T13:46:08Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![PedroR](https://avatars.discourse-cdn.com/v4/letter/p/7bcc69/32.png) [@PedroR](https://forum.inductiveautomation.com/u/PedroR)\ **Post date:** [July 14, 2025, 1:46pm UTC](https://forum.inductiveautomation.com/t/tcp-driver-device-field-delimiter/108430/1 "2025-07-14T13:46:08Z")
Hi, I am implemating a Bilanciai weighbridge serial 232 port using a Moxa Nport serial converter for TCP/IP. The table bellow is the string that the divice send. | Column 1 | Column 2 | Column 3 | Column 4 | | --- | --- | --- | --- | | 1st character | $(24H) | string start character | | | 2nd – 10th character | | net weight with sign and decimal point (if present) | | | 11th character | (20H) | space | | | 12th – 20th character | | tare with sign and decimal point (if present) | | | 21st character | (20H) | space | | | 22nd – 23rd | | unit of measurement | | | 24th character | (20H) | space | | | 25th character | | scale status | | | 26th character | | scale status | | | 27th character | | scale status | | | 28th character | | scale status | | | 29th character | (0DH) | | | | 30th character | (0AH) | | | | | | | | I have the "$" in the message delimiter and 4 field count. Now is just missing the field delimiter but look that i can´t insert a "space" in this field. Is it possible to sue a space as a field delimiter? Regards ---
**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:** [July 14, 2025, 1:50pm UTC](https://forum.inductiveautomation.com/t/tcp-driver-device-field-delimiter/108430/2 "2025-07-14T13:50:36Z")
Consider using CRLF as your ~~field~~ _ **message** _ delimiter, and accept the entire string as the value. In an OPC tag linked to the message buffer, find the offset of the `$` character, and use string slicing from there to extract the fields by position. ---
**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:** [July 14, 2025, 1:54pm UTC](https://forum.inductiveautomation.com/t/tcp-driver-device-field-delimiter/108430/3 "2025-07-14T13:54:11Z")
Using `\s` for the field delimiter may work... you'll have to try it and see. ---
**Author:** ![PedroR](https://avatars.discourse-cdn.com/v4/letter/p/7bcc69/32.png) [@PedroR](https://forum.inductiveautomation.com/u/PedroR)\ **Post date:** [July 14, 2025, 4:04pm UTC](https://forum.inductiveautomation.com/t/tcp-driver-device-field-delimiter/108430/4 "2025-07-14T16:04:56Z")
Is working with 20 fields and 0 kg. the data appears at field 8, 17, 18 and 19. 8 shows the net weight 17 show tare 18 unit of measurement 19 the 4 scale status If the kg change the fields get broken. ---
**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:** [July 14, 2025, 4:10pm UTC](https://forum.inductiveautomation.com/t/tcp-driver-device-field-delimiter/108430/5 "2025-07-14T16:10:29Z")
> [@PedroR](#): > > working with 20 fields Space delimiters won't work if the weight fields are **padded** with spaces. Use my advice above.