Difference between revisions of "SimuCUBE troubleshooting"
| [checked revision] | [checked revision] |
m (→Over voltage fault) |
(→Over voltage fault) |
||
| Line 15: | Line 15: | ||
Should the resistor measure more than 5 Ohm, and/or the MOSFET measures less than 10 kOhm, then double check your measurement, and if the results persist, then the respective component need to be changed. | Should the resistor measure more than 5 Ohm, and/or the MOSFET measures less than 10 kOhm, then double check your measurement, and if the results persist, then the respective component need to be changed. | ||
| − | [[File:Simucube regen. resistor cirquit measurement.jpg|none|thumb|SimuCUBE regenerative resistor circuit measurement pads.]] | + | [[File:Simucube regen. resistor cirquit measurement.jpg|none|thumb|SimuCUBE 1r004 regenerative resistor circuit measurement pads.]] |
=== SimuCUBE won't go into DFU mode === | === SimuCUBE won't go into DFU mode === | ||
Revision as of 10:09, 16 March 2018
This page lists common pitfalls and solutions regarding SimuCUBE. Please also refer to common firmware-related troubleshooting steps described in SimuCUBE Firmware User Guide.Over voltage fault
Even with features to reduce the risk, there is a chance that the regenerative resistor circuitry get's damaged. To prevent this, use the latest firmware, and double check your FOV (over voltage fault) setting in Granity.
Note: These steps are suitable for SimuCUBE hardware version 1 (1r004) boards. For support for hardware revision 2 (1r005), please contact Granite Devices Support.
To check if the regenerative circuitry is damaged, a multimeter (resistance meter) is needed.
- Measure the resistance from the X2 pad HV+ to RES. The measured resistance should be close to 2.2 Ohm in single resistor SimuCUBE boards, and close to 2.35 Ohm in boards where two resistors are soldered.
- Measure the resistance from the X2 pad RES to GND. The measured resistance should be around 12..15 kOhm, changing (lowering) slowly.
Please note, that some multimeters do not compensate for the test wire resistance, and this might lead to higher value when measuring the resistor.
Should the resistor measure more than 5 Ohm, and/or the MOSFET measures less than 10 kOhm, then double check your measurement, and if the results persist, then the respective component need to be changed.
SimuCUBE won't go into DFU mode
- If device does not appear as DFU mode device when plugged in, check Windows Device Manager if there is any unknown USB devices. If yes, then try unplugging SimuCUBE USB cable and see if that device disappears. If this is the case, then it indicates that device driver is not installed properly. Try installing ST DfuSeDemo software with drivers to solve the issue. DfuSeDemo Installation Directory will contain the required drivers.
- Maybe USB device is not recognized at all? Keep Device Manager open and plug/unplug SimuCUBE while keeping eye on the Device Manager list. If you see list refresh, then it is a sign that device has entered/left the list. If nothing happens, then it might indicate hardware issue as no USB device is recognized at all.
- Download & use USBDeview to see whether STM32 BOOTLOADER device or any device missing driver is listed:
SimuCUBE unexpectedly stuck in DFU mode
It is possible, but very rare, that SimuCUBE gets stuck in DFU mode or switches to DFU mode by itself without user interaction. Please refer to separate support article: SimuCUBE stuck in DFU mode
