redux-framework domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131customized-task-offer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap-hourly-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131| Management number | 212399596 | Release Date | 2026/04/06 | List Price | $16.00 | Model Number | 212399596 | ||
|---|---|---|---|---|---|---|---|---|---|
| Category | |||||||||
Description: - Maximum 9.99A 30V 60W, super power automatically limits current - Automatic control fan speed according to temperature. Capacity test support four-wire test and two - four-wire automatic recognition - Overheating protection reverse polarity protection and multiple protection features. - Suitable for assembling the power adapter - When full speed, the fan rotates very fast, even if low speed, the fan still rotates not very slow.Specification: - Working Power requirements: DC12V - Operating mode: Single-mode constant current (CC) - Discharge current: 0.20-9.99A stepper 0.1A or 0.01A - Discharge current maximum error: 0.7% -0.01A - Maximum capacity test error: 0.5A 2.5%, 2A 1.5%, 5A and above 1.2% - Offline (termination) Voltage Range: 1.0-25.0V stepping 1V or 0.1V - Discharge voltage: 1.00-30.00V - Maximum voltage measurement error: 1% + - 0.02V - Power: 60W . Over the limited power, the board will automatically limit the current. - For example, When you use 60W board, 6V can hold 9.99A, but 20V can only hold 3.00A - Highest battery test statistic: 999.9Ah or 9999Wh, reaches the value stop testing (in value by a first stop condition) - Fan control: intelligent fan control. - Protection: Overheat protection "otP", transient overpower protection "oPP", - Overpressure protection "ouP", reverse polarity protection, power supply voltage abnormal protection.Size Chart:Size: 112x70x57mm/ 4.4x2.75x2.2inch (fan prominent board about 12mm)Package Includes:1 Piece Multifunction Constant Electronic Load ModuleNote:
| Brand Name | Luzhengyang |
|---|---|
| Manufacturer | Luzhengyang |
| Power Source | Battery Powered |
| Included Components | Fuse |
If you notice any omissions or errors in the product information on this page, please use the correction request form below.
Correction Request Form