Éxito
Hola, estoy tratando de registrar el IMEI de mi SYRUS desde la plataforma: https://pegasus1.pegasusgateway.com/, pero me arroja el mensaje "The IMEI is not avaliable for registration"
buenas tardes, @JorgeQuinteroM_gitlab - favor de enviar un correo a support@digitalcomtech.com para verificar el IMEI.
Hello community. I am new to the pegasus platform. I have setup "live communication" with socket.io but I cannot get the socket.on('events', function) is not called.
This is a node.js application.
So basically from the documentation I setup a socket:
...
const socket = io('https://live.pegasusgateway.com/socket');
...
socket.emit('authenticate', credentials); // authentication is successfulThen upon successful authentication I subscribe to vehicle-events event. (the subscription is also successful because I can see from the _update handler the id of my asset is returned).
Now I go to my mobile device, I have downloaded and installed the Taurus app and my mobile is registered as an asset in the platform (id = 65). When I emit a "SOS message" for the sake of testing, my events handler is not called:
socket.on('events', function(envelope) {
console.log(envelope); // this is never called
});Thank you for any suggestion and any insight on what I am doing wrong or what I have forgot.
(In fact it seems that my event handler is never called for any event...)
To make sure everything is working, can you check if the event is reaching the pegasus application?
when you send an event, you should see the events list update, as well as the "last communication with server"
so it looks like the events are recorded. Only they seem not be sent "live"
Sorry if this is a stupid question but can you send me the link to the "pegasus gateway" so I can login? (thanks you)
Hi, DCT develop!!
Looking at: https://pegasus1.pegasusgateway.com/api-static/docs/#api-Triggers-CreateTrigger in "rule" object points to https://docs.pegasusgateway.com/#triggers but this URL has not info about triggers or rule object
Looking at: https://pegasus1.pegasusgateway.com/api-static/docs/#api-Triggers-CreateTrigger in "rule" object points to https://docs.pegasusgateway.com/#triggers but this URL has not info about triggers or rule object
let us know if you have any questions
Hi Alejandro, you'll want to check the configuration of that device and look at the gps_codes_names for their meaning
example: https://pegasus1.pegasusgateway.com/api/configurations/q275
"gps_codes_names": {
"0": {
"short": {
"fr": "évènement 0",
"en": "Periodic test",
"es": "Test periódico"
},
"long": {
"fr": "évènement rapporté 0",
"en": "Periodic test",
"es": "Test periódico"
}
},
"2": {
"short": {
"fr": "évènement 02",
"en": "Vehicle ON",
"es": "Vehículo encendido"
},
"long": {
"fr": "évènement rapporté 02",
"en": "Vehicle ON",
"es": "Vehículo encendido"
}
...code 0 refers to a Periodic test, code 2 refers to a Vehicle ON event, etc.
@dctdevelop Buenas, tengo el siguiente JSON. como puedo identificar si el vehiculo esta en movimento o no?
[
{
"code": 8,
"ecu_throttle": 0,
"sv": 14,
"event_time": "2021-03-18T15:06:53-05:00",
"ecu_torque_flag": "T",
"cv12": 0,
"source": 3,
"ecu_intake_manif_tmp_flag": "T",
"ecu_eng_oil_psi_flag": "T",
"mph": 0,
"ecu_fuel_iconsumption_flag": "T",
"system_time": "2021-03-18T15:06:56.473350-05:00",
"ecu_hours": 2309870,
"cf_cid": 6140,
"tec_ft": 0,
"cf_lac": 74,
"ecu_trans_tmp_flag": "T",
"trip_id": 8726889929253,
"io_ign": true,
"ecu_eng_oil_psi": 19,
"ecu_idle_fuel_flag": "O",
"cv10": 396,
"cv11": 0,
"io_exp_state": false,
"cv13": 0,
"vdop": 110,
"bl": 4433,
"ecu_cool_tmp_flag": "T",
"valid_position": true,
"ecu_error_flag": "T",
"ecu_distance": 735621335,
"ecu_eng_oil_tmp_flag": "T",
"ecu_intake_manif_tmp": 43,
"ecu_throttle_flag": "T",
"io_in1": false,
"io_in2": false,
"io_in3": false,
"ecu_battery": 13750,
"vid": 87,
"ecu_eng_oil_tmp": 87,
"ecu_battery_flag": "T",
"ecu_trans_tmp": 783,
"ecu_error1": 830,
"ecu_error2": 3,
"ecu_error3": 0,
"ecu_error4": 126,
"ad": 8,
"lon": -7346554,
"ecu_fuel_level_real": 248,
"io_out1_short": false,
"ecu_idle_fuel": 118140,
"head": 256,
"hdop": 63,
"ecu_torque": 8,
"io_pwr": true,
"cf_rssi": 10,
"ecu_fuel_level_flag": "T",
"tec_fn": 0,
"io_out1": false,
"io_out2": false,
"event_type": 10,
"tec_ff": 0,
"ecu_rpm_flag": "T",
"ac": 0,
"ecu_total_fuel_flag": "T",
"ip": "172.30.3.112",
"pid": 87,
"al": 346,
"vo": 383047960,
"ecu_fan_state_flag": "T",
"id": 8726890681473,
"ecu_hours_idle_flag": "O",
"io_out2_short": false,
"ecu_fan_state": 11,
"ecu_rpm": 643,
"port": 47542,
"ecu_fuel_iconsumption": 385,
"tec_st": false,
"ecu_distance_flag": "T",
"lat": 405680,
"ecu_hours_flag": "T",
"ecu_cool_tmp": 82,
"device_id": 357666051314737,
"ecu_fuel_level": 960,
"age": 2,
"pdop": 127,
"ecu_total_fuel": 3888455,
"ecu_hours_idle": 387065,
"ecu_fuel_level_real_flag": "T"
}
]
[
{
"code": 8,
"ecu_throttle": 0,
"sv": 14,
"event_time": "2021-03-18T15:06:53-05:00",
"ecu_torque_flag": "T",
"cv12": 0,
"source": 3,
"ecu_intake_manif_tmp_flag": "T",
"ecu_eng_oil_psi_flag": "T",
"mph": 0,
"ecu_fuel_iconsumption_flag": "T",
"system_time": "2021-03-18T15:06:56.473350-05:00",
"ecu_hours": 2309870,
"cf_cid": 6140,
"tec_ft": 0,
"cf_lac": 74,
"ecu_trans_tmp_flag": "T",
"trip_id": 8726889929253,
"io_ign": true,
"ecu_eng_oil_psi": 19,
"ecu_idle_fuel_flag": "O",
"cv10": 396,
"cv11": 0,
"io_exp_state": false,
"cv13": 0,
"vdop": 110,
"bl": 4433,
"ecu_cool_tmp_flag": "T",
"valid_position": true,
"ecu_error_flag": "T",
"ecu_distance": 735621335,
"ecu_eng_oil_tmp_flag": "T",
"ecu_intake_manif_tmp": 43,
"ecu_throttle_flag": "T",
"io_in1": false,
"io_in2": false,
"io_in3": false,
"ecu_battery": 13750,
"vid": 87,
"ecu_eng_oil_tmp": 87,
"ecu_battery_flag": "T",
"ecu_trans_tmp": 783,
"ecu_error1": 830,
"ecu_error2": 3,
"ecu_error3": 0,
"ecu_error4": 126,
"ad": 8,
"lon": -7346554,
"ecu_fuel_level_real": 248,
"io_out1_short": false,
"ecu_idle_fuel": 118140,
"head": 256,
"hdop": 63,
"ecu_torque": 8,
"io_pwr": true,
"cf_rssi": 10,
"ecu_fuel_level_flag": "T",
"tec_fn": 0,
"io_out1": false,
"io_out2": false,
"event_type": 10,
"tec_ff": 0,
"ecu_rpm_flag": "T",
"ac": 0,
"ecu_total_fuel_flag": "T",
"ip": "172.30.3.112",
"pid": 87,
"al": 346,
"vo": 383047960,
"ecu_fan_state_flag": "T",
"id": 8726890681473,
"ecu_hours_idle_flag": "O",
"io_out2_short": false,
"ecu_fan_state": 11,
"ecu_rpm": 643,
"port": 47542,
"ecu_fuel_iconsumption": 385,
"tec_st": false,
"ecu_distance_flag": "T",
"lat": 405680,
"ecu_hours_flag": "T",
"ecu_cool_tmp": 82,
"device_id": 357666051314737,
"ecu_fuel_level": 960,
"age": 2,
"pdop": 127,
"ecu_total_fuel": 3888455,
"ecu_hours_idle": 387065,
"ecu_fuel_level_real_flag": "T"
}
]
Hola @ajtortolero - ese campo es el nivel directo de batería del vehículo.
por lo tanto, si se trata de una batería de 12V DC, puede encontrar tablas que le indican qué voltajes se consideran buenos: https://www.aa1car.com/library/battery_runs_down.htm
el campo llega en milivoltios, por lo tanto :
por lo tanto, si se trata de una batería de 12V DC, puede encontrar tablas que le indican qué voltajes se consideran buenos: https://www.aa1car.com/library/battery_runs_down.htm
el campo llega en milivoltios, por lo tanto :
ecu_battery: 12350, ~ 60% por ejemplo
Hello @dctdevelop
When trying to test the Forwarder, with the object here : https://cdn2.pegasusgateway.com/json/all_keys.json
i'm getting the object id as answer, in Postman, wich mean that something went wrong. When trying to figure out this, i'v seen that some fields types are not the same as those listed in master fields list (in doc). For example ecu_weights field is a number in doc, and in the testing object its value is a string : "0165900,020,068620"
Please, i would like to know wich one to trust : the doc or the testing object ?
And if you have another testing object i would be glad to have it
Thanks in advance
Hi @RolandKOSSI - thanks for bringing that to our attention, we've gone ahead an updated the links on the docs to reflect the latest changes, please clear cache and refresh, they should be pointing to files found in our public repo: https://github.com/dctdevelop/pegasus/blob/master/resources
Hola @ajtortolero - acabamos de mejorar la documentacion aca Immobilize a Vehicle. Se puede usar el api de /devices para verificar si la inmovilizacion segura esta activada o no (
https://pegasus1.pegasusgateway.com/api/devices/357042062897906?select=outbox,ios_state,safeimmo_state,config
io_out1: true)https://pegasus1.pegasusgateway.com/api/devices/357042062897906?select=outbox,ios_state,safeimmo_state,config
activada & safeimmo_support true
{
"safeimmo_state": {
"instruction": true,
"_epoch": 1618318377.628331,
"uid": 1,
"set_at": 1618318372.517008,
"cid": 8994
},
"imei": 357042062897906,
"config": {
"kydef": {
"lumeway": false,
"secugen": false,
"garminmode": false,
"safeimmo": true,
"satcom": false,
"_read_at": null,
"photocam": false,
"ios_names": {...}
},
"kymod": {
"_epoch": 1602267569.458936
},
"_config_state": 1,
"_epoch": 1617041571.785082,
"safeimmo_support": true,
"values": {
"values_rpmlimit_secs": null,
"values_rpmlimit_rpm": null,
"values_speedlimit_secs": 10,
"values_speedlimit_mph": 50
},
"ky": "q740"
},
"ios_state": {
"io_pwr": true,
"io_out2_short": false,
"_epoch": 1618318402.044902,
"io_tamper": false,
"io_ign": false,
"io_exp_state": false,
"io_out1_short": false,
"io_out1": true,
"io_out2": false,
"io_in1": false,
"io_in2": false,
"io_in3": false
},
"outbox": [
]
}
Hi, as a general announcement - if you're looking to back up data from Pegasus to your own server and you're considering using rawdata vs Forwarders, the difference is that forwarders would only send data once it's activated, if you're looking for older data you'll have to use the rawdata api to get it.
Once you have the historic data we do recommend always using the forwarder to replicate data from Pegasus to your server.
Once you have the historic data we do recommend always using the forwarder to replicate data from Pegasus to your server.
Hi @RolandKOSSI -apologies for the delay, the
dev_ospeed parameter is an overspeed counter that is exclusive to the Syrus device - it works with a speed limit that is set on the configuration of the device, and anytime it goes over that speed that counter increases. if the device you're looking at is not a syrus then it does not support this feature. if it is a syrus then it could be a configuration issue.
Hello @dctdevelop ,
I'm trying to get the last position of vehicles in a geofence.
In the doc, i saw that the label for geofence is "geoin"
But that label never appear in data get from /rawdata API
For the same period of time, when i visualize rowdata from fleet-in plateform, i see some geofence name but the "geoin" label still do not appear.
Please, what can explain that ?
I'm trying to get the last position of vehicles in a geofence.
In the doc, i saw that the label for geofence is "geoin"
But that label never appear in data get from /rawdata API
For the same period of time, when i visualize rowdata from fleet-in plateform, i see some geofence name but the "geoin" label still do not appear.
Please, what can explain that ?
hi @RolandKOSSI - the generation of specific labels depends on the configuration of the device, for example in Syrus devices you can configure geofences directly on the device (not the platform) and generate the
which 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
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
Hi @RolandKOSSI - no, the forwarder can only send device events/position related data, for organizational data you'll have to query the API
Hi @/all - new release notes for upcoming changes are up
https://github.com/dctdevelop/pegasus/blob/master/releases/6.5.0.release.md
https://github.com/dctdevelop/pegasus/blob/master/releases/6.5.0.release.md
Hello,
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.
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.
Hi @RolandKOSSI - please email us support@digitalcomtech.com with the details of the application and the domain so we can test it and add it to the gateway