geoin label whenever it enters a geofence. if you're looking for the last position of vehicles in a geofence then i suggest you use the vehicle georef search api api/vehicles/search/georefwhich returns the vehicles found in a specific location
https://pegasus1.pegasusgateway.com/api-static/docs/#api-Search-SearchVehicles
you just need to provide the latitude, longitude, and a radius to search
https://github.com/dctdevelop/pegasus/blob/master/releases/6.5.0.release.md
I have encountered a small problem with the integration of fleetIn services.
On the tracking page of the FleetIn application, to obtain the list of vehicles, is it really the /api/vehicles service?
I ask this because I see that the number of vehicles on the tracking page is different from the one on the trips page.
Hello @lreyn,
Since Saturday 3:29 pm we no longer receive data from the Forwarder. Can you please check if everything is ok on your end?
Also, it happens that an event that is recorded in our database appears in the list of events (on the Fleet'in platform) that has not been processed correctly. What can explain that please ?
what if I want to get the real data of my company from the pegagus apis? Because in development I was able to connect with the login of the developer account developer@digitalcomtech.com, but every time I use our real account it does not work.
Or the api link must change in production?
so if your pegasus site is https://gps.world.com/ then the API link is https://gps.world.com/api/
once you're using the api link specific for your site you can get the real data from your company
I wanted to reproduce on my application the Tracking interface
Currently I display all the vehicles and I can draw the shapes on the map.
But I have a problem with the dash on the tracking, when I look on the web part the way you manage it is that you click twice on a car and it displays mini dash but that varies according to the element clicked.
I would like to know what services are used to display these mini-dashes?
At the bottom there are also other mini-dashes such as features, Sensors, Metrics...
I would like to know in sum the api that give this information for each dash
Hi @abdallahmouhamad - what we do is subscribe to the vehicle-events payload using websockets
alternatively you can make the following requests to obtain the information you're looking for:
Alerts: /api/alerts
- includes unattended alerts for a vehicle
Pindrop: /api/vehicles/VID/pindrop
- includes information on the safe zone created
Devices: /api/devices?imeis=IMEI1,IMEI2,etc...
- key:
trip- includes trip status information (moving/parked, since when) - key:
latest->loc- includes last event location information (for the name of the event see labels) - key:
lastrx- includes information on the last communication received by the device on the server - key:
asset- includes information on the driver assigned to the vehicle - key:
ios_state- includes information on the current state of the inputs/outputs - key:
set_out_state- includes information on any pending instruction to activate an output - key:
safeimmo_state- includes information on a pending instruction to activate the safe immobilization (output1, depends on device's config, see here for more info)
you can turn the above devices request into a single one like this:
Hi, in the api/resources/rawdata/keys api you find the following keys related to the battery status
io_pwr- Boolean, true if power is detectedbl- Battery level in milliVolts
Note that the battery level is expressed in mV, and the % calculation depends on the device that's connected and it's capacity.
You could use a generic formula like this:
parseInt( 100 * ( mV - MIN_VALUE ) / ( MAX_VALUE - MIN_VALUE ))
assuming you know the MAX and MIN values that a device reports its internal battery as
what could be the cause please?
4 replies
label = checkin if you generated check-ins using Taurus. then just pass those lat lon pairs to the routes api
11 replies
Hi @ndoyeahmed - the recommendation here would be to use the live communications to obtain the last "device-package" with the latest device data reported. The device package contains the last event reported, and the latest values for all keys. Using this info you can do the following to get the indicators:
Fuel
The fuel indicator requires parameters to be configured on the vehicle properties that tell the device which sensor it has connected, see the following forum on how to configure them.
Once configured you can see the source of the fuel data on a key calledsource, for example:
"$sensor_ecu": [
{
"name": "Fuel level 1",
"tank_volume": 200,
"decimals": 1,
"units_abbrev": "l",
"source": "ecu_fuel_level_real", # rawdata field source of the fuel data
"sensor_type": "fuel",
"units": "liters",
"type": "float",
"device": "teltonika",
"priority": false
}
]Photo
For the photos you'll want to look for the fielddphoto_ptrthis tells you that there's a photo captured. From there you can use the camera methods to get the latest photo with timestamps and everything.
"dphoto_ptr": {
"evid": 940918308080505,
"value": 29541, # any value on dphoto_ptr indicates a photo was captured
"evtime": 1639051414,
"systime": 1639051415.5058,
"trip_id": 940918307235101,
"change": {
"evtime": 1639050909,
"systime": 1639050910.280464,
"prev_value": 29540
}
}Engine Data
For the engine data you can look for any of the ECUecu_fields on the rawdata.
Hello @lreyn
We integrated the list of vehicles on the Tracking part with their stats as you can see on the capture. But the information that we have circled in red must be in real time, it is the communication of the vehicle and it is in minutes sometimes in seconds.
We would like to know how to establish communication in real time to have this information?
What type of connection and what are the parameters?
you can find more information here about the implementation
https://docs.pegasusgateway.com/#live-communications