MSgpio.com read only forums (Jan.15,2018)

As mentioned before, please tell me how I'd setup the megashift firmware on an MS2 to test it.
If you are able to identify an older MS3 firmware where it did work, please let me know that also.

I'm sailing blind at the moment. The only changes to MS3 CAN that I'm aware of from alpha12-16 were ...

great, i will add the indicator.

ms3 is not receiving the message, we added a counter for number of messages received, and the counter is not incrementing when all other CAN stuff is inactive at the time megashift should be sending the packet.

we'll keep at it.

The debug alpha with a counter for every can packet processed shows no packets when there should be shift retard. It increments if I enable can gear, can vss, and trans temp over can.

Can there be an indicator added for when retard should be applied in mega shift please ? I will upload my msq later ...

gurov,

Yep. But the MShift code can't write to MS3's memory at all, it can only send a CAN message. MS3 has to receive that CAN message properly, interpret it correctly as a 'write' command, then put the sent retard value in the right place, and then act on it appropriately. Because the B&G code ...

it's just this particular feature that's not working.

ms3 grabs gear number, speed, trans temperature from gpio.
gpio grabs tps, rpm, map from ms3 fine.

there's some disconnect in the writing to ms3 that's happening here.

okay.

so ms3's block 7 is shared in this case...



// special case for receiving CAN data
if (var_blk == 7) {
if (var_off >= 0x200) { // datax1 sharing same block no. as outpc
var_off -= 0x200; // but at addresses 0x200 and beyond
if ((var_off + var_byt) > sizeof(datax1)) {
flagbyte3 ...

gurov,

I will attach a short datalog to demonstrate this. MShift it set up with a 'retard only above' load of 90 kPa, upshift retard of 5.0º, downshift retard of 6.0º, 2nd gear retard of 1.0º, third gear retard of 2.0º and 4th gear retard of 3.0º. I was using MShift 2.111 and B&G 2.905 on MS-II ...

gurov,

Okay, if you think it is that important to compare what the two codes are doing, post a link to the latest ms3 code source files, and I will have a look in it for the CAN bugs when I get a chance.

It's worthwhile noting that the CAN code is not specific to MShift, and it is not written by ...

gurov,

I think you are missing the point. The 2.111 code works, this is proven by the fact that it works fine with 2.905. The timing retard code couldn't work with that code unless the CAN mechanism underlying it was sound.

The fact that it works with 2.905 means:
- the CAN message is being sent ...

if it doesn't work, then it will be up to the extra devs to figure out where this is broken.

gurov,

You have already shown that it doesn't work (on your MS3), so it's up to the extra developers to figure out where they have broken their code. Me trying it won't add anything at all. If I try it ...