I had been using ver. 2.5 since it's first release in beta and it's worked fine for us for many years. Since we were getting ready to hit the road home today, I installed ver. 4.0.2 the other day and made all new gauges, using the data from my 2.5 gauges. There is good news and bad news. First the good news, all my temp gauges work find, tach works, my multi-bar gauge with load, frate, and turbo works, speed and cruse speed work. Bad news: 1. Cruise status shows a constant green. Here are the parameters I used for this gauge: [inline:vmsPC cruise stat gauge-20150828.PNG=vmsPC cruise stat gauge-20150828.PNG] 2. Odometers show really strange numbers for distance. 3. Tank minder works,unless I turn off "Use recent MPG", then I get really strange numbers Here's what my gauges look like: [inline:vmsPC-20150828.PNG=vmsPC-20150828.PNG]
Ned, it appears you are confirming my results with the Tank Minder and the Cruise setting. I'm not using any odomoeters, but problems with those could be the reason the tank minder doesn't work properly. You do show a bad voltage in your screen cap. I don't remember what you drive - do you have an ISL? If so see my post and the answers just before yours. DonB
Don, ignore the voltage reading, the gauge was reading correctly all day, I don't know what happened at the moment of the screen shot. I have the Cat 3126 275hp engine. 19 years old and still going strong with 150,000+ miles. I switched back to ver. 2.5 today, it works solidly even on Windows 10. I'll wait for the next release of 4 and give it another try then, unless we're home by that time. We expect to be home on Thursday or Friday next week. Oh, one other problem with 4.0.2, the colors don't work for the gauges. Any color you want, as long as it's white.
Ned, I also went back to 2.5 for the last couple of driving days - I hope we have given them enough to chew on so that they will have a new version out shortly.
Mornin fellas We have, in deed, much to chew on. You have confirmed the fuel, cruise and shift issues. The voltage is odd--though were seeing glimpses of odd things when the engine is off (gauges inactive) or when there's a brief drop-out in the data. Then, some random data creeps in ie. 700Vdc or 3200 psi and such. We're sorting out how to run a little buffering to cover the drop-outs...then how to leverage that so the rest values stay at zero, or a reasonable number in the case of a static gauge ie. Odometer or fluid-level. Thank you for the pictures--they speak volumes in understanding errors and usage. I am *so glad* v2.5 is a pretty usable version; its the defacto fall-back at this point. Here's hoping we can squeeze out some code and a new version by friday. Cross your fingers! cheers Art //
The main page says v4 is on hold oops it works fine. My Isl 400low rpm pid sniff shows 172 174 175 as a defined value of 16383.8 for temps any thoughts why that might be ? I switched to isl 400 and it is same thing No big deal but temp might be nice to know
Re: PIDs and engine files. The engine files supply the VMSpc way to calculate Torque and Horsepower. It doesnt interact otherwise. PIDs are captured by the sniffer--and can be Googled pretty readily. Just add J1939 or J1708 and you can download an entire table of codes. These are universal and not brand specific. Its a greater man than I that can memorize the lot. cheers Art //
Not to be a pest art but I tried to find the buffer size in engine corrections to make rolling mpg a little less sensitive and I can not find where it went. Did you change how rmpg is calculated and do we have any control?
The buffer size adjustment is still managed from the Engine Corrections box. However, as you don't see it, that tells me you're still on v4.0.1 The following rev fixed this (and a dozen other things.) That rev had many issues....which led to v4.0.2 which is the one I mentioned, above, pulling from the site--until the v4.0.3 is bundled. If you like I could give you a link. cheers Art //
Well yes I had way too many versions of 4 so I got rid of all and now I am running 4.0.2 And of course it does as advertised when will we see 4.0.3 Also the verbage in home screen: might be fixed. VMSpc Downloads The VMSpc software is always available for download. Current version is v3.1b3 while v4.x is on hold for just now. Also does not show a v4 link VMSpc Downloads Attachment Size Distribution Disk Jib v3.1b3 (06-05-2015).zip 4.51 MB VMSpc Device Divers Only (04-16-2015).zip 2.2 MB VMSpc 4.0.4 Owners Manual.pdf 3.36 MB Wifi Manual Addendum Hardware v.2 rev.2.05.pdf 125.86 KB Wifi Manual Addendum Hardware v.1.pdf 85.4 KB VMSpc3.2 Owners Manual.pdf 1.6
The small point I was trying to make with that first sentence was, simply, v4 is on hold. Its pulled from the list for right now. Its issues are well documented and we're in a position that, when programming time becomes available, the various issues can be wrung out. I'd like it working tomorrow--so we can continue prioritizing the next set of features. But not today or tomorrow. Big things are brewing here, neat house-side systems far beyond whats out there. So, we all have to be patient and use the tools that will do the job, for now. Stay tuned and, as always, help us keep polishing up v4x with your ideas, no matter how different they may sound or seem. cheers Art //
I really want this system for my '01 Monaco Exec. It has a Cummins 515Hp ISSM engine. The engine data port has five pins. Does the Allison tranny feed data through this port to your software. (The transmission data port is the rectangular 12 pin and is located adjacent to the engine port.) Please tell me what I need to order.
Hey Art, since some of cannot use 3.1.b3 or of course Ver 4.xx, how about a patch for 2.5 so we can have the "Night Screen". I really like it in the Orange on Black. It also might work for me when the sun is shinning on my dash.... :)
Hello Ron The code-base for v2.5 is archived. Only guys with white gloves and a PhD are allowed to even speak (in hushed tones) of its eccentricities or even its whereabouts. It won't be getting a night screen; sorry. I kinda wish it was as easy as a cut-n-paste (as these things can often be) but the v2.5 and v4.x are different bases--not the same language exactly. So, this wouldn't work. I hope to get Josh's coding time before December for the re-release of v.4.x cheers -- Art Renda Documentation Central Silverleaf Electronics (888) 741-0259