On Fri, Apr 4, 2014 at 2:17 PM, Hanchett, Paul <phanc...@jaguarlandrover.com> wrote: > I'm curious-- > > There are no standard names for the for the signals you mention (speed, > transmission, exterior brightness), that I am aware of-- How does Murphy > know what inquiry to make of AMB? :-) >
You mean like VehicleSpeed, Transmission and ExteriorBrightness? http://otcshare.github.io/automotive-message-broker/html/interfaceVehicle_1_1org_1_1automotive_1_1VehicleSpeed.html http://otcshare.github.io/automotive-message-broker/html/interfaceVehicle_1_1org_1_1automotive_1_1Transmission.html http://otcshare.github.io/automotive-message-broker/html/interfaceVehicle_1_1org_1_1automotive_1_1ExteriorBrightness.html Maybe you mean something different? -Kevron > Paul > > > > Paul Hanchett > ------------------- > Infotainment Engineer > MSX on behalf of Jaguar Land Rover > One World Trade Center, 121 Southwest Salmon Street, 11th Floor, Portland, > Oregon, 97204 > > Email: phanc...@jaguarlandrover.com > > ------------------- > > Business Details: > Jaguar Land Rover Limited > Registered Office: Abbey Road, Whitley, Coventry CV3 4LF > Registered in England No: 1672070 > > > On Tue, Apr 1, 2014 at 5:03 AM, Puustinen, Ismo <ismo.puusti...@intel.com> > wrote: >> >> Hello Tom, >> >> > While groking AMB, I happened across the murphyplugin. >> > Therein, I see some indication of traffic from murphy to AMB; >> > "Received a message from Murphy" >> > "recvfrom_msg(mrp_transport_t *transp, mrp_msg_t *msg ....." >> > >> > Am I correct in assuming this presents a dependency AMB has on Murphy? >> > Can someone help me understand what events Murphy fires to AMB? >> >> Murphy uses basic information from AMB (such as speed, transmission, >> exterior brightness, ...) to be able to do decisions about the vehicle >> state. These decisions are then used for policing, such as regulating >> on-screen applications if the vehicle is moving. The processed states >> are then communicated back to AMB so that other applications can use the >> same information. At the moment Murphy controls "DrivingMode" and >> "NightMode" AMB properties. The control interface is the Murphy plugin >> that you have found from the AMB source code. >> >> So, to recap: from Murphy's point of view AMB is a source of system >> events and a place for propagating policy decisions to applications and >> other interested parties in the system. From AMB's point of view Murphy >> is a client for property changes and a provider of higher-level vehicle >> states. >> >> -- >> Ismo Puustinen <ismo.puusti...@intel.com> >> _______________________________________________ >> IVI mailing list >> IVI@lists.tizen.org >> https://lists.tizen.org/listinfo/ivi > > > > _______________________________________________ > IVI mailing list > IVI@lists.tizen.org > https://lists.tizen.org/listinfo/ivi > _______________________________________________ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
