openinverter forum

I prefer the second one, it conveys more information simpler. Somehow I got more lost on the first one.

Actually what I think is best - and I feel this way about most schematics - Is to not unveil the whole schematic at once. Everyone who looks at a finished schematic is overwhelmed. It's okay as a reference, but it's hard to learn from. It's what someone who already understands it would use, but not someone learning.

The schematic should tell a story. Either step by step, or as a video/animation. And, wires should be thick to represent their size.

You start off with Battery - Motor. Everyone understand that.

Then you explain that, for a DC motor that would just make it spin top speed, and for an AC motor, it wouldn't spin at all. So we need to insert a speed controller, or an inverter.

Battery - Inverter - Motor.

And then you say, the inverter can make the motor spin faster or slower, but it doesn't know when to do that, so we have to wire it to an accelerator pedal. So you add that to the circuit.

Then you talk about how all the normal electrical stuff that's in a normal car, all runs on a 12v battery, and in an electric car we keep it the same, we still run it on a 12v battery. So you can check off lights and horn and all that stuff, and show it as a second circuit connected to a 12v battery.

Then you say that on a normal car, the battery is charged by the alternator that is spun by the engine, which is always spinning if the car is on, even if it's not moving. Since we don't have an engine, and our motor only spins when we drive, we probably won't even use an alternator. We use a DC-DC converter to take the 400v down to 12v. And you connect the two circuits.

Etc etc.

It is so much less intimidating to see the circuit evolve, than to just post the final result.

All that stuff needs explaining anyways, so it might as well be explained as the schematic evolves.

Panasonic AEV14012 Contactor

i saw this heading in the Wiki:
"This means they had to use one of theese on + line and another on - side. Together you get 240A rating for system with 800A for a burst of power."

This sentence looks like a Panasonic contactor is required on the +ve side, and a Panasonic contactor is required on the -ve side. So if that is the case, looks like the contactors are in series not parallel. Meaning we only get 120A rating. (Unless I am missing something).

Kind regards,

Johnspark

Thanks all for the comments. I am going to work on cleaning up both of them, and see if I can make them both useful. I do think a large scale conceptual and not wiring version may be helpful for very early explanation, but that version is definitely too cluttered.

I don't have the skills to make this automated and clickable - if someone wants to help with that once it's ready, please let me know. I do think having the whole diagram can be helpful, but I need to do more work to make these actually useful.

No promises on timing, work is again very busy, but I'll try to get to it soon.

There is a sponsored extension for wiki editable diagrams. It uses https://app.diagrams.net/ for the editor. Has support for line jumping and links. Beyond making the diagram interactive, anyone else could contribute without having to install diagram software.

Perhaps Jonannes could check it out and install it. See: https://www.mediawiki.org/wiki/Extension:DrawioEditor

Just installed it but it doesn't work yet: "Fatal exception of type "Error""

UPDATE: works now

johu wrote: ↑Tue Jan 24, 2023 6:54 pm Just installed it but it doesn't work yet: "Fatal exception of type "Error""

UPDATE: works now

It's close. Looks like the save function makes the corresponding SVG file in the wiki filesystem, but does not display it on the page. Then upon trying to edit, it starts with a blank diagram. I'll see if I can find reports of this behavior and report back.

I did see this in the docs at first glance and wondering if we have this extension enabled:

When you intend to use SVG which is recommended, you might want to install Extension:NativeSvgHandler too. Also you need a browser that supports SVG.

Yes I installed NativeSvgHandler as it didn't run at all without it
Will see if I find something useful in the debug log. Could be a permission problem..

Hmm, I created a file with a simple box saying hello: https://openinverter.org/wiki/File:TouranTestsvg.svg
The hello is not there. If I download the file and view it locally, it's fine.
Embedded in the page it just shows some default image: https://openinverter.org/wiki/VW_Touran_Conversion

debug log is not helpful...

MattsAwesomeStuff wrote: ↑Mon Jan 23, 2023 3:55 am Actually what I think is best - and I feel this way about most schematics - Is to not unveil the whole schematic at once. Everyone who looks at a finished schematic is overwhelmed. It's okay as a reference, but it's hard to learn from. It's what someone who already understands it would use, but not someone learning.

The schematic should tell a story. Either step by step, or as a video/animation. And, wires should be thick to represent their size.

This! Time and prioritisation are lost in a complete schematic. The journey to it is the interesting bit.

Now we have the latest MediaWiki version but still no diagrams. Will keep digging...

https://openinverter.org/wiki/Schematic ... sor_boards

This page mixes deprecated information with relevant info for tuning if I am correct?
The old parts are superseded by Brain board Rev 3 and Mini mainboard, right?

There's lots of info in the wiki but it can be hard to find. I've been using Google site search to try to find things.

I'm also a visual person, so blocks of tech text melt my brain and eyes. Adding a snip of where you're typing / reading info in a how to write up helps me a ton.

I haven't found a wiki sitemap yet. Finding things linked through other pages / links can be tough. I'm not sure what the answer is. My first thought is adding organized info with links in a Trello board but I'm not sure that's the most sensible path.