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.