Here is link to his blog post.

I have created one UIView and added one UIImageView to it and loaded it with Default.png image, but when starting the program whole view is moved up for 20px, it’s y reference is starting from 0 instead from 20, so here is how to fix it easily.

In application didFinishLaunching delegate add following code before [window makeKeyAndVisible]; and after [window addSubview:yourView];

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {

[window addSubview:yourView];
[yourView setFrame:CGRectMake(0, 20, 320, 460)]; // so you are creating frame which x starts on 0, y starts on 20px and with dimensions 320px x 460px
[window makeKeyAndVisible];

return YES;
}

The fix is very simple, just delete sf_sdf.dll file from C:\Snort\lib\snort_dynamicpreprocessor directory and start snort again.

Update of snort is very simple and it can be described in few simple steps which can be used for fresh install as well:

• download Snort 2.8.6 from the www.snort.org site
• download WinPcap 4.1.1 from the www.winpcap.org
• install both of them on the target machine
• download the latest community rules from www.snort.org (you need to register and log in to be able to download them)
• extract rules to C:\Snort overwriting existing files and open Snort.conf file in the etc map
• find line nr. 155 and replace it to this dynamicpreprocessor directory C:\Snort\lib\snort_dynamicpreprocessor
• then replace line 158 to this dynamicengine C:\Snort\lib\snort_dynamicengine\sf_engine.dll
• and then comment out line 161 if you don’t have dynamic rules #dynamicdetection directory /usr/local/lib/snort_dynamicrules
• now when you are done if you are not using IPV6 delete sf_sdf.dll file from C:\Snort\lib\snort_dynamicpreprocessor to avoid this error
• start Snort to test it
• start Snort as service if test is OK

• 1x Atmega 168 or smaller chip with Arduino bootloader preprogrammed (the code compiled is only 4k)
• 1x 28-pin IC socket (so that you can use chip for other projects latter)
• 1x 16MhZ ceramic resonator
• 1x 16×2 lcd display, HD44780 compatible
• 1x 7805 5V voltage regulator
• 4x micro buttons
• 1x SFH615 optocouppler
• 2x 3mm led diodes (green for power and yellow for activity)
• 4x 220R resistors, 1x 10K resistor and 1x 1K resistor
• 2x trim potentiometers (4K7 and 10K)
• 3x male headers(6-pin, 3-pin and 2-pin)
• 3x ceramic capacitators(0.1 uF, 1uF, 10uF)
• 1x 3.5 mm female jack for connection to laser

Now this post wouldn’t be complete without Eagle schematic and board files. You can download them on the following link: Trigger schematics (116).

I don’t have schematics of the laser side because it’s simple. I’m leading 3 wires with 3.5mm audio cable, analog in, gnd and vcc(+5V). In the laser box I have laser which is connected directly to the vcc and gnd, one foto resistor that is giving to high value to analog in so I have one resistor before it connected to gnd.

So we have:

• GND wire is connected to laser gnd wire and to one side of let’s say 2M resistor which other side is connected to one leg of photo resistor
• VCC wire is connected to laser vcc wire
• Analog in wire connected to other leg of the photo resistor

It depends on which photo resistor you are using how big resistor value before it you have to use. Arduino is capable of reading analog in until value of 1024 and that’s reason why the big resistor value is needed, so you are testing which one do you need until the value of direct laser beam to the photo resistor is under 1024, mine is about 920.

The soldering was OK with only few places to be fixed because of strong acid mix, but nothing special.

Here are some pictures of the finished trigger.

P.S. This is final and last prototype of the version 1. The next one will be better, without trimpots, with 3-4 keys, lot of menus and few outputs instead of one.

Stay tuned!!

• removed triggering 3.5mm female connector, instead I have 3-pin connectors to connect wires on one or two flashes
• added 6 pin programming header so that I can program Atmega chip without removing it from the board every time
• added 3 pin jumper header for power selection (usb/external)

Here are two pictures of a fresh etched board, not perfect on the corners because of bad mixing of the acid but good enough for the first attempt.

P.S. Updated schema coming soon.

And here it is, description, schematics, video and sample pictures.

The idea has already been seen on the Internet. Arduino is controlling photo resistor on which laser beam is pointed. When resistance changes itself because of the drop that is cutting beam then Arduino is triggering Nikon camera after the amount of time specified with one trim capacitor which can be between 0 and 1023, but I have divided it with 2 so that I have better control of the delay. All information is displayed on 2×16 LCD display. Also to be able to take picture of drops colliding it’s necessary that speed of the drops be 10 drops/sec so I have implemented one button for that with proper code behind it.

I have also 4 buttons and 2 led diodes on the board. Buttons that I have are reset for resetting of the electronics, debug that is switching debug mode on and off, drops that is designed to count drops per second and ready button that is used when I’m taking pictures so that when drops are falling fast I don’t trigger camera every time when they are going down. Led diodes that I’m using are green for power and yellow for visual notification when the trigger is trigged.

Here is the final schematics that I’m using right now.

Nikon-Arduino trigger schema

For simplified solution with cables I’m using standard audio cables with 3.5mm stereo jacks on both sides, so I can use same cables for other purposes as well. I have also modified Nikon cable remote so that it has 3.5mm female stereo jack built in for simple use with trigger and without it.

Modified Nikon cable release

Here are few pictures of the whole setup.

Nikon Trigger

Of course code behind is in this NikonFastTrigger.pde (105) file available for download.

Simple instructions.

1. when the program is loaded it will display Ready on the second line
2. when drop breaks laser beam then instead of Ready on display will be Busy until you press Ready button
3. offten because I have laser box about 1m above the surface delay is needed between 150-220 ms

For drops counter I’m doing like this.

1. switch to drops counter with drops button
2. then I try to create drops stream with about 1 drop per second with help of the normal digital watch and by changing delay I set Arduino to recognize that as 1drop/sec
3. now the only thing left is to configure drops stream to 10 drops/second for colliding watterdrops

Here are couple of pictures captured with this setup and pictures of colliding drops are to come.

And here is the video from YouTube.

I tried to find service manual to see how am I going to assemble lens but without any success, at least not for free.

So finally when I have founded it and paid for it, I though why not have it here on blog so that everyone that needs it can get it for free.

So here are they, 2 files, service manual and parts list.

Enjoy.

• CANON PowerShot SD10, PowerShot SD750, Digital Elph, Digital Ixus 70, 75 Service Manual - NO PARTS LIST (526)
• CANON PowerShot SD750 DIGITAL ELPH, DIGITAL IXUS 75, IXY DIGITAL 90 Parts List (360)

Snort® is an open source network intrusion prevention and detection system (IDS/IPS) developed by Sourcefire. Combining the benefits of signature, protocol and anomaly-based inspection, Snort is the most widely deployed IDS/IPS technology worldwide.

Installation of Snort on Windows is pretty simple.

First, you need to download and install few things. For Snort to be able to act as sniffer and IDS it needs Windows Packet Capture Library which is WinPcap. The stable latest version on the site is 4.1.1 and you can download it here.

Now when we have WinPcap installed the next step will be to download Snort. The latest version for Windows is 2.8.5.1 and you can download it here. Installation shouldn’t be a problem, if you need IPv6 support and logging to Microsoft SQL or Oracle database then you need to select proper radio and check boxes and if don’t then just go next and next to the end and that’s it. Default installation directory is C:\Snort so remember it because it will be our working dir all the time.

So we have installed WinPcap and Snort but we are not finished with installation yet. We have one more thing to download and install. The Snort rules. These rules are those small files that tells Snort what it should search for in captured packages and how to identify them, as a threat, information disclosure or something else. For us to be able to download Snort rules we have to be registered on Snort site. Registration is free and rules are one month old for free users, for those who need the latest threats detected at the same moment when they are published to the community I suggest to buy VRT subscription so you will have the latest rules directly as they are announced. So now we will download snortrules-snapshot-2.8.tar.gz rules archive file.  When you open archive file you will get following structure:

Copy all four directories over those in C:\Snort replacing contents that already exists on the hard drive.

Now when we are done with easy part we need to configure Snort to run. Because these rules are written for unixoid systems we need to change some things in the main config file C:\Snort\etc\snort.conf so that Snort can start at all.

Here are the things that you need to edit to be able to run snort:

Find lines 269 and 270. These lines will not allow Snort to start, at least not on Windows because Snort detects the second one as double config detection line so we need to change this.

Change from this:

config detection: search-method ac-bnfa
config detection: max_queue_events 5

To this:

config detection: search-method ac-bnfa max_queue_events 5

Now, the next thing that we need to change is lines where we say to Snort where to find dynamic preprocessor files. On lines from 298 to 303 change this:

dynamicpreprocessor file /usr/local/lib/snort_dynamicpreprocessor/libsf_dce2_preproc.so
dynamicpreprocessor file /usr/local/lib/snort_dynamicpreprocessor/libsf_dns_preproc.so
dynamicpreprocessor file /usr/local/lib/snort_dynamicpreprocessor/libsf_ftptelnet_preproc.so
dynamicpreprocessor file /usr/local/lib/snort_dynamicpreprocessor/libsf_smtp_preproc.so
dynamicpreprocessor file /usr/local/lib/snort_dynamicpreprocessor/libsf_ssh_preproc.so
dynamicpreprocessor file /usr/local/lib/snort_dynamicpreprocessor/libsf_ssl_preproc.so

To this:

dynamicpreprocessor file C:\Snort\lib\snort_dynamicpreprocessor\sf_dce2.dll
dynamicpreprocessor file C:\Snort\lib\snort_dynamicpreprocessor\sf_dcerpc.dll
dynamicpreprocessor file C:\Snort\lib\snort_dynamicpreprocessor\sf_dns.dll
dynamicpreprocessor file C:\Snort\lib\snort_dynamicpreprocessor\sf_ftptelnet.dll
dynamicpreprocessor file C:\Snort\lib\snort_dynamicpreprocessor\sf_smtp.dll
dynamicpreprocessor file C:\Snort\lib\snort_dynamicpreprocessor\sf_ssh.dll
dynamicpreprocessor file C:\Snort\lib\snort_dynamicpreprocessor\sf_ssl.dll

Next thing to change is line 324 on which we have dynamic engine path, so change it from this:

dynamicengine /usr/local/lib/snort_dynamicengine/libsf_engine.so

To this:

dynamicengine C:\Snort\lib\snort_dynamicengine\sf_engine.dll

I don’t know why, maybe some mistake, but lines bellow should be commented out by default, but they were not so we have to comment them out. Because we are not VRT subscriber and don’t have any dynamic detection files we need to coment lines from 339 to 354, so change this:

dynamicdetection file /usr/local/lib/snort_dynamicrules/bad-traffic.so
dynamicdetection file /usr/local/lib/snort_dynamicrules/chat.so
dynamicdetection file /usr/local/lib/snort_dynamicrules/dos.so
dynamicdetection file /usr/local/lib/snort_dynamicrules/exploit.so
dynamicdetection file /usr/local/lib/snort_dynamicrules/imap.so
dynamicdetection file /usr/local/lib/snort_dynamicrules/misc.so
dynamicdetection file /usr/local/lib/snort_dynamicrules/multimedia.so
dynamicdetection file /usr/local/lib/snort_dynamicrules/netbios.so
dynamicdetection file /usr/local/lib/snort_dynamicrules/nntp.so
dynamicdetection file /usr/local/lib/snort_dynamicrules/p2p.so
dynamicdetection file /usr/local/lib/snort_dynamicrules/smtp.so
dynamicdetection file /usr/local/lib/snort_dynamicrules/sql.so
dynamicdetection file /usr/local/lib/snort_dynamicrules/web-client.so
dynamicdetection file /usr/local/lib/snort_dynamicrules/web-misc.so

To this:

#dynamicdetection file /usr/local/lib/snort_dynamicrules/bad-traffic.so
#dynamicdetection file /usr/local/lib/snort_dynamicrules/chat.so
#dynamicdetection file /usr/local/lib/snort_dynamicrules/dos.so
#dynamicdetection file /usr/local/lib/snort_dynamicrules/exploit.so
#dynamicdetection file /usr/local/lib/snort_dynamicrules/imap.so
#dynamicdetection file /usr/local/lib/snort_dynamicrules/misc.so
#dynamicdetection file /usr/local/lib/snort_dynamicrules/multimedia.so
#dynamicdetection file /usr/local/lib/snort_dynamicrules/netbios.so
#dynamicdetection file /usr/local/lib/snort_dynamicrules/nntp.so
#dynamicdetection file /usr/local/lib/snort_dynamicrules/p2p.so
#dynamicdetection file /usr/local/lib/snort_dynamicrules/smtp.so
#dynamicdetection file /usr/local/lib/snort_dynamicrules/sql.so
#dynamicdetection file /usr/local/lib/snort_dynamicrules/web-client.so
#dynamicdetection file /usr/local/lib/snort_dynamicrules/web-misc.so

Now we need to trim a bit SSH preprocessor to work on Windows as it is different from Linux one, so find line 753 and change this:

preprocessor ssh: server_ports { 22 } \
max_client_bytes 19600 \
max_encrypted_packets 20 \
disable_srvoverflow \
disable_protomismatch \
disable_badmsgdir

To this:

preprocessor ssh: server_ports { 22 } \
max_client_bytes 19600 \
max_encrypted_packets 20

Now we are good to go. We can test snort easily from the command line. So now go on Start->Run and type cmd following by enter key. Now in command prompt type following commands:

c: and then enter key

cd c:\snort\bin and then enter key

snort -v -c C:\snort\etc\snort.conf -l C:\snort\log -K ascii and then enter key

So now we have entered Snort directory and started Snort on command line. You will first see Snort starting and parsing config file snort.conf and then you will see lot of output when Snort start sniffing and controlling packages on the network. If it finds any package that is not regular network traffic it will save info about it in c:\Snort\Log\alert.ids file. Simple output of one captured packet looks like this:

[**] [1:254:7] DNS SPOOF query response with TTL of 1 min. and no authority [**]
[Classification: Potentially Bad Traffic] [Priority: 2]
12/22-12:19:12.577553 192.168.137.206:53 -> 192.168.137.10:55153
UDP TTL:128 TOS:0×0 ID:5399 IpLen:20 DgmLen:79
Len: 51

Now to explain what we have here. The first line says what type of attack is it, the second line says what classification is it and what priority does it have, and the last three lines are data about the attack, attacker IP, your IP, destination and source ports and so on.

snort /service /install -c C:\Snort\etc\snort.conf -l C:\Snort\log -K ascii

Because some of them doesn’t work on my HU I had first to build Arduino scanner to scan for those missing remote codes.

Although I’m sending codes as binaries it was easier for me to work with decimals on the serial console and then latter convert them to binary so I have wrote function for that as well.

Because the first part of signal is always the same there was not need to convert it at all, and it’s stored in variable iHello, so the part that is changed is the second part or 3 decimal numbers.

Now because there are 255*255*255 = 16 581 375 possible combinations I had to bring this to some reasonable number otherwise it would take very much time to find right codes so I have limited combinations a bit.

I took the lowest and the highest values from codes from link above for the first and the second decimals, and limited the third one to 2 possible numbers that I’m sending as finish 85 or 213.

Here are those codes that I have founded working on my HU:

1. 87  253   85 ( 01010111  11111101  01010101 ) – Pause
2. 107 247   85 ( 01101011  11110111  01010101 ) – Band/ta
3. 111  237   85 ( 01101111  11101101  01010101 ) – Defeat
4. 119 235   85 ( 01110111  11101011  01010101 ) – Power
5. 173 238 213 ( 10101101  11101110  11010101 ) – Mute
6. 183 219   85 ( 10101101  11101110  11010101 ) – Source
7. 187 218 213 ( 10111011  11011010  11010101 ) – Next Track
8. 93  250 213 ( 01011101  11111010  11010101 ) – Previous track
9. 219 214 213 ( 11011011  11010110  11010101 ) – Volume up
10. 109 246 213 ( 01101101  11110110  11010101 ) – Volume down
11. 171 239 85 ( 10101011  11101111  01010101 ) – Folder/memory up
12. 85 255 85   ( 01010101  11111111  01010101 ) – Folder/Memory down

Now because I have IR remote for my HU and defeat is not on it I assume that it’s possible to find even more codes for it but I didn’t those so I stopped here where I have everything for my first project.

Here are pictures of the interface that I have built for testing of codes. It consists of 5 buttons which have been assigned different functions and 3.5 mm female audio jack which I use for connection with HU. HU has the same 3.5 mm female jack on the back so I can use regular 3.5mm stereo cable for testing without any modifications on HU or Arduino board.

Here is the Arduino Alpine scanner (215) sketch file with all functions that I have used for scanning, saving and displaying codes on serial console.

Here are the instructions how to use this sketch to find codes.

1. First you need to erase eeprom with erase function to be sure that it’s clean on the start of scan.
2. Now comment out function for erase and uncomment function for saving combination on eeprom
3. Now you are ready for scan, so when you connect Arduino to your HU just press button 4 to start scan
4. When you see some change on HU you need to press button 4 to stop scan
5. Using buttons 1 and 3 you can go back or forward to find that combination that you discovered
6. When you find it you can verify it with button 2 which repeats it again
7. If that is combination that you are looking fore press button 5 to save it to eeprom
8. When you have found all combinations that you are interested of connect Arduino to computer and on serial console you will have all combinations that you have found, so copy and paste them in iFounded array
9. Comment out functions for saving, previous and next button and uncomment functions for import of combinations, sending of previous and next combinations
10. Now when you power up Arduino press button nr 5 to import combinations and cycle them with buttons 1 or 2 to confirm that you have right combinations saved

Now when I have all of the codes needed to control HU I can finish the first project and the post about it is coming soon.

Any comments are welcome.