MSgpio.com read only forums (Jan.15,2018)

gui67,

Sounds like you have a good plan. The metric units appears to work on my bench. An input signal of 1584 Hz is 95 kph or 60 mph. However, the units in TS are not changed, the display says 95 mph. To change the display units requires a change to the project properties 'NOT_METRIC' value (which I'm sure you know, but I put it here for others will speedo issues that might stumble on this thread).

The speedo output would be good to check with a frequency meter (or oscilloscope if you have one). Since you have no signal, the most likely problem is with the pull-up circuit (step D.5 in the instructions here: http://www.msgpio.com/manuals/mshift/4L80.html ).

Lance.

Lance, for these speeds in mph and km/h, did you change the diameter of the tire from inch to cm or did you let it in inches in the vss setup menu?
Guillaume

gui67,

I left the tire dameter value the same as it was in inches (26.00 - the default). But that's not supposed to be right (if you switch to metric, the tire *should* be in cm), and I will have a look at it in the code. This should be an easy fix.

Lance.

gui67,

I have put 2.104 code with the corrected metric conversions here: http://www.msgpio.com/manuals/mshift/V2code.html

The code now expects the tire diameter in centimeters if you choose to use metric units.

This is the only change over 2.103, so you should be able to use your 2.103 MSQ file.

Lance.

Thank you, I will try it this week-end.
I tested the 2.013 this afternoon, put everything in imperial, in tunerstudio the speed was in km/h but was correct.
I then went on the road, all gears are passing without a problem, the TCC also locks.
But the température was still 51deg when it was supposed to be around 15-20 °C. I didn't manage to measure the resistance, I will also try this week-end.
For the speedo output, I had not frequency signal on the output. is there a way to control the cpu output? or to check is the TIP120 is working correctly. I checked that the metalic part of the tip120 is not grounded.

gui67,

There is definitely a problem with the speedo output in the code, and I am working on this right now. I will post here when I have something that works.

Lance.

OK,
thank you very much.
Let me know if I can help in any way.
Guillaume

Guillaume,

I have put 2.105 code here: http://www.msgpio.com/manuals/mshift/V2code.html

The fixed speedo function appears to work properly at first glance on my bench, though I have on tested it briefly. If you try it, could you let us know how it works for you?

Lance.

Guillaume,

I have just put up new code. It is still version 2.105 and uses the same INI: http://www.msgpio.com/manuals/mshift/fi ... 05.abs.s19
(it appears as "Monitor_2105.abs.s19 19-Apr-2011 16:12 85K ")

The previous code worked, but flaked out a bit at high speeds (over 100 mph). The latest code fixes that. So if you have already downloaded the .S19 file, you might want to try the latest one if you see any problems.

Lance.

Also, the maximum the speedo output can switch at is 1/2 the frequency of the VSS signal (because the code uses the VSS interrupt to toggle the speedo output). I believe you have the speedo output to be the same as the VSS frequency, and this will not work.

<edit>Re-reading your post, I don't think you have the VSS and speedo at the same frequencies. The VSS is typically around 96000 pulses/mile, and you have the speedo set to 16000 pulses/mile. However, I would still lower this (see below) as this is still quite fast for the GPIO output to switch, and you may have trouble with the speedo at higher speeds. If you really need 16000 pulse/mile, I could edit the code further to try to make it work.</edit>

Since you have an autometer speedo, you should be able to set the pulse/mile (or pulse per km). If this was mine, I would set it to be ~2000 pulse/mile (or pulse/km) or less, this will work better than very high frequencies. Use the same pulse/mile value for the speedo and in TS for MShift, of course.

Lance.