Flashable sbec issue

[Force Fed Mopar]

Okay, so been running on the flash unit for a couple days, seems to have the cut-off problem like the TIII units do. EGR maintenance reminder maybe, like the TIII's? I didn't see anything like that in MP-Tune on the 465 cal, but I'm guessing it's not fully disassembled yet and so wouldn't show up in Mp Tune? If you turn the key off for 20 secs or so, it starts right back up.

[ShelGame]

Yes, that's it. When I get back to my hotel tonight, I'll try to hook you up with a setting in MP Tune to disable it.


Sent from my iPhone using Tapatalk

[Force Fed Mopar]

Cool, thanks.

[ShelGame]

Hmm, well what I was going to do doesn't seem to work right when editing a binary (I guess that table type only works on a .tpl). How are you with a hex editor?

Alternately, I can modify the 465.bin (or any other .bin you want) manually to skip the EMR routine. Not sure how much tuning you've already done.

Also, I updated the .mpt file a little bit, if you want the latest one. Just a couple of new tables, but they're timing related...

[Force Fed Mopar]

I'm not very adept with hex editors, but I can probably follow directions The 465 cal is a 5-spd cal and causes high idle on an auto car when in gear, so not using that one. Was going to use the 357 cal as it is (I believe) and auto cal, normal idle in gear, but while running it the last few days I found the cruise doesn't work. Swapped my stock auto computer back in and the cruise works again. So it seems that the 357 cal is for an auto with no cruise control?

I haven't got a new ftdi cable yet so I have no way to try the other cals yet, any way to tell which is for an auto with cruise control? That's the cal I need to be using.

[wowzer]

Hmm, well what I was going to do doesn't seem to work right when editing a binary (I guess that table type only works on a .tpl). How are you with a hex editor?

Alternately, I can modify the 465.bin (or any other .bin you want) manually to skip the EMR routine. Not sure how much tuning you've already done.

Also, I updated the .mpt file a little bit, if you want the latest one. Just a couple of new tables, but they're timing related...

rob L, which mpt file did you update - the 465 or 357 cal? i'ld like to get a copy. btw, i assume you have disassembled both cals(?). did the ram locations change between them? i had set Rob M up with a custom layout for mpscan that he appeared to be able to successfully log with. it was based on the 465 cal, but based on the above info, he is using the 357 cal witch looks like it has a different ram layout from the disassembly i looked at. so don't know how it worked !!.....

[ShelGame]

I actually don't seem to have the 357 binary file. Which is odd, because I do still have an old .tbl file for it.

Can someone send me the '357?

[Force Fed Mopar]

I actually don't seem to have the 357 binary file. Which is odd, because I do still have an old .tbl file for it.

Can someone send me the '357?

It's on your Google Drive that you posted here lol. 90V6_357.bin

http://www.turbo-mopar.com/forums/sh...=1#post1109001

[ShelGame]

Derrr...


Sent from my iPhone using Tapatalk

[Force Fed Mopar]

Yep, the FTDI chip is in the USB connector...


Sent from my iPhone using Tapatalk

So I just got my new cable in, got this one:

https://www.amazon.com/dp/B00XRCT662...ing=UTF8&psc=1

Should be the correct cable, right? Is there anything special I might need to do to use it? Drivers? Reason I ask is I tried to flash with it tonight and it wouldn't work, said boot download failed, serial errors. Does the SCI board look for a certain cable, or are they all the same? Also tried logging with it and it wouldn't do that either, com port setup issues I think it said.

[ShelGame]

So I just got my new cable in, got this one:

https://www.amazon.com/dp/B00XRCT662...ing=UTF8&psc=1

Should be the correct cable, right? Is there anything special I might need to do to use it? Drivers? Reason I ask is I tried to flash with it tonight and it wouldn't work, said boot download failed, serial errors. Does the SCI board look for a certain cable, or are they all the same? Also tried logging with it and it wouldn't do that either, com port setup issues I think it said.

Yes, that's the right cable. You need to make sure the I/O logic levels are inverted. Use the FT_PROG program to set those. Careful, if it's not truly an FTDI cable, FT_PROG may render it useless. They detect and disable counterfeit parts.

That's the right price for a true FTDI part. The counterfeit parts usually sell for like $5.

[Force Fed Mopar]

Yes, that's the right cable. You need to make sure the I/O logic levels are inverted. Use the FT_PROG program to set those. Careful, if it's not truly an FTDI cable, FT_PROG may render it useless. They detect and disable counterfeit parts.

That's the right price for a true FTDI part. The counterfeit parts usually sell for like $5.

The FT_Prog, you have to download it, or comes installed on computers?

[wowzer]

http://www.ftdichip.com/Support/Utilities.htm#FT_PROG

[Force Fed Mopar]

So invert TXD and RXD?

[wheming]

So invert TXD and RXD?

-Yes..

[Force Fed Mopar]

-Yes..

Ok, so how does this work? I checked the invert txd and rxd boxes and saved it, seems to save as a template but how does it get applied to the cable? Do you have to click Program under Devices?

[Force Fed Mopar]

I tried right clicking and selecting Apply Template, seems to show txd and rxd inverted but it still won't connect or flash. I really hate being illiterate about this stuff...

[wowzer]

responded to your email. make sure you unplug the cable after you are done programming it and then plug it back in again.

[1BADVAN]

What version of Windows? Is it showing up as a serial device under the device manager? I had trouble getting it to work as a serial device until I manually installed the driver, which would be weird because I know you already had one working

[Force Fed Mopar]

I think I got it, about to go try it.