[DIY vipec display]

ok i will try with this new shield. The ardrunio has 12mhz and 16mz chips on it and the new CANBUS has 16mhz on it. The old CANBUS has no MHz markings on it anywhere. Even with a basic "loopback" test it wouldn't work on the current board and shield so I'll see if loopback test works ok the new shield 

[DIY vipec display]

slight update, turns out the libraries define the clock speed and subsequent block sizes.  We were using a 16Mhz library and the can shield had an 8Mhz clock...  Replaced the 8Mhz clock with a 16Mhz and the comms is now working well

Testing with a really cheap shield: http://www.aliexpress.com/item/EMS-Free-shipping-6870C-0243C-LC420WUN-LC470WUN-SBA1-Logic-board-High-quality-Hot-sale/620222773.html

I think this issue the i have a the moment. im using the sparkfun can shield in the first post of this page and i think its a "cheap" canbus shield. ive brought a new canbus shield which has 16mhz on it from here so hopefully this works for me. https://tronixlabs.com.au/arduino/shields/can-bus/can-bus-shield-for-arduino-australia/

 

 

[DIY vipec display]

yeah i have only seen it once, and it was when vipec was connected and i opened VTS, i didnt even click on connect to ECU or anything and it came up.... ?

[DIY vipec display]

I've ordered another CANBUS controller in case this one is faulty 

[DIY vipec display]

thanks JMP, thats what i thought. im expecting a crapton of CAN packets once it works, even if the values are 0's at least i would recieve valid CAN packets on the bus network. still stuck with no real way out ive msg'd lekonna the original devloper to check a few things but i cannot find out what on earth i am doing wrong.

 

all i can think of is

 

a) get a CAN emulator and give it to my friend to get it working (saves going to the garage each time)

or b ) get a CAN  sniffer but all that will do is confim vipec is ok (i think it is) and my wiring is right (100% certain, but you never know

 

 

[DIY vipec display]

can someone confirm the vipec will send can packets with the key set to ON, but engine not running? I assume as as all the vipec status stuff looks OK and the ECU is alive and reads all the sensors etc... its just this is how i am testing if CANBUS is working or not, plugging into the CAN HI and LO wires with the car key ON but engine not running. have tried a million different vipec CAN settings, try store/save, car off, car on and still no packets from VIPEC.

 

do i need to request packets from the vipec (i.e ask for Engine RPM) and then the vipec will send it, or will it instantly fire packets out the CANBUS from the "selected" values on the CAN configurations. thats what im expecting, the second i plug in, i see a crapton of CAN packets on the BUS and its all the sensors ive ticked on the "CAN configuration" page. is my understanding and expectation correct?

 

also last time i plugged in and opened VTS, before even doing "Connect to ECU" it came up with....

"CAN is not supported by this version of firmware, upgrade firmware and try again"

whats that all about? running 4.10.2 (serial 5224) with vipec v44 topboard with the CAN fix already applied

 

[DIY vipec display]

thanks and probably agree, just i have no way of knowing or checking, other than a lot of serial.print statements in each of the main blocks to work out if im actually receiving canbus packets or not.

once im receiving packets i can troubleshoot the rest no problems, but im not even sure im receiving packets from the vipec properly.

 

[DIY vipec display]

is there any way to check i have my CAN wires correct, i.e what happens if CAN wires are backwards? how else can i verify the vipec is sending CAN packets properly? I assume it is but it would be great to confirm 100%. ill do some more debuggin in my code to try and see if the CAN sheild is actually receiveing any packets from the vipec

[DIY vipec display]

still not working with the vipec, have added some more troubleshooting code to help work out where its not working. hopefully can report back soon

[DIY vipec display]

hi all, we fixed a number of issues and now have a working canbus board, in short, we changed the ardunio board, hopefully can demo it tonight.

 

ECU Reader
initializing can
initing the mcp2515
pins are set up
mcp2515 in configuration mode
speed set
interrupt activated
Can init ok
1135:OiT=-50,OiP=0,AFR=0,FuP=0,Map=0,IaT=0,Ign=0,Vbt=0,Spd=0,ECT=0,Idc=0,lmc=0
1199:OiT=-50,OiP=0,AFR=0,FuP=0,Map=0,IaT=0,Ign=0,Vbt=0,Spd=0,ECT=0,Idc=0,lmc=0
1282:OiT=-50,OiP=0,AFR=0,FuP=0,Map=0,IaT=0,Ign=0,Vbt=0,Spd=0,ECT=0,Idc=0,lmc=0
1364:OiT=-50,OiP=0,AFR=0,FuP=0,Map=0,IaT=0,Ign=0,Vbt=0,Spd=0,ECT=0,Idc=0,lmc=0
1447:OiT=-50,OiP=0,AFR=0,FuP=0,Map=0,IaT=0,Ign=0,Vbt=0,Spd=0,ECT=0,Idc=0,lmc=0
1531:OiT=-50,OiP=0,AFR=0,FuP=0,Map=0,IaT=0,Ign=0,Vbt=0,Spd=0,ECT=0,Idc=0,lmc=0

 

[EVO 8 V44 plugin - no knock or speed input?]

thanks for the help, the idle speed control fix of adjusting the RPM lockout made it idle a fair bit better, still the occassional 2000+rpm but it behaves a lot better now

 

with the cold start enrichment i made changes as per below but didnt notice any difference....

should I consider changing my pre-crank mode from IGN to key-ON and dial in a whole heap of pre-fuel for when its cold?

 

[EVO 8 V44 plugin - no knock or speed input?]

I've noticed its harder to start my car in the cold winter, do I need to adjust fuel correction to add in more fuel when it's really cold? This is with 98RON and a strong battery always connected to CTEK charger.

I usually turn key to ON wait a good 10aecs for everything to wake up then try and crank the engine. In winter it definetly takes a few more cranks before it fires up.

 

[DIY vipec display]

ok the issue i have is with the CANSHIELD not initialising properly. will fix soon and report back

this is where it locks up in the ardunio code for anyone interested (nothing to do with vipec)

 

[DIY vipec display]

ive double checked my pin outs and found an issue which ive fixed and im certain its right now (famous last words). one thing i want to be absolutely certain of, there are no other wires required other than CAN HI and CAN LO. what about ground between the vipec and the CAN device? they dont share a ground wire or anything like that?

[DIY vipec display]

will talk to my coder on monday and see if we can work out whats happening.

 

our design is a little different as dashboard space for my car i want to be clean and free of messy wires and boxes etc so we going to do something like this;

[DIY vipec display]

thanks, got it working as you mentioned by pressing enter. still no comms output to ardrunio with using hard wired serial cable

did you see the error status screens under "runtime values" - are these errors anything to worry about ? now working on channel ID 0 but still no comms at the ardruino side - will check with my coder

[DIY vipec display]

i think ive worked out why i dont get any comms. im using an Rj45 to serial plug as that was seen to be easier, but it appears inside the RJ45 to serial shell, all the pinouts are not mapped 1 for 1 so therefore wires are missing

ill try a raw serial cable

[DIY vipec display]

thanks, just lookign at lekkonna's code on page one of this thread, he used ID 0 and it worked Ok for him/her? I assume his/her CAN code for the ardruno expects ID 0 so thats why Im trying to use ID 0.

 

even if I try and put in Id 444 and click OK, the VTS software never saves the ID, it always defaults back to the "saved" channel IDs. ill record a video if you want to demo the issue if it helps

[DIY vipec display]

I'm sure I'm doing something simple wrong 

[DIY vipec display]

i tried CANBUS tonight, no good, no matter how hard I try the vipec will not use any other channels other than 360 or 1000. ive tried storing, reloading, restarting the car, save, closing etc etc

its stuck on Id of 1000 and nothing works. check out the vipec run time values screen below, is something internally cooked or are these red cos theres no active CANBUS stream? my ardruino assumes Channel ID 0 but vipec wont let me choose this channel Id, even putting 0 then hitting apply or save it accepts it, but if i go back its back to 1000 again

 

 

[DIY vipec display]

Looking at the limit flags defintion (frame 13) in the CAN packets, I was wondering if there is a way to generate a limit packet on demand? I want to use the in-built IC spray button on the evo 8/9 to trigger a Limit Flags defintion packet via CAN so that my CAN display when it see's this special limit value it changes the display mode.

Just limits the amount of buttons I need on the CAN display and integrates the design into the existing car's buttons.

Does this make sense? is there some way i can dummy up an AUX or Virtual AUX to watch the IC spray manual button on the evo and trigger some sort of CAN packet or CAN limit flags packet? my CAN coder can then watch the CAN stream for this special value or packet and change the display mode

[EVO 8 V44 plugin - no knock or speed input?]

thanks will try tonight

[EVO 8 V44 plugin - no knock or speed input?]

Thanks , should I change both the TPS % and RPM lockout at the same time? What's a reasoable setting for RPM lockout?  Perhaps I'll try 2200rpm for RPM Lockout would this be enough to test it?

[EVO 8 V44 plugin - no knock or speed input?]

ok here is a PC log of the idle issue, it was the same with the old vipec so its not a new issue i just never got around to fixing it

note this is with a stone cold evo, stroker kit, mega cams and large injectors so i dont expect perfect idle but this its nuts, over 2000rpm IDLE, see logs

 

http://www.paulr33.com/evo/recent.zip

 

 

idle

 

 

this is with the car in the garage, stone cold. at first it seems ok around 1300rpm, then if it tap the throttle it cranks right up, if i continue to repeat it cranks up the idle RPM even more and likewise when i move the steering wheel, even more RPM until it peaks around 2300rpm. should see it when i try and reverse it down the drive, its hopeless, over 2500rpm idle in some cases and it rev's its ass off

[EVO 8 V44 plugin - no knock or speed input?]

ive uploaded current tune and "on board ecu log" in case anyone feels like troubleshooting my mega 2800rpm IDLE =)

its only on cold start so i guess its one of the correction values etc, ill spend some time on it shortly

i did do a PC record log but for some reason the vipec didnt connect properly so only got onboard logging

i can replicate it but will have to wait until tomorrow when its stone cold again

 

http://www.paulr33.com/evo/current.zip

 

thanks for everyones help

 

v helpful people on here