|
|
| Line 1: |
Line 1: |
| − | '''6-48V Intelligent Automotive grade Power Supply'''<br><br>
| + | The author is called Gertude. Nevada is where my home is. To canoe just what she does every 7 days. The job I've been occupying in numerous drinks . is a average control and order gel. If really want to find out more the look at my website: http://598m.com/home.php?mod=space&uid=64964<br><br>Also visit my blog post ... [http://598m.com/home.php?mod=space&uid=64964 lush 2 By Lovense] |
| − | ==Introduction==
| |
| − | The DCDC-NUC was designed to provide user specified(+12V or +19V) regulated power output from a wide input voltage(6V-48V). Default output setting is set to +12V.<br> | |
| − | It has a range of intelligent functions not found in any traditional USB DC-DC converters.<br>
| |
| − | The unit is able to send ON/OFF ‘pulse signals’ to motherboards based on filtered input voltage levels or Ignition sensing, making it an ideal device for automotive or battery powered installations.<br>
| |
| − | Two main [http://wiki.mini-box.com/index.php?title=DCDC-NUC#Operating_modes'''modes of operation'''] are possible:DUMB and AUTOMOTIVE.<br>
| |
| − | The output voltage setting (12V or 19V) can be changed through the
| |
| − | [http://wiki.mini-box.com/index.php?title=DCDC-NUC#Configuration_switches '''Configuration switches'''] .<br>
| |
| − | The configuration switches can also be used to enter bootloader mode for updating firmware which is detailed in [http://wiki.mini-box.com/index.php?title=DCDC-NUC#Bootloader_Mode '''Bootloader Mode'''] section.<br>
| |
| − | More advanced parameters are detailed in the [http://wiki.mini-box.com/index.php?title=DCDC-NUC#Parameter_List '''Parameter list'''] which can be configured using the [http://wiki.mini-box.com/index.php?title=DCDC-NUC#Configuration_Software'''Configuration Software'''].<br>
| |
| − | | |
| − | ==Product images==
| |
| − | <span style="display:inline-block;padding:5px; width:150px; border:1px solid #eee;margin-right:15px;">[[File:Mini-Box-DCDC-NUC-front.png|150px|front view]]</span><span style="display:inline-block;padding:5px; width:150px; border:1px solid #eee;margin-right:15px;">[[File:Mini-Box-DCDC-NUC-isometric.png|150px|isometric view]]</span><span style="display:inline-block;padding:5px; width:150px; border:1px solid #eee;margin-right:15px;">[[File:Mini-Box-DCDC-NUC-back.png|150px|back view]]</span><span style="display:inline-block;padding:5px; width:150px; border:1px solid #eee;margin-right:15px;">[[File:Mini-Box-DCDC-NUC-angle.png|150px|angle view]]</span><span style="display:inline-block;padding:5px; width:150px; border:1px solid #eee;margin-right:15px;">[[File:Mini-Box-DCDC-NUC-cables.png|150px|cables view]]</span>
| |
| − | <br>
| |
| − | | |
| − | ==Features==
| |
| − | * Input between 6V-48V<br>
| |
| − | * Programmable voltage thresholds<br>
| |
| − | * Selectable output voltage(+12V,+19V)<br>
| |
| − | * Anti Thump output in automotive mode<br>
| |
| − | * Motherboard startup/shutdown control by ON/OFF pulse<br>
| |
| − | * Motherboard shutdown control by USB<br>
| |
| − | * Highly customizable startup/shutdown timers<br>
| |
| − | * Low Power consumption<br>
| |
| − | * HID-USB connection<br>
| |
| − | * Input, Output Voltage and Current measurement<br>
| |
| − | * Temperature measurement<br>
| |
| − | * Motherboard detection using output Power measurements or 5V USB<br>
| |
| − | * Programmable Spread Frequency Modulation for reduced EMI<br>
| |
| − | * [http://wiki.mini-box.com/images/0/07/DCDCNUC_Dimensions.pdf Physical dimensions]<br>
| |
| − | | |
| − | ==Operating modes==
| |
| − | The operating modes can be selected by setting the NUCMODE parameter to 0(DUMB mode) or 1(AUTOMOTIVE mode) using the [http://wiki.mini-box.com/index.php?title=DCDC-NUC#Configuration_Software'''Configuration Software''']. The default setting is AUTOMOTIVE. | |
| − | For basic operation, you would need to connect a power source to the input connector. Polarity is marked on the PCB. See [http://wiki.mini-box.com/index.php?title=DCDC-NUC#Diagram_.26_Schematics Diagram & Schematics] section for further details<br>
| |
| − | Without any further settings if the input conditions are satisfied the unit will generate +12V regulated.<br>
| |
| − | Further parameters can be customized by changing in the [http://wiki.mini-box.com/index.php?title=DCDC-NUC#Parameter_List Parameter List].
| |
| − | For configuration or firmware update USB connection is sufficient.<br>
| |
| − | | |
| − | ===Dumb Mode===
| |
| − | ;Starting the unit
| |
| − | :In this mode starting can be performed by applying an input voltage higher than the value set by the VIN_MIN_STARTUP parameter.In order to filter out unwanted noise the input voltage should be higher than this threshold for the duration set by the VIN_COUNT parameter.<br>
| |
| − | :12V output and Thump output will be activated.<br>
| |
| − | :After output is ON and a timeout elapses set by the MOB_PULSE_TOUT parameter, the motherboard will be pulsed with a 500ms pulse set by the MOB_PULSEWIDTH parameter.
| |
| − | | |
| − | ;Stopping the unit
| |
| − | :During ON state output will be only turned OFF immediately if the filtered input voltage becomes less than the threshold set by the VIN_MIN_RUNNING parameter.<br>
| |
| − | | |
| − | ===Automotive Mode===
| |
| − | ;Starting the unit
| |
| − | :In this mode Starting can be performed by applying input voltage higher than the value set by the VIN_MIN_STARTUP parameter and applying ignition voltage higher than the IGN_HIGH_THRESHOLD parameter.<br>
| |
| − | :The input voltage should be higher than VIN_MIN_STARTUP for the duration set by the VIN_COUNT parameter.<br>
| |
| − | :The Ignition voltage must be higher than IGN_HIGH_THRESHOLD for the duration set by the IGN_COUNT parameter in order to filter out unwanted noise in automotive environment.<br>
| |
| − | :After Ignition is considered ON output will be turned ON after IGN_ON_TO_OUTPUT_ON_TOUT elapses.<br>
| |
| − | :12V output will be activated. Thump output will be activated after timeout elapses set by the THUMP_TOUT parameter.<br>
| |
| − | :After output is ON and a timeout elapses set by the MOB_PULSE_TOUT parameter, the motherboard will be pulsed with a 500ms pulse set by the MOB_PULSEWIDTH parameter.<br>
| |
| − | | |
| − | ;Stopping the unit
| |
| − | :During ON state output will be only turned OFF immediately if the filtered input voltage becomes less than the threshold set by the VIN_MIN_RUNNING parameter.<br>
| |
| − | :If Ignition voltage becomes lower than IGN_LOW_THRESHOLD and Ignition canceling is over (set by the IGN_CANCEL_TOUT parameter) a shutdown sequence will be initiated
| |
| − | :If Ignition is considered OFF the motherboard is pulsed for shutdown after IGN_OFF_TO_MOB_PULSE_OFF_TOUT elapses.
| |
| − | :After the HARD_OFF_TOUT timeout elapses the output will be turned OFF and the unit will enter in a low power state.
| |
| − | | |
| − | ===Motherboard control===
| |
| − | The following options are available to control the motherboard by pulsing the on/off pins on the motherboard.
| |
| − | First the the motherboard on/off pins should be connected to the P4.1,P4.3 pin on the P4 [http://wiki.mini-box.com/index.php?title=DCDC-NUC#Interface_connectors '''Interface_connector'''].<br>
| |
| − | The pulse width is 500ms by default which can be altered by changing MOB_PULSEWIDTH parameter from the [http://wiki.mini-box.com/index.php?title=DCDC-NUC#Parameter_List '''Parameter_List'''].<br>
| |
| − | There are various ways to control the motherboard depending the configuration of the CONFIG1 register from the [http://wiki.mini-box.com/index.php?title=DCDC-NUC#Parameter_List '''Parameter_List'''].<br>
| |
| − | Example:If startup of the motherboard is not needed when input is present, the startup pulse can be disabled by setting CONFIG1.b1 to 0.<br>
| |
| − | The same way the shutdown pulse can be inhibited by setting CONFIG1.b2 to 0.<br>
| |
| − | There are cases when motherboard started(ON) or OFF presence must be detected in order starting/stopping by pulses behavior work properly.<br>
| |
| − | For example the Operating System could be shutdown already from software. In case the unit is is a shutdown sequence not knowing this piece of information would lead by sending the shutdown pulse which would wake up instead the system.<br>
| |
| − | There are two kinds of feedback information to detect motherboard status.<br><br>
| |
| − | The first detection mode is by measuring the consumed output power, knowing that a motherboard when started consumes much more power than when in standby.<br>
| |
| − | In order to enable this feature the following steps should be performed:<br>
| |
| − | 1. Enable this feature, CONFIG1.b3 should be set to 1.<br>
| |
| − | 2. Observe and note the consumption of the connected motherboard when in standby and when is ON.
| |
| − | Our unit measures the output power(POUT) which is displayed in the configuration software.<br>
| |
| − | 3. Set POUT_HIGH_THRESHOLD and POUT_LOW_THRESHOLD parameters from the [http://wiki.mini-box.com/index.php?title=DCDC-NUC#Parameter_List '''Parameter_List'''] accordingly with a good margin. <br>
| |
| − | POUT<POUT_LOW_THRESHOLD motherboard is considered OFF.<br>
| |
| − | POUT>POUT_HIGH_THRESHOLD motherboard is considered ON.<br><br>
| |
| − | The second detection mode is by measuring the +5VUSB signal. Usually motherboards turn OFF the +5VUSB signal when they are OFF.<br>
| |
| − | In order to enable this feature CONFIG1.b5 must be set to 1.<br><br>
| |
| − | If CONFIG1.b4 set, the PSU can shut down the OS by sending a Power Button event on USB.
| |
| − | | |
| − | ==Diagram & Schematics==
| |
| − | <div style="display: inline; float: left;">[[File:Nucconnectors.png|230px|thumb|left|Connectors nomenclature]]</div>
| |
| − | <div style="clear: both;"></div>
| |
| − | | |
| − | ==Connectors==
| |
| − | ===Power Input connectors===
| |
| − | ;P1 Output (4pin mini-FIT JR)
| |
| − | : P1.1, P1.2 - GND
| |
| − | : P1.3, P1.4 - Output voltage
| |
| − | ;P2 Input (4pin mini-FIT JR)
| |
| − | : P1.1 - GND
| |
| − | : P1.2 - Ignition
| |
| − | : P1.3 - Input voltage
| |
| − | : P1.4 - Thump
| |
| − | ;P7 Auxiliary output
| |
| − | : P7.1, P7.2 - GND
| |
| − | : P7.3, P7.4 - Output voltage
| |
| − | | |
| − | ===Interface connectors===
| |
| − | ;P4 Motherboard POWER SW connection, no polarity (JST PH connector, 3pin)
| |
| − | : P4.1: SW1
| |
| − | : P4.2: GND
| |
| − | : P4.3: SW2
| |
| − | ;P6 USB header (not populated)
| |
| − | : P6.1: GND
| |
| − | : P6.2: USB D+
| |
| − | : P6.3: USB D-
| |
| − | : P6.4: +5V
| |
| − | ;P3 programming header, MCU reset (POGO pins)
| |
| − | : P3.1: nMCLR
| |
| − | : P3.2: GND
| |
| − | : P3.3: +5V
| |
| − | : P3.4: PGD
| |
| − | : P3.5: PGC
| |
| − | ;P5 USB connector (micro-USB connector)
| |
| − | | |
| − | ===Configuration switches===
| |
| − | <div>
| |
| − | <div style="display: inline; float: left;">[[File:DIP SW.png|230px|thumb|left|DIP Switch closeup]]</div>
| |
| − | ;Switch 1
| |
| − | : ON : Output voltage is 19V
| |
| − | : OFF: Output voltage is 12V
| |
| − | ;Switch 2
| |
| − | : Reserved
| |
| − | ;Switch 3
| |
| − | : Reserved
| |
| − | ;Switch 4
| |
| − | : Reserved
| |
| − | ;Switch 5
| |
| − | : ON : Switch to Bootloader mode
| |
| − | : OFF: Switch to Firmware mode
| |
| − | | |
| − | Switching between the two available output voltages must be done with the device powered off.
| |
| − | </div>
| |
| − | <div style="clear: both;"></div>
| |
| − | | |
| − | ==NUC and OS Settings==
| |
| − | <br>
| |
| − | *'''NUC related settings'''<br><br>
| |
| − | <div>
| |
| − | <div style="display: inline; float: left;">[[File:BIOS.png|230px|thumb|left|NUC Visual BIOS 2.0 Setting]]</div>
| |
| − | :Setting up the NUC's behavior when power is re-applied:<br>
| |
| − | :- press '''F2''' key during the boot sequence to entering the NUC's BIOS (Visual BIOS 2.0)<br>
| |
| − | :- first click on '''Advanced''' then click on '''Power''' menu button<br>
| |
| − | :- in '''Secondary Power Settings''' section select '''Power On''' option for '''After Power Failure'''<br>
| |
| − | :- the picture shows the right option in a red framework<br>
| |
| − | :- now the power supply should be able to '''START''' the NUC by applying corresponding voltage to its power input<br>
| |
| − | </div>
| |
| − | <div style="clear: both;"></div>
| |
| − | | |
| − | *'''OS related settings'''<br><br>
| |
| − | <div>
| |
| − | <div style="display: inline; float: left;">[[File:Power BTN.png|230px|thumb|left|Windows 7 Power Button Setting]]</div>
| |
| − | :Setting up the Windows 7 '''Power Button''' behavior:<br>
| |
| − | :- from '''Control Panel''' select '''Power Options''' then on the left pane select '''Choose what the power buttons do''' (or do: Control Panel\Hardware and Sound\Power Options\System Settings)<br>
| |
| − | :- then at '''Power and sleep button settings''' select '''Shut down''' option for power button<br>
| |
| − | :- the picture shows the right option in a red framework<br>
| |
| − | :- now the power supply should be able to '''STOP''' the OS (and thus the NUC too) by sending a shut down command via USB<br>
| |
| − | </div>
| |
| − | <div style="clear: both;"></div>
| |
| − | Note: CONFIG1 parameter bit4 field should be set to "1" (see [http://wiki.mini-box.com/index.php?title=DCDC-NUC#Parameter_List Parameter List])
| |
| − | | |
| − | ==Bootloader Mode== | |
| − | It is recommended that you only connect USB power to the device
| |
| − | when making a firmware update via “bootloader mode”.
| |
| − | | |
| − | There are two ways to enter in bootloader mode: 1a) or 1b).<br>
| |
| − | 1a) Slide the SW1 DIP switch button 1 in ON position.<br>
| |
| − | 1b) Press the Switch to bootloader button on the configuration software's user interface.<br>
| |
| − | 2) Start the [http://wiki.mini-box.com/images/a/ae/Bootloader_Software.zip '''HIDBootloader v2.9j.exe'''] software provided to flash the new firmware.<br> | |
| − | 3) Press File->Import Firmware Image<br>
| |
| − | 4) Press Open new Hex [http://wiki.mini-box.com/images/8/8b/DCDC-NUC_FW_ver_1.4_for_loading_with_bootloader.zip '''File''']<br>
| |
| − | 5) Press Program->Erase/Program/Verify Device<br>
| |
| − | 6) If used option 1a) slide the SW1 DIP switch button 1 in OFF position, else skip this step.<br>
| |
| − | 7) Press Program->Reset Device<br>
| |
| − | 8) After the device reconnects on USB with the configuration software the new firmware version will be displayed in the title bar of the software.<br>
| |
| − | | |
| − | ==Blink modes==
| |
| − | '''Deep Sleep'''<br>
| |
| − | 2 fast blinks and a pause, repeated every 5s<br>
| |
| − | Low energy state,used in AUTOMOTIVE mode<br>
| |
| − | | |
| − | '''Initial delay or USB only mode'''<br>
| |
| − | 3 fast blinks and a pause, repeated every 750ms<br>
| |
| − | Signals the Initial Delay, before conditions are met for startup or if the unit is only USB powered<br>
| |
| − | | |
| − | '''Output ON'''<br>
| |
| − | Led is allways ON, signals the Output is ON<br>
| |
| − | | |
| − | '''OffDelay'''<br>
| |
| − | Led is blinking every 2 sec,ON for 1 sec, OFF for 1 sec<br>
| |
| − | In AUTOMOTIVE mode, signals the period between Ignition is OFF and the Motherboard OFF pulse is sent, see IGN_OFF_TO_MOB_PULSE_OFF_TOUT parameter<br>
| |
| − | | |
| − | '''HardwareOff Delay'''<br>
| |
| − | Led is blinking 3 times during a 2 sec period<br>
| |
| − | In AUTOMOTIVE mode, signals the period between Motherboard OFF pulse is sent and Output is turned OFF, see HARD_OFF_TOUT parameter<br>
| |
| − | | |
| − | ==Characteristics==
| |
| − | <div style="display: inline; float: left; padding-right: 10px; border-right: 1px solid #ccc;">
| |
| − | Minimum Input Operating voltage<br>
| |
| − | Maximum input Operating voltage<br>
| |
| − | Sleep mode Current Consumption<br>
| |
| − | Storage and operating temperature<br>
| |
| − | MTBF<br>
| |
| − | Input connectors<br>
| |
| − | Output Connector<br>
| |
| − | </div>
| |
| − | <div style="display: inline; float: left; margin-left: 10px;">
| |
| − | 6V<br>
| |
| − | 48V <br>
| |
| − | 1mA<br>
| |
| − | -40<sup>o</sup>C to +85<sup>o</sup>C (storage), -40<sup>o</sup>C to +65<sup>o</sup>C (operating)<br>
| |
| − | 50K Hrs @ 85<sup>o</sup>C, >= 200K Hrs at 65<sup>o</sup>C (projected)<br>
| |
| − | Mini-Fit JR<br>
| |
| − | Mini-Fit JR
| |
| − | </div>
| |
| − | <div style="clear: both;"></div>
| |
| − | | |
| − | '''Output/Input Rail Output Current (buck/boost converter)'''
| |
| − | <br>
| |
| − | Maximum input current: 5A<br>
| |
| − | Peak Input current: 6A(<30 seconds)<br>
| |
| − | Maximum output current: 5A (input current dependent)<br>
| |
| − | Peak output Current: 6A(<30 seconds @48V input)<br>
| |
| − | | |
| − | NOTE:
| |
| − | When operating at high voltage (input or output) or/or operating at elevated temperatures
| |
| − | de-rating up to 30% might be necessary, forced ventilation required.
| |
| − | For long life operation, please ensure that hottest component on-board is kept below 65C.
| |
| − | | |
| − | Efficiency Measurements (voltages measured at input/output connectors)<br><br>
| |
| − | [[File:Efficiency Vout 12V.png]][[File:Efficiency Vout 19V.png]]
| |
| − | | |
| − | ==Support and warranty==
| |
| − | Standard Hardware Warranty 1Year / US, 2 Year EU.
| |
| − | | |
| − | ==Parameter List==
| |
| − | {| class="wikitable"
| |
| − | ! NAME
| |
| − | ! Description
| |
| − | |-
| |
| − | | NUCMODE[-]
| |
| − | | <pre>
| |
| − | 0-Dumb mode (DUMB)
| |
| − | 1-Automotive mode (AUTOMOTIVE)
| |
| − | </pre>
| |
| − | | |
| − | |-
| |
| − | | INIT_TOUT[ms]
| |
| − | |
| |
| − | When all power supply start-up conditions are met, the PSU will wait this time before continuing with the start-up sequence.<br>
| |
| − | | |
| − | |-
| |
| − | | VIN_MIN_STARTUP[mV]
| |
| − | |
| |
| − | If the input voltage is beyond this threshold and all other start-up conditions are met, the PSU can start.<br>
| |
| − | | |
| − | |-
| |
| − | | VIN_MIN_RUNNING[mV]
| |
| − | |
| |
| − | Instantly turn off the PSU if the input voltage is below this threshold.<br>
| |
| − | | |
| − | |-
| |
| − | | VIN_MAX_SHUTDOWN[mV]
| |
| − | |
| |
| − | If the input voltage is below this threshold and all other start-up conditions are met, the PSU can start.<br>
| |
| − | If this condition is not satisfied during run time, the PSU will turn off instantly.<br>
| |
| − | | |
| − | |-
| |
| − | | VIN_MIN_DEEP_DISCHARGE[mV]
| |
| − | |
| |
| − | If input voltage is below this threshold during IGN_OFF_TO_MOB_PULSE_OFF_TOUT then shutdown sequence will be initiated immediately.<br>
| |
| − | If input voltage is below this threshold during HARDOFF, output will be turned OFF immediately depending on CONFIG1 bits.<br>
| |
| − | | |
| − | |-
| |
| − | | VIN_COUNT[ms]
| |
| − | |
| |
| − | Input voltage filtering<br>
| |
| − | | |
| − | |-
| |
| − | | IGN_COUNT[ms]
| |
| − | |
| |
| − | Ignition voltage filtering<br>
| |
| − | | |
| − | |-
| |
| − | | IGN_HIGH_THRESHOLD[mV]
| |
| − | |
| |
| − | If ignition voltage is beyond this threshold, ignition is considered to be ON.<br>
| |
| − | | |
| − | |-
| |
| − | | IGN_LOW_THRESHOLD[mV]
| |
| − | |
| |
| − | If ignition voltage is below this threshold, ignition is considered to be OFF.<br>
| |
| − | | |
| − | |-
| |
| − | | IGN_ON_TO_OUTPUT_ON_TOUT[s]
| |
| − | |
| |
| − | After ignition is considered ON, the PSU will wait this time before the output is turned ON.<br>
| |
| − | | |
| − | |-
| |
| − | | THUMP_TOUT[s]
| |
| − | |
| |
| − | After the output is turned ON, the PSU will wait this time before the THUMP output gets enabled. This setting is only valid in automotive mode.<br>
| |
| − | | |
| − | |-
| |
| − | | MOB_PULSE_TOUT[ms]
| |
| − | |
| |
| − | After the output is turned ON, the PSU will wait this time before sending the start-up pulse to the motherboard.<br>
| |
| − | | |
| − | |-
| |
| − | | MOB_PULSE_WIDTH[ms]
| |
| − | |
| |
| − | The length of the start-up/shutdown pulse sent to the motherboard.<br>
| |
| − | | |
| − | |-
| |
| − | | IGN_CANCEL_TOUT[s]
| |
| − | |
| |
| − | After the motherboard boots up, the ignition voltage sensing will be disabled for this period.<br>
| |
| − | | |
| − | |-
| |
| − | | IGN_OFF_TO_MOB_PULSE_OFF_TOUT[s]
| |
| − | |
| |
| − | If ignition is considered to be OFF, the PSU will wait this time before sending the shutdown pulse to the motherboard.<br>
| |
| − | This shutdown signal can be sent through the ON/OFF pins or through USB, depending on the configuration of the CONFIG1 parameter.<br>
| |
| − | | |
| − | |-
| |
| − | | HARD_OFF_TOUT[s]
| |
| − | |
| |
| − | After the shutdown pulse is sent to the motherboard, the PSU will wait this time before the output is turned OFF.<br>
| |
| − | This time-out allows the operating system to perform a clean shutdown.<br>
| |
| − | | |
| − | |-
| |
| − | | IOUT_LIMIT[mA]
| |
| − | |
| |
| − | Output current limit setting. Resolution is 1280mA, minimum setting is 560mA.<br>
| |
| − | | |
| − | |-
| |
| − | | PWM_SPREAD_MODULATING_PERIOD[ms]
| |
| − | |
| |
| − | Modulation period parameter of the Random Spread Frequency Modulation module (used for EMI reduction purposes)<br>
| |
| − | | |
| − | |-
| |
| − | | PWM_SPREAD_PERCENT[%]
| |
| − | |
| |
| − | Frequency deviation parameter of the Random Spread Frequency Modulation module (used for EMI reduction purposes)<br>
| |
| − | | |
| − | |-
| |
| − | | PWM_FREQ[kHz]
| |
| − | |
| |
| − | Operating frequency of the Switched Mode Power Supply. Default 300kHz<br>
| |
| − | | |
| − | |-
| |
| − | |CONFIG1[bit7..bit0]
| |
| − | |
| |
| − | Configuration register. Used for enabling/disabling modules. 0 - disabled, 1 - enabled <br>
| |
| − | bit7:reserved<br>
| |
| − | bit6:reserved<br>
| |
| − | bit5:If set, the USB sense is enabled, +5V USB is used to detect the Motherboard alive status<br>
| |
| − | bit4:If set, the PSU can shut down the OS by USB by sending a Power Button event.<br>
| |
| − | bit3:If set, the PSU will detect motherboard alive presence by measuring the output power consumed.Check POUT_... parameters<br>
| |
| − | bit2:If set, shutdown pulse is enabled through the PWRSW connector.<br>
| |
| − | bit1:If set, startup pulse is enabled through the PWRSW connector.<br>
| |
| − | bit0:If set, output power cycle is enabled during HARDOFF period so it can reset the connected sytem.<br>
| |
| − | | |
| − | |-
| |
| − | |CONFIG2[bit7..bit0]
| |
| − | |
| |
| − | Configuration register. Used for enabling disabling modules. 0 - disabled, 1 - enabled<br>
| |
| − | bit7-reserved<br>
| |
| − | bit6-reserved<br>
| |
| − | bit5-reserved<br>
| |
| − | bit4-reserved<br>
| |
| − | bit3-reserved<br>
| |
| − | bit2:reserved<br>
| |
| − | bit1:reserved<br>
| |
| − | bit0:reserved<br>
| |
| − | | |
| − | |-
| |
| − | | POUT_HIGH_THRESHOLD[mW]
| |
| − | |
| |
| − | If output power measured is higher than this threshold the connected motherboard is considered to be ON.<br>
| |
| − | Together with POUT_LOW_THRESHOLD parameter sets a hysteresis for motherboard status.
| |
| − | | |
| − | |-
| |
| − | | POUT_LOW_THRESHOLD[mW]
| |
| − | |
| |
| − | If output power measured is lower than this threshold the connected motherboard is considered to be OFF.<br>
| |
| − | Together with POUT_HIGH_THRESHOLD parameter sets a hysteresis for motherboard status.
| |
| − | | |
| − | |-
| |
| − | | WRITE_COUNT[count]
| |
| − | |
| |
| − | The number of times the internal Flash program memory has been written.<br>
| |
| − | |}
| |
| − | | |
| − | ==Software manual==
| |
| − | ===Windows OS built-in support===
| |
| − | The DCDC-NUC implements one generic USB class (USB HID), therefore most of the
| |
| − | operating systems are recognizing it without any additional driver installation.
| |
| − | ===Configuration Software===
| |
| − | The configuration software provides interface for DCDC-NUC monitoring, logging and setup.
| |
| − | It's recommended to be used by users with deeper understanding of the DCDC-NUC hardware since permits setting voltages, currents and other parameters which can be
| |
| − | dangerous if they are set without precaution.<br />
| |
| − | The configuration software has two main screens (Status and Settings) and a header with the important voltage/current values.<br />
| |
| − | | |
| − | ====The first main screen is the "Status"====
| |
| − | Example of this screen is shown in the next image:<br />
| |
| − | <div style="display: inline; float: left;">
| |
| − | [[File:DCDC-NUC-Status.JPG|x350px|thumb|left|Status screen]]
| |
| − | </div>
| |
| − | | |
| − | The title bar shows the connection status, the firmware version and the mode of the DCDC-NUC. Example: "DCDC-NUC Connected v1.0 Mode: Dumb"
| |
| − | | |
| − | The header of the status screen contains:
| |
| − | :VIn: Input Voltage
| |
| − | :VOut: Output Voltage
| |
| − | :VThump: Thump Voltage
| |
| − | :IIn: Input Current
| |
| − | :IOut: Output Current
| |
| − | :Temp: Temperature
| |
| − | :VIgn: Ignition Voltage
| |
| − | :POut: Output Power
| |
| − | | |
| − | The "Status" screen contains extended information about the current state of the DCDC-NUC like internal state machine, voltages, currents, temperature, different read only state flags.
| |
| − | The user also have the possibility to log the current state into a *.csv file in the "Log" section.
| |
| − | The "Debug" section is for debug/support and can change between different firmware versions.
| |
| − | <div style="clear: both;"></div>
| |
| − | | |
| − | ====The second main screen is the "Settings"====
| |
| − | Example of this screen is shown in the next image:<br />
| |
| − | <div style="display: inline; float: left;">
| |
| − | [[File:DCDC-NUC-Settings.JPG|x350px|thumb|left|Settings screen]]
| |
| − | </div>
| |
| − | | |
| − | | |
| − | This screen contains two main sections: the individual parameter setup for experienced users and the parameter save/load into/from file section.
| |
| − | | |
| − | The main section of the "Settings" screen is the individual parameter settings.<br>
| |
| − | This is recommended to be done only by experienced users. Any parameter of the DCDC-NUC can be set from here.
| |
| − | | |
| − | Changing one parameter is simple:
| |
| − | :- select the desired parameter from the "Parameter" list (simple click to select, double-click to edit). Below the parameter list a helper text is displayed (same from this manual).
| |
| − | :- after double click introduce the new value in the new popup dialog and press OK
| |
| − | :- the introduced value is checked - if something is wrong (out of limit, bad value etc.) error message will be shown
| |
| − | :- the ! sign will blink on the "Sync all parameters to the DCDC-Nuc" button to show edited but not saved/synced variables
| |
| − | :- after You have done with all parameter setting press the "Sync all parameters to the DCDC-Nuc" button to send all values to the DCDC-Nuc. IMPORTANT: without this step the new values will be lost, nothing is sent to the DCDC-NUC!
| |
| − | | |
| − | IMPORTANT: any parameter setting is taken into account by the DCDC-NUC in this cases:
| |
| − | : - after a full restart either with power cut from all sources (usb, vin)
| |
| − | : - hitting the "Restart DCDC-Nuc" button
| |
| − | : - keeping the "Reload parameters on the fly after sync" checked.
| |
| − | Do any parameter change with precaution, check the parameters and wires before applying it!
| |
| − | | |
| − | For users who need to setup more devices with the same DCDC-NUC settings, it is recommended to use the save/load parameters buttons.
| |
| − | The "Parameters: DCDC-Nuc ===> File (settings.ini)" button loads a full configuration from the DCDC-Nuc and saves it to the settings.ini file. You can disconnect
| |
| − | the current DCDC-Nuc from the USB and insert a new one, than press the "Parameters: DCDC-Nuc <=== File (settings.ini)" button to send the last saved configuration into the new DCDC-Nuc.
| |
| − | | |
| − | The "Parameters: DCDC-Nuc ===> CSV File (settings.csv)" button loads all parameters from the connected DCDC-NUC and saves it into a csv file. This type of file can be opened by any spreadsheet editor (OpenOffice, Microsoft Excel etc.) and contains the full set of parameters in human readable form.
| |
| − | | |
| − | The "Switch to bootloader" button is intended to be used for firmware updates. After You press this button the DCDC-NUC will disconnect, it will switch to bootloader mode and firmware can be updated as described [[DCDC-NUC#Bootloader_Mode|here]]
| |
| − | | |
| − | Every save/load/sync operation on the "Settings" screen affects the progress bar and the status bar on the bottom of the screen (labelled with "State:"). In rare cases You
| |
| − | might get error here with "try again" message. This happens in case of one parameter byte get's corrupted or timeout occurs during USB communication and/or DCDC-NUC flashing
| |
| − | operation. Please try again and contact our support team only if the device gives this error 4-5 times in a row.
| |
| − | | |
| − | ===Windows System monitor===
| |
| − | The system monitor is a tray bar software which shows the current state on the tray bar icon and a semi transparent "always on top" capable small window.<br>
| |
| − | The popup window can be moved anywhere on the screen and can be customized. Our current setup has two skins but any combination is possible playing with the
| |
| − | "skin*.mbs" files installed together with this application. The current skin can be selected right clicking on the try icon.
| |
| − | The "skin*.mbs" files are simple text ones editable with any text editor (notepad for example).<br>
| |
| − | Adding a new skin is pretty simple – make a skin1.mbs (use the existing skin0.mbs for starting content) and start playing with the values from the new
| |
| − | file.<br>
| |
| − | The values are self explanatory – skin name, background image files, font descriptions and label/value pair coordinates for all the important DCDC-NUC values.
| |
| − | The size of the popup is defined by the background image – transparent parts can be defined as well (see for example: "bubble1.bmp").
| |
| − | Example screenshots:<br />
| |
| − | <div style="display: inline; float: left;">
| |
| − | [[File:DCDCNUC_sm_tray2.jpg|x150px|thumb|left|System monitor skin1 connected]]
| |
| − | </div>
| |
| − | <div style="display: inline; float: left;">
| |
| − | [[File:DCDCNUC_sm_tray3.jpg|x150px|thumb|left|System monitor skin1 disconnected]]
| |
| − | </div>
| |
| − | <div style="clear: both;"></div>
| |
| − | | |
| − | Right clicking on the tray icon will pop-up a simple menu:
| |
| − | <div style="display: inline; float: left;">
| |
| − | [[File:DCDCNUC_sm_menu.jpg|x150px|thumb|left|System monitor settings]]
| |
| − | </div>
| |
| − | <div style="clear: both;"></div>
| |
| − | From which You can see firmware version and state of the DCDC-Nuc from the properties and set some visual parameters of the application (transparency, skin) from Skin:
| |
| − | <div style="display: inline; float: left;">
| |
| − | [[File:DCDCNUC_sm_traysettings.jpg|x150px|thumb|left|System monitor settings]]
| |
| − | </div>
| |
| − | <div style="clear: both;"></div>
| |
| − | | |
| − | For auto start with the system make a shortcut of AppTray.exe from the standalone package in the system Startup ([http://windows.microsoft.com/en-us/windows/run-program-automatically-windows-starts#1TC=windows-7 '''Windows 7'''], [http://support.microsoft.com/kb/2806079 '''Windows 8''']).
| |
| − | | |
| − | ===Download software===
| |
| − | | |
| − | {| class="wikitable" style="text-align: center;"
| |
| − | | |
| − | |'''Version'''||'''Change list'''
| |
| − | |-
| |
| − | ||[http://wiki.mini-box.com/images/c/c5/DCDCNUCv1.0.zip '''1.0''']||First version
| |
| − | |-
| |
| − | ||[http://wiki.mini-box.com/images/4/47/DCDCNUCv1.0.0.1.zip '''1.0.0.1''']||Bugfix (MOB_PULSEWIDTH and INIT_TOUT max value risen to 2550)
| |
| − | |}
| |
| − | | |
| − | ===Developer manual===
| |
| − | Mini-box.com provides one DCDC-Nuc API in a DLL (NUCLib.dll) and examples in Visual C++, Visual Basic and Visual C#.<br>
| |
| − | Basic C++/Visual Basic/C# knowledge is needed to use this examples together with the API.
| |
| − | The API dll has manifest embedded to permit C# and Visual Basic dynamic load.
| |
| − | | |
| − | The API has a set of functions exported to access the full functionality of the DCDC-NUC.
| |
| − | This functions are:
| |
| − | <code>
| |
| − | :extern "C" NUCLIB_API unsigned char nucOpenDeviceHandler(unsigned int timer);//open device handler. timer sets the refresh period in miliseconds (4 messages will be sent in this period). IMPORTANT: the handler can be kept open to notice any DCDC-NUC plugged in
| |
| − | :extern "C" NUCLIB_API void nucCloseDeviceHandler();//close device handler
| |
| − | :extern "C" NUCLIB_API void getNUCDevicePath(char* path);//Get opened device path @param path - recommended length 1024, will return empty string if no device opened
| |
| − | :extern "C" NUCLIB_API unsigned char isNUCConnected();//0=not connected, 1=normal state,2=loading settings from device,3=saving settings from pc,4=saving settings from file
| |
| − | :extern "C" NUCLIB_API unsigned char getNUCMode();//get DCDC-NUC mode: 0=Dumb, 1=Automotive
| |
| − | :extern "C" NUCLIB_API unsigned int getNUCInputFlags();//get DCDC-NUC input flags
| |
| − | :extern "C" NUCLIB_API unsigned int getNUCOutputFlags();//get DCDC-NUC output flags
| |
| − | :extern "C" NUCLIB_API float getNUCVIn();//get DCDC-NUC Input Voltage
| |
| − | :extern "C" NUCLIB_API float getNUCIIn();//get DCDC-NUC Input Current
| |
| − | :extern "C" NUCLIB_API float getNUCVOut();//get DCDC-NUC Output voltage
| |
| − | :extern "C" NUCLIB_API float getNUCIOut();//get DCDC-NUC Output Current
| |
| − | :extern "C" NUCLIB_API float getNUCTemperature();//get DCDC-NUC temperature - 1000 deg C is invalid value (output not enabled)
| |
| − | :extern "C" NUCLIB_API float getNUCVIgnition();//get DCDC-NUC Ignition Voltage
| |
| − | :extern "C" NUCLIB_API float getNUCPOut();//get DCDC-NUC Output Power
| |
| − | :extern "C" NUCLIB_API float getNUCVThump();//get DCDC-NUC Thump Voltage
| |
| − | :extern "C" NUCLIB_API unsigned char getNUCVerMajor();//get DCDC-NUC major version of the firmware
| |
| − | :extern "C" NUCLIB_API unsigned char getNUCVerMinor();//get DCDC-NUC minor version of the firmware
| |
| − | :extern "C" NUCLIB_API unsigned char getNUCDbgByte(int i);//get DCDC-NUC debug bytes
| |
| − | :extern "C" NUCLIB_API unsigned int getNUCTimer(unsigned int cnt);//get DCDC-NUC timer
| |
| − | :extern "C" NUCLIB_API unsigned int getNUCStateMachine();//get DCDC-NUC internal state machine
| |
| − | :extern "C" NUCLIB_API void restartNUC();//restart DCDC-NUC
| |
| − | :extern "C" NUCLIB_API void restartNUCInBootloaderMode();//restart DCDC-NUC in bootloader mode
| |
| − | :extern "C" NUCLIB_API void setNUCCommand1Byte(unsigned char command, unsigned char value);//DCDC-NUC direct commands (for debugging)
| |
| − | :extern "C" NUCLIB_API void setNUCCommand2Byte(unsigned char command, unsigned int value);//DCDC-NUC direct commands (for debugging)
| |
| − | :extern "C" NUCLIB_API void setNUCCommandBuffer(int len, unsigned char* values);//DCDC-NUC direct commands (for debugging)
| |
| − | :extern "C" NUCLIB_API unsigned int getNUCMaxVariableCnt();//get DCDC-NUC maximum variable count
| |
| − | :extern "C" NUCLIB_API unsigned char getNUCVariableData(unsigned int cnt, char* name, char* value, char* unit, char* comment);//get DCDC-NUC variable data
| |
| − | :extern "C" NUCLIB_API void startNUCLoadingSettings(unsigned char to_file, unsigned char compare_with_old);//start loading data from device
| |
| − | :extern "C" NUCLIB_API unsigned char getNUCLoadingSettingsState();//get load settings current state: 0-64 - steps, 100=success, 0xF1-0xFF=failure
| |
| − | :extern "C" NUCLIB_API unsigned char setNUCVariableData(unsigned int cnt, char* value);//set DCDC-NUC variable data for a given variable
| |
| − | :extern "C" NUCLIB_API void startNUCSaveSettings(unsigned char from_file);//start saving data to device
| |
| − | :extern "C" NUCLIB_API unsigned char getNUCSaveSettingsState();//get saving current state: 0-64 - steps, 100=success, 0xF1-0xFF=failure
| |
| − | See the examples for usage.
| |
| − | </code>
| |
| − | | |
| − | IMPORTANT: the API dll needs 4 files from Visual Studio 2005 redistribution pack (Microsoft.VC80.CRT.manifest, msvcm80.dll, msvcp80.dll, msvcr80.dll).
| |
| − | | |
| − | IMPORTANT: the API supports only one DCDC-NUC connected to the computer.
| |
| − | | |
| − | ====Visual C++ Example====
| |
| − | Open DCDCNUCTestAPI.sln from the package, set CLibTest project as active project, run it and see CLibTest.cpp for usage example.
| |
| − | ====Visual Basic Example====
| |
| − | Open DCDCNUCTestAPI.sln from the package, set VBLibTest project as active project, run it and see Module1.vb for usage example.
| |
| − | ====Visual C# Example====
| |
| − | Open DCDCNUCTestAPI.sln from the package, set CSLibTest project as active project, run it and see Program.cs for usage example.
| |
| − | | |
| − | ===Download API and example projects===
| |
| − | | |
| − | {| class="wikitable" style="text-align: center;"
| |
| − | | |
| − | |'''Version'''||'''Change list'''
| |
| − | |-
| |
| − | ||[http://wiki.mini-box.com/images/f/f1/DCDCNUCApiTestV1.0.zip '''1.0''']||First version
| |
| − | |-
| |
| − | ||[http://wiki.mini-box.com/images/4/44/DCDCNUCApiTestV1.0.0.1.zip '''1.0.0.1''']||Bugfix (MOB_PULSEWIDTH and INIT_TOUT max value risen to 2550)
| |
| − | |}
| |