Quote:
Originally Posted by bg305
but if could control from my phone or headunit.. that is a bonus.
|
Read all, quoted the key message and understand fully what you are saying. And you are 100% correct. Main challenge being that cross-platform impediment and management from a coding perspective; Steve got an iPhone, Ruth got an Android, lil sister got an HTC, big sister got the new XYZ and cousin have his Blackberry, you see where I'm going with this...
Sought of using a cross-platform one-fit-all solution e.g. a browser addy
http://xxx.xxx.xxx.xx:XXXX and port over lets say a NRF24L01+ or a LT8920 radio IC (2.4Ghz) but then the work involved is equivalent if not more than simply coding an X&Y axis touch screen. The radio would also require FCC ID (if compliance is an issue for anyone) :/
Finally, if the device would be used daily like a tune-in radio or similar then it would make sense to put in connectivity but in this case chances the color & brightness settings will be set once (or twice) then forgotten.
Not all lost cause. We'll have extra GPIOs on the device and probably use a nice quad size for developers to expand this controller to what-ever-they-want. That would include connectivity if what they add in the future requires that feature!!!
If there is anything that could convince me otherwise please do let me know and I'll reconsider my opinions. Thanks for trying to help out, appreciated btw!
Edit: Adding in a MCP2021A-330E/SN, sort of a gift to our Devs who wish to have both read & write access to the ECU and car data and/or build their own HMI around that (comm via k-line over 10400baud). So see, plenty of other tricks you'll be able to do with this lil cool box
