[mmdepace]

Looking forward to having ability to change configs without using laptop. Currently turning on & off Key_Off_Cell_Balance in the morning and afternoon due to battery getting quite out of balance on morning commute, but do not want to be pulling superwarmed cabin air across it in the afternoon.

 

[mmdepace]

Should we all stick with the same size / model display, or is it relatively easy to compile for different sizes when using in conjunction with the LiBCM firmware package?

 

[mmdepace]

My Nextion has arrived. Excited to get it going, but not going to happen for a couple weeks. Thank you for your work on this Natalya.

Would it be an accurate assessment that I could pull your code in to the latest beta firmware by making sure these are included:
LiDisplay.cpp
LiDisplay.h

With changes made to:
LiBCM.h
#include "LiDisplay.h"

Config.h
// #define LCD_4X20_CONNECTED //Comment to disable all 4x20 LCD commands
#define LIDISPLAY_CONNECTED //Comment to disable all LiDisplay commands
#define LIDISPLAY_SPLASH_PAGE_MS 2000

Or, have I not looked deep enough in to all the routines in the MVP firmware, where there may be additional calls to your code. If it goes much beyond this, I'll probably just use your firmware as is and update when available.

Thanks

 

[mmdepace]

I forgot that LiDisplay has its own dedicated output connector on LiBCM, next to the USB connector on the board. Natalya, could you post a link to the cable you purchased? Thanks.

Edit: I suspect it may be a JST04R-JWPF-VSLE

 

[mmdepace]

I'm alive (on a desk). "K" model version.

 

[mmdepace]

Thanks Natalya, I appreciate it. May install this week, but if not, will wait until the next version comes out. When HMI booted on the desk with no connection to the pack, the "screen" button in the bottom left corner did not toggle screens. Possibly need to connect to LiBCM first.

Noticed the IMA display is on the right had side of the screen, but have seen pictures with it on the left. Maybe I do not have the most recent HMI version. Downloaded some time ago.

 

[mmdepace]

I was compiling the old .HMI file and uploading using UART. Ended up opening a blank project, clicking upload, then picking the new .tft file. This happened moments ago by coincidence. Exciting.

Hope I picked the right connector for the LiBCM side.

 

[mmdepace]

Used small, appropriately sized 3M velcro strips / squares on the three edges. Should provide the ability to adjust as desired. My connector was wrong. Lead spacing, silly mistake. Knew it was 2.54 but evidently ordered with lack of attention. Used some breadboard jumpers, soldering, and the tiny diameter glue filled heat shrink to pull it all together.
Cool, fresh upgrade as we approach the 1 year mark of LiBCM. Much appreciated.

 

[mmdepace]

I think the big one will be changing the config.c items on the screen.
Once some of the wishlist configs start making their way in to the firmware, there will probably be more to play with.
Would love to see something like: disable background regen above SOC 35 (as an example)

 

[mmdepace]

Noticed last night that the merge with 0.8.5 LiBCM firmware was posted last week.

GitHub - Lady-Natalya/Honda_Insight_LiBCM-1 at lidisplay

Replacement BCM for G1 Honda Insight Lithium Conversion - GitHub - Lady-Natalya/Honda_Insight_LiBCM-1 at lidisplay

github.com

Happy to report I was and running smoothly for today's commute.

 

[mmdepace]

Will file an update this week. Happy to test. Thanks for continuing the development.

 

[mmdepace]

New LiDisplay has worked fine. No abnormalities compared to the old firmware.
I do need to report that with old and new I do not receive data during grid charging.
Detail - have seen gridcharging data twice. Not sure what I did differently when data displayed. I grid charge 5 days/week.

 

[mmdepace]

I have uploaded the new .tft. Will be using it with the 0.8.5 LiBCM / LiDisplay firmware for now unless there is a new recommended LiBCM firmware.

 

[mmdepace]

I did see that. Will stand by for the next firmware. I was able to view the new grid charger screen. Very cool. They were all red as you mentioned. Previously I had only gotten to the grid charge screen twice over many nights of grid charge. This time I think I plugged in the grid charger before the contactor opened after key-off.

After viewing the new screen, I toggled gridcharger power OFF-Wait-ON and it did not call the gridcharge screen. Went to the "Driving" screen with no data. Will keep tabs on which screen pops up during grid charge in the coming days.

 

[mmdepace]

Two days of grid charge update - Both days, the driving screen opens when I plug in. (Not GC screen).

My routine is: park, jump out with extension cord reel in hand. Set reel on the ground at front bumper, walk 25 feet, plug in to outlet, walk back to car, plug in to grid charger power cable in front bumper. It all happens pretty quickly, but not before the contractor turns off.

I'm sure they aren't related, but these are two config settings I use that may be different from others.

#define KEYOFF_DISABLE_THERMAL_MANAGEMENT_BELOW_SoC 100 //set to 100 to disable fans entirely when keyOFF (unless grid charger plugged in)

#define ONLY_BALANCE_CELLS_WHEN_GRID_CHARGER_PLUGGED_IN //uncomment to disable keyOFF cell balancing (unless the grid charger is plugged in)

 

[mmdepace]

I just compiled and sent the .hex to my phone for upload tomorrow. Will report tomorrow night.

 

[mmdepace]

Plugged in for GC, driving screen displayed. Should I test whether GC screen displays if plug in GC before contactor opens? It may have been a coincidence.

 

[mmdepace]

LiBCM Firmware: GitHub - Lady-Natalya/Honda_Insight_LiBCM-1 at lidisplay
.tft for NX4832K035_011: GitHub - Lady-Natalya/LiDisplay: LiDisplay for LiBCM

I'll re-upload LIBCM firmware tomorrow, just to be sure I didn't pick the wrong one, and retest.

 

[mmdepace]

Repeatable. Plug in GC w/ contactor open causes driving screen. Plug in GC w/ contactor closed after key turned off receive P1648 screen (A) followed by working Grid charge screen (B).

 

[mmdepace]

Thibble, do your SOC bars update while driving, or do they only update after key-off / key-on. I may have brought this one upon myself by pretending I can edit code, so I have hesitated to post about it.