I’ve confirmed that data from an external Bluetooth device can be forwarded to my server (this direction works fine).
Now I’m trying to understand whether there is also a reverse channel:
Can the server send data back through the FMC003 to the paired Bluetooth device?
On some Teltonika devices I found documentation mentioning CMD ID / Type = 0x0E or 0x10 for forwarding to external devices (e.g. RS232 / Bluetooth forwarding). However, on the FMC003 I can’t get this working:
In debug logs, the commands seem to be recognized, but there is no effect on the external device.
0x0E returns something like “RS232 not configured” (makes sense since FMC003 has no Hardware RS232).
0x10 doesn’t seem to provide the “forward to paired Bluetooth device” function on this model.
So my question is:
Is there any supported way on FMC003 to send arbitrary data/commands from the server back to a paired Bluetooth device?
I’ve seen some posts in this community suggesting that the answer might be yes.
If yes, which codec/command type should be used (Codec12/13/14?), and are there any required configuration steps?
Indeed as you mentioned, it’s possible to send commands from you Server back to the Bluetooth device that’s paired with the FMC003.
Please ensure that Data Link is configured in Blutooth Tab > Auto Connect to External Device, and Bluetooth is Enabled.
Also, the command that needs to be fowarded to the External Bluetooth device needs to be encapsulated in a Codec 12 message format, then sent to the Teltonika tracker over GPRS when the Data Link (GPRS Session) between the FMC003 and Server is Open.
Make sure that Codec 12 protocol is implemented on your Server. You can learn more about this protocol by clicking on the link below:
For example, let’s say you need to send the following command to the External Bluetooth device to control a certain fonctionality: #FWD DAT= 3,1,A00101A2
#FWD DAT= 3,1,A00101A2 => Covert it from ASCII to Hex =>
0x 23 46 57 44 20 44 41 54 3D 20 33 2C 31 2C 41 30 30 31 30 31 41 32 => Encapsulate it in a Codec 12 message format => 0x 00 00 00 00 00 00 00 1E 0C 01 05 00 00 00 16 23 46 57 44 20 44 41 54 3D 20 33 2C 31 2C 41 30 30 31 30 31 41 32 01 00 00 14 0C => Send this command to the FMC003 from your Server when the Data Link (GPRS Session) is Open
thanks for your message — that was the breakthrough. I did know that I have to wrap it using Codec12, but I’m still missing one key part: where is the #FWD command documented?
When I search for it, I can only find hints in the firmware/debug logs, but no official documentation page describing the syntax and parameters.
Regarding the example:
#FWD DAT= 3,1,A00101A2
The first parameter seems to indicate the interface. From what I can tell: 1/2/3 = RS485 / RS232 / Bluetooth (or similar mapping depending on model). Is that correct for the FMC003?
What exactly does the second parameter represent?
And for the payload: A00101A2 looks like raw hex bytes. Is there a way (a parameter/format change) to send an ASCII string directly, or do I always need to convert the string to hex bytes before sending?
Hi again,
I think i get it. The second parameter is 0 for text data, 1 for binary.
What is de maximum datasize ?
But the big question is open, where is this documented
