TFT1OO Raw Data Problem

Hello,
I am trying to receive data from the TFT100 device via TCP/IP using the Node-RED platform.
At this point, I am experiencing a problem.
The raw data arriving at the Node-RED platform shows the Manual CAN data as 00 00 00 00 00 00 00 00.

An example raw data array is as follows:

[0,0,0,0,0,0,4,137,142,3,0,0,1,149,200,151,249,240,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,3,132,0,43,0,6,0,239,0,0,240,1,0,21,5,0,200,0,0,69,2,0,113,94,0,6,0,181,0,0,0,182,0,0,0,66,46,48,0,24,0,0,0,67,15,233,0,68,0,0,0,1,0,241,0,0,111,185,0,30,3,132,65,0,58,0,0,0,0,0,3,133,0,0,0,0,0,0,0,0,3,134,0,0,0,0,0,0,0,0,3,135,0,0,0,0,0,0,0,0,3,136,0,0,0,0,0,0,0,0,3,137,0,0,0,0,0,0,0,0,3,138,0,0,0,0,0,0,0,0,3,139,0,0,0,0,0,0,0,0,3,140,0,0,0,0,0,0,0,0,3,141,0,0,0,0,0,0,0,0,3,142,0,0,0,0,0,0,0,0,3,143,0,0,0,0,0,0,0,0,3,144,0,0,0,0,0,0,0,0,3,145,0,0,0,0,0,0,0,0,3,146,0,0,0,0,0,0,0,0,3,147,0,0,0,0,0,0,0,0,3,148,0,0,0,0,0,0,0,0,3,149,0,0,0,0,0,0,0,0,3,150,0,0,0,0,0,0,0,0,3,151,0,0,0,0,0,0,0,0,3,152,0,0,0,0,0,0,0,0,3,153,0,0,0,0,0,0,0,0,3,154,0,0,0,0,0,0,0,0,3,155,0,0,0,0,0,0,0,0,3,156,0,0,0,0,0,0,0,0,3,157,0,0,0,0,0,0,0,0,3,158,0,0,0,0,0,0,0,0,3,159,0,0,0,0,0,0,0,0,3,160,0,0,0,0,0,0,0,0,3,161,0,0,0,0,0,0,0,0,0,0,0,0,1,149,200,151,253,216,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,3,133,0,43,0,6,0,239,0,0,240,1,0,21,5,0,200,0,0,69,2,0,113,94,0,6,0,181,0,0,0,182,0,0,0,66,46,101,0,24,0,0,0,67,15,245,0,68,0,73,0,1,0,241,0,0,111,185,0,30,3,132,65,0,58,0,0,0,0,0,3,133,22,213,22,213,0,0,6,83,3,134,0,0,0,0,0,0,0,0,3,135,0,0,0,0,0,0,0,0,3,136,0,0,0,0,0,0,0,0,3,137,0,0,0,0,0,0,0,0,3,138,0,0,0,0,0,0,0,0,3,139,0,0,0,0,0,0,0,0,3,140,0,0,0,0,0,0,0,0,3,141,0,0,0,0,0,0,0,0,3,142,0,0,0,0,0,0,0,0,3,143,0,0,0,0,0,0,0,0,3,144,0,0,0,0,0,0,0,0,3,145,0,0,0,0,0,0,0,0,3,146,0,0,0,0,0,0,0,0,3,147,0,0,0,0,0,0,0,0,3,148,0,0,0,0,0,0,0,0,3,149,0,0,0,0,0,0,0,0,3,150,0,0,0,0,0,0,0,0,3,151,0,0,0,0,0,0,0,0,3,152,0,0,0,0,0,0,0,0,3,153,0,0,0,0,0,0,0,0,3,154,0,0,0,0,0,0,0,0,3,155,0,0,0,0,0,0,0,0,3,156,0,0,0,0,0,0,0,0,3,157,0,0,0,0,0,0,0,0,3,158,0,0,0,0,0,0,0,0,3,159,0,0,0,0,0,0,0,0,3,160,0,0,0,0,0,0,0,0,3,161,0,0,0,0,0,0,0,0,0,0,0,0,1,149,200,152,5,168,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,3,133,0,43,0,6,0,239,0,0,240,1,0,21,5,0,200,0,0,69,2,0,113,94,0,6,0,181,0,0,0,182,0,0,0,66,46,89,0,24,0,0,0,67,15,243,0,68,0,75,0,1,0,241,0,0,111,185,0,30,3,132,65,0,58,0,0,0,0,0,3,133,22,212,22,212,0,0,6,83,3,134,0,0,0,0,0,0,0,0,3,135,0,0,0,0,0,0,0,0,3,136,0,0,0,0,0,0,0,0,3,137,0,0,0,0,0,0,0,0,3,138,0,0,0,0,0,0,0,0,3,139,0,0,0,0,0,0,0,0,3,140,0,0,0,0,0,0,0,0,3,141,0,0,0,0,0,0,0,0,3,142,0,0,0,0,0,0,0,0,3,143,0,0,0,0,0,0,0,0,3,144,0,0,0,0,0,0,0,0,3,145,0,0,0,0,0,0,0,0,3,146,0,0,0,0,0,0,0,0,3,147,0,0,0,0,0,0,0,0,3,148,0,0,0,0,0,0,0,0,3,149,0,0,0,0,0,0,0,0,3,150,0,0,0,0,0,0,0,0,3,151,0,0,0,0,0,0,0,0,3,152,0,0,0,0,0,0,0,0,3,153,0,0,0,0,0,0,0,0,3,154,0,0,0,0,0,0,0,0,3,155,0,0,0,0,0,0,0,0,3,156,0,0,0,0,0,0,0,0,3,157,0,0,0,0,0,0,0,0,3,158,0,0,0,0,0,0,0,0,3,159,0,0,0,0,0,0,0,0,3,160,0,0,0,0,0,0,0,0,3,161,0,0,0,0,0,0,0,0,0,0,3,0,0,190,29]

However, when I define the device on the Flespi platform, the Manual CAN data is displayed correctly.
Additionally, when I connect to the device via Bluetooth,
I can also see the correct data.

What could be the possible reasons for this issue? Thank you for your help.

Dear @skayz,

I hope you are doing well. Based on your feedback, it seems that the device was properly sending the data to the server, however the Node-RED was not able to parse the data correctly.

Suggesting that you confirm if the platform is following the Codec Protocol for parsing the device’s raw data. For more information, you may refer to this link: Codec - Teltonika Telematics Wiki

Best regards,
Patrick

Hello Dear @Patrick_Sangalang,

I am following the relevant documentation to parse the raw data in the current situation, but I am experiencing a few problems.

I can see the correct Manual Can values via Bluetooth connection via
Configurator on the device installed in the vehicle.

However:

1 - The server always receives the same raw data over TCP/IP.
2 - The Manual Can values in the received raw data are incorrect.

What are the possible problems?
What approach should I take?

Thank you.

Hi @skayz,

Good day! Were you able to acknowledge the number of records received from the device? In this case, if not you would received the same raw data again and again.

On the other hand, Manual CAN values first needs to be checked from the specific AVL ID and then convert the HEX data to a either Decimal or Binary as per the parsing required from the component you had connected the device.

Kind regards,
Patrick S.

Dear @Patrick_Sangalang

The current loop is as follows:

TCP Connection → IMEI → IMEI Response [0x1] → TCP Out
TCP Connection → AVL Data → AVL Response [0x0,0x0,0x0,0x3] → TCP Out
TCP Connection → IMEI → IMEI Response [0x1] → TCP Out
TCP Connection → AVL Data → AVL Response [0x0,0x0,0x0,0x3] → TCP Out

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