Your comments

Salut Lionel,

Looks good, this is the last BMS version Vectrix has offered and should be fully compatible with the CAN requirements. 


In terms of the firmware versions my question was not precise enough, what I've meant the complete list of all hex files you have available to use (for example if you have the actual MCR2042-1.hex which is shown on your screenshot). 

The defective fuse is not related to your problem, they are simply protecting the Murata supercapacitors and sometimes they fail indeed. Since this exact type is not in production anymore, we tend to replace them with equivalent SMD fuses.

Hi, 

   There might be multible issues based on your description. The first detail that stands out is the firmware on the motor controller (MC). The FRA firmwares are written by Framuga to support his BMS in terms of the communication between the various components - in other words he has written dedicated versions to allow the charger, the motor controller and the ICM to work seamlessly with his hardware.

Accordingly you may need to replace the firmware on the MC to match your stock BMS. Worth noting the MC FW change requires particular attention since any disruption during the process may erase the controller and recovery requires special tools and knowledge (I am able to restore it). The best practice is to completely disconnect the charger and the BMS from the CAN bus for this step. 

If you could share a picture of your BMS board(s) and the list of FW versions you have currently.

"For now I want to konw if is possibile to calibrate the reading show in display?" As mentioned you will not be able to fix this with your current setup in my view. The reason is the ICM simply interprets the values sent by the MC on the CAN. It is not an analog value you can adjust.

Got it. First of all this setup is far from being optimal since the functional entities in the Vectrix (namely the MC, BC, BM/BMS, ICM and the display) heavily rely on the proper CAN communication.

In your case the BMS is not compatible and the original BC is not present (I guess). As a result the CAN communication falls back to a mode designed for a BC failure scenario with the MC trying to spoof the missing values.

Long story short you would not be able to fix this with your current setup in my view. I also doubt if an MC FW upgrade would fix this - in fact it could make things worse since the Li MC firmware would expect CAN messages from the BMS.

In addition if you could share the BC FW version as well.

It is a bit tricky when you change from NiMH to Li. First question - do you refer to the voltages during charging or while riding the bike (and using diag mode) ?

Hi, I think the file is way too big for using email. Please try this link instead : https://drive.google.com/file/d/1L3fkze-MbzSaros77GScYjXlqWo9RYi5/view?usp=sharing (available until Sunday).

Hi,

I have the service manual, it is a 23 MB zip file. The DB9 diagnostic socket is in the glove box, you'd need a proper CAN-USB adapter as well to read/write the data.

Does not seem to be tragic.

Hi Lionel,

  Right, it looks like we have the same page of the diagram. I also remember to replace those MOSFETs (IXFK or IX2P) in one case however I forgot what has been the outcome - if they failed again or not. I will be back in Antibes the second half of next week where I can take a look at the details on an actual charger. In the meantime you could share the picture(s) indeed.

Cheers, Zsolt