MalibuJack's UTEC DigitalDash
#1
MalibuJack's UTEC DigitalDash
Ok guys.. I hacked together a rudementary Digital dash (the dash itself isn't 100% working yet..)
Working features..
Selectable Comm port (I adapted a VB Term app I had laying around) and other comm port features
data logging to file
Rudimentary I/O to the serial port (basic terminal features without true VT100 emulation.. you'll see why in a moment)
simultaneously view data while dashboard displays
TCP Listener, YES you can telnet to the program and use a real VT100 emulator so you can adjust settings..
Little if any error correction..
Stuff I'm still working on..
Graphical GUI (Munging data) a true "Digital Dash"
logger playback through the same exact GUI and I/O (useful for both a playback feature and for demo of the product)
Autostart features (starting connection, enabling port, starting logging)
allow several simultaneous TCP connections for different data acquisition tools
GPS Location and delta info (this will be used for clocking ET's and calculating horsepower and acceleration data)
---------------------------------------------
At the moment, the program is very rough, the GUI basically recognizes the logging data (Shift-1) and displays it in a text field, it will eventually munge that data and seperate it into a real display and do realtime graphing.
Once I get a GUI that is readable, and fairly stable, I'll post a demo of it for you guys to try out..
And for what its worth, VB is going to run faster at displaying I/O from the serial port, than the serial port can send data, so there should be very little latency..
For the time being, the App is UGLY and crashes if you do some common things with it, such as, telnet to the listener, and disconnect while data is being transferred, it will recover automatically in the future..
Ok guys.. So, whatcha think? I'd post a few photos, but you probably would not have a clue what your looking at.. I am focusing on the functionality before the GUI..
But not too bad for 2 days of work..
Working features..
Selectable Comm port (I adapted a VB Term app I had laying around) and other comm port features
data logging to file
Rudimentary I/O to the serial port (basic terminal features without true VT100 emulation.. you'll see why in a moment)
simultaneously view data while dashboard displays
TCP Listener, YES you can telnet to the program and use a real VT100 emulator so you can adjust settings..
Little if any error correction..
Stuff I'm still working on..
Graphical GUI (Munging data) a true "Digital Dash"
logger playback through the same exact GUI and I/O (useful for both a playback feature and for demo of the product)
Autostart features (starting connection, enabling port, starting logging)
allow several simultaneous TCP connections for different data acquisition tools
GPS Location and delta info (this will be used for clocking ET's and calculating horsepower and acceleration data)
---------------------------------------------
At the moment, the program is very rough, the GUI basically recognizes the logging data (Shift-1) and displays it in a text field, it will eventually munge that data and seperate it into a real display and do realtime graphing.
Once I get a GUI that is readable, and fairly stable, I'll post a demo of it for you guys to try out..
And for what its worth, VB is going to run faster at displaying I/O from the serial port, than the serial port can send data, so there should be very little latency..
For the time being, the App is UGLY and crashes if you do some common things with it, such as, telnet to the listener, and disconnect while data is being transferred, it will recover automatically in the future..
Ok guys.. So, whatcha think? I'd post a few photos, but you probably would not have a clue what your looking at.. I am focusing on the functionality before the GUI..
But not too bad for 2 days of work..
#4
hey, can someone upload (as a csv file) a GIGANTIC "Shift-1" datalog that has AFR info in the last column? The longer the log the better? I'm developing with a nullmodem to another PC and dumping data to the program through its serial port for testing.. since Its been too crappy out to get my Tuner installed, I am making assumptions about the log format..
ALSO Upcoming toys..
Hardware dashboard appliance (in Windows PocketPC2003) that also has these features based on the same code.. Turns out the code ported over to my pocketPC in about 10 minutes..
Oh, and I fabbed up a bluetooth device to hook up to the port on the UTEC.. I hate wires.. I may make that device available as a product for anyone who needs to make a close rangewireless serial connection to an on-board serial device (OBD-II logger etc)
I also added some routines to do some obd-II logging (using the scantool.net OBD-II device) simultaneously over an alternate serial port, but that doesnt work yet.. not sure how useful that data is going to be other than getting some snapshot data.
ALSO Upcoming toys..
Hardware dashboard appliance (in Windows PocketPC2003) that also has these features based on the same code.. Turns out the code ported over to my pocketPC in about 10 minutes..
Oh, and I fabbed up a bluetooth device to hook up to the port on the UTEC.. I hate wires.. I may make that device available as a product for anyone who needs to make a close rangewireless serial connection to an on-board serial device (OBD-II logger etc)
I also added some routines to do some obd-II logging (using the scantool.net OBD-II device) simultaneously over an alternate serial port, but that doesnt work yet.. not sure how useful that data is going to be other than getting some snapshot data.
Last edited by MalibuJack; Apr 5, 2004 at 09:21 PM.
#6
Here's a first look at the app.. as you can see, VT100 telnet (almost) works, the dashboard shows data (it will be GUI soon), logging is functional as is the serial interface.. (BTW This is communicating over bluetooth! but at the moment not to the UTEC but my other laptop)
Last edited by MalibuJack; Apr 5, 2004 at 10:30 PM.
Trending Topics
#9
Made some performance improvements to the serial I/O, began work on the playback feature (figured out how fast to read the file and send the data to the GUI), and verified that Bluetooth works from inside the car.. Wireless UTEC Tuning!!
Started working on decoding the map exports, and looking at the map upload/download feature.. Started building a Grid Control GUI for the Maps. I'm hoping to find out from TXS if there are some shortcuts for sending data, or a way to quickly send configuration info back and forth from the UTEC (Raw data or diagnostic mode)
I'd like some input from TurboXS guys if they have some time..
Started working on decoding the map exports, and looking at the map upload/download feature.. Started building a Grid Control GUI for the Maps. I'm hoping to find out from TXS if there are some shortcuts for sending data, or a way to quickly send configuration info back and forth from the UTEC (Raw data or diagnostic mode)
I'd like some input from TurboXS guys if they have some time..
#11
Evolving Member
iTrader: (7)
Join Date: Jun 2003
Location: Import Image Racing
Posts: 391
Likes: 0
Received 0 Likes
on
0 Posts
utec tells you if your knocking, dynoflash doesnt. utec u can switch maps while moving, dynoflash doesnt. dynoflash is cheaper than a utec. wait but turbo trix is prob the best place to get it tuned...hmmm they have done nothing but great things for my cars, you should give them a try.
#12
although this is offtopic, so I can't too much of a reply for ya in this thread.. Each has its advantages. It really depends on how much interaction you want with your car. Given a good tuner, both can yield the same results. The main advantage to the utec is several different maps and its ability to be retuned when necessary. Anyway.. back to the normal thread.. PM Me if you want specific info and pros/cons.