28/02/2018 at 5:48 pm #896
What possible Internet of Things data might be gathered? What sensor data is already being generated? Who might value this IoT and sensor data? What end-to-end solutions might be imagined?15/03/2018 at 8:04 am #913
One of the present obstructions to the uptake of EVs is that people think they drive further than they do. Consequently they think that EVs would not serve their needs. If people knew how far they drove now they could make the decision when to change based on information, not guesswork.
At the same time the range of new EVs is increasing, but at the expense of lithium consumption.
We run the risk of only getting people out of their fossil burners when we supply they with extravagantly over powered EVs.
Getting data logging, interrogation and logging into present cars will enable early adoption of EVs with the concomitant savings on emissions and money. They will also help inform the inevitable shift to road pricing.
16/03/2018 at 11:39 am #917
- This reply was modified 1 year, 1 month ago by Neil Kermode.
Nice one Neil. Can we not just buy this data off Google? There are also apps on Android that individuals can turn on to see both how they drive and distance.16/03/2018 at 12:16 pm #921
Interesting questions. The pieces I can see, here, in terms of an IoT service seem to be:
How to gather the data from the car? including who does the piece (third party app, car manufacturer, as present, I am not aware that google has agreements in place to do this wholesale, which is probably a good thing for privacy)
How to gather data from car? including, is this gathered by diary entry by car owner using a smartphone app, or is this gathered from the car itself (in which case, you need to add a transceiver to the car and ‘mod’ the processor, or possibly get some special agreement from manufacturer and owner)
Another option is to go for the end-points, and build smarts into the car charging sites. Then they talk to each other (peer to peer car charging) and work out the distance between charges. I have no idea if there is a data signal in the car charging system already, that could talk to the onboard processor.
Finally, who do we know who might be able to answer some of these questions? Who do we know who might be needed to be ‘in’ to such a network? (We need cars, owners, IoT network providers…).
That’s my thoughts. Please add…16/03/2018 at 12:35 pm #925
After 1996 all cars should have a OBD-II (On-board diagnostics II) port and there are tools to plug in and get the data. Also some cars have data automatically transmitted by mobile data technology to the manufacture.16/03/2018 at 12:43 pm #926
Are these the same ports here as the AA use to plug in their “Car Genie” device? I’ve had look as to whether my wife’s car (2012 Peugeot estate) and my car (2013 Ford Fiesta) were compatible. I was informed that although the Peugeot was compatible, the Ford didn’t have the required port for the device.16/03/2018 at 12:53 pm #928
Yes. There are minimum standards to what everyone can read. As ever, manufacturers go above and beyond and put in data and codes that you need the manufactures information to decode. This however is advanced information and the basic data can be interpreted easily enough.16/03/2018 at 1:55 pm #929
There is something out there whereby data is available. A number of years back there was a trial to look at data for vehicle travels. Among the organisations taking part in the pilot were BT and technology specialist Neul (who have moved into IoT now), which was to work with the Department for Transport to test a new traffic information system along the A14 between Felixstowe and Cambridge.
Using white spaces to transmit data on traffic congestion and varying traffic conditions to vehicles, the technology is designed to improve information to drivers and could reduce congestion and improve road safety.
I do not think though the trials went live.16/03/2018 at 2:37 pm #930
Just another piece to this puzzle. I’ve talked to my local car electronic engineer colleague, who has explained that there is, in essence, no API or standard for data gathering in-car. OBDII is generally only used for fault reporting and diagnostics. The internal CANBUS protocol is used in widely different ways for different makes and models. Some manufacturers in higher end car models, in some countries, transmit GPS data. My colleague, who programs cars, explained that information on journeys is not stored (and even if it were, it would vary in the way it was stored from model to model). There is little data storage in cars, in general. In short, you’re not going to generalise any data service in-car any time soon (you need bespoke solutions for each make and model).
However, you could (perhaps) reconstruct car travel distance from smartphone movements. The surveillance issues are obvious. (See discussion on privacy and data, perhaps). If I were in the ‘project management’ software business, I would have an App for that, so that a salesrep could auto-log their miles and it would be billed as appropriate. Same underlying tech, different use.
Finally, with regard to road pricing methods, apparently Sweden had that for diesel cars in the past. People self-reported their mileage and it was checked against their mileometer.
Finally, here’s one I (sort of) made earlier, an App for EV range estimation:
Hope that all’s helpful…
Keep the ideas flowing.
You must be logged in to reply to this topic.