I need to do some experimenting with a thread that writes DAC samples and gets ADC samples,Gert van Loo wrote:[I will see what is possible as this seems a very specific application which would benefit more from running the whole algorithm on the board.
Beware that the ADC are not very fast (about 1 millisecond per sample) and that the DACs have only limited range.
thousands of points, and 1 ms per sample is fast enough for most of the things I want to do.Gert van Loo wrote:Furthermore I found that the DACs need to be calibrated as they seem to have a slightly different range between processors.
I will look at what it takes to produce a waveform from the DACs.
What output sample length and frequency are you thinking off?
What information is available for people who want to try writing their own gertbot code?Gert van Loo wrote:In general: the Gertbot can be bulk-erased which will remove the security bit (but also the normal code) after which anybody
can write and download their own code to it.
Sorry, I should have been more clear. I want to sample from 1 or 2 ADCs, getting thousands of samples in total, as fast as I can (like 1 or 2 ms per sample).mikronauts wrote:You will not be able to sample thousands of points every ms.
You will be able to sample thousands of points in just a bit over (number of points)*1ms
assuming you add enough multiplexers / ADC channels
No worriesexperix wrote: Sorry, I should have been more clear. I want to sample from 1 or 2 ADCs, getting thousands of samples in total, as fast as I can (like 1 or 2 ms per sample)
I will release more information over the weekend.What information is available for people who want to try writing their own gertbot code?
As promised.I will release more information over the weekend.
This requires user to reprogram the gertbot. Maybe it would be worthwhile to give it a 'baud-change' command (no board re-design needed for that apparently), or jumpers to select the baud. What is the highest reliable baud?Gert van Loo wrote: You can then switch to 115Kbaud giving you more then enough bandwidth to transport
two twelve-bit ADC's values every millisecond.
I know how hard it is to get something to the point where I feel it can be released to the ignorant masses, although I am not financially dependent on the return. I'm sure you know best where your interests lie. But I have always believed that the best, most long-lived projects are the ones that release everything and develop a user community with a vested interest in keeping it alive and improving.I would love to give out the full schematics and the software. Unfortunately there are many unscrupulous people out there.
(They call themselves "Robin Hood: Steal from the rich and give to the poor" I am not rich neither are they poor.)
It took me over a year working 96 hours a week as well as 120% of my money to get the products out,
so you can see that I am reluctant to give it all away.
Yes!Do these commands: 'Stop All', 'Execute Sync' and 'Emergency Halt' act on all boards simultaneously?
They set the board ID.What are the four pins (I think they are labelled J13) with jumpers on them near J12?
The JTAG to the controller. The pins are described in the "advanced user guide".What is J10?
I assume you mean the Raspberry-Pi GPIO pins.Does the board do anything with the GPIO pins besides the power, ground and serial port?
Many Thanks Gert will try the new firmware and give some feedbackGert van Loo wrote:Your wish has been granted!
Gertbot SW release 2.6 supports quadrature encoders.
With it come a series of new commands like:
- Set current position to X.
- Got position Y.
- Do NOT go past position MAX/MIN (as the end-stops are no longer available)
- When close to max/min/goto position start running slowly (Prevents overshoot)
Users browsing this forum: No registered users and 1 guest