ATS intents

ATS intents

ATS communicates with other applications and services using implicit intents.  Implicit intents read by ATS include:


Action
Extras
Description
com.micronet.dsc.ats.ping

Can be sent periodically to guarantee that ATS is running or to start ATS if it is not running.
com.micronet.dsc.ats.server.send
dataSourceId<String>:  the user-specified ID for making the request
dataRequestId<String>: user-specified ID for the individual request.  This should be unique within each dataSourceId.
dataPayload<byte[]>: payload that should be forwarded to the servers.  Maximum size of 400 bytes.
Can be sent to ask ATS to forward a packet of data to the remote servers.





Implicit intents broadcasted by ATS include:

Action
Extras
Description
com.micronet.dsc.ats.replyPing

Reply sent from ATS whenever it receives com.micronet.dsc.ats.ping.message
com.micronet.dsc.ats.server.replySend
dataSourceId<String>: the user-specified ID that was sent with .server.send
dataRequestId<String>: the user-specified ID for the individual request.  This should be unique within each dataSourceId.
dataResult<int>: the result of the request (0 = successfully received the request, negative number indicates an error in the request)
Reply sent from ATS whenever it receives the com.mironet.dsc.ats.server.send message
com.micronet.dsc.ats.device.status
ignitionState<int>: Is the ignition on?
inputXState<int>: Is input X logically active? Note that  X is an integer from 1-6 inclusive.
badAlternatorState<int>: is the alternator bad?
lowBatteryState<int>: is the battery low?
engineState<int>: is the engine on?
idlingState<int>: is the vehicle idling?
speedingState<int>: is the device speeding?
brakingState<int>: is the device braking?
corneringState<int>: is the device cornering?
batteryVoltage<double>: the voltage of the battery in volts
virtualOdometerMeters<long>: value of the virtual (GPS-driven) odometer in meters
continuousIdlingSeconds<long>: amount of time in seconds that the device has been continuously idling
sent from ATS once per second, contains current state information for parameters reported by device
com.micronet.dsc.ats.vehicle.status
parkingBrakeState<int>: is the parking brake on?
reverseGearState<int>: is the vehicle in reverse?
actualOdometerMeters<long>: value of the odometer in meters, as reported by the vehicle
fuelConsumptionMeters<long>: total fuel consumed in milliliters of fuel, as reported by the vehicle
fuelEconomyMetersPerLiter<long>: current fuel economy in meters per liter, as reported by the vehicle
lampsBitfield<int>: a bitfield indicating which lamps are currently on [protect lamp, amber lamp, red lamp, malfunction indicator lamp]
numDtcs<int>: number of currently active trouble codes, as reported by the vehicle
dtcX<long[3]>: value for a currently active trouble code, where  X is the zero-based Index. Each active trouble code is its own separate extra (the total count is reported by the numDtcs extra). For example, "dtc0" is the first trouble code, "dtc1" is the second trouble code, etc. The data take the form of [bus type, trouble code, source address].
Sent from ATS once per second, contains current state information for parameters reported by the vehicle.  This requires the VBS application to be installed and at least one vehicle bus type in Setting #35 to be active.
com.micronet.dsc.ats.device.event
eventCode<int>: ID for the event that describes the event. See Event Codes table.  Only event codes with values >= 20 and <= 69 will generate a broadcast.
eventData<byte[]>: Additional data related to the event. The meaning is specific to the event and is the DATA field of Mobile Originated Message.
sent from ATS when a change is made to the state of selected parameters which ATS monitors from the sensors on the device.
com.micronet.dsc.ats.vehicle.event
eventCode<int>: ID for the event that describes the event. See Event Codes table.  Only event codes with values >= 70 and <= 89 will generate a broadcast.
eventData<byte[]>: 
sent from ATS when a change is made to the state of selected parameters which ATS monitors from the vehicle.  This requires the VBS application to be installed and at least one vehicle bus type in Setting #35 to be active.
com.micronet.dsc.ats.vehicle.raw
busType<int>: the vehicle bus over which the message was received.
messageType<int>: the "message" (PGN or PID) as designated in Configuration Setting #30
sourceAddress<int>: the address of the node on the vehicle bus that sent this data. This value is determined by the node and type of bus.
rawData<byte[]>: the raw data for the message (PGN or PID) received from the vehicle bus.
sent from ATS when a matching data packet is received from the vehicle's bus.  Matching data packets are determined by Setting ID #30 (Forward Raw Bus Data).   This requires the VBS application to be installed and at least one vehicle bus type in Setting #35 to be active.





    • Related Articles

    • Basic ATS information

      ATS is a service that allows Android applications to communicate with vehicle hardware.  Originally, ATS stood for "A-317 Telematics Service," but its functionality was expanded to the SmartHub.  ATS is configured using an xml file and uses implicit ...
    • Event codes

      Below is a list of event codes broadcasted by ATS to both the server configured in Setting 1 and other applications using an implicit intent with action com.micronet.dsc.ats.device.event or com.micronet.dsc.ats.vehicle.event. Code Event name ...