Interesting. I never saw the M_ACT go to zero in my logs. It was always 1 or 2. 0x399 only popped up when the M button was pressed, it wasn't continuously advertising like I would have expected.
This thread was specifically for flashing and coding of modules the other will be for MDrive/MDM. The mods will move it eventually. @doublespacesKeeping this here to continue my string of thoughts. Not sure why there are two threads for this now...
I did more data logging, focused on 0x399 and making sure it could be reproduced accurately and found some interesting things. It's transmitted three time each time the M button is pressed, 160ms apart, and then again every 10 seconds (I wasn't being patient enough.) There is a counter that increments 0 -> E, in the upper nibble of Byte0, every time the packet is transmitted, and what the IKM0S docs calls a "checksum" in the lower nibble of Byte0 that I can't figure out. Any thoughts?
View attachment 48112
I also looked around for a while and couldn't find the status of the DSC (on/off/MDM) or the status of the Power (normal/sport/sport+.) I would have through they would have been transmitted by the DSC and DME respectively but 0x19E (DSC Status) doesn't have the DSC mode, and 0x1D0 (Motor Data) doesn't have the Power mode.
What do i wire it to? I tried pin 41(from dsc) to the dtc button (pins 1&3 below the blinkers) but it did nothing. From what was said earlier in the post, the dtc button had to be wired to the dsc directly.The pin on the DSC.... let me find it for you hold on
Edit you were right it Pin 41 on DSC should work
Im pretty sure its on a bus. When I plugged the dsc commection to the dtc pin 3, inpa kept recognizing it changing (pressed/not pressed). Im assuming the m3s dtc button is just a normal +/out/ground?The DTC button and I believe it pulls to ground when pressed but I’d need to check that
Lol is there a forum on saving fried modules? I think my dsc died. It was fine earlier after i coded back to stock.That’s right. The button on a 335 goes to the JB. You need to disconnect and reconnect to a ground and pin 41
Update: it wasnt fried. I reflashed it to the m3 dsc flash again and it worked fine,just like before. I connected the dtc button to ground and no lights come up on the dash. I check the continuity and its fine. Does the m3 have a different light than the standard 335 kombi? If thats true, how would I check to see if dtc is on or not?What makes you think it’s fried ?
I wouldn't necessarily be opposed to testing program changes, but I've had mixed results, so I'd want to be really, really sure it isn't going to corrupt or leave TCU stuck in boot loop before flashing anything.