stereofan
Jul 02, 2006, 10:46 AM
I'm facing a large learning curve since I've just recently become interested in radio and diy electronics. I'm comfortable with most of the terminology and some of the concepts, but I need help to execute my plan and I'm unsure of the best solution: I've already priced and planned a live video feedback project using a/v cabling.. the multiplexer comes out to be the most expensive part since I need to place two genlocked cameras in stereo parallax and broadcast field-sequenced ntsc (or page-flipped vga) to get a 3d signal.
I'm trying to figure out how to minimize hardware size and power demands. In considering a wireless version, I'm wondering whether -- a) in the ntsc (or pal) version, using a timing switch or alternately hopping frequencies according to the timing of even/odd field acquisition is better in terms of stability, ease of assembly and expense; and b) in using the vga mode (for which, in sufficient quantity, I can get genlockable sensors) what is the minimum amount of hardware I can get away with? Most people tell me to use a pc, but I've gotten the idea that ICs and microcontrollers (perhaps GPUs, too) are the way to go.
The range on this project is tiny -- within 10 meters, so I'm also looking at using a specification called ZigBee which is used for Wireless Personal Area Networks. The spec on this, however, is 250 kbit/sec on the 2.4 GHz band and I don't yet know the data transmission demands for stereovideo (nor have I looked at the data transmission reduction resulting from using an MPEG-4 codec).
If I hopped frequencies, I'd want to switch the receiver up and down while holding the transmission constant on two separate bands; if I use a timing switch, I suppose I have the option of powering the circuit off/down (off probably causes too much noise, down would limit transmission radius, effectively switching the received signal -- although I'm unsure of the signal graphs and timing you would have to use) or... using a capacitor-based shunt, maybe?
I'm sure that if I undertake this wireless design, there are amateur to pro considerations that I might not take into account :confused: and that I certainly don't have enough background to spec out these considerations,:eek: although I might have enough to evaluate the options once I know how to contextualize the options and/or have the facts at my fingertips.
Thanks in advance to the DIY Electronics RC Groups forum for the time and expertise provided -- I hope this discussion will prove fruitful.
I'm trying to figure out how to minimize hardware size and power demands. In considering a wireless version, I'm wondering whether -- a) in the ntsc (or pal) version, using a timing switch or alternately hopping frequencies according to the timing of even/odd field acquisition is better in terms of stability, ease of assembly and expense; and b) in using the vga mode (for which, in sufficient quantity, I can get genlockable sensors) what is the minimum amount of hardware I can get away with? Most people tell me to use a pc, but I've gotten the idea that ICs and microcontrollers (perhaps GPUs, too) are the way to go.
The range on this project is tiny -- within 10 meters, so I'm also looking at using a specification called ZigBee which is used for Wireless Personal Area Networks. The spec on this, however, is 250 kbit/sec on the 2.4 GHz band and I don't yet know the data transmission demands for stereovideo (nor have I looked at the data transmission reduction resulting from using an MPEG-4 codec).
If I hopped frequencies, I'd want to switch the receiver up and down while holding the transmission constant on two separate bands; if I use a timing switch, I suppose I have the option of powering the circuit off/down (off probably causes too much noise, down would limit transmission radius, effectively switching the received signal -- although I'm unsure of the signal graphs and timing you would have to use) or... using a capacitor-based shunt, maybe?
I'm sure that if I undertake this wireless design, there are amateur to pro considerations that I might not take into account :confused: and that I certainly don't have enough background to spec out these considerations,:eek: although I might have enough to evaluate the options once I know how to contextualize the options and/or have the facts at my fingertips.
Thanks in advance to the DIY Electronics RC Groups forum for the time and expertise provided -- I hope this discussion will prove fruitful.