https://wiki.mini-box.com/index.php?title=DCDC-NUC&feed=atom&action=historyDCDC-NUC - Revision history2024-03-29T11:59:52ZRevision history for this page on the wikiMediaWiki 1.35.9https://wiki.mini-box.com/index.php?title=DCDC-NUC&diff=23&oldid=prevAdmin: Created the page2020-10-20T12:55:18Z<p>Created the page</p>
<p><b>New page</b></p><div>'''6-48V Intelligent Automotive grade Power Supply'''<br><br><br />
==Introduction==<br />
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><br />
It has a range of intelligent functions not found in any traditional USB DC-DC converters.<br><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><br />
Two main [http://wiki.mini-box.com/index.php?title=DCDC-NUC#Operating_modes'''modes of operation'''] are possible:DUMB and AUTOMOTIVE.<br><br />
The output voltage setting (12V or 19V) can be changed through the <br />
[http://wiki.mini-box.com/index.php?title=DCDC-NUC#Configuration_switches '''Configuration switches'''] .<br><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><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><br />
<br />
==Product images==<br />
<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 />
<br><br />
<br />
==Features==<br />
* Input between 6V-48V<br><br />
* Programmable voltage thresholds<br><br />
* Selectable output voltage(+12V,+19V)<br><br />
* Anti Thump output in automotive mode<br><br />
* Motherboard startup/shutdown control by ON/OFF pulse<br><br />
* Motherboard shutdown control by USB<br><br />
* Highly customizable startup/shutdown timers<br><br />
* Low Power consumption<br><br />
* HID-USB connection<br><br />
* Input, Output Voltage and Current measurement<br><br />
* Temperature measurement<br><br />
* Motherboard detection using output Power measurements or 5V USB<br><br />
* Programmable Spread Frequency Modulation for reduced EMI<br><br />
* [http://wiki.mini-box.com/images/0/07/DCDCNUC_Dimensions.pdf Physical dimensions]<br><br />
<br />
==Operating modes==<br />
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.<br />
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><br />
Without any further settings if the input conditions are satisfied the unit will generate +12V regulated.<br><br />
Further parameters can be customized by changing in the [http://wiki.mini-box.com/index.php?title=DCDC-NUC#Parameter_List Parameter List].<br />
For configuration or firmware update USB connection is sufficient.<br><br />
<br />
===Dumb Mode===<br />
;Starting the unit<br />
: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><br />
:12V output and Thump output will be activated.<br><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 />
<br />
;Stopping the unit<br />
: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><br />
<br />
===Automotive Mode===<br />
;Starting the unit<br />
: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><br />
:The input voltage should be higher than VIN_MIN_STARTUP for the duration set by the VIN_COUNT parameter.<br><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><br />
:After Ignition is considered ON output will be turned ON after IGN_ON_TO_OUTPUT_ON_TOUT elapses.<br><br />
:12V output will be activated. Thump output will be activated after timeout elapses set by the THUMP_TOUT parameter.<br><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><br />
<br />
;Stopping the unit<br />
: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><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<br />
:If Ignition is considered OFF the motherboard is pulsed for shutdown after IGN_OFF_TO_MOB_PULSE_OFF_TOUT elapses.<br />
:After the HARD_OFF_TOUT timeout elapses the output will be turned OFF and the unit will enter in a low power state.<br />
<br />
===Motherboard control===<br />
The following options are available to control the motherboard by pulsing the on/off pins on the motherboard.<br />
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><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><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><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><br />
The same way the shutdown pulse can be inhibited by setting CONFIG1.b2 to 0.<br><br />
There are cases when motherboard started(ON) or OFF presence must be detected in order starting/stopping by pulses behavior work properly.<br><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><br />
There are two kinds of feedback information to detect motherboard status.<br><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><br />
In order to enable this feature the following steps should be performed:<br><br />
1. Enable this feature, CONFIG1.b3 should be set to 1.<br><br />
2. Observe and note the consumption of the connected motherboard when in standby and when is ON.<br />
Our unit measures the output power(POUT) which is displayed in the configuration software.<br><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><br />
POUT<POUT_LOW_THRESHOLD motherboard is considered OFF.<br><br />
POUT>POUT_HIGH_THRESHOLD motherboard is considered ON.<br><br><br />
The second detection mode is by measuring the +5VUSB signal. Usually motherboards turn OFF the +5VUSB signal when they are OFF.<br><br />
In order to enable this feature CONFIG1.b5 must be set to 1.<br><br><br />
If CONFIG1.b4 set, the PSU can shut down the OS by sending a Power Button event on USB.<br />
<br />
==Diagram & Schematics==<br />
<div style="display: inline; float: left;">[[File:Nucconnectors.png|230px|thumb|left|Connectors nomenclature]]</div><br />
<div style="clear: both;"></div><br />
<br />
==Connectors==<br />
===Power Input connectors===<br />
;P1 Output (4pin mini-FIT JR)<br />
: P1.1, P1.2 - GND<br />
: P1.3, P1.4 - Output voltage<br />
;P2 Input (4pin mini-FIT JR)<br />
: P1.1 - GND<br />
: P1.2 - Ignition<br />
: P1.3 - Input voltage<br />
: P1.4 - Thump<br />
;P7 Auxiliary output<br />
: P7.1, P7.2 - GND<br />
: P7.3, P7.4 - Output voltage<br />
<br />
===Interface connectors===<br />
;P4 Motherboard POWER SW connection, no polarity (JST PH connector, 3pin)<br />
: P4.1: SW1<br />
: P4.2: GND<br />
: P4.3: SW2<br />
;P6 USB header (not populated)<br />
: P6.1: GND<br />
: P6.2: USB D+<br />
: P6.3: USB D-<br />
: P6.4: +5V<br />
;P3 programming header, MCU reset (POGO pins)<br />
: P3.1: nMCLR<br />
: P3.2: GND<br />
: P3.3: +5V<br />
: P3.4: PGD<br />
: P3.5: PGC<br />
;P5 USB connector (micro-USB connector)<br />
<br />
===Configuration switches===<br />
<div><br />
<div style="display: inline; float: left;">[[File:DIP SW.png|230px|thumb|left|DIP Switch closeup]]</div><br />
;Switch 1<br />
: ON : Output voltage is 19V<br />
: OFF: Output voltage is 12V<br />
;Switch 2<br />
: Reserved<br />
;Switch 3<br />
: Reserved<br />
;Switch 4<br />
: Reserved<br />
;Switch 5<br />
: ON : Switch to Bootloader mode<br />
: OFF: Switch to Firmware mode<br />
<br />
Switching between the two available output voltages must be done with the device powered off.<br />
</div><br />
<div style="clear: both;"></div><br />
<br />
==NUC and OS Settings==<br />
<br><br />
*'''NUC related settings'''<br><br><br />
<div><br />
<div style="display: inline; float: left;">[[File:BIOS.png|230px|thumb|left|NUC Visual BIOS 2.0 Setting]]</div><br />
:Setting up the NUC's behavior when power is re-applied:<br><br />
:- press '''F2''' key during the boot sequence to entering the NUC's BIOS (Visual BIOS 2.0)<br><br />
:- first click on '''Advanced''' then click on '''Power''' menu button<br><br />
:- in '''Secondary Power Settings''' section select '''Power On''' option for '''After Power Failure'''<br><br />
:- the picture shows the right option in a red framework<br><br />
:- now the power supply should be able to '''START''' the NUC by applying corresponding voltage to its power input<br><br />
</div><br />
<div style="clear: both;"></div><br />
<br />
*'''OS related settings'''<br><br><br />
<div><br />
<div style="display: inline; float: left;">[[File:Power BTN.png|230px|thumb|left|Windows 7 Power Button Setting]]</div><br />
:Setting up the Windows 7 '''Power Button''' behavior:<br><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><br />
:- then at '''Power and sleep button settings''' select '''Shut down''' option for power button<br><br />
:- the picture shows the right option in a red framework<br><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><br />
</div><br />
<div style="clear: both;"></div><br />
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])<br />
<br />
==Bootloader Mode==<br />
It is recommended that you only connect USB power to the device <br />
when making a firmware update via “bootloader mode”.<br />
<br />
There are two ways to enter in bootloader mode: 1a) or 1b).<br><br />
1a) Slide the SW1 DIP switch button 1 in ON position.<br><br />
1b) Press the Switch to bootloader button on the configuration software's user interface.<br><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><br />
3) Press File->Import Firmware Image<br><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><br />
5) Press Program->Erase/Program/Verify Device<br><br />
6) If used option 1a) slide the SW1 DIP switch button 1 in OFF position, else skip this step.<br><br />
7) Press Program->Reset Device<br><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><br />
<br />
==Blink modes==<br />
'''Deep Sleep'''<br><br />
2 fast blinks and a pause, repeated every 5s<br><br />
Low energy state,used in AUTOMOTIVE mode<br><br />
<br />
'''Initial delay or USB only mode'''<br><br />
3 fast blinks and a pause, repeated every 750ms<br><br />
Signals the Initial Delay, before conditions are met for startup or if the unit is only USB powered<br><br />
<br />
'''Output ON'''<br><br />
Led is allways ON, signals the Output is ON<br><br />
<br />
'''OffDelay'''<br><br />
Led is blinking every 2 sec,ON for 1 sec, OFF for 1 sec<br><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><br />
<br />
'''HardwareOff Delay'''<br><br />
Led is blinking 3 times during a 2 sec period<br><br />
In AUTOMOTIVE mode, signals the period between Motherboard OFF pulse is sent and Output is turned OFF, see HARD_OFF_TOUT parameter<br><br />
<br />
==Characteristics==<br />
<div style="display: inline; float: left; padding-right: 10px; border-right: 1px solid #ccc;"><br />
Minimum Input Operating voltage<br><br />
Maximum input Operating voltage<br><br />
Sleep mode Current Consumption<br><br />
Storage and operating temperature<br><br />
MTBF<br><br />
Input connectors<br><br />
Output Connector<br><br />
</div><br />
<div style="display: inline; float: left; margin-left: 10px;"><br />
6V<br><br />
48V <br><br />
1mA<br><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><br />
50K Hrs @ 85<sup>o</sup>C, >= 200K Hrs at 65<sup>o</sup>C (projected)<br><br />
Mini-Fit JR<br><br />
Mini-Fit JR<br />
</div><br />
<div style="clear: both;"></div><br />
<br />
'''Output/Input Rail Output Current (buck/boost converter)'''<br />
<br><br />
Maximum input current: 5A<br><br />
Peak Input current: 6A(<30 seconds)<br><br />
Maximum output current: 5A (input current dependent)<br><br />
Peak output Current: 6A(<30 seconds @48V input)<br><br />
<br />
NOTE:<br />
When operating at high voltage (input or output) or/or operating at elevated temperatures <br />
de-rating up to 30% might be necessary, forced ventilation required.<br />
For long life operation, please ensure that hottest component on-board is kept below 65C.<br />
<br />
Efficiency Measurements (voltages measured at input/output connectors)<br><br><br />
[[File:Efficiency Vout 12V.png]][[File:Efficiency Vout 19V.png]]<br />
<br />
==Support and warranty==<br />
Standard Hardware Warranty 1Year / US, 2 Year EU.<br />
<br />
==Parameter List==<br />
{| class="wikitable"<br />
! NAME<br />
! Description<br />
|-<br />
| NUCMODE[-]<br />
| <pre><br />
0-Dumb mode (DUMB)<br />
1-Automotive mode (AUTOMOTIVE)<br />
</pre><br />
<br />
|-<br />
| INIT_TOUT[ms]<br />
| <br />
When all power supply start-up conditions are met, the PSU will wait this time before continuing with the start-up sequence.<br><br />
<br />
|-<br />
| VIN_MIN_STARTUP[mV]<br />
| <br />
If the input voltage is beyond this threshold and all other start-up conditions are met, the PSU can start.<br><br />
<br />
|-<br />
| VIN_MIN_RUNNING[mV]<br />
| <br />
Instantly turn off the PSU if the input voltage is below this threshold.<br><br />
<br />
|-<br />
| VIN_MAX_SHUTDOWN[mV]<br />
| <br />
If the input voltage is below this threshold and all other start-up conditions are met, the PSU can start.<br> <br />
If this condition is not satisfied during run time, the PSU will turn off instantly.<br><br />
<br />
|-<br />
| VIN_MIN_DEEP_DISCHARGE[mV]<br />
| <br />
If input voltage is below this threshold during IGN_OFF_TO_MOB_PULSE_OFF_TOUT then shutdown sequence will be initiated immediately.<br><br />
If input voltage is below this threshold during HARDOFF, output will be turned OFF immediately depending on CONFIG1 bits.<br><br />
<br />
|-<br />
| VIN_COUNT[ms]<br />
| <br />
Input voltage filtering<br><br />
<br />
|-<br />
| IGN_COUNT[ms]<br />
| <br />
Ignition voltage filtering<br><br />
<br />
|-<br />
| IGN_HIGH_THRESHOLD[mV]<br />
| <br />
If ignition voltage is beyond this threshold, ignition is considered to be ON.<br><br />
<br />
|-<br />
| IGN_LOW_THRESHOLD[mV]<br />
| <br />
If ignition voltage is below this threshold, ignition is considered to be OFF.<br><br />
<br />
|-<br />
| IGN_ON_TO_OUTPUT_ON_TOUT[s]<br />
| <br />
After ignition is considered ON, the PSU will wait this time before the output is turned ON.<br><br />
<br />
|-<br />
| THUMP_TOUT[s]<br />
| <br />
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><br />
<br />
|-<br />
| MOB_PULSE_TOUT[ms]<br />
| <br />
After the output is turned ON, the PSU will wait this time before sending the start-up pulse to the motherboard.<br><br />
<br />
|-<br />
| MOB_PULSE_WIDTH[ms]<br />
| <br />
The length of the start-up/shutdown pulse sent to the motherboard.<br><br />
<br />
|-<br />
| IGN_CANCEL_TOUT[s]<br />
| <br />
After the motherboard boots up, the ignition voltage sensing will be disabled for this period.<br><br />
<br />
|-<br />
| IGN_OFF_TO_MOB_PULSE_OFF_TOUT[s]<br />
| <br />
If ignition is considered to be OFF, the PSU will wait this time before sending the shutdown pulse to the motherboard.<br><br />
This shutdown signal can be sent through the ON/OFF pins or through USB, depending on the configuration of the CONFIG1 parameter.<br><br />
<br />
|-<br />
| HARD_OFF_TOUT[s]<br />
| <br />
After the shutdown pulse is sent to the motherboard, the PSU will wait this time before the output is turned OFF.<br><br />
This time-out allows the operating system to perform a clean shutdown.<br><br />
<br />
|-<br />
| IOUT_LIMIT[mA]<br />
| <br />
Output current limit setting. Resolution is 1280mA, minimum setting is 560mA.<br><br />
<br />
|-<br />
| PWM_SPREAD_MODULATING_PERIOD[ms]<br />
| <br />
Modulation period parameter of the Random Spread Frequency Modulation module (used for EMI reduction purposes)<br><br />
<br />
|-<br />
| PWM_SPREAD_PERCENT[%]<br />
| <br />
Frequency deviation parameter of the Random Spread Frequency Modulation module (used for EMI reduction purposes)<br><br />
<br />
|-<br />
| PWM_FREQ[kHz]<br />
| <br />
Operating frequency of the Switched Mode Power Supply. Default 300kHz<br><br />
<br />
|-<br />
|CONFIG1[bit7..bit0]<br />
|<br />
Configuration register. Used for enabling/disabling modules. 0 - disabled, 1 - enabled <br><br />
bit7:reserved<br><br />
bit6:reserved<br><br />
bit5:If set, the USB sense is enabled, +5V USB is used to detect the Motherboard alive status<br><br />
bit4:If set, the PSU can shut down the OS by USB by sending a Power Button event.<br><br />
bit3:If set, the PSU will detect motherboard alive presence by measuring the output power consumed.Check POUT_... parameters<br><br />
bit2:If set, shutdown pulse is enabled through the PWRSW connector.<br><br />
bit1:If set, startup pulse is enabled through the PWRSW connector.<br><br />
bit0:If set, output power cycle is enabled during HARDOFF period so it can reset the connected sytem.<br><br />
<br />
|-<br />
|CONFIG2[bit7..bit0]<br />
|<br />
Configuration register. Used for enabling disabling modules. 0 - disabled, 1 - enabled<br><br />
bit7-reserved<br><br />
bit6-reserved<br><br />
bit5-reserved<br><br />
bit4-reserved<br><br />
bit3-reserved<br><br />
bit2:reserved<br><br />
bit1:reserved<br><br />
bit0:reserved<br><br />
<br />
|-<br />
| POUT_HIGH_THRESHOLD[mW]<br />
| <br />
If output power measured is higher than this threshold the connected motherboard is considered to be ON.<br><br />
Together with POUT_LOW_THRESHOLD parameter sets a hysteresis for motherboard status.<br />
<br />
|-<br />
| POUT_LOW_THRESHOLD[mW]<br />
| <br />
If output power measured is lower than this threshold the connected motherboard is considered to be OFF.<br><br />
Together with POUT_HIGH_THRESHOLD parameter sets a hysteresis for motherboard status.<br />
<br />
|-<br />
| WRITE_COUNT[count]<br />
| <br />
The number of times the internal Flash program memory has been written.<br><br />
|}<br />
<br />
==Software manual==<br />
===Windows OS built-in support===<br />
The DCDC-NUC implements one generic USB class (USB HID), therefore most of the<br />
operating systems are recognizing it without any additional driver installation. <br />
===Configuration Software===<br />
The configuration software provides interface for DCDC-NUC monitoring, logging and setup.<br />
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<br />
dangerous if they are set without precaution.<br /><br />
The configuration software has two main screens (Status and Settings) and a header with the important voltage/current values.<br /><br />
<br />
====The first main screen is the "Status"====<br />
Example of this screen is shown in the next image:<br /><br />
<div style="display: inline; float: left;"><br />
[[File:DCDC-NUC-Status.JPG|x350px|thumb|left|Status screen]]<br />
</div><br />
<br />
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"<br />
<br />
The header of the status screen contains:<br />
:VIn: Input Voltage<br />
:VOut: Output Voltage<br />
:VThump: Thump Voltage<br />
:IIn: Input Current<br />
:IOut: Output Current<br />
:Temp: Temperature<br />
:VIgn: Ignition Voltage<br />
:POut: Output Power<br />
<br />
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.<br />
The user also have the possibility to log the current state into a *.csv file in the "Log" section.<br />
The "Debug" section is for debug/support and can change between different firmware versions.<br />
<div style="clear: both;"></div><br />
<br />
====The second main screen is the "Settings"====<br />
Example of this screen is shown in the next image:<br /><br />
<div style="display: inline; float: left;"><br />
[[File:DCDC-NUC-Settings.JPG|x350px|thumb|left|Settings screen]]<br />
</div><br />
<br />
<br />
This screen contains two main sections: the individual parameter setup for experienced users and the parameter save/load into/from file section.<br />
<br />
The main section of the "Settings" screen is the individual parameter settings.<br><br />
This is recommended to be done only by experienced users. Any parameter of the DCDC-NUC can be set from here.<br />
<br />
Changing one parameter is simple:<br />
:- 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).<br />
:- after double click introduce the new value in the new popup dialog and press OK<br />
:- the introduced value is checked - if something is wrong (out of limit, bad value etc.) error message will be shown<br />
:- the ! sign will blink on the "Sync all parameters to the DCDC-Nuc" button to show edited but not saved/synced variables<br />
:- 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!<br />
<br />
IMPORTANT: any parameter setting is taken into account by the DCDC-NUC in this cases:<br />
: - after a full restart either with power cut from all sources (usb, vin)<br />
: - hitting the "Restart DCDC-Nuc" button<br />
: - keeping the "Reload parameters on the fly after sync" checked. <br />
Do any parameter change with precaution, check the parameters and wires before applying it!<br />
<br />
For users who need to setup more devices with the same DCDC-NUC settings, it is recommended to use the save/load parameters buttons.<br />
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<br />
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.<br />
<br />
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.<br />
<br />
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]] <br />
<br />
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<br />
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<br />
operation. Please try again and contact our support team only if the device gives this error 4-5 times in a row.<br />
<br />
===Windows System monitor===<br />
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><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<br />
"skin*.mbs" files installed together with this application. The current skin can be selected right clicking on the try icon.<br />
The "skin*.mbs" files are simple text ones editable with any text editor (notepad for example).<br> <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<br />
file.<br><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.<br />
The size of the popup is defined by the background image – transparent parts can be defined as well (see for example: "bubble1.bmp").<br />
Example screenshots:<br /><br />
<div style="display: inline; float: left;"><br />
[[File:DCDCNUC_sm_tray2.jpg|x150px|thumb|left|System monitor skin1 connected]]<br />
</div><br />
<div style="display: inline; float: left;"><br />
[[File:DCDCNUC_sm_tray3.jpg|x150px|thumb|left|System monitor skin1 disconnected]]<br />
</div><br />
<div style="clear: both;"></div><br />
<br />
Right clicking on the tray icon will pop-up a simple menu:<br />
<div style="display: inline; float: left;"><br />
[[File:DCDCNUC_sm_menu.jpg|x150px|thumb|left|System monitor settings]]<br />
</div><br />
<div style="clear: both;"></div><br />
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:<br />
<div style="display: inline; float: left;"><br />
[[File:DCDCNUC_sm_traysettings.jpg|x150px|thumb|left|System monitor settings]]<br />
</div><br />
<div style="clear: both;"></div><br />
<br />
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''']).<br />
<br />
===Download software===<br />
<br />
{| class="wikitable" style="text-align: center;"<br />
<br />
|'''Version'''||'''Change list'''<br />
|-<br />
||[http://wiki.mini-box.com/images/c/c5/DCDCNUCv1.0.zip '''1.0''']||First version<br />
|-<br />
||[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)<br />
|}<br />
<br />
===Developer manual===<br />
Mini-box.com provides one DCDC-Nuc API in a DLL (NUCLib.dll) and examples in Visual C++, Visual Basic and Visual C#.<br><br />
Basic C++/Visual Basic/C# knowledge is needed to use this examples together with the API.<br />
The API dll has manifest embedded to permit C# and Visual Basic dynamic load.<br />
<br />
The API has a set of functions exported to access the full functionality of the DCDC-NUC.<br />
This functions are:<br />
<code><br />
: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<br />
:extern "C" NUCLIB_API void nucCloseDeviceHandler();//close device handler<br />
: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<br />
: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<br />
:extern "C" NUCLIB_API unsigned char getNUCMode();//get DCDC-NUC mode: 0=Dumb, 1=Automotive<br />
:extern "C" NUCLIB_API unsigned int getNUCInputFlags();//get DCDC-NUC input flags<br />
:extern "C" NUCLIB_API unsigned int getNUCOutputFlags();//get DCDC-NUC output flags<br />
:extern "C" NUCLIB_API float getNUCVIn();//get DCDC-NUC Input Voltage<br />
:extern "C" NUCLIB_API float getNUCIIn();//get DCDC-NUC Input Current<br />
:extern "C" NUCLIB_API float getNUCVOut();//get DCDC-NUC Output voltage<br />
:extern "C" NUCLIB_API float getNUCIOut();//get DCDC-NUC Output Current<br />
:extern "C" NUCLIB_API float getNUCTemperature();//get DCDC-NUC temperature - 1000 deg C is invalid value (output not enabled)<br />
:extern "C" NUCLIB_API float getNUCVIgnition();//get DCDC-NUC Ignition Voltage<br />
:extern "C" NUCLIB_API float getNUCPOut();//get DCDC-NUC Output Power<br />
:extern "C" NUCLIB_API float getNUCVThump();//get DCDC-NUC Thump Voltage<br />
:extern "C" NUCLIB_API unsigned char getNUCVerMajor();//get DCDC-NUC major version of the firmware<br />
:extern "C" NUCLIB_API unsigned char getNUCVerMinor();//get DCDC-NUC minor version of the firmware<br />
:extern "C" NUCLIB_API unsigned char getNUCDbgByte(int i);//get DCDC-NUC debug bytes<br />
:extern "C" NUCLIB_API unsigned int getNUCTimer(unsigned int cnt);//get DCDC-NUC timer<br />
:extern "C" NUCLIB_API unsigned int getNUCStateMachine();//get DCDC-NUC internal state machine<br />
:extern "C" NUCLIB_API void restartNUC();//restart DCDC-NUC <br />
:extern "C" NUCLIB_API void restartNUCInBootloaderMode();//restart DCDC-NUC in bootloader mode<br />
:extern "C" NUCLIB_API void setNUCCommand1Byte(unsigned char command, unsigned char value);//DCDC-NUC direct commands (for debugging)<br />
:extern "C" NUCLIB_API void setNUCCommand2Byte(unsigned char command, unsigned int value);//DCDC-NUC direct commands (for debugging)<br />
:extern "C" NUCLIB_API void setNUCCommandBuffer(int len, unsigned char* values);//DCDC-NUC direct commands (for debugging)<br />
:extern "C" NUCLIB_API unsigned int getNUCMaxVariableCnt();//get DCDC-NUC maximum variable count<br />
:extern "C" NUCLIB_API unsigned char getNUCVariableData(unsigned int cnt, char* name, char* value, char* unit, char* comment);//get DCDC-NUC variable data<br />
:extern "C" NUCLIB_API void startNUCLoadingSettings(unsigned char to_file, unsigned char compare_with_old);//start loading data from device<br />
:extern "C" NUCLIB_API unsigned char getNUCLoadingSettingsState();//get load settings current state: 0-64 - steps, 100=success, 0xF1-0xFF=failure<br />
:extern "C" NUCLIB_API unsigned char setNUCVariableData(unsigned int cnt, char* value);//set DCDC-NUC variable data for a given variable <br />
:extern "C" NUCLIB_API void startNUCSaveSettings(unsigned char from_file);//start saving data to device<br />
:extern "C" NUCLIB_API unsigned char getNUCSaveSettingsState();//get saving current state: 0-64 - steps, 100=success, 0xF1-0xFF=failure<br />
See the examples for usage.<br />
</code><br />
<br />
IMPORTANT: the API dll needs 4 files from Visual Studio 2005 redistribution pack (Microsoft.VC80.CRT.manifest, msvcm80.dll, msvcp80.dll, msvcr80.dll).<br />
<br />
IMPORTANT: the API supports only one DCDC-NUC connected to the computer.<br />
<br />
====Visual C++ Example====<br />
Open DCDCNUCTestAPI.sln from the package, set CLibTest project as active project, run it and see CLibTest.cpp for usage example.<br />
====Visual Basic Example====<br />
Open DCDCNUCTestAPI.sln from the package, set VBLibTest project as active project, run it and see Module1.vb for usage example.<br />
====Visual C# Example====<br />
Open DCDCNUCTestAPI.sln from the package, set CSLibTest project as active project, run it and see Program.cs for usage example.<br />
<br />
===Download API and example projects===<br />
<br />
{| class="wikitable" style="text-align: center;"<br />
<br />
|'''Version'''||'''Change list'''<br />
|-<br />
||[http://wiki.mini-box.com/images/f/f1/DCDCNUCApiTestV1.0.zip '''1.0''']||First version<br />
|-<br />
||[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)<br />
|}</div>Admin