More info



First of all, thanks for the replies so far.

Actually, we need to develop a final product with all the embedded
hardware designed in a case: PCB for the controller and for the
input/output modules.

The NI solution is very interesting and fast, but as far as I could
understand I will have to start from "zero" to design the final hardware.

For this reason, it is important to start working with a development kit
that offers most of the needed devices.

The Labview is being considered to develop a prototype. A DAC board is
being considered to generate the analog signals (simulating a conditioned
signal) used for the ADC inputs. Then, the digitalized signal is going to
be fed (using SPI, Parallel, etc) to the controller.

For the controller, I have seen so far two options:
1. From Atmel, the DIOPSIS 940HF
2. From TI, the TMS320F3812
cause both combine DSP and uC.

For the ADC, I am looking for an evaluation board that offers simultaneous
sampling for many channels (preferably as many as possible, since we need
at least 40 analog channels). So far, I found some options from TI:
- ADS8365, but uses parallel output
- ADS1178, that uses SPI

Since a lot of data is to be stored, it is also important to have at least
16-32Mb of SRAM, and a higher mass storage media such as SD cards of
2-4GB.

Digital input varying from 24 to 250Vdc is also needed: at least 2 times
the number of analog channels, which means at least 80 DI. Again, for the
prototype, a DO board with Labview is being considered.

Digital output for alarm purposes is also considered.

Communications features (Ethernet, USB) is basic requirement, as it is
also a keypad, LCD, etc.

When the prototype with the "final" firmware is designed, then the final
PCB input modules together with the controller PCB will be developed. The
test will be carried out using a digital box capable to generate the real
analog values coming from the field: currents ranging from 1 to 20pu (1 pu
equals to 1 or 5A) and voltages ranging from 1 to 2pu (1 pu equals to 66 or
115V).

But for prototyping, the ADC board and the controller are the critical
hardware components that I need to define until next week.

Well, that is the "architecture" we have envisaged so far. Any ideas are
welcomed.

Hope I was clear enough. Any other detail, please, just ask me.

Thanks again for all.
.



Relevant Pages

  • Re: Data Acquisition - More details
    ... understand I will have to start from "zero" to design the final hardware. ... be fed to the controller. ... PCB input modules together with the controller PCB will be developed. ...
    (comp.dsp)
  • Re: Has anyone produced a board using Kicad?
    ... I've provided demonstratable boards to Harry, DJ, etc that demonstrate ... gschem and PCB is painful at best. ... pull spice data for not only the design, ... I'm an avid hardware hobbiest, and most of the really dense and fun ...
    (sci.electronics.cad)
  • Re: crazy boost converter for LED use is too noisy!
    ... it is needless to say that the inductor and associated PCB traces ... Should I thrown the design in the bin and start over with a more ... make a controller from scratch too:P ...
    (sci.electronics.design)
  • Re: DC Motor Control: H-Bridge +5A, 48v
    ... >>developing their own controller. ... > hardware design projects. ... > PCB, and power supply / hydraulic coil driver PCB for the ECHO ... One of my experiences with customer service early on involved, ...
    (sci.electronics.design)
  • Re: why multiple controllers for multiple speeds?
    ... |> Why does USB have to have multiple controllers for multiple speeds? ... |> But what I see is that things like a USB controller that has both 1.1 ... Sounds to me like we should not be allowing hardware manufacturers to be ... at that point I'd design a generic DMA BUS message passing scheme for ...
    (comp.os.linux.hardware)