devojet wrote:Hi james, Do you plan to add the CAN code to your Microsquirt transmission code.
Done. Only took just over an hour and seems to work ok with MS2/Extra.
I've not released this new version yet.
James
Does that mean it now relies on can for the RPM/TPS or (i.e. i will need to upgrade to MS2) or you can still share signals, aka your original alpha.
Long term I intend to upgrade to ms2/extra, but my existing ms1 works just fine!
I better tag mr shurvalot for a ms2 processor chip i guess.
eliotmansfield wrote:Does that mean it now relies on can for the RPM/TPS or (i.e. i will need to upgrade to MS2) or you can still share signals, aka your original alpha.
That next release of my trans code lets you choose between local signals and CAN acquired data.
I just set up two MS2extra's on the bench and had a play with the ADC's over the CAN. It worked well. I then tried the GPIO tranmission code with MS2extra but the transmission processor wasn't receiving any info over CAN. I must have a setting wrong somewhere. I then tried the GPIO trans code with the latest B&G code and it worked fine.
This CAN stuff is very interesting. When can I get a copy of the new version of the trans code so I can have a play with it?
devojet wrote:I just set up two MS2extra's on the bench and had a play with the ADC's over the CAN. It worked well. I then tried the GPIO tranmission code with MS2extra but the transmission processor wasn't receiving any info over CAN.
I haven't uploaded the CAN-enabled trans code yet - that's why it didn't work....
(new copy sent by email)
Hi James, it was Lance's trans code I was trying to use with MS2extra that didn't work. It doesn't worry me though as I plan to use MS2extra and your trans code plus I was probably doing something wrong. Just thought I would let you know that it didn't work for me.
I had your new trans code working today on one of my megasquirts and it was talking to my other MS running MS2extra beta 17. It seemed to work fine except for two little things;
1. It doesn't recieve CLT temp over the CAN.
2. The Line Pressure output doesn't make it passed the AND chip on MS2. I think the PWM2 output (see MS2 schmatic) needs to be set low.
I have started building my own trans controller using an MS2 card and Vero Board. see attached photo.
Last edited by devojet on Thu Jan 15, 2009 8:54 pm, edited 2 times in total.
On the EPC, I think you need to make a minor mod to your MS2 card to get that pin out if I'm right. Because both pins going to the AND gate are used.
Run a small jumper wire from each of the AND gate inputs to one of the spare MS2 pins.
e.g. AND gate pin 4 to DIP40 pin 4
AND gate pin 5 to DIP40 pin 5
Pin4 = uS IGN2
Pin5 = us INJ2
These will be inverted with respect to the Microsquirt equivalent pins, let me know and I can change this inversion in the code.
Thanks for the new code and clarification, I forgot the other pin going to the AND gate is being used. I won't have to do those mods with my board as the two outputs are already sent directly to pins on the MS2 card. I only suggested that "Bug" as I thought others might want to try use a V3 pcb as a trans controller. The outputs also won't need inverting in the code as I have allowed for this in my circuits.
I tried out the new alpha trans code today. I installed MS2extra beta 18 on one MS2 and the trans code on the other MS2. The CLT input now works over CAN but TPS no longer works at all CAN or Local.
Also another issue I found earlier but forgot to mention it. When the Trans code is running in local mode (No CAN) with a stim plugged in when I turn the EGO pot the gear selector changes as it should but the CLT gauge also moves. I'm not sure if this is hardware or software issue, but the EGO input should have nothing to do with the CLT input.
Cheers
Daniel.
P.S. do you want me reporting bugs here or would you prefer me to email you privately?
I found that TPS, EGO and CLT behaved normally in local mode. However, if nothing is wired to the new CLT input and it is floating it may inadvertently pickup some voltage from the other signals - perhaps.
How's the physical testing?
I'd have thought a car on jackstands would be useful for some rudimentary testing at least. e.g.
-does gear lever selection display correctly
-does it upshift under low load ok
-do manual gears hold
Even if this is incomplete or basic testing it is still good info on whether the code is vaguely useful at this point.
Just for other people reading this. My plan is to use this code with a Toyota A341E gearbox which is found behind the 1uzfe V8 and others. This gearbox functions simular to a 4L80E except the shift solinoids have a different patern for gear shifts which is not a big deal to change in the code.
James,
I had the CLT input floating so I guess that is all that was. The Physical testing is still a little way off though, I haven't even wired up the MS to the engine yet, not to mention the fuel system, exhaust, cooling system, etc. I'm back at work this week so I only have a couple of hours a night to work on this. I only finished off the vero board circuits last night but it still has a bug I need to work out.
I will continue to do what ever testing I can with this though. Controlling the A341E gearbox has been a back ground project of mine for a few years now. I just never had a reason to do anything about it until I started building my hot rod.
I'm supprised there isn't more people wanting to test this. There always seems to be people on these forums asking about gearbox control. Maybe they are just waiting for the GPIO.
No it's not just you! I have been thinking that as well. But to test the gearbox I will need a cooling system, But I could always wear earmuffs instead of fitting an exhaust. Although the exhaust I have is only a set of flanges bolted to the heads, with no pipes at all!
One question, If I have no exhaust where do I put my WBO2??
I tested out the latest version of the code and finished off my vero board controller. It all seems to be working well now. Next I will have a go at modifying the code to suit the shift patern of my gearbox, then start looking at wiring up the engine and gearbox.
Attached is an updated picture of my controller. When I get a chance I will update the schematic for my controller and post it.
James,
I have your trans code running on the bench, it is pulling all the CAN values from a 2.886 controller fine. One thing I found though:
When I call the och get command ("r\x07\x07\x00\x00\x00\x2c"), I am expecting 44 bytes, but it will actually just keep giving me bytes well beyond 44. I didn't test how far... With all the other Firmwares TunerStudio was throwing an exception if i got more than I was expecting, as it was assumed that what I got is probably not what I was looking for, so it is garbage.
To avoid this I had to force a break on read when I hit the expected byte count, which is simple enough, but means I will be bypassing the check for all firmwares. Any Idea why this code does this?
Also; Is CAN pass through enabled on this code? Should I be able to connect to it through the EFI controller? Currently i can only connect by putting the serial cable on the Unit running the trans code.
I can answer the last question. CAN pass through works if your efi controller is running the extra code. James changed something in the extra code that allowed the CAN pass through to work with Megatune.
26 Chev hotrod with a 1UZFE and MS3x, Flex fuel, GPIO Transmission control and LCDash.
Twin turbo LS3 powered Race boat with MS3pro and GPIO.
MS2 on a 22r in a Hilux (mates car).
MS2extra on a turbo EF Falcon (brothers car).
Toyota Supra 1jz MS2extra, COP.
13B Turbo MS2extra.