Foretravel Owners' Forum

Foretravel Motorhome Forums => Foretravel Tech Talk => Topic started by: Mike J on May 22, 2018, 12:11:41 pm

Title: VMSPC Engine file, ISL 400, and missing sensors
Post by: Mike J on May 22, 2018, 12:11:41 pm
Hi,

Finally had our coach out for a run in preparation for trip in a few weeks. First time out with the VMSPC. Using the correct engine file for our ISL 400. Lots of gauges available in the menu but only a few seem to actually have corresponding sensors on our powertrain. Did a PID sniff with engine running for more sensors and that didn't change what is actually available to use. Attached photo, (taken away from coach) shows which gauges had data coming from engine during our test drive. For clarity I deleted those that didn't find sensors

Some of the gauges I would really like to use are: The "fuel tank minder" and "retarder temp, on/off, etc". Also thought the "transmission indicator" would be nice to have. Any suggestions on accessing missing sensors? Or do they simply not exist? If not, why are they available in the VMSPC ISL400 profile?

Thanks, Mike

Title: Re: VMSPC Engine file, ISL 400, and missing sensors
Post by: Keith and Joyce on May 22, 2018, 12:44:33 pm
Mike,

Give Silverleaf a call at (888) 741-0259.  They are always helpful.

Keith
Title: Re: VMSPC Engine file, ISL 400, and missing sensors
Post by: Roger & Susan in Home2 on May 22, 2018, 01:50:39 pm
Mike, the Engine Type file you select has nothing to do with what data is available.  It is a data file that helps VMSpc calculate HP and Torque values (and some others) for display purposes.

Which VMSpc version are you using?

The data that is available on the diagnostic data busses is what you can display on your screen.

The tank minder and the Gear and Range selection should work fine. Retarder Temp is a common gauge. Retarder on/off and % are not.  The data channels are there, data depends on whether the appropriate sensors were installed.

The screen shown is for a 2002 U295 ISL400.  Same Engine and Transmission as yours.  There are 30 gauges on this screen. everyone is function except maybe the calculated HP and Torque.  They may work for the 2002 ISL400.  They are inconsistent on the ISM450 from 2001.  This is a live screen shot from pre-delivery testing this morning.  It is hooked up to my ISM450.

I have attached pdf files on setting up your retarder temp, editing your screens and most of standard VMSpc features.

Roger
 
Title: Re: VMSPC Engine file, ISL 400, and missing sensors
Post by: Keith and Joyce on May 22, 2018, 04:07:30 pm
Roger, thank you for posting that.  That's what is great about this forum no matter what there is always someone who is an expert on whatever question one posts.

Keith
Title: Re: VMSPC Engine file, ISL 400, and missing sensors
Post by: Roger & Susan in Home2 on May 22, 2018, 05:58:37 pm
I am not going to claim to be an expert, maybe just a bit more experience.  I still call when I get stuck.

I am glad to be helpful when I can.  The give and take of useful help on the Forum is its best quality.

Title: Re: VMSPC Engine file, ISL 400, and missing sensors
Post by: DavidS on May 22, 2018, 06:57:30 pm
What is the CSPD box? Mine is usually 75ish
Title: Re: VMSPC Engine file, ISL 400, and missing sensors
Post by: Mike J on May 22, 2018, 07:10:48 pm
Thanks Roger and Keith!

Our VMSPC version is 4.0.7. JIB JS501 USB. Purchased it a few months ago from Art at Silverleaf. Running it on a MS Surface Book Windows 10.

Put call into Art this morning. Should have gone there first but am happy that I came to the forum with my question. Sharing his answers may be helpful to others.

He was especially puzzled that I had fuel temperature data while so much else was missing. Within seconds, (once he knew date of our coach build) he had a fix for us to implement. Apparently, a transition period involving databuses occurred right around our build. In early 2002, coaches, engines/transmissions were transitioning between J1708 or J1939. Turns out ours may use both. This was/is unusual. He spoke a lot of tech info as to why but I recall him saying most coaches use one or the other. His fix: Under the advanced menu for Communication Settings there is a check box for either of these or both. Based on what I had been getting he correctly surmised we were using J1939. Changed it to "Both". and selected "auto restart".

Can't test out the changes just yet. Coach is in shop getting new inverter/charger installed. That is another story.

I'll test out Art's fix in a few days and report back here. Thanks everybody!


Title: Re: VMSPC Engine file, ISL 400, and missing sensors
Post by: Mike J on May 22, 2018, 07:21:47 pm
Hi David,

CSPD is cruise speed, (I think). So how fast do you drive?

Driver bringing coach to us from Virginia last year checked in with a cell phone pic of speedo at 80mph, driving across Montana with toad in a cross wind. Said in drove rock solid. He was very impressed. He had 17 years of RV, Motorhome, coach work in his own business before selling to partner about 15 years ago. He never saw/experienced a Foretravel before ours.

We drive 60-70 depending on which way the winds blow.
Title: Re: VMSPC Engine file, ISL 400, and missing sensors
Post by: AC7880 on May 22, 2018, 07:24:31 pm
What is the CSPD box? Mine is usually 75ish



Cruise set speed you have selected.
Title: Re: VMSPC Engine file, ISL 400, and missing sensors
Post by: Roger & Susan in Home2 on May 22, 2018, 07:26:14 pm
CSPD is the speed set on your cruise control.  All of my screens have substantial customization. I have tried to make gauge labels more readable, warning levels more realistic and organized in a way to make the most information available with the minimum eyes away from the road time. 

Mike, there was a 4.0.7 version that left off the "Both" set as default.  It was replaced quickly with a 4.0.7b version.

It has been replaced with  4.0.8.  If you move to the vew version it will not over write the 4.0.7 version so both will be available.

Roger
Title: Re: VMSPC Engine file, ISL 400, and missing sensors
Post by: DavidS on June 02, 2018, 05:24:50 pm
I guess that might be right... little faster a little slower depends on traffic and the wind