>
> On Sun, Apr 18, 2021 at 5:22 PM Jason Arnold <
arnold...@gmail.com> wrote:
>>
>> Welcome back, Charles. I've seen your name in the annals of GEVCU's history books, what was your role back when you were involved?
Thanks. I helped with the software development, although nothing significant. I added the ability to detect/set the throttle type and limits, and did the initial web page gauges, but at least in Michael’s branch it’s been completely revamped to the point that I don’t deserve any credit :)
>> Like you, I do appreciate that Michael and Collin have kept this project alive, such as it is, but have also found myself wondering about its future. I've been following an eerily parallel effort currently being spun up on the OpenInverter community known as the ZombieVCU (
https://openinverter.org/wiki/ZombieVerter_VCU), with a fair bit of interest. It's open-source, proposes can control of a host of setups via CAN, has a Wi-Fi interface, and, maybe most importantly, is under active development - in a lot of ways it feels like the next generation of GEVCU, even though there's no direct link between the two projects (that I know of). I really appreciate the effort that's gone into GEVCU over the years, but given the current pace of development, wonder if it wouldn't be served to hitch this project to a bigger wagon. Zombie VCU started out as SAM3X-based as well and has since been ported to STM32, so (in my naive, not software developer opinion) moving the GEVCU software over is doable. One thing I'd love to see ZombieVCU get into its features is the very trick throttle mapping that GEVCU has. I think it's an ideal marriage, does this idea appeal to anyone else?
>>
>> As an alternative for you particular situation, Charles (assuming you're using an AZD setup), something else to consider is ditching the DMOC entirely and using a gen 3 Prius inverter to run the Siemens 1PV5135. Damien did this in his latest re-conversion of his E39 "Land Yacht" - more here:
https://www.youtube.com/watch?v=2ISZffhCs4I
I’ll take a look at these, thanks. I have too much time/money invested in the siemens, but I am open to other inverters if possible/necessary.
Funny story - since Lars was having problems I though it would be a good idea for me to hook everything up and get back to my last known working state, which was a bench setup using a rectifier as a power source and be able to spin the motor mated to the gearbox (transfer case in my case). It would have helped narrow down his problem and help me get back into this. But with the motor/gearbox installed in the vehicle, I can’t even position the DMOC to be able to connect the cables without lengthening them. Sigh :)
I’m going to go back to plan A, which is use one of two battery packs I have accumulated (neither of which I want to use in this project as a final solution) - a gen 1 volt, and a gen 1 leaf, and get the charging side of things working, since that’s where I left off. I assume I can do this without the DMOC having a motor attached.
> On Apr 18, 2021, at 5:16 PM, Collin Kidder <
col...@kkmfg.com> wrote:
>
> So, for the past few years not a lot has gone on with GEVCU6.
> I'm appreciative that Michael is still doing some things with the
> GEVCU4 based design. In fact, if you stick with your existing hardware
> I'd recommend working with him. The old GEVCU4 code is as good as dead
> to me honestly. His version is far better anyway.
I haven’t been paying a lot of attention - i hadn’t realized you switch to a new branch for the 6 boards! At a high level, what differences are there between your branch for 6.2 and Michael’s that prevent us from going back to one master branch? Or is this something I am going to have to go do diffs to figure out myself?
I don’t recall what board Michael has, but afaik there isn’t anything stopping his working on a 6.x board (but just guessing) but if you made another branch, i’m also guessing bringing them back together would be a pain.
But as you can tell, I am not thrilled about two independent efforts for essentially the same thing, and IMHO this shouldn’t be needed or desired by *anyone*. And if wanting to be on the most recent and available hardware conflicts with the software side of things, it makes my decision even more difficult.
Also, are the hardware differences documented somewhere in laymans terms? I know the connectors changed and you added bluetooth, but there was some issue with it Lars said? Even between the v2 and v4, which have the same connector, some of the pinouts have changed, and something affecting the throttle, although I haven’t looked into it yet - i just know I can’t plug in my v4.2 board and have my throttle work like it does on the v2. I think Michael's branch has the pinouts documented through 4.2 and showed no differences for the throttle pins.
I hope my dilemma is clear - I am faced with having to go with unsupported hardware with different connectors/wiring harness that if fails my truck is dead, and who knows what it would take to repair/replace, or buy the latest unsupported hardware with slightly better likelihood of getting a it repaired/replaced, but can at least buy a spare, and it sounds like use your branch, and lose all the wonderful contributions Michael brings.
Hey Michael, any plans to upgrade your hardware to v6+? :D
> Now. more recently, since Jack's passing, we've been looking to see
> what we've got for items we produce and what we want to do with them.
> Good news on two fronts. 1: EVTV is not planning to go anywhere. It
> has new ownership (Jack's daughter) and I'm not aware of any plans to
> sunset the business or anything. We're pushing for the long haul 2: In
> taking stock of what we've got, it has been decided to see what we can
> do with GEVCU6 and perhaps create a new, more versatile design.
This is good news. Is there anyone else helping with the hardware design, or just you?
> But, the forums were
> essentially dead anyway. The only reason I'd go there is to go look up
> some old posts or download some old files when someone needed them.
My only comment on this is that I also believe everything needed should be on gtihub, and I absolutely *hate* Jack’s decision to take his documentation in house and not share it. Basically what that did was make his worse, and ours non-existant.
> One thing that hasn't changed is that I'm still here. I'm quite busy
> these days so I don't always get to providing support for everyone but
> I try. And, I am still building electric cars so I do still work on
> GEVCU sometimes if only for my own uses.
Good to hear. Roughly how many GEVCUs are out there in the wild? I am interested in knowing for both v4 and v6. Yes, it matters (to me) and shouldn’t be a secret, right?
> TL;DR - If you stick with your existing hardware go with Michael's
> code, it was much improved. GEVCU4 and below are basically deprecated
> according to me. Otherwise, maybe watch to see what happens in the
> next 1-2 months - there could be some good news.
I’ll try and be patient, and I have lots of non EV related work to do on my project, but I am in-between contracts and would like to take advantage of the time off. My horizon is likely well more than 2 months, and I can use what I have to finish getting my charger(s) to work so I guess there is nothing stopping me. But at some point I need to start making proper wiring harnesses and make a commitment to an approach.