Recurso Confiable
Forward GPS positions, cargo temperature, and humidity from Navixy to the Recurso Confiable platform over SOAP, used across Mexico and Central America.
Recurso Confiable is a security and logistics platform for transport operations, and this protocol forwards vehicle data from Navixy into it. Carriers use it to deliver tracking data to customers who monitor shipments through Recurso Confiable, without giving those customers access to the Navixy account. It's used in Mexico, Colombia, the United States, and Central America.
Navixy also offers Recurso Confiable (Walmart), a variant for forwarding to Walmart through Recurso Confiable. It's configured the same way as described here.
In Navixy, select Recurso Confiable in the Protocol dropdown.
What Navixy sends
Navixy sends one SOAP request per message to the GPSAssetTracking method. The request contains these fields:
code
The AVL event code for this message. See Recurso Confiable event codes.
asset
The license plate, from the first part of External ID
shipment
The shipment id, from the second part of External ID
customer
The customer id and customer name, from the third and fourth parts of External ID
serialNumber
The Navixy device id
date
When the device recorded the message
latitude, longitude, altitude
Position in degrees, altitude in meters
speed, course, direction
Speed, heading in degrees, and heading as a compass direction
ignition
Whether the ignition is on
odometer
Distance traveled
battery
Battery level
temperature
Cargo temperature, when the device reports it
humidity
Cargo humidity, when the device reports it
vehicleType, vehicleBrand, vehicleModel
Vehicle details from Fleet management
When Navixy sends
Navixy sends a message when it has valid coordinates, or when it reports an urgent event. An urgent event goes out even without a position. Any other message without coordinates is skipped.
Before you start
Collect the following from Recurso Confiable:
The endpoint address and port. The address is commonly
http://gps.rcontrol.com.mx/Tracking/wcf/RCService.svcon port80.Your Recurso Confiable user id and password. Navixy requires both and won't save the retranslator without them.
The license plate, shipment id, customer id, and customer name for each vehicle, as registered on the Recurso Confiable side.
Navixy authenticates by calling GetUserToken with the user id and password, then reuses the token until it expires.
Set up forwarding
Set the External ID
Click the link icon at the right of the retranslator row, then enter up to four values joined by pipe characters, in this order:
For example, ABC123|1|123|John.

Only the license plate is required, and it must be 5 to 7 characters:
When you skip a value in the middle, keep its pipe so the remaining values stay in the right positions:

Repeat this step and the previous one for every device that forwards to Recurso Confiable. The retranslator configuration is shared across the account, but External ID is set per device.
Manage forwarding
To change or stop forwarding to Recurso Confiable:
Click the link icon at the right of the retranslator row to change the External ID of a device.
Switch off the toggle to stop forwarding for one device, and keep the configuration for the others.
Click Protocols, select the row, and edit it to change the name, address, or credentials. The change applies to every device linked to this retranslator.
Delete the configuration from the Protocols list to stop forwarding for all devices. Confirm in the dialog.
Troubleshooting
When data doesn't appear in the Recurso Confiable system, check the following in order:
The retranslator is enabled, and its toggle is switched on for the device.
The user id and password are correct. Navixy can't request a token without them, so no data is sent at all.
The address and port are correct.
External ID has the values in the right order, with pipes kept for any value you skipped.
The license plate, shipment id, customer id, and customer name match the records on the Recurso Confiable side.
The device reports valid coordinates, unless you expect only urgent events.
When positions arrive but temperature or humidity is empty, the device has no sensor that Navixy recognizes for that reading. Check the sensor configuration for the device.
Last updated
Was this helpful?