USB-SATA powerswitch - Revision history

Cartridge1987: /* future software enhancements */

2015-11-11T11:01:47Z

future software enhancements

Cartridge1987: /* future hardware enhancements */

2015-11-11T11:01:38Z

future hardware enhancements

Cartridge1987: /* writing programs */

2015-11-11T11:01:25Z

writing programs

Cartridge1987: /* programming */

2015-11-11T11:01:11Z

programming

Cartridge1987: /* pinout */

2015-11-11T11:00:54Z

pinout

Cartridge1987: /* overview */

2015-11-11T11:00:41Z

overview

Cartridge1987: /* USB SATA powerswitch */

2015-11-02T12:04:25Z

USB SATA powerswitch

Rew: /* USB SATA powerswitch */

2014-11-28T14:14:40Z

USB SATA powerswitch

Rew: /* future hardware enhancements */

2014-11-28T14:08:00Z

future hardware enhancements

Rew at 14:07, 28 November 2014

2014-11-28T14:07:10Z

@@ Line 153: / Line 153: @@
 * Replace the SMD inductor with an TH version (1.3: Done!)
-== future software enhancements ==
+== Future software enhancements ==
 * program the LUFA bootloader.

@@ Line 149: / Line 149: @@
 Similarly, the 5V and 3.3V outputs are switched by logic level N-FETS which are driven with their gates to 12V. So for the 5V output the drive on the gate is 7V. As this is a logic-level N-FET, this works just fine. But increase the switched voltage on the 5V line to more than 8V and things become critical.
-== future hardware enhancements ==
+== Future hardware enhancements ==
 * Replace the SMD inductor with an TH version (1.3: Done!)

@@ Line 129: / Line 129: @@
 Get the "flip" program from Atmel. http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3886
-== writing programs ==
+== Writing programs ==
 The chip is an at90usb162. http://www.atmel.com/dyn/resources/prod_documents/doc7707.pdf

@@ Line 84: / Line 84: @@
 For info on how to flash this .hex into your controller, see the section on programming below.
-== programming ==
+== Programming ==
 This section describes how you get your program into the processor.
@@ Line 125: / Line 125: @@
 Apparently the FLIP program is now available for Linux too. See below.
-=== windows ===
+=== Windows ===
 Get the "flip" program from Atmel. http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3886

@@ Line 14: / Line 14: @@
 == External resources ==
-== pinout ==
+== Pinout ==
 * led1 is connected to VCC
@@ Line 39: / Line 39: @@
 * 3,3V IN
 * 3,3V OUT
 == Default operation ==

@@ Line 7: / Line 7: @@
 You can buy the USB SATA powerswitch in the [http://www.bitwizard.nl/shop/usb-boards/usb-sata-powerswitch BitWizard shop].
-== overview ==
+== Overview ==
 The USB SATA powerswitch PCB has an USB connector and connection points for 3 power rails. The brains of the PCB is an at90usb162 (or compatible) chip.

@@ Line 2: / Line 2: @@
 This is the documentation page for the USB SATA powerswitch PCB. The firmware was updated around Nov 2014. If you have yours since longer ago, look here: [[Old USB-SATA powerswitch]]
+The old firmware used single character commands (s, c), the new version uses "words" (set/clear).
 == overview ==

@@ Line 1: / Line 1: @@
 = USB SATA powerswitch =
-This is the documentation page for the USB SATA powerswitch PCB.
+This is the documentation page for the USB SATA powerswitch PCB. The firmware was updated around Nov 2014. If you have yours since longer ago, look here: [[Old USB-SATA powerswitch]]
 == overview ==
@@ Line 25: / Line 25: @@
 Viewing with the USB connector on the left side, and the power pads on the lower side:
-* 12V OUT (12V IN for V1.1)
+* 12V IN
-* 12V IN (12V OUT for V1.1)
+* 12V OUT
 * GND
 * GND
@@ Line 36: / Line 36: @@
 * 3,3V OUT
-Mind the reversed order for the 12V pads on version 1.0, compared to the 5V and 3,3V pads!
 == Default operation ==
@@ Line 48: / Line 47: @@
  cat $tty &
  pid=$!
- (sleep 0.2; echo s0 ; sleep 0.2 ; echo s1 ; sleep 0.2 ; echo s2 ) > $tty
+ (sleep 0.2; echo set 0 ; sleep 0.2 ; echo set 1 ; sleep 0.2 ; echo set 2 ) > $tty
  sleep 0.5
  kill $pid
-"s0" means "set output zero", which is the 12V output. "s1" id the 5V output, and "s2" is the 3V3 output. The four status LEDs are connected to output 3,4, 5, and 6.
+"set 0" means "set output zero", which is the 12V output. "set 1" id the 5V output, and "set 2" is the 3V3 output. The four extra status LEDs are connected to output 3,4, 5, and 6.
-To turn off an output, simply send "c0", meaning "clear output zero".
+To turn off an output, simply send "clear 0", meaning "clear output zero".
+Note that we start with output zero, or the 12V. We have experienced that harddrives will powerdown nicely (i.e. not burn down in flames) when you keep 12V powered and interrupt the 5V supply. So powering up the drive by bringing up the 12V and then the 5V should work. Below you see that John does things the other way around. Apparently that too doesn't cause immidate problems. BitWizard recommends powering up the 12V first, and then the other power rails. But if you want to do otherwise, feel free. Powering down we recomend inverting the powerup sequence. 3.3V first, 5V next, 12V last.
-Reading from the device is necessary, because it needs to dump its output. If you don't read it's output, the device may (or will) freeze.
+Reading from the device is necessary, because it needs to put its output somewhere. If you don't read it's output, the device may (or will) freeze.
 John tells us that he uses the following windows script.
@@ Line 65: / Line 66: @@
  ::For sending info to COM port
  sleep -m 200
- echo s2 > COM3
+ echo set 2 > COM3
  sleep -m 200
- echo s1 > COM3
+ echo set 1 > COM3
  sleep -m 200
- echo s0 > COM3
+ echo set 0 > COM3
 The "type COM3" line is controversial. I would expect that line to block and the script to stop processing there. On windows, it seems it works  fine without it.  Then, I think John put the line back, but maybe as "copy com3: con:". Apparently that does not block. Please let us know how your experience is.
@@ Line 86: / Line 87: @@
 In general what you need to know is that the processor will boot into the code you programmed into it on powerup. Once you're done developing your program, that's the way you'll use it: Powerup, run.
 If there is no program loaded or if you press the reset button the chip comes up in "firmware upload mode". This is done by a bootloader. You should take care not to overwrite or erase the bootloader, because there is no way to put the bootloader back once it is gone.
 === Linux ===
-Get the dfu-programmer for atmel chips package. (link?)
+Get the dfu-programmer for atmel chips package. [[https://dfu-programmer.github.io/]]
-On sufficiently recent Ubunu distributions that is as simple as:
+On sufficiently recent Ubutnu distributions that is as simple as:
   sudo apt-get  install dfu-programmer
@@ Line 153: / Line 155: @@
 == Changelog ==
+.3
+* Moved to screw terminals for the power connections.
+.2
+* ??
 .1