DSP Robotics Support

I thought it would be good if had a "standard" Ruby Counter,
that everyone can use and modify straight away.
This is what i got so far. Not much, but it works.

I'd like to start with a re-set trigger. I can't work it out yet...keep failing.

Tried with timer/delay after afterload?

not yet.tried lots of things...its really fun to fail at this.
Learning heaps but nothing i try works
next attempt in 12 hours...bummer..

That is the same result I can get.
We are calling Ruby time.
I decided to make a tick counter instead, with my homebrew seq method.
Hopefully trog might pop in here and shed some light on this.
The current counter u have made gives the time since the Ruby component is turned on I think.
All success

nix wrote:decided to make a tick counter instead, with my homebrew seq

Yeh I somehow missed it, or forgot it, but it's doing the trick for me at the moment.
The homebrew seq is great man...I'm always using it, to check something or to pull something out
A great "playground" for ruby noobs to cut their teeth...
I know you've taken it underground, but if it dosn't work out there, seriously consider
expanding the whole thing and turning it into a massive "tweakable" tutorial.

I have this...


Not sure it suits your needs...

tektoog wrote:Not sure it suits your needs...

Thanks mate. Unfortunatly, no, it dosn't suit, as your cheating...

The general Plan is for a ruby module with in's/out's like these.


I don't mind spending the next 6 months, chipping away at this..... all good...great fun
It's just that a "counter" is a "crucial" building block, and i thought it might be better
to create it faster, so people can get on with more important stuff.

But yeh, I'm enjoying it. Spent another hour yesterday failing, trying from other perspectives.
I'll get it one day.
Good entertainment for the "Ruby guru's" as well, watching a ruby noob struggle with 1+1=2.

billv wrote:it dosn't suit, as your cheating...

Hehe, ok...
I wasn't sure if it was a "total ruby counter" you were after...
now, I know!
I'll try to get in if I can...

tektoog wrote:I'll try to get in if I can..

Cheers mate. don't sweat it. No real hurry.

It's just so weird. I got a signal going in, and all i want to do is stick a number on each signal.
And I still can't do it....
I'm glad I've got Nix's example, which clearly shows a method that semms to work, so i can work of
that a bit.
It's just real dissapointing I still can't work out how to do it on my own.

I think it's best if i maybe fork out some cash for a few lessons by a pro tutor or something.
Cause it's just not happening here. The skills i picked up doing visual basic a few years back
are not returning and i'm sick of waiting for them to turn up
The learning curve is just too much at the moment........hhhhhmmmmmmm

Here's a counter that should cover most bases...

...it's not necessarily the most efficient code - but written with lots of comments that will hopefully make it useful to learn from.

One little note of caution though...
If you are working entirely with 'green' inputs/outputs, a Ruby based counter like this one may not be the best solution. The stock counters will be super-fast compiled 'C' routines, whereas Ruby has to run in its interpreter - so it's probably best to carry on using the old ones, unless your schematic has special requirements that need extra features.