Announcement

Collapse
No announcement yet.

PC requirements for fastest response time for Guages

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • 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
    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, 01:26 PM.

    Comment


    • #3
      The OBDLink S would be significantly faster than the MX, due to the USB interface. (http://www.mp3car.com/vbulletin/engi...ml#post1484476) 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

      Comment


      • #4
        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.

        Comment


        • #5
          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.

          Comment


          • #6
            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.

            Comment


            • #7
              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...

              Comment


              • #8
                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, 04:04 AM.

                Comment


                • #9
                  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?

                  Comment


                  • #10
                    i only see like 200 watt dc power supplies on ebay...

                    Comment


                    • #11
                      I will be looking at this more soon. I am interested in how you end up doing your screens since I have the same dash.
                      I have been looking at some very cheap screens but they are low resolution. May work fine for this application however. I want to see if I can fit two screens into the dash like they did in the video.

                      I have a spare dash sitting here that I will be trying to redo to support the screens. A 7 inch screen will be very small for this.

                      In one of the videos I was looking at they mentioned they used a beagle board. That board was a dual processor board and it runs BOTH of the screens. They have one screen setup to always display the speedo, turn signals and other information while the other shows the other gauges and information such as navigation etc.

                      I will have limited time this summer to work on this but I hope to atleast get 1 or more screens in the cluster housing. I have a 2003 1500 Avalanche with the transmission gauge added and a 2500 overlay. I also have installed blue LED's for the backlighting of my dash and door buttons.

                      The boards mentioned here are really for a PC and are WAY over powered for what you need.

                      I am looking to make use of the following hardware to make mine work...
                      Freescale development board...
                      Home made board using Parallax Propeller and Scantool microOBD 200 or similar module...
                      Cheap LDVS screens (Under $50 apiece)
                      I will plan to use linux as the OS for this..

                      You could use an Aduino instead but the propeller is more powerful. I plan to use the propeller to decode the ODBII information that the dash gets as well as have it detect the turn signals and such if needed then pass this to the ARM based board for processing. All of the necessary signals and power are available on the connector so it should be relatively simple. May need to remove the stepper motors to give more room to mount the hardware and to reduce the power consumption by the dash. I plan to keep the cluster in place so that the mileage continues to totalize if I ever decide to sell my truck.
                      Last edited by redheadedrod; 05-01-2013, 02:52 PM.

                      Comment


                      • #12
                        It really doesn't eat power, but I run with this. http://store.mp3car.com/Mp3Car_DSATX_p/pwr-023.htm If your running i3 with that board I think you could get away with using this http://store.mp3car.com/M2_ATX_HV_14..._p/pwr-027.htm If you only use it for the mainboard and don't start powering your screen, hubs, ect with it. SNO

                        Comment


                        • #13
                          I am using am M3-ATX with my board I think. It fits VERY snuggly in the 350 case. But have had no issues with power. The only thing I don't like is the power supply is tight up against the case housing and I am afraid it will break it off at some point but then again it allows the case to be used as a heat sink sort of...

                          I have left it running for hours on my desk and it has never gotten warm. You can BARELY feel any temperature difference when you feel the case. I am guessing I am only about 20-30 watts.

                          Again though, this is very much over kill for such a project. Using an ARM board is more than sufficient and FAR less power hungry. I should be able to get my ARM board booted and running faster than the diagnostics on the car normally take. (With a modified boot sequence they have gotten these boards down to .2 seconds from power up to having an active display. 2 seconds to be fully running without network support. The network depends on the IP addressing you are using. For hard coded IP you are at the 2 second mark for full up and running. )

                          Comment


                          • #14
                            This looks very interesting. I think it might be very expensive though. SNO http://www.youtube.com/watch?feature...78CF11268448#!

                            Comment


                            • #15
                              Yes, you will be able to do that with one of these ARM boards. They likely have their own variation of an ARM board running those displays. QNX has a very fast display that they are doing some of that stuff with. A local shop a friend works at is trying to develop something similar. And if you look at some of the commercial vehicles they now come with some sort of digital screens. I know the new buses we got when I was still driving last summer were getting about a 7" square screen showing the speed digitally and the other stuff as well.

                              Realistically these are not that expensive to do yourself if you just need the screens, a board to run the screen and some hardware to back it up. The hard part comes when you have to program the screen. For a non programmer this would be a pain in the butt but otherwise it is simple. But programming the display is something anyone will have to do since there really is no software that does this available YET...

                              Comment

                              Working...
                              X