FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

4167 questions

4739 answers

3460 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
500 views
in Vehicle tracking by anonymous
We are going to use FMC640 to send RS232 data to the server. How to enable RS232 and transfer the RS232 data in Codec 8 protocol?

Can you please kindly guide us the document for this use case?

1 Answer

0 votes
by anonymous

Hello,

If you are going to use the TCP Link mode via RS232 to transfer the information from an external device to the server, this action can only be performed through Codec12. If you want to add a timestamp to the packet, then the codec used will be Codec13. 

You can read about the FMC640 RS-232 modes and Codecs on the followings links: 

Kind regards. 
Best answer
by anonymous

Thank you very much. How to set the FMC640 to use Codec12 or Codec13? I open the configuration tool, can only find Codec8 and Codec8E.

by anonymous

Hello! 

Codec 12 does not need activation, it sets automatically when you select the TCP Link mode. Same way for Codec 13, it sets automatically when you enable the Message Timestamp on RS232 Settings.

You can identify which codec the tracker sends to the server by the Codec ID:

  • Codec8: 0x08
  • Codec 8 Extended: 0x8E
  • Codec 12: 0x0C
  • Codec 13: 0x0D

Best regards. 

by anonymous
Thanks. In our case, we will use UDP to send RS232 data to server. It seems the protocol codec12 and 13 only describe for TCP.

Is there a description of codec12 and codec 13 protocol for UDP?
by anonymous

Hello,

The structure of the sent commands is the same. There is no difference in what protocol is used to open a session/send records, TCP or UDP. The structure of commands sent over UDP is the same as the structure of commands sent over TCP.

Kind Regards.

by anonymous
Thanks.

The structures of AVL record (codec8) for TCP and UDP have many differences... I thought codec12 should should be different for UDP and TCP too.

Kind regards