Protocol Error

[Jay_D79]

So I went to change some settings this evening (going from fuel only to HEI spark control), and while running through different settings I suddenly lost communication and the "protocol error" light on the lower right is on. I opened the protocol stats tool.. canQueueFull and okCount both count up from zero. canQueueFull counts up at about 5x the rate of okCount.. All the rest stay at zero..

Here's what I've tried..
-restarting everything
-reinstalling serial adapter drivers
-tried my old usb-serial adapter that worked but would randomly drop connection while driving

MS2 3.57 and Tunerstudio 2.6.04 registered to me.

Any insight? Everything was working just fine then it just dropped connection and here I am..

Thanks,
Jason

[LT401Vette]

Do you have a CAN controller in your project?

It sounds like it was trying to talk to a CAN controller and wasn't finding it on the network.

[Jay_D79]

No can controller of any kind, just the megasquirt unit.. The trans is non electronic, no cruise, nothing.. Just some fan relays triggered by MS..

[LT401Vette]

If you can post a project Archive, it might help. It sounds like something is trying to talk through CAN.

[Jay_D79]

ok here's the archive.. I'm not sure where the spark/ignition settings are at this point, I was having trouble getting an rpm signal after switching things around and then I lost communication completely..

[LT401Vette]

All looks Ok in there.

However, if there are no CAN devices and the project looks to be setup for the default CAN ID of 0 and you lost all communications, my next guess would be that the CAN ID of your MS got changed from 0.

If you can post your TunerStudioAppDebug.txt it should tell what CAN ID it is now on if running a new firmware.

[Jay_D79]

ok.. Where do I find that? I looked around briefly but couldn't find it. Do I need to be attached to the ecu and attempting to connect? I'll be home in an hour or so.

[LT401Vette]

In the TunerStudioProjects folder.

[Jay_D79]

I don't see it in there at all..

[Jay_D79]

OK I went and created a new project and tried connecting to the MS just to see what happened..

Got an actual prompted error with this one that says "too many triggers". It will intermittently connect to the controller then immediately disconnect and go offline.. With the new project under communication settings COM1 will test successful, while in the original project (86monte454) it fails every single time.

There's no TunerStudioAppDebug.txt file anywhere on this computer. Is there a setting I have to change for the software to generate one?

[Jay_D79]

Mine was going along very well too.. I was able to log a full 50 samples/second after finding a better serial adapter.. Mine started this while sitting in the driveway, ignition on, engine off..

[LT401Vette]

Jay and mill383, I would be interested in seeing the TunerStudioAppDebug.txt for both of you. Even better if you can capture it with Comm Debug turned on. That will allow me to see all the communication and protocol errors that are happening.


Jay, The TunerStudioAppDebug.txt is always generated automatically. It will be in the parent folder of your Project folder. By Default this is in
Documents/TunerStudioProjects/

However, if you move you project folder to a different folder, that is where it will be.
So where ever that MyCar folder is, check up 1 directory.

[LT401Vette]

While responding to another post another possibility occurred to me... While connected over BT or USB, do you have the other disconnected?
If you have both connected, but are only using 1, you can get protocol errors that will cause the pauses.

[Jay_D79]

ok I see it.. I must have had a brain fart looking for it yesterday..

I created the "my car" project just to see if there was any difference.. The only real difference I can see is that com1 tests good with "my car" and it gives me the trigger error, but fails with the "86 monte" project and doesn't ever try to connect..

[LT401Vette]

Jay, it looks like your CAN ID is set to 255 on the MS, so it isn't going to work.

In your project it is still set to 0, which is the default. There seems to have been some type of corruption issue. The new protocol should protect against corruption so I'm not sure how it would have happened.

You are likely going to need to reload your firmware, then load the msq from that project.

[Jay_D79]

Makes perfect sense.. I'll try that this evening and report back.

Thanks for all the help, I dragged my feet for a few years after purchasing the unit but everything was really straightforward with the wiring and the initial setup. Had I known it was this user-friendly I would have started the wiring before the MS even showed up..

[jsmcortina]

I loaded up your MSQ on the bench and don't get any errors, so it does look like something has become corrupted.

As an aside, do be sure to use "Save Tune As" frequently - there are no saved tunes in the archive you posted.

James

[Jay_D79]

That's odd.. there are 31 msq's in my project folder..

[Jay_D79]

ok.. reloaded firmware and it seems to have straightened it right out..

Thanks again for the help..

Now back to no rpm input lol... I should probably start a new thread in the appropriate section for that..

[DeadStiff]

If your using USB you need to unplug the Bluetooth from the MS. I get protocol errors too if I don't remember to unplug it while using USB.