I assumed there will be a momentary-contact switch near the charge inlet, to do user-input things such as:
* discontinue charging
* turn on the charge port light (to aid in guiding the nozzle to the port)
* or whatever . . .


Personally I have this on the dash, and the only thing it does is ...

I'd wire the ignition key via a diode to the wakeup line to allow the user to wake up the board. If you just want the key-on events then I suppose it's the good old series resistor again...

If course if there's any module on the system that's wired to both ignition and wakeup it can make the wakeup ...

If you make sure the STM32 can put everything on the board into shutdown/standby and that the regulator setup is efficient at currents in the range of 1mA, then I don't think it's a problem if the STM32 is always powered when plugged in. Managing the sleep states and wakeups of course takes some ...

Bashersday is any day someone thinks ESP32 is a good alternative to documentation!

I declare it done now, for my part. I think it's pretty good:

https://github.com/davefiddes/openinver ... ool/pull/1

Maybe this is correct?


Listing TX mappings
SDO 0x3100.0: can_id=0x101
SDO 0x3100.1: dataposlen=0x80007d3
SDO 0x3100.2: gainofs=0x3e8
-> Decoded mapping: tx 0 2 can_id=0x101 param='temp1'(id=2003) pos=0 len=8 gain=1.0 offset=0
SDO 0x3100.3: dataposlen=0x82007d5
SDO 0x3100.4: gainofs=0x3e8 ...

I don't quite get the protocol used to list the mappings. Somehow multiple mappings appear or disappear on the listing when I add or delete one. The index/subindex thing where sometimes they're used as a pair that can be translated to something, sometimes index is a command and sometimes subindex ...

It sure is fairly approachable to me at least. Just another Python tool!

CAN map listing and manipulation works now:

https://github.com/celeron55/openinverter-can-tool/tree/canmap

I'll submit a PR when I finish tweaking this.


$ oic -n 22 can list
CAN mappings:
(empty)
$ oic -n 22 can add tx ...

b) use cansend


Yeah that's what I was probably going to get to next. I can implement this now in OIC now that I can cross check between your explanation and the ESP32 source code.

As long as OIC becomes fully featured, I have no need to mess with the firmware build and no need to complain ...

You can erase the last flash page, it contains the saved parameters. Then you edit param_prj.h (with vi !) and change the default values to what you need them to be. Then recompile. Option one achieved :)


How can I set the CAN mappings?

EDIT: I suppose I can just add a bunch of

canMap ...

I would prefer it if the configuration and integration parameters were built into the firmware binary and were unmodifiable at runtime. In my world view, source code is configuration.

The second best option is OIC.

An ESP32 wifi web interface is one of the worst possible options imaginable to me ...

I tried it, it works a bit but absolutely sucks. Can mappings don't work at all and the dashboard is blank, and everything is unresponsive and completely confidence destroying. I refuse to use it.

It all worked out, now to the point that I need to access the CAN mappings on the board, by using OIC. What's the status on that?

EDIT: I started working on it now

johu wrote: ↑Fri Feb 16, 2024 4:33 pm Yes and please pester Dave to implement the CAN mapping

Yeah I think my next problem will be exactly that. Clara is quite useless without CAN mapping.

Here's the CAN log for "oic -n 22 serialno" , for future reference. I did censor my serial number, but trust me, it was pretty boring:


(000.000000) can0 616 [8] 40 00 50 02 00 00 00 00
(000.001659) can0 596 [8] 43 00 50 02 XX XX XX XX
(000.001862) can0 616 [8] 40 00 50 01 00 00 00 00
(000 ...

Ah the frigging hex files already included the address offset. OpenOCD was trying to flash above 0x10000000 and that's no good. So, this is much better:


source [find interface/stlink.cfg]
source [find target/stm32f1x.cfg]
init
targets
reset halt
flash write_image erase stm32_canloader.hex
flash ...

To avoid off-topic in the OIC thread, I'll continue here:

Wait what? I thought I pulled, compiled and flashed the latest clara!

This is supposed to be 0cb9745a3bea0e8171c03f190f38181dfb1a5f1c, and I built it on 9th February, just a week ago. The hex file I used has that date on it.

My OpenOCD ...

Wait what? I thought I pulled, compiled and flashed the latest clara!

This is supposed to be 0cb9745a3bea0e8171c03f190f38181dfb1a5f1c, and I built it on 9th February, just a week ago. The hex file I used has that date on it.

I'll go continue in the clara thread as this is off-topic here. https ...

I posted about my problems in the OIC thread. The problem could be in ccs32clara too, I don't really have a clue: viewtopic.php?p=67380#p67380

I'm trying to use this to communicate
- with my focci board (https://github.com/uhi22/foccci)
- running the ccs32clara firmware (https://github.com/uhi22/ccs32clara)
- using a Lawicel CANUSB adapter (https://www.canusb.com/products/canusb/)
- on Fedora Linux 38

This is not going exactly swimmingly ...

Right now the console is used for excessive logging. With that turned off it's a 1-liner to have the console on that pin. But then what are you going to connect to it that you couldn't also connect to CAN?


It is true that if the CAN configuration interface is easy to set up in various ...

Definitely should mention all these options in the ccs32clara user manual:
- ESP32 web interface (currently mentioned as the only option)
- https://github.com/davefiddes/openinverter-can-tool
- Porting the ESP32 web interface CAN code to any Arduino based system (making this even more portable ...

Is the CAN protocol used to configure and monitor ccs32clara documented anywhere?

I really despise esp32s and wifi and have had so many bad experiences with them (every time I try to use them I get more and more traumatized and days and days are erased from my expected lifespan) that I want to do ...

Does the heatsink temperature spike happen always at the same speed?

I don't think you necessarily have to lock the output gears. As long as the PSD is locked, just make sure to ramp the torque slowly from standstill to let the oil pump engage the clutches without too much heat from slippage. Some kind of special software limit would be a good idea.

Or, of course ...