Unable to get MSGPIO and MS2 communicating after TunerStudio Update
Posted: Sun Oct 16, 2016 4:42 pm
Hi Everyone,
New to the forum but I haven't had to post as I've had great luck with my MS2 and Megashift combination - until now. I was running Code 2.920 and MShift 4.127 in my car, connecting using Tunderstuido 2.0.8. I had gotten the combo running 2 years ago, but didn't do much tuning due to an ignition noise issue that I could not figure out. After a long hiatus, I resumed working on the car, upgraded my distributor (and fixing an ignition noise issue) and was ready to hit the road and start tuning. However Tunerstudio forced me to upgrade to verson 3.0.10, and it all fell apart. What happens is when I turn on the car, the ECU comes online, then TS finds CAN1, then everything goes offline for a second, comes back online, goes offline, and then it happens all over again, indefinitely. Basically it seems that TS cannot find CAN1. Again no changes to the ECU settings, just a tunerstudio update. I cannot load my previous version of Tunerstudio as it forces an update (which is odd, that it does this even if my computer is disconnected from the internet).
I can get TS to connect to my MS2, and I can get it to connect to the MSGPIO, individually. However, when I try and connect them together in TS, the project seems to think the MSGPIO should be using 2.920 firmware, which is clearly not correct. See attached screenshot of the error message.
I upgraded the MSGPIO to MSShift 5.201, and updated all my settings. Then in my main project I updated the CAN ECU definition to 5.201. It still doesn't connect. I am at this point out of the car and on the bench using a JimStim and wirng between the MS2 and MSGPIO. Even if I start a new project, and have TS detect the firmware, it correctly detects the 5.201 but says there's a mismatch and expects 2.920 instead.
I guess my question is if anyone has had this issue before. I know this is more of a tunerstudio question but I decided to post here since there's more experience connecting via CAN. I think it may be an issue with how TS is saving a configuration file, but that's just a guess.
New to the forum but I haven't had to post as I've had great luck with my MS2 and Megashift combination - until now. I was running Code 2.920 and MShift 4.127 in my car, connecting using Tunderstuido 2.0.8. I had gotten the combo running 2 years ago, but didn't do much tuning due to an ignition noise issue that I could not figure out. After a long hiatus, I resumed working on the car, upgraded my distributor (and fixing an ignition noise issue) and was ready to hit the road and start tuning. However Tunerstudio forced me to upgrade to verson 3.0.10, and it all fell apart. What happens is when I turn on the car, the ECU comes online, then TS finds CAN1, then everything goes offline for a second, comes back online, goes offline, and then it happens all over again, indefinitely. Basically it seems that TS cannot find CAN1. Again no changes to the ECU settings, just a tunerstudio update. I cannot load my previous version of Tunerstudio as it forces an update (which is odd, that it does this even if my computer is disconnected from the internet).
I can get TS to connect to my MS2, and I can get it to connect to the MSGPIO, individually. However, when I try and connect them together in TS, the project seems to think the MSGPIO should be using 2.920 firmware, which is clearly not correct. See attached screenshot of the error message.
I upgraded the MSGPIO to MSShift 5.201, and updated all my settings. Then in my main project I updated the CAN ECU definition to 5.201. It still doesn't connect. I am at this point out of the car and on the bench using a JimStim and wirng between the MS2 and MSGPIO. Even if I start a new project, and have TS detect the firmware, it correctly detects the 5.201 but says there's a mismatch and expects 2.920 instead.
I guess my question is if anyone has had this issue before. I know this is more of a tunerstudio question but I decided to post here since there's more experience connecting via CAN. I think it may be an issue with how TS is saving a configuration file, but that's just a guess.