Search:

@PaulStoffregen

Hi Paul, the need for a more deployable function for the button, has come up again. Is there still not adequate time or interest for this? Again, we need that the button result...

@PaulStoffregen

Hi Paul, is there any chance of this happening?

If you are too busy for this, if instructions and source available, perhaps one of us could have a go at it.

The board described in this thread was designed to provide high precision low noise signal acquisition, waveform generation and digital I/O in a programmable board with an open API that interfaces...

This might be helpful for your project. It is starts with low noise. I can probably help you with the signal processing also.

...

@FHorn

I am a little bit familiar with NI, and I am not a fan. Moreover, with their focus on expensive software (400/year to 5K/seat plus fees for deployment), it is not easy to see why they...

@notthetup Yes, it was the mccdaq and the labjacks, that led me to feel the need to do this. This is better than any of those, for a few reasons.

Here are a few of the specs that I was...

@tonton81 - No, that would not be robust for deployment and you could not use it in a professional context.

Think of it in terms of sending a board to the space station, or antartica, or a...

Defragster raises a separate point, he wants a "halt". He could do that by having a "halt" program ready to load when he pushes the button.

I feel that "Reset" aligns better with what users...

I would like to request a feature or enhancement, for the function of the button on the Teensy.

After pushing the button, if a connection is not found to an instance of the Teensy Loader (on the...

Hi Paul, the twitter response seems promising. I plan to ask for a quote today for a small production run. Will let you know how it comes out.

Great, thank you. I see two replies already, the first might be talking about a pci/pcie board from general standards, they usually go for 5-8 K$.

It takes me about four hours to build one by hand, with tweezers and a magnifier, and then a few minutes in a small reflow oven. Having the pcb service that I regularly use, do the assembly for a...

So, can we talk? I emailed you my contact info.

And yes, of course, I did plan to produce and sell the board, and would be happy to do it if there is interest. I think there a lot of researchers in science and engineering who would benefit.

I am happy to publish the python gui, and probably the firmware that runs the board as well. The intent is that it be a flexible instrumentation grade DAQ interface and still be very affordable. ...

Hi Paul, I have one extra board. I am probably going to use it in the lab. Can we talk off-line?

One of us (not me) taught the instrumentation electronics course for some decades, and now has instruments around the outer planets. We collaborated on the design and part selections. Notably, he...

What are the design goals and requirements for the 4.0? How does it differ, at a high level, from the 3.x boards?

In numerous postings it has been said that the limit for the Teensy ADC is substantially less than 16 and less than the performance metrics stated in the processor data sheets. However, measurements...

Would it meet your requirements to have a similar sort of board that has a mount for the teensy, and with fast high precision ADC's on it? I need to check the interfaces available on the teensy...

if you like we can continue in email

I'll have to go back and see what we did, but as i recall, on the Teensy 3.1, the default vref is a filtered version of the VOUT33. I am pretty sure that 3.3V is our full scale at the input to the...

Yep, the DAC is 12 bits. We run it through a nice driver circuit, which you can see in the lower left part of the board, and indeed 12 bits is what we see.

We're getting 16 bits at 300 ks/s. The data that was listed in our thread is showing noise at less than 1 LSB at 200 ks/s.

I am getting 16 bits, using the on board ADC, and an instrumentation grade input design with surface mount parts.

See this:

https://forum.pjrc.com/threads/53173-USB-DAQ-with-the-Teensy

Your requirement to acquire 16 bit data at 1, 2, 10 MHz, seems to exceed the maximum sampling rate of the on-board analog input as listed in the data sheet.

See...

In fact, the noise that I reported for our design in #6 above (0.05 mv to 0.08 mv), does not change when I run other interfaces at the same time. It stays in the 10^-5V range.

In the picture in...

See https://forum.pjrc.com/threads/53173-USB-DAQ-with-the-Teensy

I get 16 bits, no problem. I use an instrumentation grade front end with some specific circuit design to deal with the Teeny's...

DAQ vendors in general are miserable sources of DAQ software, and very few are conscientious even about their hardware.

That in part, is why I built this. I needed a system with strong...

The GUI is written in Python, and I have run it on Linux, Windows 10, and Windows 7, and desktops and laptops for each. I have not seen any crashes.

A few weeks should be easy. Assuming careful design, the limits are usually storage, cooling and power.

See my post at https://forum.pjrc.com/threads/53173-USB-DAQ-with-the-Teensy

Scroll down to post #6, the analog input noise is at 1 bit in 16 bits.

See my post at https://forum.pjrc.com/threads/53173-USB-DAQ-with-the-Teensy

I have some experience in this area. For example, I have developed systems with similar specs for extended deployments on the ocean floor.

For a Teensy Data Acq board that would be suitable for...

Here are signal and noise measurement for the four inputs in 16 bit mode, with the first three channels unconnected, and the output from the DAC set at 1.0 V and connected to Ain3. Notice that the...

Here is a capacitance measurement, it was made by measuring amplitudes as a function of frequency. The parallel resistance refers to leakage current.

In addition to the conventiional DAQ...

I am indeed willing to share. This is a screen shot of the python GUI that we use for testing our solid state lighting devices. You'll notice that it is pretty quiet, even though I just now ran it...

I want to add that the noise performance for the Teensy DAQ board is better than 0.1 mV.

Working with a senior instrumentation specialist, we have implemented a USB DAQ module using the Teensy 3.2, with analog circuits designed around the electrical characteristics of the Teensy ADCs and...

BTW guys, everything is working/ Thank you all for you suggestions and help in every form.

I worked it out, from the hardware documents. Its about 10 lines and runs two adc channels at 330 kHz, with a dac write in the loop, and all with less than 0.1% jitter. That should tighten-up with...

I'd like to chime in here.

I come to this with about 40 years experience in real time and systems. I've deployed code on platforms from DSPS to racks and with data rates at the physical limits of...

Correction, that's 330KHz

It worked out. By hand coding the ADC, using default settings and both ADC0 and ADC1, two channels can be sampled together at 1.1 MHz. That should be plenty fast enough for what I need to do. I...

Yes, I saw that, it might provide some useful examples for the setups, but it has a lot more going on. my first impression is that it might be easier to just read the hardware manuals.

To manitou, that is a fantastically useful link. thank you

And to Theremingenieur, yes, that is exactly what I plan to do. again, thank you

I'll likely switch to the ADC library from the...

Yes, but it seems clear now that the best route is going to be to work with the chip directly and not use the libraries. I may continue with the library as a stop gap, until i finish building up...

Follow up, from the documentation


bool ADC::startSynchronizedContinuous ( uint8_t pin0,
uint8_t pin1
)

Starts a continuous conversion in both ADCs simultaneously.

Okay, here is a truly, minimum example. The only edits are that each ISR has its own counter, and increments that counter each time it is called. The 'p' command lists the three counters.

The...

Look at the PDB ISR. There you will see that it increments a counter pdbknt

Also, each of the two ADC ISRs has its own counter, for ADC0 it is nbuf, and for ADC1 it is nbuf2

When the...