Missing VMSpc info

You need to scan your engine computer for the correct PIDS and then change the affected gauge to read the correct PID number. Select each gauge one at a time. The color changes for the engine load graph are part of the same as the correct PID number under the Parameter Editor under the Advanced Tab at the top. Or read the manual from the download section which has pictures and explains the above.

Hey there Chris, Hiya Rhodes I suspect this is a v4.0.8 software bug. You haven't mentioned the rev you're on--yet, I'm suspicious. If you are using the new software, instead, install the v3.0 and reassess. This next month we should be done with 4.0.9--Conner is hammering away at J1708 parsing just now (and so salient to what you describe;) the path forward is looking good. The coloring is generic and, as Rhodes pointed out, can be tweaked in Parameter Editor. The limits are not as intuitive as I'd like. And I'd like the PID sniffer and Param' editor combined into one (more usable tool). But, alas, not yet... I'm hopeful 4.1.x will have this. cheers Art //

Dare I hope that Conner will solve all the J1708 display failures?? It would be MUCH appreciated!

I've seen the round gauges--they are coming together nicely. Hey folks--we've got a tall order for the version 4.0.9 coder. He's not only learning the system and new programming tricks, but also sorting out the gotchas' we ran into with trying to parse-backwards. That's what I call it, anyway. At any rate, he's found a 'shift' problem in the code; apparently it *does* matter if a column of info is slightly offset. So he's found these offsets and so next we'll be testing it on our donor coach: 1997 Safari Sahara. The numeral in the middle of the gauge still seems puny--so he's working on that. He does have the TST parsing built, so that's good. He's tweaking on the Tankminder just now. All must be modded to add the "Radial Gauge" options... However...I would like to add, version 3.0 is a very stable program and is currently being used by thousands. A person would do well to stick that and not experiment with 4.0.anything for now. Its no longer a beta--but the bugs and gaps remain. So, if you can help us identify, define and work through critically the bugs--thats great!! If you define this process by using the *er, h'hem* 'failures' then, well, v2.5 or v3.0 should just be your go-to for now.... Its an important process--bringing you something new and fun--And Usable. However, all steps lead forward and, I've found, none begin with the word 'failure.' cheers Art //

I decided to take a "FEW DAYS" to configure and color all my normal Ver 2.5. gauges in prep for Ver 4.0.1. What I found is that, once again, coloring Day Time gauges with custom colors causes the Default Night Time colors to show as the set Day Time colors... so when I switch to Night Time I get the custom colors I set for Day Time and NOT the Default Night Time colors. I want the Default Night Time colors to show at night. Forgot some info; Win ver 7 (netbook) 2000 Dutch Star, Cummins 8.3, 300hp Ron

Any updates on this issue? Thanks.

Chris, Its as though no engine file were selected. Would you confirm your model and HP are? Thanks Art //

I still have the no torque and HP issue. I tried V3.0 and still no luck. All other parameters display properly, although the road speed and cruise set speed jump about 5 mph.

I have a 330 HP CAT C7 engine and have selected that engine parameter. I have reloaded the program a few times. I have reloaded the drivers a few times.

The PID sniffer says that the torque and HP values are derived. What are they derived from? Could there be an issue with those values?

After 9 months of trying different things I'd really like to get this figured out. I know that I am not the only one that is experiencing this problem...

The values for torque and horsepower are derived from a lookup table using two factors to sort out the actual output(s). These two factors are Engine-Load (PID 92) and Engine Speed (PID 190). With these, the table created by the Engine OEM is cross-referenced for the derived value.

If you're not seeing these it could be for one...or several reasons.

1. One not so obvious one has nothing to do with our program, but a simple 'convenience' introduced by Microsoft with Win-10. They made a default setting to _Not Show_ File Extensions of Known File Types. Here's a link to follow for undoing that. This also keeps our program from seeing the file extension.

2. Blank PIDs - Check out those two factors, making sure they're seeing real data, not zeros.

3. Off chance here...a maybe... it could be that the J1708/ J1587 parsing in your particular jib is faulty. We see this where the chip doesn't outright fail, but, in combination with internal timing and how the j1708 data are batched (and sent via USB) a given gauge never gets updates. See, the jib grabs a small armload of data, formats it for USB and sends it onto the PC. Where it starts grabbing from, and where it stops (for a return trip) is not randomised...but happens at the exact same spot, every time. Missed once its always missed. A jib update with a faster clock and updated firmware can do wonders. If you can see valid data (PID sniffer) for those two factors, this is not likely however.

If after ruling out Possibilities 1 and 2 you still don't have success, you could send in the jib for an update to see if that works around the issue. We saw that the clock update, designed entirely around 2017-and-newer engines made unexpected improvements to the J1708 parsing. That was another good reason to just start over with VMSpc v5.0, too.

cheers

Art

//