Geotab Support Forum

The attached document can be used to send 3rd party data to the GO unit. The document applies to GO2/GO3 and GO4 units. A separate harness is required that connects to the GO3/GO4 external UART, and provides a RS232 connection. The harness is sold separately. The attached document also includes the schematic for GO3/GO4 units. There is an option in Checkmate under the logging parameters tab to "beep on custom data". When this option is enabled, the unit will beep every time it receives a valid RS232 message. The logging parameters tab can be found by editing a device in the Setup-Devices window.

Once the data is delivered to checkmate, the RS232 data will be stored in the "CustomData" table in the SQL database.

I understand that the data is in the database table "CustomData", but is the custom data available in Checkmate some how?

You can access the data from the "CustomData" table or write an application to interpret the bytes as Checkmate would not know how to interpret it. It will just receive the data from the GO device and store it in the table.

Hello tonypartheniou,is it possible to connect my improvise harness direct to pin connector configuration as per your attachment.

Hello,

We offer an optional RS232 harness for GO2 and GO3/GO4 units. if you have the proper connector, you can create your own harness - however we recommend ordering the optional harness from your local dealer since it is built in a production environment.

Hello Tony,

With regards to the "beep on custom data" configuration option where has this gone in the latest version of Checkmate? I have hooked up an external device and I would like to verify that I am receiving data.

Thanks,

olds_gearhead

Hi,

The setting has been removed from the software since it is not commonly used. You can use the custom parameter that I've included below to apply the setting to your device. You can apply the parameter by selecting 'Edit' for the device in question; select the 'More' option under the device tab; select the 'Custom parameter' tab. Copy and paste the string below into the Custom Parameter

A few more questions on this as follows.

What beeps are typical with use of the 3rd party data?
If you look at a decrypted text file how can you identify the 3rd party data?
Are there any indicators in the GPS data string that can verifiy that the data is being transmitted?
Who is currenty using this successfully and for what peripherals?
Has any one tried to connect a road watch temperature sensor to a Go device?
Is the RS232_External_Data_Message_Format.zip document the most up to date version of using an external device over the RS-232?

Thank you

What beeps are typical with use of the 3rd party data?

Single beep on very third party message if the "beep on third party" is enabled

If you look at a decrypted text file how can you identify the 3rd party data?

The data should be visible in the Engine Status view in Checkmate under the data ID that they were assigned

Are there any indicators in the GPS data string that can verifiy that the data is being transmitted?

We reply with a third party data acknowledge on receipt of every message

Who is currenty using this successfully and for what peripherals?

We use it for Garmin and Iridium satellite, I believe some resellers have connected a weigh scale and RF ID.

Has any one tried to connect a road watch temperature sensor to a Go device?

I have not heard of anybody connected a road watch temperature sensor however, as long as they follow the 3rd party message format the device will save the data in the custom data table.

Is the RS232_External_Data_Message_Format.zip document the most up to date version of using an external device over the RS-232?

No, that is an old document. For the newest Thirdy Party document please go to our downloads section and download the document called Third Party Protocol.