status 65 and loss of MSShift CAN

For discussing Phil Tobin's TunerStudio MS is the MegaSquirt edition of TunerStudio, a next generation tuning application. It provides the ability to configure and tune all GPIO/MShift(tm) controllers and is 100% compatible with MegaTune ini files and msq's.
Post Reply
mill3833
Posts: 72
Joined: Mon Jan 27, 2014 3:33 pm

status 65 and loss of MSShift CAN

Post by mill3833 » Tue May 13, 2014 5:59 pm

Ok Lance,

I am confused. After trying to troubleshoot other issues, I've really goofed something up.

See attached screen shot. After powering up the system, using Bluetooth, I comms working (according to the blinking lights in the lower right hand corner). But when I go to my MSShift screen, TPS load dial is none responsive, and when I start the engine, MSShift is not seeing rpm, and no line pressure, etc.

What has me confused is why "MS-II CAN ID" and "MS-II outpc block" are ghosted?

After applying power, Status =1 (which is normal), after about 15 secs, TS comms comes back, Status=1. After another 7 secs Status changes to 65. Manual says 65= low voltage. But I know that is wrong as MSPro is reporting good voltage (12-13V).

I have attached two screen shots. One now with ghosted stuff, and the other is one I took a while back during bench testing, when I got the CAN working.

I can't figure this out. Need some help.

Dave
Attachments
working CAN screen shot.jpg
working CAN screen shot.jpg (36.68 KiB) Viewed 2029 times
messed up msshift.jpg
messed up msshift.jpg (45.19 KiB) Viewed 2030 times

Bernard Fife
Posts: 1696
Joined: Fri Apr 04, 2008 1:28 pm

Re: status 65 and loss of MSShift CAN

Post by Bernard Fife » Tue May 13, 2014 6:19 pm

Dave,

It looks like MS3 and/or is sending garbage to be burned into the flash memory of MShift, which is causing the CANbus comms to crash. The outpc size setting of 30 is enough by itself to cause your problems, and there are likely other corruption issues too. It could be that TunerStudio is sending the wrong data to MS3, or it could be that TS is sending the right info to MS3 but MS3 is forwarding it incorrectly to the GPIO/MShift. Phil should be able to tell, and you might want to raise the issue with the MS3 developers as well.

The fact that MS2 w/ 2.920 works fine indicates to me that the problem is not with the MShift code itself.

There is another user reporting similar problems to yours, so that should help get this sorted out.

I have also contacted Al to see if there have been any recent developments in the CANbus/serial code that should be incorporated into the MShift code.

Lance.
"Never wrestle with pigs. You both get dirty and the pig likes it." - George Bernard Shaw

Post Reply