Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: PC requirements for fastest response time for Guages

  1. #1
    Low Bitrate
    Join Date
    Feb 2012
    Posts
    106

    PC requirements for fastest response time for Guages

    I am going to be doing a guage replacement with a 2003 Chevy HD2500. Having the carputer feed the speed, RPM and fuel info to a 7 inch screen. I think i am going to use OBDlink for the USB interface. What should I be looking for as far as a montherboard and CPU so I have minimal or no lag and fast real-time response to the LCD screen? Anyone have a setup like this that they really like?

  2. #2
    FLAC SNOtwistR's Avatar
    Join Date
    Nov 2009
    Location
    Keswick,On Canada
    Posts
    1,645
    You would be better served using the scan MX it has a faster display rate and is bluetooth. As for mainboard/cpu, I would highly recomment the gigabyte z77n-wifi mni-itx and the i5-3570. Mickz and myself both have this board and have done lots of tests. see the other post for more info. SNO

    http://www.mp3car.com/software-and-s...oot-times.html
    Last edited by SNOtwistR; 12-03-2012 at 12:26 PM.

  3. #3
    North of the land of Hey Huns
    Auto Apps:loading...

    Join Date
    Jun 2004
    Location
    Westminster, MD
    Posts
    2,127
    The OBDLink S would be significantly faster than the MX, due to the USB interface. (OBDLink MX -- coming soon to MP3Car.com) Not sure about the standard OBDLink.

    How fast of a PC you need depends GREATLY on what software you are using. Most response time has to do with the scantool, not the software anyway. Your vehicle is probably CAN, so you should be able to get 20+ pids per second, plenty enough to do gauges, especially if your software is smart about how it requests pids (Coolant you only need once every 30 seconds or so, rpm as often as possible, etc). I get near instant response time out of a 1.6ghz single core Atom, but I'm not running RR or CF. My car only returns 5 pids per second, but it's still almost enough for a cluster (Don't use it as one, only as a supplemental display) since I get rpm/speed every time, and things like coolant and fuel level once a minute.
    "stop with the REINSTALLS, what do you think we got some lame-o installer!!!" - mitchjs
    RevFE
    My Shop

  4. #4
    Low Bitrate
    Join Date
    Feb 2012
    Posts
    106
    This sounds exactly like what i am looking for Malcom. Thanks! SNOtwistR thanks for your reply! I will look into the gigabyte z77n , we used to use only gigabyte mobos in computer builds with my internship in College. I will report my finding in the projects section. Give me 3 months to get it going.

    thanks soo much.

  5. #5
    Maximum Bitrate
    Join Date
    May 2012
    Location
    Grandville, MI
    Posts
    632
    I responded to this message recently but I don't see it here...

    I have a 2003 Avalanche 1500 that has basically the same dash setup you do.

    Currently I am in touch with some people that have made their own touch screen displays run off a Parallax Propeller microprocessor. I will be picking up a couple of these screens in the next month and will be starting to play around with them. My intent is to use 3 small screens inside the dash cluster to provide the information the gauges do now. I have a junkyard dash I will be playing around with to make this work. The only modifications I will be making to the original dash cluster is to remove the needle motors. I will be getting my power and the ODBII signals right off the connector so it should just plug in.

    This design will dedicate 1 Propeller to each display and will use one to talk to the ODBII bus. While the Propeller has the ability to connect to the ODBII bus on its own I will likely built it with one of ScanTool's chips and dedicate it for the dash module. I will likely just configure the ODBII to monitor what is going on in the system and pull its information that way. The dash cluster uses ODBII to get its information from what I understand so It should be relatively easy to make this.

    This setup will be designed to use multiple displays to display the dash on but you should be able to use this on pretty much any size display or any number of monitors since the propeller on the display will be responsible for making the display and the ODBII propeller will just be sending simple numbers to the displays to display.

    I am planning on supporting needle displays, digits, and bar graphs both segmented and non segmented.

    The people playing with these displays showed me a demo where they have a totally functioning pac-man game running on one of these displays with no exterior processors. Looks like these can be made to work with most any generic TTL driven monitor so you have MANY choices to choose from.

  6. #6
    Low Bitrate
    Join Date
    Feb 2012
    Posts
    106
    Quote Originally Posted by redheadedrod View Post
    I responded to this message recently but I don't see it here...

    I have a 2003 Avalanche 1500 that has basically the same dash setup you do.

    Currently I am in touch with some people that have made their own touch screen displays run off a Parallax Propeller microprocessor. I will be picking up a couple of these screens in the next month and will be starting to play around with them. My intent is to use 3 small screens inside the dash cluster to provide the information the gauges do now. I have a junkyard dash I will be playing around with to make this work. The only modifications I will be making to the original dash cluster is to remove the needle motors. I will be getting my power and the ODBII signals right off the connector so it should just plug in.

    This design will dedicate 1 Propeller to each display and will use one to talk to the ODBII bus. While the Propeller has the ability to connect to the ODBII bus on its own I will likely built it with one of ScanTool's chips and dedicate it for the dash module. I will likely just configure the ODBII to monitor what is going on in the system and pull its information that way. The dash cluster uses ODBII to get its information from what I understand so It should be relatively easy to make this.

    This setup will be designed to use multiple displays to display the dash on but you should be able to use this on pretty much any size display or any number of monitors since the propeller on the display will be responsible for making the display and the ODBII propeller will just be sending simple numbers to the displays to display.

    I am planning on supporting needle displays, digits, and bar graphs both segmented and non segmented.

    The people playing with these displays showed me a demo where they have a totally functioning pac-man game running on one of these displays with no exterior processors. Looks like these can be made to work with most any generic TTL driven monitor so you have MANY choices to choose from.
    Any progress with this Red? Very interested.

  7. #7
    Maximum Bitrate
    Join Date
    May 2012
    Location
    Grandville, MI
    Posts
    632
    Quote Originally Posted by SNOtwistR View Post
    You would be better served using the scan MX it has a faster display rate and is bluetooth. As for mainboard/cpu, I would highly recomment the gigabyte z77n-wifi mni-itx and the i5-3570. Mickz and myself both have this board and have done lots of tests. see the other post for more info. SNO

    http://www.mp3car.com/software-and-s...oot-times.html
    Ps, I also have this motherboard but have an i3 on it with 16 gig of ram.. Works great...

  8. #8
    Maximum Bitrate
    Join Date
    May 2012
    Location
    Grandville, MI
    Posts
    632
    Quote Originally Posted by psi3000 View Post
    Any progress with this Red? Very interested.
    I haven't had time to get into this yet. I am looking at some options. After looking at this video I have decided to go a different route:
    http://www.youtube.com/watch?v=SSwRsJLSXjY

    I currently have a Freescale QUAD core ARM based development board that I am looking to use to build a dash display very similar to the one in this video. (They use a panda board that isn't anywhere near the power of the board I am using so it should work fine.)

    I will be loading Linux onto this board and currently with nothing optimized the board is up and running in about 20 seconds which is probably as long as it takes for the normal dash to setup. Once I get a chance to play around with this board I should be able to get a display up and running in about a half second.. (Current record is 200ms or 1/5th of a second to have a graphics display up and running.)

    I am considering my options right now but I have a line on some freebee 5" screens that I may be able to make use of. I am a full time college student so I have very limited time to work on this right now but with Linux running on this board I can get 3 screens up and running pretty easily. They have demos of 4 screens running on one of these boards. I have another board that is a single core board that I may eventually use for this since I don't believe it needs much processing power but we shall see. I think the 1 core only supports 2 screens.

    Once I can get Linux up and running with a graphics display I will go from there. Going to see how easy it will be for me to get screens for this. I have a fellow classmate that seems to think I can get screens for next to nothing. I can get the 5" screens because they are test screens that the company gets for free that they are tossing after they are done with them. (Very limited supply so I may only be able to get a few screens for my use. Before I get 30 PM's asking for free 5" capacitive screens... )

    I will be doing something similar to the center screen but mine will be 2 10" screens mounted in the dash running off the motherboard mentioned above with an i3 at first.. Maybe an i7 if I need it.

    I am going to try to have a psudo dash setup in the next 3 months if I can get the parts together.

    Also, I will be using scantool's Chip on a board for mine. There is an ODBII connection to the dash cluster since it is run off the ODBII bus for everything. I should also be able to get all of my other signals off the same connector. Should be interesting.
    Last edited by redheadedrod; 03-20-2013 at 04:04 AM.

  9. #9
    Low Bitrate
    Join Date
    Feb 2012
    Posts
    106
    Quote Originally Posted by SNOtwistR View Post
    You would be better served using the scan MX it has a faster display rate and is bluetooth. As for mainboard/cpu, I would highly recomment the gigabyte z77n-wifi mni-itx and the i5-3570. Mickz and myself both have this board and have done lots of tests. see the other post for more info. SNO

    http://www.mp3car.com/software-and-s...oot-times.html
    what do you power that with?

  10. #10
    Low Bitrate
    Join Date
    Feb 2012
    Posts
    106
    i only see like 200 watt dc power supplies on ebay...

Page 1 of 2 12 LastLast

Similar Threads

  1. So What Is The Fastest Boot Up Time I Can Expect............??
    By jmciver in forum Operating System Optimization
    Replies: 22
    Last Post: 12-03-2008, 12:32 PM
  2. whats your fastest boot time on a pIII 700mhz-1ghz
    By hari-bhari in forum Operating System Optimization
    Replies: 28
    Last Post: 06-01-2007, 03:18 AM
  3. <Fastest CarComp Startup Time>
    By Payback001 in forum General MP3Car Discussion
    Replies: 29
    Last Post: 08-17-2005, 04:56 PM
  4. Fastest possible boot up time
    By OriginalNick2 in forum Media Engine
    Replies: 37
    Last Post: 07-12-2004, 12:13 PM
  5. IR remote response time
    By spectrrr in forum Input Devices
    Replies: 5
    Last Post: 05-11-2004, 09:44 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •