I have thought of things like this in the past, and it looks like someone has taken the time to actually do it:
http://www.gizmag.com/go/7293/
I think that they have gone down the wrong road for the mouse part though…
[ I chose not to make the reasons why it is not appropriate and what can be done to remedy it to be private, since this is a bladdy good idea. Anyone interested, please email me. ]
Once again, for future reference I have found a nice little freeware program that can not only automate a windows installation (xp or vista) you can also change what is installed and what isnt including external drivers and programs, hotfixes and updates. Pretty much everthing you can think of
Nlite
After months and days of searching I cant find any websites that are developing a hobby based phased array soultion for robots or whatever, so I am very very tempted to get to work on this straight away when I move in, rather than spending time on my robot like I had planned. Also, another idea for today was to control stuff throught the pretty much redundant lifedrive we have, it is bluetooth and wifi enabled, so these could be utilised to form an advanced remot control?
Just for future reference Ive found some sites with a T610 LCD pinout and some code and stuff. Links:
I could mount the IR and the IR rx on the top and bottom of the boards, then I wouldnt have to worry about them interfering with each other! Cant believe I didnt think of that before! Might not fit with the wiskers on though?
Also, I could add some transistors to make the power output a bit more beefy.
I have finished rewriting all the subroutines now and I have manage to increase the speed even more. When rewriting, I got rid of any grossly underperforming code and now at 100mm/h it runs through in just under a second.
But once again, the errors are still plaguing the system. At this rainfall rate there are quite a few ghost drops and therefore still quite a lot of missed drops. The one I have just done is at 9% and I can clearly see at least 2 ghost drops. Have to investigate this further.
However, I think its about time I stopped for Christmas, so I don’t think I will be doing much except maybe showing a few people what I have done over the holidays.
Merry Christmas all!
Update
Just a quick update, I continued tarting up the code, and it now reports all ghost drops and all missing drops and why they were missed (ghosting/verification/etc.). Ive just done a beefy test at 100mm/h over 1 second:
run(’..\..\Create Samples\V0_7\V0_7′); V0_9;
7966 Drops Generated
Elapsed time is 143.394716 seconds.
12.7% Error
Thats without all the warning and debug messages. As a results Ive found that the thresholding/peak detection routine does not always find all the pulses. In fact, it only finds them at very slow rain rates. As a consequence I have had to pad the data so they are all the same length. So I am definitely going to have to look into that.
The graph also now shows the errors so it makes them easier to pick out. So just for formality, here are a few screenshots and program outputs:
run(’..\..\Create Samples\V0_7\V0_7′); V0_9;
79 Drops Generated
Elapsed time is 1.486008 seconds.
Ghost Detected at: (0.2093440.1,-0.3657250.1) Due to Pulses: 3774,3492,3380,3705
Ghost Detected at: (0.3033100.1,-0.0157940.1) Due to Pulses: 3619,3407,3602,3758
Ghost Detected at: (-0.0449920.1,0.3495790.1) Due to Pulses: 3481,3749,3880,3702
Ghost Detected at: (0.0771620.1,-0.4683740.1) Due to Pulses: 4014,3790,3505,3864
Ghost Detected at: (0.3148400.1,0.0721700.1) Due to Pulses: 4199,4023,4276,4384
Drop Missed: Number 6. The data did not pass varification tests.
Drop Missed: Number 30. The data was eaten by Ghosts!
Drop Missed: Number 31. The data was eaten by Ghosts!
Drop Missed: Number 32. The data was eaten by Ghosts!
Drop Missed: Number 33. The data did not pass varification tests.
Drop Missed: Number 36. The data was eaten by Ghosts!
Drop Missed: Number 37. The data was eaten by Ghosts!
Drop Missed: Number 38. The data was eaten by Ghosts!
Drop Missed: Number 39. The data was eaten by Ghosts!
Drop Missed: Number 40. The data was eaten by Ghosts!
Drop Missed: Number 41. The data was eaten by Ghosts!
Drop Missed: Number 56. The data did not pass varification tests.
79 drops originally, we have found 67
15.2% Error
And Some output Screenshots:
Just been looking around for some open source sound libraries to work in Qt, since Qt has no native support for low(ish) level access.
After a knock in the right direction from Kevin, I found a slight error in the Multilateration routines. When simplifying U, we chose points on the edge of the tank to solve for. The point which is at the top right of the tank was wrong. I was solving for x^2+y^2 = 1. I should have been solving for x^2 + y^2 = d^2. Fixed that, and now the results are a lot more accurate. No more inaccuracies around the outsides of the tank. Somewhere near +/-0.2mm. Too small to measure.
Still the largest problem is the number of false detects. I have started rewriting the code, but because of this silly error today, I have not had any time to continue rewriting the rest of the code.
I would like to have a play with facial recognition algorithms, so I had a quick sgeggy on the net to see what I could find. I found quite a few:
Would be great if I could implement a simple algorithm in a PIC. There are a few hits, but nothing specific.
On another note, I am definatly going to do my NFX software Idea of a pedal testing system. This should give me some more good experience in Qt. Have to move this from the back to the front burner.
Well here it is. A good couple of months worth of work summed up in a single image. Says a lot doesnt it…
