# How to fix this language TCP

**URL:** <https://discourse.nodered.org/t/how-to-fix-this-language-tcp/48565>\
**Category:** General\
**Created:** [19 July 2021 06:09 UTC](https://discourse.nodered.org/t/how-to-fix-this-language-tcp/48565 "2021-07-19T06:09:01Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![ohmsouak](https://avatars.discourse-cdn.com/v4/letter/o/e47c2d/32.png) [@ohmsouak](https://discourse.nodered.org/u/ohmsouak)\
**Post date:** [19 July 2021 06:09 UTC](https://discourse.nodered.org/t/how-to-fix-this-language-tcp/48565/1 "2021-07-19T06:09:01Z")

</div>

i want to sent data from sensor but data received it doesn't know what language.  
have idea for me thank you.

 ![Screenshot (318)](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/e/1efbb427c7bc258d1e8cd18d81d66b3ec4ed2d9e.png)

---

<div class="post-metadata">

**Author:** ![Gunner](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gunner/32/43582_2.png) [@Gunner](https://discourse.nodered.org/u/Gunner)\
**Post date:** [19 July 2021 06:32 UTC](https://discourse.nodered.org/t/how-to-fix-this-language-tcp/48565/2 "2021-07-19T06:32:25Z")

</div>

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/2/5266b59b494ba2252e9a18325bb9b313f39dea36.png)

As it shows, it is a buffer of info that needs "decoding"... What is it you are expecting to see?

---

<div class="post-metadata">

**Author:** ![craigcurtin](https://avatars.discourse-cdn.com/v4/letter/c/94ad74/32.png) [@craigcurtin](https://discourse.nodered.org/u/craigcurtin)\
**Post date:** [19 July 2021 06:32 UTC](https://discourse.nodered.org/t/how-to-fix-this-language-tcp/48565/3 "2021-07-19T06:32:34Z")

</div>

that is a reall weird IP address you have assigned - that normally comes about from MS when you do not have a valid connection - but anyway

You will need to give us a bit more info - what is the data packet that is coming in on port 2000 ?

Craig

---

<div class="post-metadata">

**Author:** ![PNWw](https://avatars.discourse-cdn.com/v4/letter/p/67e7ee/32.png) [@PNWw](https://discourse.nodered.org/u/PNWw)\
**Post date:** [19 July 2021 07:00 UTC](https://discourse.nodered.org/t/how-to-fix-this-language-tcp/48565/4 "2021-07-19T07:00:43Z")

</div>

Both the IP address and the port can be configured by the sensor module. It's a thickness sensor. It communicates in ASCII. We studying how to get the measured value. But We not sure how to resolve this issue with the submitted data.

---

<div class="post-metadata">

**Author:** ![Gunner](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gunner/32/43582_2.png) [@Gunner](https://discourse.nodered.org/u/Gunner)\
**Post date:** [19 July 2021 07:09 UTC](https://discourse.nodered.org/t/how-to-fix-this-language-tcp/48565/5 "2021-07-19T07:09:13Z")

</div>

> [@PNWw](#):
>
> We studying how to get the measured value

Sounds like a school project 😛 I don't get any class credit for studying, so I would suggest you looking at the sensors datasheet to see precisely the format it sends. It might make it easier for you to figure out the rest. Such as determining the best node to use for the "processing/parsing" of the `msg.payload`

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [19 July 2021 07:12 UTC](https://discourse.nodered.org/t/how-to-fix-this-language-tcp/48565/6 "2021-07-19T07:12:31Z")

</div>

> [@PNWw](#):
>
> Both the IP address and the port can be configured by the sensor module

You must configure it with an IP address that is accessible on your network.

---

<div class="post-metadata">

**Author:** ![PNWw](https://avatars.discourse-cdn.com/v4/letter/p/67e7ee/32.png) [@PNWw](https://discourse.nodered.org/u/PNWw)\
**Post date:** [19 July 2021 07:26 UTC](https://discourse.nodered.org/t/how-to-fix-this-language-tcp/48565/7 "2021-07-19T07:26:03Z")

</div>

I understand it can connect and get data back. But it is different from sensor software if you use sensor software to view the values. And I don't know what to do.

---

<div class="post-metadata">

**Author:** ![Gunner](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gunner/32/43582_2.png) [@Gunner](https://discourse.nodered.org/u/Gunner)\
**Post date:** [19 July 2021 07:29 UTC](https://discourse.nodered.org/t/how-to-fix-this-language-tcp/48565/8 "2021-07-19T07:29:50Z")

</div>

> [@PNWw](#):
>
> But it is different from sensor software if you use sensor software to view the values. And I don't know what to do.

We can't even see the data from that IP

As I said, read up on the sensor datasheet, search Google and this forum for other ways of "parsing" data from whatever type the sensor sends (assuming it is not too proprietary... You may even have to write some code in a function node if that is the case).

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [19 July 2021 09:03 UTC](https://discourse.nodered.org/t/how-to-fix-this-language-tcp/48565/9 "2021-07-19T09:03:57Z")

</div>

169.x.y.z is not a valid IP

> **169.254.x.x:** This is what's called an Automatic Private IP address. An IP in this range means that the computer cannot see the network. A computer using [DHCP](https://kb.iu.edu/d/adov) needs to have an external server tell it what IP address to use.

See this [link](https://kb.iu.edu/d/aoyj)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [17 September 2021 09:04 UTC](https://discourse.nodered.org/t/how-to-fix-this-language-tcp/48565/10 "2021-09-17T09:04:13Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
