--
You received this message because you are subscribed to the Google Groups "Open Software Radio Peripheral" group.
To post to this group, send email to open-software-r...@googlegroups.com.
To unsubscribe from this group, send email to open-software-radio-p...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/open-software-radio-peripheral?hl=en.
Do you think you can handle the IDE protocols? Usually IDE devices in operating
systems are recognized as storage devices with storage device drivers.
I guess the hard drive protocol is not suited for such applications
and that a new communication protocol has to be defined.
For USB 3 there might be a possibility to use the driver from USRP1
with slight modifications.
Another problem of IDE: I don't have free slots any more.
My laptop has no slot at all.
Why not using USB2 for cheap devices and USB3/Ethernet
for higher-bandwidth devices?
At least SCSI is used for other than storage devices, like scanners.
> My interest in using PATAPI lay in the simple use of cheap hardware to
> convert the PATAPI interface into USB 2.0/3.0, or ESATA, or Firewire.
> Basically whatever you want easily.
But I think also the drivers convert IDE storage devices to standard
USB storage devices. I didn't need a special driver for the IDE to USB
hard drive connector. Surely you would have to develop a special driver
to handle "alternative" IDE devices. It would be kind of low-level if
the IO-pins have to be controlled individually. Usually, there is also
a master-slave system for IDE drives sharing a bus. But I don't know the
details of this protocol.
Possibly an advantage: if the IO pins could be controlled individually,
it might not need a special controller chip for the ADC.
Just connecting the ADC parallel pins to the IDE, plus a few control lines.
Will it work this way? Needs a pin-count ...
> plus PATAPI already runs at 100 Megabytes/sec Farhad claims it can be
> made to run up to 200MB/s, in any case way faster then USB 2.0, and
> 100BaseT Ethernet
Data rates are Ok. But for a low-cost solution, also the USB 2
data rate would be sufficient to cover about 10 MHz bandwith.
> other then my vote for PATAPI, I'm also in favor of using Gigabit
> ethernet, followed by USB 3.0
With USB 3 you are still USB 2 compatible at lower data rates.
Ethernet has the advantage that it can be switched on a local
network, it facilitates cabling, and it allows very long lines
(only a few meters for USB and IDE).
So, you could place the hardware close to the antenna, control
the device via network cables. It can save many valuable Decibels
of RF power.
At least SCSI is used for other than storage devices, like scanners.
A. I still have to research further just how much of the SCSI protocols are used in the latest stable version of the ATAPI standard.
But I think also the drivers convert IDE storage devices to standard
USB storage devices. I didn't need a special driver for the IDE to USB
hard drive connector. Surely you would have to develop a special driver
to handle "alternative" IDE devices. It would be kind of low-level if
the IO-pins have to be controlled individually. Usually, there is also
a master-slave system for IDE drives sharing a bus. But I don't know the
details of this protocol.
Possibly an advantage: if the IO pins could be controlled individually,
it might not need a special controller chip for the ADC.
Just connecting the ADC parallel pins to the IDE, plus a few control lines.
Will it work this way? Needs a pin-count ...
Data rates are Ok. But for a low-cost solution, also the USB 2
data rate would be sufficient to cover about 10 MHz bandwith.
With USB 3 you are still USB 2 compatible at lower data rates.
Ethernet has the advantage that it can be switched on a local
network, it facilitates cabling, and it allows very long lines
(only a few meters for USB and IDE).
So, you could place the hardware close to the antenna, control
the device via network cables. It can save many valuable Decibels
of RF power.