Megasquirt Support Forum (MSEXTRA)

tried to start truck with low battery and lost tune on tranny controller. reflashed firmware and reloaded msq. as it stands right now after several attemps to get this right I can tune directly to gpio. in ts at this point all is well. I can open engine tune and all good but when I open truck tune (this is the combined ts tune with both controllers) this is where the issues come. i can see comms between the 2 controllers and get data back and forth just fine until i open the vss config screen. then kablewie. i get different comm errors, serial errors and it corrupts controller data. i can adjust vss directly from gpio and as long as i do not open vss config screen from "truck" all seems ok. i get data between the 2 controllers via canbus. i downloaded new s19 and ini for gpio and that didn't help. removed and reloaded tuner studio. the only thing i have not done yet cuz i just thought of it is to dump and reload msII firmware.
ms2 v3.0 3.4.2
gpio 5201

here is more.. anything else you might need???
thank you

It looks like there is an error reading page 2.
When you open a dialog that triggers a page refresh.

To see what the error is, I likely need a COM Debug log. That would be the TunerStudioAppDebug.txt like you attached, but with Comm Debug turned on under the communications menu.

OK I will get it to you soon. Also it might be a problem with the gpio. Tried to drive it and tune vss directly and seemed to lose tune. I parked it for now.

reflashed firmware on gpio and loaded msq. turned on comm debug opened up "truck" and went to vss settings,opened up and generated error. I didn't see a different error log so I assume the extra data is in the same debug log

It looks like a problem with the MShift firmware.

just did a fresh download of -- Monitor_5201.abs.s19 size 88.8kb (90934) size on disk 92.0 (94208) -- from the msgpio website. I will try it tonight if I can find 10 min. is there anyway to verify the integrity of the file besides the bit count?
also I have always loaded firmware "the ol fashioned way" with ms download 2.0. should I be using the new function of tuner studio with the gpio board?

so I reflashed the firmware I downloaded today and got the same error. soon as I open vss in the combined project. so I decided to try to load firmware thru ts in the "transmission" project and it flashed but when it got to the point where it tried to open the project to load msq it hung and corrupted the project. now that doesn't open... here is todays log and the firmware I downloaded today

I need help!

so I went out and reflashed everything. new firmware on ms2 and also the gpio. same issue. upgraded tuner studio. didn't help. same thing no matter what I do. soon as I open the combined project and open the vss config page all hell breaks loose. get the cascade of errors, ts shuts down comms on the gpio and when I get back in to the gpio all that's left is gibberish. I am about to order another gpio board but I would feel better knowing its a hardware issue. there is also a post with the same topic in the gpio forum

What gearbox are you trying to control? If it is one of the supported ones, you may have more success with the "Microsquirt transmission control" firmware.

http://www.msextra.com/product-range/ex ... n-control/

James

Running a 4l80e. I also use paddle shifters and the led gear indicators. The gpio has been flawless for 3 years until it pooped out. I don't think the microsquirt has the IO capabilities I use. I wish I knew what the issue was exactly. Don't like to be "a part changer" troubleshooter. I bought another gpio and will build it then fix this one and have a spare.

I am posting in several locations in hopes someone can figure this out. same results. ordered new gpio from diy, built it, other than upgrading to a drac its the same setup that has been flawless for 3 years. so the issue was not a hardware issue with the board.-now I have a spare ;) - I can load tune and configure thru serial directly. I can connect thru can and see data but soon as I open vss page I get can config errors ,corrupted data ( after today I think its in tuner studio only because when I reconnected back directly to gpio it had correct tune- need to verify that) main controller is 0 gpio is 1. I posted in msxtra/tuner studio and phil looked at some comm logs but nothing conclusive ........

As stated before, it really seems like an MShift firmware issue handling the CAN pass through.

The GPIO forum is likely your best place for support with that.

so I have reloaded firmware on both the squirt and the gpio deleted and reinstalled tuner studio bought and built another gpio to eliminate a hardware issue redownloaded and reflashed the firmware for the gpio( its the same version for over a year and a half) so if its a firmware issue why all of a sudden and I have used the firmware from when I originally downloaded it and also did a fresh download at some point while trying to figure this out. I am at wits end of what to try and I have not seen a post from lance in awhile. the only one who chimed in over there was matt. I don't know what else to check

If you are not getting support there, you can try James's suggestion above.

It just don't make sense to me. Same firmware that has worked for years, on the squirt and gpio. Been able to do this since 2014 without issue until last month.Can comms work until I touch that one page thru the dual project. I can tune directly just fine and can make changes to the tranny thru can bus as long as I don't touch that one page. I guess at this point I will live with it and see if I can catch Lance. I am going to delete everything and start as a new build. I am not going to use my old files and manually configure everything from scratch and see what happens. I do read a lot of posts here every night, it's how I put myself to sleep

So what changed in your install between when it was working and when it stopped working?

James

I had went on vacation and when I had come back I went to drive truck and battery was low and didn't crank strong. 2 short attempts and put it on charge overnight. when I started it the next day I had no gear lights active and that made me look at the tune on the gpio and it was corrupt. didn't think nothing of it, reflashed msq, loaded tune and when I was doublechecking all my settings is when I caught the issue with the vss page- only the vss page-. I have wiped and reloaded redownloaded and rewiped everything. tuner studio,ms2 and gpio. I can go in thru the canbus from the ms2 and do everything except for that one page. I can edit tables in the gpio. that page is the only one where when you change a setting and hit enter the burn icon goes active with a banner informing the user that the board needs to be power cycled for settings to take effect.... at that point is when all the errors happen. if I adjust settings directly thru the serial port all works fine. the errors all have to do with can comms. one of the errors says that the device does have the correct aon first read with outddress but it finds issue and shuts it down anyway. if requested I can write them all down but they should be in the second debug log I posted here. I went and read the gpio ini file but its a bit difficult to completely figure out without some kind of guide. around the same time I also had a issue with one of the login accounts on my laptop and deleted it, it was the main login that I had always used to tune. I had tuner studio on the other login but it was the lite version so I put license in and then deleted and reinstalled. I had a tough 10 days there other than the trip. so I had a couple different things it could be. so at this point I am going to use a different computer and manually redo everything by hand at some point. but at least for now I am not dead, all I have to do is get the vss set and be done for now.... but now I have a spare gpio board and I might as well build another ms2 while I am at it

Hmm... I'm not very familiar with the GPIO, but I tried out your configuration (ish) but using an MS3 as the main ECU. Like you say, when I open the VSS page, the GPIO loses comms - in fact the code crashes.

I also tried connecting to the "GPIO" over serial, but when I enabled "CAN_COMMANDS" it got totally corrupted.

However... unless I'm mistaken, TunerStudio isn't following the ini directives which could easily cause a problem.

#if CAN_COMMANDS
blockingFactor = 64
#endif

18/05/17 21:50:58 :Info: Target on CAN ID:1, blockingFactor: 256, tableBlockingFactor: 512

EDIT: On reflection, I don't think this is the issue.

James

I do remember a tuner studio update not too far back. could there be a change in that? the fact that you can replicate the issue I know its not hardware. I was wondering if I had a ms2 issue. still plan to build a spare.... well I do thank you for going the extra mile! did you download msq/ini from website or use what I posted. so how do we find the issue?