:::RHMT::: Real Home Made Turbo
General Category => Engine Management => Topic started by: HiProfile on March 02, 2010, 02:42:27 AM
-
I bought one and I can't get it to work. I wanted to use my crome license again to play with my winter beater a bit. I know some people haven't had luck with Crome, but that's what I have to test it ATM.
If I burn the crome map to a chip, it works in my car fine. If I write it to the Demon, it verifies, can be read back into crome, but appears to be seen as a blank chip by the ecu (solid CEL, doesn't run the Crome map). I also found a Moates utility called EmUtility that can also pull the data off of it and byte-for-byte matches the crome bin file. It shipped with the newest firmware.
I would assume this is a Demon problem? I just assumed that Moates tested every unit before shipping.
-
Are you using the option in emulator settings (in Crome) to emulate a 512 chip?
Try using emutility to program the deamon to the 8000-FFFF range and see if it works then...
It seems as if it may not be quite configured properly... Or a bad contact with the deamon... But I atleast know with my batronix 3.3 I can read my ostrich... It was how I tested the 3.3 when I acquired and repaired it.
-
Also make sure the battery has 2.5+ volts across it.
-
Update to the latests drivers, it should fix the problem. Ftdi had an issue with a driver release and it affected the demon. I spoke to moates about it last week and this is how i was instructed to fix it.
-
Created yet another test P30 rom, burned to chip, runs the car fine.
I then wrote it to my Demon, which has 2.89v in the battery. No go.
Original drivers were off the Moates site (first FTDI drivers installed on this PC), then I tried the raw files, then the executable from the FTDI site. No go.
Then I tried putting my crome bin stacked as a 512k rom (2x), uploaded via EmUtility to make sure. Reads back as the same file. No go.
This includes using the reset tool to make sure it's set to crome, along with making sure I have the latest firmware.
Same bullshit, solid CEL with the Demon, but runs perfect with the BIN on a chip. So that makes a 3rd faulty Moates product: Ostrich2 (same exact bullshit), Demon, and O-meter that loves to blink garbage when it's below 60F outside. I forgot to add, I can upload the bin to my good Ostrich2 and it runs the car fine just like the chip. So I feel safe saying it's definately the demon.
-
Did you just update the drivers? Thats what was happening to me, my ostrich worked perfectly, demon didnt.
make sure to get the lastest drivers here http://www.ftdichip.com/Drivers/VCP.htm (http://www.ftdichip.com/Drivers/VCP.htm)
-
Did you just update the drivers? Thats what was happening to me, my ostrich worked perfectly, demon didnt.
make sure to get the lastest drivers here http://www.ftdichip.com/Drivers/VCP.htm (http://www.ftdichip.com/Drivers/VCP.htm)
Went to Device Manager, clicked the port, update driver, navigated to extracted ZIP files, but it said it could not find any newer drivers. Then got the .exe, which installed itself, and next time I plugged the Demon in it came up with the auto-install bubbles in the bottom right of the XP bar. Same crap, no go. FYI the exact same exe listed on the FTDI site is what's listed on the Moates site. How else would I update the drivers?
-
Last time I had driver issues I used FTClean or whatever it was called to remove the old drivers. Then I downloaded and unzipped the ones I wanted to use. Then when I plugged in the device and let it autoinstall with the exception of navigating to the directory that the new drivers were in.
Otherwise I couldn't get it to recognize the 'new' driver as a better driver.
-
Jeff, contact Moates support and go from there.
-
contact support or do driver cleanout do you have the demon reset software
-
Honestly...
Try the deamon in another ecu... I know it's asking a bit.... But there is a common trend... Atleast one...
If your able to emutility it to and from the deamon.... The deamon -is- working and able to save data sent to it... So I think that rules out the driver IMHO...
What are you using to try and EEPROM read the deamon? What settings are you using to read it?
-
I have a bad prototype Ostrich v2.0 that acts the same. It was killed when a moron started pulling plug wires to isolate an ignition miss.
-
ecu chipped properly?
-
I would think it's chipped properly, I did it myself and it wasn't my first. It has also run other chips as well as ectune via ostrich at one point, but I'll try another when I'm done with work tonight. Fucking rear caliper decided it should stay locked today.
I'll definately be calling support next chance I get.
-
It was killed when a moron started pulling plug wires to isolate an ignition miss.
same thing happened to me on my first honda. fried the ignitor in the dizzy. $100 mistake i won't make again
-
You know what the good thing about maotes support is? Sometimes you get to talk to Dave Blundell. It's true.
-
You know what the good thing about maotes support is? Sometimes you get to talk to Dave Blundell. It's true.
Fuck, I'll be calling asap in that case. I want to talk to him about some of his projects he's mentioned lately. :)
-
Every time I've called moates customer support they have been extremely helpfull. Even if the product was bad (ostrich 1.0) they took it back and sent me a new one for no charge, he even sent me the new one (v 2.0) before he got mine back!
It was killed when a moron started pulling plug wires to isolate an ignition miss.
Shit, I do this once in a while. Never had any problems, didnt even know it was possible to jack your shit up by doing this.
-
The new ones it isn't, but I don't care to abuse electronic gear.
-
i had trouble with the demon also, but they sent me a reset program and you pick crome and i will work
-
Okay just an update since I'm a happy camper now.
Talked to Craig, he connected to my PC, did his magic, and both my spare ostrich and "new" demon work. I think it was just the reset program that did it...but i *swear* I tried both the ectune and universal reset programs. Before AND after trying the EmUtility program. For the demon I think it was also from not connecting CN2 (datalogger). I still can't find any how-to instructions, and in initial excited rush probably didn't bother with that.
FYI it's a known issue with the O-Meter to not like cold weather.
So for future reference, do not bother with his forum or email support - just give him a call.