Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.


  • Content Count

  • Joined

  • Last visited

Community Reputation

5 Neutral


About Reggie

  • Rank
    Sub Dwarf

Contact Methods

  • Website URL
  1. A very sad day indeed, he was a true giant in his field and an inspiration, RIP Sir Patrick.
  2. You just need to short the polyfuse, don't need a resistor.
  3. Seems I was entirely wrong on the path you actually have to install libv4lconvert0 and libv4l-0 (if you 'sudo apt-get install webcam' it will install both as dependencies automatically). you can then find the modules in /usr/lib/arm-linu-gnueabihf/libv4l/. look at this page for instructions: http://linuxtv.org/downloads/v4l-dvb-apis/libv4l.html#id3156114 in the 'v4l1compat.so wrapper library' section at the bottom of the page.
  4. There is something in the v4l drivers that allows you to use a 'compat' module as a wrapper, (I think you use ld or something to load it before running the actual app. that you want to use.) I think there are probably plenty of cameras that the pi will work with, we just haven't tested them and we desperately want the spc900nc to work. I think one of the issues for the pi is that it's using a kernel that is 'too new' for the pwc drivers, the drivers were better it would appear around 2.6.xx rather than 3.x.x. I think if enough of us turn up on the raspberry pi forums at the same time asking questions, we might get better support over our driver, the first thing is definitely getting > 160x120 resolution, this could be down to raspberry pi usb issues or it could be down to pwc ioctls being missing. I'm going for a mixture of both.
  5. Hi Gina, that's a lovely set of nested if's you've got there, have you ever considered using a 'switch/case' statement instead?
  6. I think the key point here is that this is a development platform and it doesn't work for the spc cameras (which really are old in the context of things) whereas it does work for the qhy5, so it's not all bad!!
  7. It's funny that whilst the licenses for arm11xx chips were originally released in 2002, arm11xx chips have featured heavily in the mobile market, having more recently been in iphone 3g for instance. So whilst it's 10 years old, it's a well trodden road, the main distro support doesn't matter, they've got/will get it into the mainline kernel and have their own distribution, it was doing pretty well on just squeeze, now in the space of a few months they've put raspbian on there (converted to run faster with vfp. Getting driver fixes and updates isn't an issue but I will concede that some issues may never get solved. But what exactly did you expect for £25 (board price)? And the chip in the PI is being used in current retail products too (not 10 years old). Of course it was meant to be a development tool, that's what teaching programming is about, development As for the pwc driver, I agree, it's been updated and messed with, bit's taken out etc. but it really doesn't feel like it's been touched for 3.x kernels. For instance, for some reason, I cannot change framerate using any of the userland tools. I also cannot capture in any resolution above 160x120 (I think that's a pi issue).
  8. Nice to see someone has tried this, I have been working on trying to get openPHD working with the philips webcams (I've got code that allows us to do long exposure already) but unfortunately right now, there is a bug in the pi usb driver that stops the philips from working at all. I had expected to look at this soon, so I'm guessing that the qhy behaves vastly differently to the philips webcam as it seems the qhy5 just works. Regards, Reggie.
  9. My son's pi has now turned up, along with my Dads The mod my pi cases are probably about the best looking out there (Imho) . There seem to be quite a lot of issues with USB devices and powering the pi. You really must make sure that you power the pi with a decent 5v supply!! 700ma phone chargers don't really quite cut the mustard, as they have a tendency to drop voltage whenever they approach full current draw. Cruddy usb cables can cause issues too, somewhere in the order of 0.5v voltage drop with the usb cables and my usb hib being plugged in I found the samsung galaxy microusb cables to be the best (they're marked with a samsung sticker with 'u2' on it). With the usb, it's important that you get a decent usb hub. the 7port cheapies off ebay *are not suitable* for the raspi, they have inadequate protection and allow power to 'backwash' down the Vusb cable. The 7 ports are really unusable unless you alter the circuit on the usb hub. As for plugging in usb devices, be aware that the pi's 2 ports can only supply a maximum of 100ma, so anything more than a simple keyboard and mouse *must* be plugged into a hub, if you don't you'll most likely trip the polyfuses on the usb ports on the pi and it'll stop working (until its cooled sufficiently for the polyfuses to re-fuse). Not all usb stuff will work out of the box, some of it may not work at all, bit of a roullette atm but the situation is improving slowly. Sd card issues are mostly sorted, most cards are correctly recognised and put into the appropriate mode/speeds, the pi is limited to 50Mhz for the emmc controller clock speed, so maximum speed you will get from an SD card is around 20MB/s, theoretical limit is 25MB/s but doubtful you'll hit that due to overheads. So even if you have got a card that's marked as '45MB/s', it will never work that fast in the pi. Perhaps in the future there might be an upgraded pi design to address the faster speeds. If you have any issues with anything at all, I would suggest trying the new debian wheezy image that the foundation released a couple of days ago, this has fixed SD drivers and other patches. There is also the Rasbian wheezy version, which should theoretically be faster than the debian image as raspbian is using 'hard float'. Cya, Reggie.
  10. try virtualbox instead? That will allow you to install XP in a virtual machine. It's free, it doesn't particularly care what host OS you're using
  11. if you can get the case open and see what major chips are on the board, I'll have look around the net and see if I can find datasheets, you never know, there might be a long exposure mod to be done....
  12. nightvision, that's why i suggested aerogel, I know the slabs of the stuff are insanely expensive but perhaps a small amount of the aerogel pellets or some of the cloth cut so that all of the heat generated by the unit is encouraged away from the sensor, towards 1 face that is left un-insulated.
  13. Finally got my hands on a raspberry pi today, all worked quite well straight out of the box. Grabbed a random 4GB microSD card, put it in an adapter, used the windows image writer software and put raspbian on the card with it, plugged in usb keyboard, mouse, internet cable and hdmi, powered the pi up, booted to the console, put username and password in, typed 'startx' hit enter, a few moments later and I'm at the desktop Opened a console and pinged the bbc, job done Very simple to use, very happy with my pi so far.
  14. Reggie

    Water Cooling

    Gina, have you sorted out the icing problem yet? I was wondering when I saw yesyes gui for his TECs and saw that he had ambient dewpoint listed, it occurred to me that once you hit that, then you will have more of a chance of moisture being attracted to the sensor? I'm wondering what other ways you could mitigate that apart from sealing the unit? I guess airflow across the sensor is a bit of a no no? Fatwoul, have you looked at xbox360/ps3 custom cooling solutions? They're designed to fit inside the meagre cases of ps3/360s might be an avenue to explore?
  15. Kind of, you can actually make your own www.aerogel.org has instructions.I was really looking at the aerogel blanket for you guys, which is considerably cheaper than the blocks, the small pellets are cheaper than the blocks too!
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.