Skip to content

9. Errors

9.1. Errors while Scanning

Errors that can be encountered while scanning data during live monitor are listed below:-

9.1.1. Comm Settings Error

This error is associated with selecting the wrong communication settings. In such case, an alert will be displayed to the user and he will be prompted to check the communication settings and try again.

Note the following in relation to Comm Settings Error:-

  • The application will try to communicate with the BMS over the user specified settings for a time period of ~37 seconds after which a Comm Settings error will be thrown if there is no response from the BMS.
  • Scanning will stop and can bus will be shutdown.

9.1.2. CAN Error

This error is associated with something wrong in the physical CAN connection to the BMS. In such case, an alert will be displayed to the user and he will be prompted to check the CAN connection and try again.

Note the following in relation to Comm Settings Error:-

  • The application will try to communicate with the BMS over the user specified settings for a time period of ~10 seconds after which a CAN error will be thrown if communication fails to be established to the BMS.
  • Scanning will stop and can bus will be shutdown.

9.2. Errors while Configuring

Errors that can be encountered while doing various tasks on the configuration page are listed below:-

9.2.1. Operation Skipped Error

This error can be thrown due to two reasons:-

9.2.1.1. BMS too busy

This error is thrown when the user clicks "Read BMS" or "Write BMS" but a stable channel to the BMS through the canbus cannot be established.

Note the following in relation to BMS too busy Error:-

  • The application will try to communicate with the BMS over the user specified settings for a time period of ~5 seconds after which a BMS too busy error will be thrown if a stable channel to the BMS through the canbus cannot be established.
  • The read or write operation will terminate and can bus will be shutdown.
  • This error happens due to BMS too heavy or BMS too busy.

9.2.1.2. CAN Error

This error is thrown when the user clicks "Read BMS" or "Write BMS" but a stable channel to the BMS through the canbus cannot be established.

Note the following in relation to BMS too busy Error:-

  • The application will try to communicate with the BMS over the user specified settings for a time period of ~5 seconds after which a BMS too busy error will be thrown if a there is something wrong with the physical CAN connection to the BMS.
  • The read or write operation will terminate and can bus will be shutdown.
  • This error happens due to physical connection error to the BMS.

9.2.2. Wrong Input for Parameters

This error is associated with filling in wrong input value in the parameter text field and then clicking the "Write BMS" button.

Note the following in relation to Wrong Input Error:-

  • The application will validate all entries when user clicks "Write BMS" button. If a wrong input value in detected, this error is thrown.
  • Writing operation will not happen at all when this error is thrown.
  • Examples of wrong inputs include :-
    - putting alphabet or special character in numerical input parameter

9.2.2. Wrong file chosen while doing "Read from File"

This error is associated with choosing the wrong file to read the settings from.

Note the following in relation to File can't be read error:-

  • The application will try to read the selected file when user clicks "Read from File".
  • Read file operation will terminate and a toast message will be displayed to user.
  • Examples of wrong files include :-
    - file not a .txt file - file not in correct format as saved from the "Save to file" operation