openinverter forum

Thank you sir!

Sooo...
Any alternates to the JTA1020T/cm,118? The 1021 looks to be identical and MCP2003AT-E/SN was listed as an alternate to the JTA1021T/CM,118.
I just talked to a rep at digikey and they weren't sure what the differences between the 1020 and 1021 were.
Otherwise the chip shortage strikes again.

We tried a few different machines to talk to the VCU today in the hope of recovering it and had quite varied results. The best / most consistent thing in terms of connection and getting response from the dashboard was actually an iPhone! I dare say that could account for some of the difficulty using the GUI.
However this particular board remains "dead" after many firmware updates.

Wifi might be a factor. I've also tried it at my home, with the router turned off - but still no luck after further update attempts.

I do think we may have zapped it somehow, which is one of those things, only worrying bit is I'm not sure what caused it.

PS thanks for the video Damien, just watched that and will add a few more notes to the wiki.

Thanks to Johannes we now have fully functioning regen in the vcu. Here is a little teaser:

Jack Bauer wrote: ↑Sun Oct 24, 2021 3:00 pm

I'm a little behind on this but trying to find ways to contribute.

Question for Damien:

I've never even got as far as using the OI interface to run a motor, so, shooting in the dark here... but... the second half of this Part 2 video seems to mostly be you verbally describing the purpose of the parameters. Since lots of these seem VCU specific, I'm guessing they didn't exist in the original OI or OI wiki? I went to the VCU wiki, and they're not listed there.

Is that something that I could contribute? Take more or less what you described verbally and add that to the VCU wiki? Or does that information exist elsewhere and I'd just be duplicating it?

Also, I don't know about others, but on config pages like this, I find it far more user friendly to have the help section somehow inline. I.E. Every parameter has a (?) beside it that you can click on and it brings up an overlay description of what it is and how to use it. Rather than having to have your references elsewhere and correlate the two. Is that simple to do? Can there be like a... I dunno... a help database of some kind where it automatically pulls from, I dunno, the wiki section for that parameter? I don't know other places I've seen implement this, or if being open source and wiki-based makes it something you wouldn't reasonably do.

Hello
I need your help again
I have ordered the shunt and connected it

unfortunately I don't get any correct data displayed in the web interface

for example

udc 16777.18
udc2 -33554.4
udc3 -64225.25
idc -50311.62

If I connect an Arduino CAN shield with this code

https://openinverter.org/wiki/Getting_s ... bus_shield

then I get the correct data displayed

What I have seen is that in the Arduino code
CAN_1000KBPS
and VCU CAN is set to 500KBPS.

Thanks
Peter

Hey Koppi - that looks like what I saw at first, and initialising it with the code in the zombieverter project (ISA::initialize) solved the problem.

Matt: I've recently added a section to the VCU wiki (Initial start-up) which covers some of the critical parameters and is a rough procedure to follow to get started (based on my own experience and memory so may well need correcting).
Is that format helpful?

I agree a list of all the params relevant to this project and what they do would be good to have. To be fair many of them are self explanatory.
Simplest option might be to add comments to each one in the source file (here) https://github.com/damienmaguire/Stm32- ... aram_prj.h and link to that from the wiki.

Thanks for the answer !
Where can I find the code ?
( code in the zombieverter project (ISA::initialize) )

unfortunately I have a problem with the shunt !

It is strangely set to 1000kbps ( should be 500 )

I then tried to set it to 500kbps according to the instructions.

now I cannot receive any data

Do you have any tips on how I can bring the shunt back to life?

Have a nice weekend
Peter

Hey Peter,
I don't have much experience with the shunt sorry. All I can suggest is try setting your Arduino to the 3 possible bitrates that the shunt supports, see if you can regain communication?

https://www.isabellenhuetteusa.com/wp-c ... _V1.02.pdf

The initialization code used for the zombie is here, you can check the message it's sending and replicate that on your arduino, might be the easiest approach.
https://github.com/damienmaguire/Stm32- ... _shunt.cpp


Good luck and do write it up once you have success

Thank you

unfortunately I don't have an Arduino Due
only Nano

Have I understood this correctly?
This is a code that I run via an Arduino which then sets the correct parameters in the Shant ?
I will try it


One more question
If I apply voltage to the Zombie board, should CAN signals arrive at CAN2?

I don't get any CAN signals
what could be the reason and how can I check it ?

Thanks
Peter

So this will be covered in the next video but here's the basics :
under Comms there is now an ISAMode option. By default its in "Normal". If you want to initialise a new shunt, connect it up, power on shunt and vcu, select "Init", hit save parameters to flash. Power cycle vcu and shunt at same time (should be on same 12v feed anyway). Shunt will initialise. Select ISAMode "normal", save to flash again and reboot again. Shunt should now be up and running. I've attached binaries with this implemented but will be available on Github shortly.

thank you for the support !!

only short question

should on CAN2 from the VCU signals come only with 12V applied ?

So that I can control my CAN connection and be sure that the VCU is working properly!
Now there are no CAN signals!

Jack Bauer wrote: ↑Sun Oct 31, 2021 9:07 am Shunt will initialise.

Awesome!

Question: the first releases had the GD chip on it. Is there any difference in the software for them? Or GitHub etc.?

I know you switched to the ST original one, but I can't remember reading the exact reason of it. Did you run into issues?

Hi,

i have a problem with can2. Port does not send any messages. Shunt won't initialize (on oscilloscope I see that the shunt is sending messages). There is no communication with inverter and pdm. Can1 (vehicle can) works ok. I checked the pcb for short circuits etc and everything looks ok.

Where should I look for the problem?

Hi,
Does anybody know where the ICs go that where supplied separately with the zombieverter board?
I just got it in and checked out the schematic from github, however, the resolution is too low to actually be able to read the IC numbers.
mvg
Paul

Hi Dämon
I have the same problem and can't get CAN signals to CAN2.


Hi Paul
I can take photos tomorrow of how I soldered the loose components onto the board.

then we can try to compare

PaulHeystee wrote: ↑Tue Nov 02, 2021 7:08 pm Hi,
Does anybody know where the ICs go that where supplied separately with the zombieverter board?
I just got it in and checked out the schematic from github, however, the resolution is too low to actually be able to read the IC numbers.

Hey Paul, I think you might be looking at the preview image of the schematic? If you go "download" and then open the PDF, you can zoom right in on each section and see everything clearly.

Hope that helps.
https://github.com/damienmaguire/Stm32- ... ematic.pdf

thanks for the video !

It has shown me many interesting things !

Second board arrived! A lot more parts to fit this time, and I have a couple of questions.

The unpopulated spaces on the PCB vs the parts listed on the schematic are:

IC10 = MCP25625T
IC14 = TJA1020
IC19 = NCV7356
IC20 = TJA1055T
IC21, 22 = AD5160
IC27, 28, 29 = FAN3122


The parts supplied are as below, they match apart from:

There is an extra 8 pin SOP which looks like the digi pot, but no place for it.
The remaining IC which should be IC14 is marked SN65185 as far as I can tell.

On the old board, the IC14 is marked "1020", so that seems correct.
The one supplied seems to be an RS-485 transceiver, so that is presumably a replacement for the LIN transceiver? Just checking..

The TJA1020 is a lin transciever that of course can't be obtained due to the chip shortage. There should be an MCP2004 supplied as a replacement. Now however it looks as if I can't even trust RS to put the right parts in my orders. Great. Looks like I gave you an extra digi pot by mistake.

No biggie, it's built, we can use without IC14 for now.

Yeah LIN is not used at the minute in software anyway. I'll send over an mcp2004 to you in a few days.