Open Inverter Data Logger CANLITE

[Boxster EV]

Just noticed this in Johu’s shop.

https://openinverter.org/shop/index.php ... duct_id=78

Seems like a brilliant solution but just checking I haven’t misunderstood the functionality. Can I just connect it to my Tesla LDU CAN BUS (open inverter logic board) and then stream the data via wifi to my phone’s browser?

[johu]

Yes that the plan

The logging feature isn't implemented, but all necessary hardware fitted & working.

[Boxster EV]

Yes that the plan

The logging feature isn't implemented, but all necessary hardware fitted & working.

Thank you. But I can use it to change parameters and see spot values?

[johu]

Yes works exactly like the onboard wifi

[Boxster EV]

Placing an order now!

[Boxster EV]

Thank you for such fast shipment of the board. I have wired it in and can see the board access point. However, I can’t get past the error message. Any suggestions?

[johu]

bus speed must be 500k and firmware must be pretty new, like 5.27 at least, 5.35 is more reliable

[Boxster EV]

Okay thanks. I’m a bit nervous about updating firmware from 5.20r as the car is running PERFECTLY. Will give it a whirl.

[johu]

Are you using throttle over CAN? Then 5.27 or better read through the release info and go straight to 5.35

If traditional throttle read this
viewtopic.php?t=5075
And consider 5.35 as well

[Boxster EV]

Thanks.

No throttle over CAN. Using the original OE potentiometer Porsche pedal.

[Boxster EV]

If traditional throttle read this
viewtopic.php?t=5075
And consider 5.35 as well

Will add a 10k resistor. 26k miles never had a runaway Tesla LDU.

[johu]

No, it's one of those probability things. 999 people never bump into the issue, one will

[Boxster EV]

Me again… I’ve upgraded the sine firmware to 5.35. Wow. I’ll write about that in another thread but it’s a significant improvement.

Still can’t get the data logger to establish a connection. These are my comms settings:

[johu]

Can you check the console available on the TX pin next to the wifi module?

Usually it's something with the physical connection. Are there any .json files on the file system? If so delete them and power cycle

[Boxster EV]

Sorry, are you referring to the file system on the esp8266 attached to the logic board inside the drive unit?

[johu]

No, the ESP32 CAN Board

[Boxster EV]

No, the ESP32 CAN Board

I haven’t uploaded anything to it. Simply just connected 12v and connected the CAN lines.

[Boxster EV]

Drive unit is spitting out CAN map data correctly on the same bus, as messages on other systems are being received correctly. The data logger just doesn’t seem to want to connect to the STM.

I’ve also tried disconnecting everything else from the network (connecting data logger directly to LDU bus) but still no bueno.

[Boxster EV]

Will check the TX console when back from work on Friday. Thanks for your help

[Boxster EV]

I don’t have access to a scope so I can’t really properly test the tx / rx line. I tried connecting a 3.3v external CAN transceiver but also could not get it to work. I did however notice the following:

On the console to the right of the wifi module, the pin marked 5v is outputting 12v.

In the absence of a scope, I don’t really know what else to try.

[johu]

On the console to the right of the wifi module, the pin marked 5v is outputting 12v.

Oh yes, I use the header for programming and feed 5V into this pin. There used to be a diode in between but the voltage drop was too large. So not it is connected straight to the 12V input of the 3.3V reg

[Boxster EV]

To report back: I managed to get this working, sort of. In summary, here's what I did:

1) Upgraded to the latest Inverter firmware
2) Deleted the ESP file system .json file with cURL
3) Connected using a PC (rather than an iPhone). Upon first connection I needed to toggle the node ID from from 1 to 2 and back to 1 again. Didn't need to do this after a power cycle.

This then connected the ESP with the STM as expected and data loaded onto the browser Huebner interface.

What doesn't work:

1) Tried unsuccessfully to connect using various IOS devices. The IP address brings up the OI interface but it says that ESP cant connect with STM
2) When scrolling the parameter list (using a PC), it doesn't load the parameters beyond what's initially loaded on the screen. IE as soon as the curser is used to scroll down, no further parameters load.

[P.S.Mangelsdorf]

So just getting up to speed on this; want to make sure I'm understanding things correctly:
There can be multiple devices on the bus, and just need to assign them different Node IDs, is that correct?
How is the Node ID changed?

[uhi22]

There can be multiple devices on the bus, and just need to assign them different Node IDs, is that correct?

Exactly. The normal use case is, that there is one CANopen "master" (which is the ESP32 web interface) and multiple CANopen "slaves".

How is the Node ID changed?

* In the web interface, you can select the node ID with the up/down arrows in the left column, or type in the intended ID in the white box and press enter. This selects, to which "slave" the web interface shall talk to.
* The Node ID of a certain "slave" is programmed in its software, it is a function call like "canSdo->SetNodeId(....)". It depends on the project, whether this is hardcoded or adjustable via a parameter. For the inverter and foccci/clara, there is the parameter "nodeid" or "NodeId", which is exactly the place where it is possible to adjust the Node ID. After changing this parameter (and safing it to flash), a restart of the control unit may be necessary to apply the setting, and the communication from the web interface will be lost, because nobody will respond on the old node ID anymore. After switching the node ID in the left column of the web interface, the communication shall work again.

[P.S.Mangelsdorf]

For the inverter and foccci/clara, there is the parameter "nodeid" or "NodeId", which is exactly the place where it is possible to adjust the Node ID. After changing this parameter (and safing it to flash)

Great, thank you!