My Duinomite Mega Canview V4 equivalent Project

I will keep you posted. I will try again using a simple program just using getcandata() and updateVGA. Let us know when you have a second beta available. Thanks.

EDITED: The problem is that I cannot use my existing program with your implementation due to bugs so I can only be able to test/find bugs on the weekend.

 

When I ran the command memory. The program was about 45% use of memory. When you go into edit online or edit mode it uses the remainder of the memory. In my case I was getting the reply "Insufficient memory". However if I reduced the number of lines used in the program then less memory was used when being used to go into edit mode. Hence smaller program uses less memory in edit mode.

 

I have split my CAnview_V4.0_BMS+.BAS program into smaller programs for the purpose of debugging JDH2550's CAN commands. The CAN commands have been converted from Frank's CAN commands to JDH2550's CAN commands. Files are attached. They have not been tested yet. I need my Duinomite Mega to drive to work so I do not want to flash it every five minutes.

 

Your CAN command for receiving works well except for your output problem. I got my passive can basic program Ie. CANPASS.BAS to work and it was faster than ever. I can now remove unnecessary logic that was previously used due to the buffer overflow problem. I cannot get your CAN transmit command to work. Tried different variations. It had a problem with the data array. Obviously you have not got it working yet. Hope to see your beta2.

I used your ECT.BAS program to measure how often the passive PIDs are broadcasted over the CANBUS.

HV Battery temperature - H3CB - 90mS
BMSplus - H555 - 94mS
Brake - H030 - 0 to 1 mS
Current - H03B - 0 to 1 mS
ECT - H52C - 992mS
Gas Tank - H5A4 - 0 to 1 mS
ICE kW - H038 - 0 to 1 mS
ICE Temperature - H039 - 0 to 1 mS
KPH - H0B4 - 6mS
Power - H03A - 0 to 1 mS
ICE RPM - H3C8 - 56mS
Gas pedal position - H244 - 16mS
Intake temperature - H3CF - 118mS

 

Thanks for the progress report. Just wondering, how are you testing your TX command?

I got my CanviewV4.BAS program to work but cannot transmit so I cannot clear my DTC. So now I am driving around with a DTC all the time. However the updating of parameters is now turbo charged.

 

Sorry to hear that you have lost your job. I know how distressfull it is to not have a job to pay off the mortgage, i have been there. Maybe you can ask the US government for a financial bailout (comic relief). I am sure that a software Engineer as talented as yourself will have no trouble finding work. But don't let your current situation affect your mojo. I never thought I would have to advise an American to keep their confidence up. I do not care how long it takes you to get CAN TX working as long as you are confident that it can be done.

I keep my old Norm's Canview V4.0 in my Prius just incase. The latest copy of my CANVIEWV4.0_BMS.BAS in my first post still uses Frank's CAN commands. It will not be updated to your CAN commands until I am confident that they all work well.

Anyhow, good luck with the job hunting.

 

It has just come to notice to me in another thread that the ICE ECU can be spoofed simply by resending the modified CAN message to inhibit the ICE. This should allow EV mode at higher speeds than the normal 45kph limit. At some point in the future I will try this and see whether it actually works. Apparently if you send the message soon after the original the I'CE ECU will ignore the first message. But can the Duinomite Mega be quick enough to do this. I think that there is a small window of opportunity in time after the original is sent that the modified must be sent in order for the first message to be ignored.

 

It would not hurt to spin the ICE now and then for the lubrication of the ICE. However there is a lot of speculation around whether it is necessary or not and nobody has made a good case either way or stated how often or for how much time the ICE must spin. Nobody using the OOG mode has reported any lubrication issues so I guess there is no imminent danger if you do not spin the ICE. However I would spin the ICE now and then just to be sure. I have read that the fuel like E15 that I use has 15% ethanol added to it and it may separate over a long time of not being used causing timing issues or knocking of the ICE. I have heard a lot about car engines that knock or misfire due to using E15 because these engines are not suited for E15 but are only suited to full unleaded fuel. And the fuel not being used after a certain amount of time may become degraded. So to me the fuel issue is a lot bigger than the ICE lubrication issue.
I remember from watching a documentary that in South America they use engines that are timed and modified to use 100% ethanol fuel. So South America is not dependent on crude oil.

 

I have not heard of MG1 over revving before. I can see how once the ICE inhibit spoof is removed and the spoofed H3C8 byte 2 is also removed the ICE will come on at the target rpm which is probably too high as the Hybrid ECU does not know that the ICE was inhibited. It can normally go up to 10000 rpm. Once the ICE inhibit and H348 byte 2 (ICE rpm feedback to HV ECU) spoof is removed the ICE target rpm can be lowered by spoofing H348 byte 2 and then brought up gradually to the original value. This way the initial high torque will not cause MG1 to over rev.

At the moment it is all just theory. I will need to spend more time studying CAN frames of interest i.e. H348, H3C8, H03A and H3CA.