MegaShift Not Working

[VolvoGuy50]

Bug report #2

When I create a new project in TS for my MegaShift, I direct it to the INI file that I downloaded from their page. When I do that, TS throws a fit about null errors in the ini file, says the ECU configuration isn't valid, throws 2 more null errors at me, and then bombs out and say it can't open the project.

It does it on TS 1.11, but it works perfectly on 1.004, sans the fact that it's complaining every time I open a window that there's no default MSQ loaded - none exists for MegaShift. I think I need to be connected to a controller, but I'm waiting for Lance to confirm that. The screen caps below are in the order that I get the messages under 1.11.








On a side note, I keep the installer for EVERY TS version since I've started using it - like wayyy back to well before 0.9x so I revert back if something like this happens.

[LT401Vette]

Yep this just got reported today on the gpio site.. That is fixed for the next release.

[VolvoGuy50]

Yep this just got reported today on the gpio site.. That is fixed for the next release.

haha, that was me that reported it.

[dch]

Phil

I loaded V1.12 last night and Megashift will load and run as a project but when you try to load a project for CAN it wont load I get this error ( failed to subscribe to DashComp output CH, 21 times ) also posted in MSgpio

Dave

[LT401Vette]

I get this error ( failed to subscribe to DashComp output CH, 21 times )

I assume that if you switch to the MShift dashboard there are a lot of gauges with red circle and cross on it?

If you reload the default MShift dash see if the errors go away?
If not I may need your project zipped up and sent to me.

[dch]

Phil

Yes there is,

If I reload the dash TS will start working but the status bar will activate 3 times and gives a error message returned error serial failure, unable to get all pages of data after multiple attempts. This error was also there the first time. And I'm hard wired no USB/BT

[LT401Vette]

How is your project set up?
What controller are you connected to via serial? (Including firmware version)
What Controller is set up via CAN?

What is the CAN ID of each set to on the Controller and in the Project Properties?

Is CAN_COMMANDS set to Active in Project Properties on the Settings Tab?

[dch]

Phil

Sorry should have added that
MSII V3 rev2.905 can ID 0, via CAN GPIO board Mshift rev2.109 using can ID 1, CAN_COMMANDS set to Active, I left the serial protocol to firmware default.

Dave

[LT401Vette]

Can you delete the TunerStudioLogFile.txt
- Start TS with the controllers off.
- Turn on Comm Debug under the communications menu
- Power on the controllers

Once the error happens, shut it all off and send or post the TunerStudioLogFile.

[dch]

Phil
I'll do that after work and send it to you
Thanks Dave

[dch]

Phil
here is the log file

[VolvoGuy50]

Phil
here is the log file

The trouble starts just above 1/2 through the log. There's a bunch of mis-reads from the controller.

[LT401Vette]

Does this project work in 1.004?

It looks like you are configured correctly, and is communicating with both controllers, however it is consistently coming up one byte short on the read from the MShift during interrogation.

[dch]

Yes this did work with 1.004, I had some PC problems that's why I had to upgrade

[LT401Vette]

Can you install 1.004 in parallel and try that same project?

I don't have an MShift controller here to actually recreate your exact setup. But I do have CAN controllers setup, even turned on blockingFactor like the MSII base code uses and it seems to be working. I don't quite know why your MShift is getting 1 byte short....

If you edited the MShift ini to check page 1 to 632 bytes instead of 633, I bet it would go right online. But, I don't know what byte might be missing. It might be the last one, if maybe something in the middle.

Do you have a project that speaks to the MShift via serial working?

How about a project that has only the MShift set up as the main controller, but you talk to it through the MSII?

[VolvoGuy50]

Can you install 1.004 in parallel and try that same project?

I don't have an MShift controller here to actually recreate your exact setup. But I do have CAN controllers setup, even turned on blockingFactor like the MSII base code uses and it seems to be working. I don't quite know why your MShift is getting 1 byte short....

If you edited the MShift ini to check page 1 to 632 bytes instead of 633, I bet it would go right online. But, I don't know what byte might be missing. It might be the last one, if maybe something in the middle.

Do you have a project that speaks to the MShift via serial working?

How about a project that has only the MShift set up as the main controller, but you talk to it through the MSII?

Where can we get 1.004? As I said before, I keep all old versions, but many aren't so lucky. Maybe you should keep 1 version back (1.004 in this case) up for DL in case of stuff like this?

[LT401Vette]

Here:
http://tunerstudio.com/downloads/TunerS ... v1.004.exe

But I actually was just email Lance and he is using 1.004 and getting the exact same thing. Only 632 bytes coming back...

Any firmware changes since it last worked?

VolvoGuy50, you were using through an MS3, but don't actually have it yet, right?

[LT401Vette]

Ok, I think Lance got this sorted.
It seems the the the MSII code didn't like the last odd sized 57 byte block of data. Lance has updated the MShift code to make it a rounded out 64 and it all seems to work again.

He has posted new MShift code over at:
http://www.msgpio.com/manuals/mshift/V2code.html

[VolvoGuy50]

Ok, I think Lance got this sorted.
It seems the the the MSII code didn't like the last odd sized 57 byte block of data. Lance has updated the MShift code to make it a rounded out 64 and it all seems to work again.

He has posted new MShift code over at:
http://www.msgpio.com/manuals/mshift/V2code.html

I got the latest MShift firmware/INI from the site as well as TS 1.13. It's MUCH better now, but every time I open TS, I get this error.

IDK WTH that's all about. I'm guessing it's saying that all of those gauges don't exist.

[LT401Vette]

Right click on the dash for each CAN device, select Load and load the default dash.

I just found that this morning, it appears when it first creates the default Dash for CAN devices it is not assigning the CAN device configuration, so it is looking for those Outputchannels on the Main Controller. It seems to work properly when you load a new Default Dashboard.