Too easy? Ok, a real ninja hacker solution would had been taking apart the photo frame, put a Linux on the nice ARC processor through the JTAG interface and then plug some Wi-Fi dongle and do Everything directly on the DPF itself. But that’s just dreaming, we don’t have experience nor time for that.

Now you may ask, why didn’t you plug a monitor on the machine and just display whatever you want directly on the monitor? and the first reason is, we don’t have spare LCD monitors for this purpose (in fact we have many CRT monitors that nobody uses, but that requires just too much space). The second reason is that we wanted to do something more exiting, like hacker things .

So we setup everything: we made the scripts to generate the images, installed Ubuntu Linux 10.4 on the Itona and actually we borrowed another 512mb (flash) hard disk form another Itona and put it in the secondary IDE to get a RAID configuration with 1GB of space, just enough for Ubuntu and our script. Then realized of a small problem, as soon as you plug the DPF on the USB port, it enters in “transfer mode” and stops displaying the images. No matter if you eject, unmount, safe remove, shut down the computer, etc. the photo frame wont show the pictures until you physically unplug the USB cable (cut off the +5V). Here is were our ingenious circuit enters in action. A USB interrupter controlled by the parallel port (I guess serial RS-232 would work fine also using one of the signal pins).
After googling, I’ve found a circuit that seemed usable for this purpose. Just a couple transistors and a few resistors is everything we need.

Crop the board and put it in a case…



Finally, the whole thing mounted:
The Itona hidden behind the desk…

And the DPF showing the reports!!

For the circuit you will need:

• 1k resistor (2)
• 10k resistor (2)
• PNP transistor
• NPN transistor
• USB connectors, 1 to plug into the computer, the other whatever is better for your DPF
• DB-25 male connector (if you decided to do it via parallel too)

IMPORTANT: following image was borrowed from http://forum.allaboutcircuits.com/showthread.php?t=38544&page=2

I’ve connected the control-in to the PIN #2 of the DB-25, and the PIN #20 to the ground.
To turn the parallel port signal on/off I’ve made the following program in C (para.c):

#include 
#include 
#include 
#include 
#include 
#include 
#include 

#include


static int pfd;

int main(int argc, char* argv[])
{
	unsigned char data=0;

	if (argc != 3) {
		printf("Usage:\n\tpara [port] [val]\n\nport: parallel port e.g. /dev/parport0\nval:  1 to activate all data bits in parallel port, or\n      0 to disable all data bits in parallel port\n\n");
		return 1;
	}
	if (argv[2][0] == '1') {
		data=0xff;
	}
	pfd = open(argv[1], O_RDWR);
	if (pfd < 0) {
		perror("Failed to open port");
		exit(0);
	}
	if ((ioctl(pfd, PPEXCL) < 0) || (ioctl(pfd, PPCLAIM) < 0)) {
		perror("Failed to lock port");
		close(pfd);
		exit(0);
	}
	printf("Setting %s data bits to: %.2X\n", argv[1], data);
	ioctl(pfd, PPWDATA, &data);
	close(pfd);
	return 0;
}

The idea of this project is to control (switch off/on) two power sockets with a computer by using its USB port. I’ve chosen USB in first place because I wanted to experiment with the PIC18F4550 microchip’s microcontroller, and secondly because the power supplied by this port (500mA) is enough to activate a relay without any additional power supply.

The firmware is based in SIXCA USBDAQ which is in turn based on microchip’s CDC sample. USBDAQ is extremely easy to use. It implements a very simple set of ASCII commands to turn on/off the digital outputs, that I use to control the two relays. I just needed to adjust the bMaxPower in order to negotiate the 500mA with the host, and I also changed the vendor ID and the name of the device to USocket.

I’ve also made the schematic and board design of the circuit with Eagle, but I never used it since I made it on a strip board , so if you plan to use it please double check everything before.

The whole project including PIC firmware and Eagle files is available for download. You are free to use or modify it as you like, but please verify Microchip’s CDC sample license if you plan to use it for commercial applications.

Disclaimer: This project involves high voltage electricity. You should not attempt this project unless you are comfortable with basic concepts of AC and DC electricity, induction, and reading circuit schematics. You and your adult supervisor are responsible for your safety when doing this project!

Advice: Despites the high voltage part of the circuit is virtually isolated from the controller circuit by relays, these devices always represents a risk of mechanical failure and they can possibly damage your equipment or even cause physical injuries, so we (the author or the webmasters) are not responsible of any lose or damage.

The Circuit

Figure 1 – Schematic

Pretty much the same as USBDAQ but two (identical) sub-circuits were added to control the relays. A Darlington-transistor is used to protect the hardware. Once again, the idea was obtained from the web (thanks to google) and here is the link to the original article.

The PCB is divided in 3 little boards, for commodity and socket case space issues. (I’ve used only 2 strip boards in the actual prototype).

Figure 2 – Board

List of materials:

• IC1 – PIC16F4550 Microchip’s micro-controller (datasheet)
• Q2 – Crystal 20Mhz
• R1 – Resistor 4.7K
• R2 – Resistor 1M
• R3, R5 – Resistors 150
• R4, R6 – Resistors 100K
• K1, K3 – 5v Relays. I’ve used FBR211 by Fujitsu (datasheet)
• D1, D2, D3. D4 – Diodes 1N4004
• Q1, Q3 – BC517 Darlington-transistors (datasheet)
• LED1, LED2 – Regular leds
• C1, C2 – Capacitors 22pF
• C3 – Capacitor 470pF
• X1 – Mini-USB Connector Type B (datasheet)

PIC Firmware

Here is what I needed to modify from the original SIXCA USBDAQ:

I set bMaxPower to 250, which means 500mA. The power provided by hosts and hubs is twice the value of bMaxPower field, but in reality they are likely to allocate either 100 or 500 milliamperes rather than the specified amount.

The file modified is the one that contains the USB descriptor: fw/cdc/autofiles/usbdsc.c

/* Configuration 1 Descriptor */
CFG01=
{
/* Configuration Descriptor */
sizeof(USB_CFG_DSC),    // Size of this descriptor in bytes
DSC_CFG,                // CONFIGURATION descriptor type
sizeof(cfg01),          // Total length of data for this cfg
2,                      // Number of interfaces in this cfg
1,                      // Index value of this configuration
0,                      // Configuration string index
_DEFAULT,               // Attributes, see usbdefs_std_dsc.h
250,                    // Max power consumption (2X mA) 250 = 500mA

...

In the same file I modified the Vendor ID, Product ID and corresponding strings

/* Device Descriptor */
rom USB_DEV_DSC device_dsc=
{
sizeof(USB_DEV_DSC),    // Size of this descriptor in bytes
DSC_DEV,                // DEVICE descriptor type
0x0200,                 // USB Spec Release Number in BCD format
CDC_DEVICE,             // Class Code
0x00,                   // Subclass code
0x00,                   // Protocol code
EP0_BUFF_SIZE,          // Max packet size for EP0, see usbcfg.h
0xAF01,                 // Vendor ID
0xAF0A,                 // Product ID: CDC RS-232 Emulation Demo
0x0000,                 // Device release number in BCD format
0x01,                   // Manufacturer string index
0x02,                   // Product string index
0x00,                   // Device serial number string index
0x01                    // Number of possible configurations
};

...

rom struct{byte bLength;byte bDscType;word string[16];}sd001={
sizeof(sd001),DSC_STR,
'a','l','f','e','r','s','o','f','t','.',
'c','o','m','.','a','r'};

rom struct{byte bLength;byte bDscType;word string[21];}sd002={
sizeof(sd002),DSC_STR,
'A','l','f','e','r','S','o','f','t',' ',
'U','S','o','c','k','e','t',' ','1','.','0'};

And the file driver/win2k_winxp/mchpcdc.inf  Windows, to match the new vendor, product ID and description

[DeviceList]
%DESCRIPTION%=DriverInstall, USB\VID_AF01&PID_AF0A

...

;------------------------------------------------------------------------------
;  String Definitions
;------------------------------------------------------------------------------

[Strings]
MCHP="alfersoft.com.ar"
MFGNAME="alfersoft.com.ar"
DESCRIPTION="Communications Port"
SERVICE="AlferSoft USocket 1.0"

Programming the PIC

I’ve used WinPic800 to program the PIC. Here is a screenshot of the parameters I used to program it.

Commands

I didn’t modified any of the USBDAQ commands. They are all available but I only need to use these 4 commands:

• *A01 (activate relay 1)
• *A00 (deactivate relay 1)
• *A11 (activate relay 2)
• *A10 (deactivate relay 2)

All the commands are followed by an enter (chr(13) or ‘\n’).

Installing (Windows)

1. Plug the device into the USB port, the following message will appear in the tray bar.



2. In the first page of the “Found New Hardware Wizard” select “No, not this time” and click Next button.



3. Select the “Install from a list or specific location (Advanced)” option and click Next button.



4. Mark the “Include this location in the search:” and browse for the directory where the .inf file is located (driver\win2k_winxp)



5. This message will appear:



6. And then this one:



7. When the installation is done press “Finish”



8. After that the hardware is ready to use.

Testing (Windows)

1. Go to the device manager and locate the new COM port added, in my example COM10 was added



2. Open Hyperterminal and choose a name for the new conection



3. Select the new COM port



4. Set the Bit rate to 115200



5. This step is optional to see what we are typing on the screen, choose ASCII Setup



6. Then mark “Echo typed characters locally”



7. Finally connect and type one of the commands

Installing (Linux – Ubuntu)

1. Plug it. That’s it! a new device probably called /dev/ttyACM0 will be added by the OS.

Testing (Linux – Ubuntu)

1. Open gtkterm if you don’t have it installed type “sudo apt-get install gtkterm” from a terminal



2. Go to Configuration -> Port, set the port to /dev/ttyACM0, the speed to 115200 and click OK



3. Select Configuration -> Local echo
4. Type the command and press enter

Problem

After I mounted everything in the case a problem appeared, if I plug the USB cable to the computer and then the socket to the wall, the PIC hangs. But it works well the other way round (first plug to the wall and the to the computer). That is probably because the high voltage cables are too close to the PIC and unfortunatelly I’m not an expert in that matter and I don’t know how to fix it except by putting the circuit in a separated box. Experts needed! If you know another way to fix it please let me know!

Pictures

Download

Link to download USocket project, enjoy it!