Printable View
Elton-Quote:
Originally Posted by fastbikes76
I had similar problems - looked underneath and discovered a sloppy front carrier, and the rear is borderline.
Haven't fixed them yet, but I suspect rather strongly they are responsible for my knock, especially because I was experiencing low-rpm/low-load reports.
When I hammer it in third to check boost, I was getting no more than a count or two at most.
The knock ONLY shows on the peak recall section but not in the live knock readings. It also doesn't trip the knock alarm which is set to 3 or more, and doesn't show up in evoscan . I suspect it's a glitch in communication rather than knock (phantom or real) ?Quote:
Originally Posted by j2k4
:)
Ah - I went directly to the real-time display to suss mine when I was bumping duty-cycle to raise boost.
That was when I noticed the lack of correlation to what the car was actually doing, relative to load.
In anticipation of a third-gear pull, I would gently roll up through 1st, then 2nd, and out of nowhere, I would watch it hit 4, or 6, 8, 12, 14...didn't tumble to the mismatch until, out of the blue, I banged a 28, which is the limit the ECU will report.
Paranoia is required, with these cars, but the no/low-knock 3rd-gear pulls tell the story, I think.
I'll watch for further developments from you. :)
I bought a ferrite core after work but then the weather went bad so I decided to keep the car in the garage today. I'll have go at this tomorrow instead.Quote:
Originally Posted by fastbikes76
Damn.... I had too google that lol. I have no idea with this sort of thing so im a bit like a sheep following the pack. Hell I don't even know how to do the update so that's why I was waiting too see if it cured yours first :Bwahaha:Quote:
Originally Posted by Unlogic
When you download the update, it has instructions inside.
The good news is the boxed version LCDBC now defaults to the 2nd serial port (datalogging port), so you don't have to hold down the rotary encoder button anymore during power up. There's no need to worry about screwing up an update, cuz if it does screw up, it lets you reflash as often you like. So no brick scenario.
I've been trying to flash my LCDBC with firmware version 3.11 for two hours now using a FTDI based USB-Serial adapter (this one to be precise).
When I start the flashing program and turn on the LCDBC the screen on the LCDBC goes blank after a few seconds and I get the following messages in the console:
If I try to run the flash program again while the screen is blank on the LCDBC I get this message instead:Quote:
C:\Users\Unlogic\Downloads\UPDATE311>avrdude.exe -F -v -pm644p -cstk500v1 -P\\.\COM7 -b38400 -D -Uflash:w:"C:\Users\Unlo
gic\Downloads\UPDATE311\FIRMWARE311_20mhz.hex":i
avrdude.exe: Version 5.4-arduino, compiled on Oct 11 2007 at 19:12:32
Copyright (c) 2000-2005 Brian Dean, BDMICRO MAVRIC ATmega128 AVR Microcontroller Boards, Relays, and Optoisolators
System wide configuration file is "C:\Users\Unlogic\Downloads\UPDATE311\avrdude.conf "
Using Port : \\.\COM7
Using Programmer : stk500v1
Overriding Baud Rate : 38400
avrdude.exe: stk500_getsync(): not in sync: resp=0x00
avrdude.exe: stk500_disable(): protocol error, expect=0x14, resp=0x51
avrdude.exe done. Thank you.
Once I got this message but I never managed to get this far again afterwards:Quote:
C:\Users\Unlogic\Downloads\UPDATE311>avrdude.exe -F -v -pm644p -cstk500v1 -P\\.\COM7 -b38400 -D -Uflash:w:"C:\Users\Unlo
gic\Downloads\UPDATE311\FIRMWARE311_20mhz.hex":i
avrdude.exe: Version 5.4-arduino, compiled on Oct 11 2007 at 19:12:32
Copyright (c) 2000-2005 Brian Dean, BDMICRO MAVRIC ATmega128 AVR Microcontroller Boards, Relays, and Optoisolators
System wide configuration file is "C:\Users\Unlogic\Downloads\UPDATE311\avrdude.conf "
Using Port : \\.\COM7
Using Programmer : stk500v1
Overriding Baud Rate : 38400
avrdude.exe: stk500_getsync(): not in sync: resp=0x30
avrdude.exe: stk500_disable(): protocol error, expect=0x14, resp=0x51
avrdude.exe done. Thank you.
Got any ideas what I could be doing wrong?Quote:
C:\Users\Unlogic\Downloads\UPDATE311>avrdude.exe -F -v -pm644p -cstk500v1 -P\\.\COM7 -b38400 -D -Uflash:w:"C:\Users\Unlo
gic\Downloads\UPDATE311\FIRMWARE311_20mhz.hex":i
avrdude.exe: Version 5.4-arduino, compiled on Oct 11 2007 at 19:12:32
Copyright (c) 2000-2005 Brian Dean, BDMICRO MAVRIC ATmega128 AVR Microcontroller Boards, Relays, and Optoisolators
System wide configuration file is "C:\Users\Unlogic\Downloads\UPDATE311\avrdude.conf "
Using Port : \\.\COM7
Using Programmer : stk500v1
Overriding Baud Rate : 38400
AVR Part : ATMEGA644P
Chip Erase delay : 9000 us
PAGEL : PD7
BS2 : PA0
RESET disposition : dedicated
RETRY pulse : SCK
serial program mode : yes
parallel program mode : yes
Timeout : 200
StabDelay : 100
CmdexeDelay : 25
SyncLoops : 32
ByteDelay : 0
PollIndex : 3
PollValue : 0x53
Memory Detail :
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
eeprom 65 10 128 0 no 2048 8 0 9000 9000 0xff 0xff
flash 33 6 256 0 yes 65536 256 256 4500 4500 0xff 0xff
lock 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
lfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
hfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
efuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
signature 0 0 0 0 no 3 0 0 0 0 0x00 0x00
calibration 0 0 0 0 no 1 0 0 0 0 0x00 0x00
Programmer Type : STK500
Description : Atmel STK500 Version 1.x firmware
avrdude.exe: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x00
avrdude.exe: stk500_getparm(): (a) protocol error, expect=0x14, resp=0xfe
avrdude.exe: stk500_getparm(): (a) protocol error, expect=0x14, resp=0xe0
Hardware Version: 16
Firmware Version: 4417552.4368076
avrdude.exe: stk500_getparm(): (a) protocol error, expect=0x14, resp=0xfe
avrdude.exe: stk500_getparm(): (a) protocol error, expect=0x14, resp=0xe0
avrdude.exe: stk500_getparm(): (a) protocol error, expect=0x14, resp=0xe3
avrdude.exe: stk500_getparm(): (a) protocol error, expect=0x14, resp=0xe0
avrdude.exe: stk500_getparm(): (a) protocol error, expect=0x14, resp=0x1e
Vtarget : 200098120.5 V
Varef : 268691.6 V
Oscillator : 1.373 Hz
SCK period : 51.0 us
avrdude.exe: stk500_getparm(): (a) protocol error, expect=0x14, resp=0xf0
avrdude.exe: stk500_getparm(): (a) protocol error, expect=0x14, resp=0xa0
avrdude.exe: stk500_initialize(): (a) protocol error, expect=0x14, resp=0xe0
avrdude.exe: initialization failed, rc=-1
avrdude.exe: AVR device initialized and ready to accept instructions
Reading | | 0% 0.00s
avrdude.exe: stk500_read_sig_bytes(): (a) protocol error, expect=0x14, resp=0xe1
avrdude.exe: error reading signature data for part "ATMEGA644P", rc=-2
avrdude.exe: error reading signature data, rc=-1
avrdude.exe: stk500_disable(): protocol error, expect=0x14, resp=0x00
avrdude.exe done. Thank you.
I'm using a HP Elitebook 2740p with Win7 x64.
After quite a few flash attempts the display on my unit has started to fade a few seconds after powering it on until nothing is visible on the display :sad:
Here is a video:
http://www.youtube.com/watch?v=WynbQdrtVTw
Cycling the power of the unit brings the display back for a few seconds again before it starts to fade again.
Unlogic: In regards to flashing, when the LCDBC first powers on, it checks to see if an updated flash file is available. If more than 2 second passes by it exits and runs the normal LCDBC software. So when you flash, timing is critical to get started. On the PC Side, when you see the black DOS window, power up the LCDBC. If you mess up, you have to wait for the black DOS window to close on its own.
Also when you see your screen fade like that, the +5v voltage regulator is not doing it's job. Are you able to solder a new LM7805 voltage regulator on it?
I must have tried to flash it 100 times last night trying all sorts of timing combinations. I suspect that the dimming of the display issue could be related to the inability to flash cause the problem only started after a few flashing attempts.
Soldering on a new voltage regulator is no problem, can I replace it with a Texas Instrument UA7805?
I also tried logging via CoolTerm but as soon as I connect the serial cable the screen starts to fade very quickly (even quicker than on the video I posted). I'll rip out the board and double check all the solder points today.