Difference between revisions of "Teltonika FMx 640 With TCP Link Mode"
Fouad Karman (talk | contribs) |
Fouad Karman (talk | contribs) (image size) |
||
| (14 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | ==='''Introduction:''' Understanding what is FMB640 RS232/RS485 TCP Link mode:=== | ||
| + | |||
In this mode link with external device (for example PC) using text messages can be established. FMx has to be connected to the external device through RS 232 on COM1/COM2 port of FMx. Any string of data coming to COM port will be routed to server (if link is currently active). Messages that are exchanged between FMx device and server, have to be packed in Codec.12 format. Here for TCP link establishment, we will use Hercules. For sending messages from FMx to server Terminal will be used. | In this mode link with external device (for example PC) using text messages can be established. FMx has to be connected to the external device through RS 232 on COM1/COM2 port of FMx. Any string of data coming to COM port will be routed to server (if link is currently active). Messages that are exchanged between FMx device and server, have to be packed in Codec.12 format. Here for TCP link establishment, we will use Hercules. For sending messages from FMx to server Terminal will be used. | ||
| − | ==='''Step 1.''' Connect the FMx640 | + | ==='''Step 1.''' Connect the FMx640 to the RS232 on COM1: === |
| − | [[File:FMX640 and RS232 illustration v1.2.png|alt=|center | + | |
| + | |||
| + | |||
| + | [[File:FMX640 and RS232 illustration v1.2.png|alt=|center|800x800px|A Picture to Illustrate the Physical Connection from device side.|frameless]] | ||
==='''Step 2.''' FMx640 Configuration:=== | ==='''Step 2.''' FMx640 Configuration:=== | ||
| − | The FMx configurator you have to set parameters for COM1 or COM2 (depends on which COM port you are using) in global parameters window. You have to modify the server sittings to | + | The FMx configurator you have to set parameters for COM1 or COM2 (depends on which COM port you are using) in global parameters window. You have to modify the server sittings to your PC IP and your TCP port. |
| − | [[File: | + | [[File:GPRS_sittings_.jpg|alt=|frameless|1164x1164px]][[File:RS232_Sittings.jpg|alt=|frameless|1167x1167px]] |
| − | [[File: | ||
| Line 19: | Line 23: | ||
| − | '''Note:''' Try to make sure that your TCP Port is open by checking | + | '''Note:''' Try to make sure that your TCP Port is open by checking it with any port checker websites. |
| + | ==== Message Timestamp==== | ||
| + | |||
| + | Message Timestamp parameter is used to determine if it is necessary to include a timestamp in the RS232 TCP packet when sending it to the server. If the parameter is Enabled, then Codec 13 is used for data sending. Otherwise, Codec 12 is used. | ||
| + | |||
| + | You can also use RS485 which is also suitable for Ascii TCP Link mode. In order to make a link between FMx640 device and server, Domain and Target Server Port have to be set in the working device profile, GPRS data sending Settings section. When the right parameters are set, you can save the configuration to the FMx640 device. | ||
==='''Step 3.''' Establishing FMx test link with server through Hercules and sending messages with Hercule:=== | ==='''Step 3.''' Establishing FMx test link with server through Hercules and sending messages with Hercule:=== | ||
| Line 30: | Line 39: | ||
Here you have to send acknowledgement after receiving the IMEI from the device. then You have to send 01 as a server response. | Here you have to send acknowledgement after receiving the IMEI from the device. then You have to send 01 as a server response. | ||
| − | [[File: | + | [[File:Hercules .jpg|alt=|none|thumb|666x666px|Sending messages with Hercules]] |
| − | |||
You have to choose TCP Server section from the upper menu. In the marked fields. | You have to choose TCP Server section from the upper menu. In the marked fields. | ||
| Line 37: | Line 45: | ||
In this step we need to use the terminal log. When you want to send a message from FMx 640 to the server, write it in Terminal but change your com port and select port which is assigned for COM1/COM2. | In this step we need to use the terminal log. When you want to send a message from FMx 640 to the server, write it in Terminal but change your com port and select port which is assigned for COM1/COM2. | ||
| − | + | [[File:Terminal.jpg|alt=|none|thumb|1002x1002px|Terminal Log Sending Text]] | |
| − | [[File:Terminal | ||
After doing the mentioned configuration you can type your message in the marked field, check +CR and press Send button. If sent successfully, you will see it in Hercules Received data field. | After doing the mentioned configuration you can type your message in the marked field, check +CR and press Send button. If sent successfully, you will see it in Hercules Received data field. | ||
| − | [[File: | + | [[File:TCP ASCII Receive.jpg|alt=|none|thumb|660x660px|Receiving Text from The Terminal to Server Hercules]] |
| Line 50: | Line 57: | ||
In this mode link with an external device for example PC using text messages can be established. We can apply this scenario on FMx640 or FMx125 which have to be connected to the external device through RS232 or RS485. Any string of data coming to device via RS232 or RS485 will be routed to the server ''(if the link is currently active)''. Messages that are exchanged between FMx device and server, have to be packed in Codec.12 format and will receive to the Hercules receiver successfully. | In this mode link with an external device for example PC using text messages can be established. We can apply this scenario on FMx640 or FMx125 which have to be connected to the external device through RS232 or RS485. Any string of data coming to device via RS232 or RS485 will be routed to the server ''(if the link is currently active)''. Messages that are exchanged between FMx device and server, have to be packed in Codec.12 format and will receive to the Hercules receiver successfully. | ||
| + | |||
| + | ====Links for download==== | ||
| + | 1. [https://www.hw-group.com/software/hercules-setup-utility Hercules SETUP utility] | ||
| + | |||
| + | 2. [https://sites.google.com/site/terminalbpp/Terminal20141030.zip?attredirects=0&d=1 Terminal download] | ||
| + | |||
| + | [[Category:FMB640 Manual| 6]] | ||
Latest revision as of 09:52, 23 March 2023
Main Page > EOL Products > FMB640 > FMB640 Manual > Teltonika FMx 640 With TCP Link ModeIntroduction: Understanding what is FMB640 RS232/RS485 TCP Link mode:
In this mode link with external device (for example PC) using text messages can be established. FMx has to be connected to the external device through RS 232 on COM1/COM2 port of FMx. Any string of data coming to COM port will be routed to server (if link is currently active). Messages that are exchanged between FMx device and server, have to be packed in Codec.12 format. Here for TCP link establishment, we will use Hercules. For sending messages from FMx to server Terminal will be used.
Step 1. Connect the FMx640 to the RS232 on COM1:
Step 2. FMx640 Configuration:
The FMx configurator you have to set parameters for COM1 or COM2 (depends on which COM port you are using) in global parameters window. You have to modify the server sittings to your PC IP and your TCP port.
· Modify the Mode from silent to TCP/UDP Ascii mode.
· Make sure that the Baud rate is matching with the baud rate in the terminal, in our example it is the sensor
Note: Try to make sure that your TCP Port is open by checking it with any port checker websites.
Message Timestamp
Message Timestamp parameter is used to determine if it is necessary to include a timestamp in the RS232 TCP packet when sending it to the server. If the parameter is Enabled, then Codec 13 is used for data sending. Otherwise, Codec 12 is used.
You can also use RS485 which is also suitable for Ascii TCP Link mode. In order to make a link between FMx640 device and server, Domain and Target Server Port have to be set in the working device profile, GPRS data sending Settings section. When the right parameters are set, you can save the configuration to the FMx640 device.
Step 3. Establishing FMx test link with server through Hercules and sending messages with Hercule:
In this case we have a PC that is considered to be a server and an external device at the same time. When FMx is configured and connected to the external device, next that we have to do is to start Hercules which is in server side and will be used for sending and receiving messages.
Here you have to send acknowledgement after receiving the IMEI from the device. then You have to send 01 as a server response.
You have to choose TCP Server section from the upper menu. In the marked fields.
Step 4. Receiving messages with Hercules:
In this step we need to use the terminal log. When you want to send a message from FMx 640 to the server, write it in Terminal but change your com port and select port which is assigned for COM1/COM2.
After doing the mentioned configuration you can type your message in the marked field, check +CR and press Send button. If sent successfully, you will see it in Hercules Received data field.
The Conclusion:
In this mode link with an external device for example PC using text messages can be established. We can apply this scenario on FMx640 or FMx125 which have to be connected to the external device through RS232 or RS485. Any string of data coming to device via RS232 or RS485 will be routed to the server (if the link is currently active). Messages that are exchanged between FMx device and server, have to be packed in Codec.12 format and will receive to the Hercules receiver successfully.
