meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:controller:diagnostics [2024/02/22 05:53]
vasilisk
en:controller:diagnostics [2024/03/14 04:33] (current)
vasilisk [Writing a log to file]
Line 14: Line 14:
  
 Check if the brake is pressed, the main screen will show the **P** icon, check the range of the analog brake sensor if connected.\\ Check if the brake is pressed, the main screen will show the **P** icon, check the range of the analog brake sensor if connected.\\
-Check if neutral is turned on, the main screen will show **N**. \\+Check if neutral is turned on, the main screen will show **N**.\\
 Check the **Controller flag** > **Status flags** > **Overcurrent**, if it is **On** then try to turn the motor by hand, if it resists - disconnect the controller phases from the motor and twist by hand again if the torsion resistance remains then the motor is faulty, if the motor starts to rotate freely — contact for technical support, the controller may be faulty. Check the **Controller flag** > **Status flags** > **Overcurrent**, if it is **On** then try to turn the motor by hand, if it resists - disconnect the controller phases from the motor and twist by hand again if the torsion resistance remains then the motor is faulty, if the motor starts to rotate freely — contact for technical support, the controller may be faulty.
 ===== Regenerative braking is missing / shuts-off ===== ===== Regenerative braking is missing / shuts-off =====
Line 25: Line 25:
 Increase detection current (for example, twice), you can also push the motor with your hand at the start (be careful).\\ Increase detection current (for example, twice), you can also push the motor with your hand at the start (be careful).\\
 Check the performance of the hall sensors in the **Controller** > **Debug information** > **Hall input** section, this parameter has three digits, each shows the signal level, if you rotate the motor slowly by hand, then all three digits should change. If none of them changes, check if the hall connector is connected or the ground may be broken. If one of the numbers does not change, there is no contact or the sensor wire is broken. To check the contacts in the controller, you need to disconnect the hall connector and measure the voltage at the controller connector. There should be about 4V on the signal lines of the halls, 5V on the power supply and about 3V on the temperature sensor line. Check the performance of the hall sensors in the **Controller** > **Debug information** > **Hall input** section, this parameter has three digits, each shows the signal level, if you rotate the motor slowly by hand, then all three digits should change. If none of them changes, check if the hall connector is connected or the ground may be broken. If one of the numbers does not change, there is no contact or the sensor wire is broken. To check the contacts in the controller, you need to disconnect the hall connector and measure the voltage at the controller connector. There should be about 4V on the signal lines of the halls, 5V on the power supply and about 3V on the temperature sensor line.
- 
 ===== Display turns off when accelerating ===== ===== Display turns off when accelerating =====
  
 Try decrease battery current in **Сontrol modes** in controller menu or check you battery BMS settings for maximum allowable current.\\ Try decrease battery current in **Сontrol modes** in controller menu or check you battery BMS settings for maximum allowable current.\\
-Usually this happens when BMS turns off everything in case of overload. +Usually this happens when BMS turns off everything in case of overload.
  
 +===== Battery Wh usage does not reset at full charge =====
  
-===== Battery Wh usage does not reset at full charge ===== +The display calculates the remaining battery capacity based on Wh consumption from the controller(s). If your statistics do not reset at full battery charge, check that in the Controller-**[[:en:controller:setup#battery|Battery]]** menu, your **Full charge** delta is sufficient to trigger a reset at full charge, or ensure that your battery min-max voltage is configured correctly.\\
-The display calculates the remaining battery capacity based on Wh consumption from the controller(s). If your statistics do not reset at full battery charge, check that in the Controller-**[[en:controller:setup#battery|Battery]]** menu, your **Full charge** delta is sufficient to trigger a reset at full charge, or ensure that your battery min-max voltage is configured correctly.\\+
 Reset calculated as: **Supply max** - **Full charge** = reset threshold.\\ Reset calculated as: **Supply max** - **Full charge** = reset threshold.\\
-It happens only when the controller turns on, and if the voltage is above the threshold, consumption will be reset.+It happens only when the controller turns on, and if the voltage is above the threshold, consumption will be reset.\\
  
 +===== Writing a log to file =====
 +In the **Controller **  > **Logger**  menu section, you can enable and configure the data logging during the operation of the Controller. Full documentation about logger [[en:controller:setup#logger|here]].\\
 +For this you will need microSD card or bluetooth dongle with app.
 +  - Navigate to **Controller** > **Logger** and select **Start logging = On**.
 +  - Logging will start automatically when the bike is in motion by default.
 +  - Reproduce the problem or perform a full-power acceleration to reach the top speed.
 +  - Stop the vehicle.
 +  - Go to **Controller** > **Logger** and select **Stop logging = On**.
 +  - (Optionally) If the problem did not occur, repeat the process to write additional logs. Return to step 2.
 +  - Copy the files from the microSD card or from the phone and send all NClogX.csv files to support.
 +\\
 +Note: Log rates faster than 10ms (e.g., 1ms and less) may result in gaps in logger data due to the limits of the CAN bus speed. You can select 'Mode = Max rate' to attempt recording at the maximum possible data rate.