Thread: Rotate Images, Logic Builder, Counters

Originally Posted by keyvan

Hey Dan thanks for your reply, could you please elaborate, perhaps provide a link? I'd love to be exposed to all the options so as to pick the best one. In return I will keep you all posted and post pics and tutorials and whatnot.

Well, I maybe spoke before reading every word of your post. I was thinking of speedometer pulse generators for cars, not motorcycles.

If a bike has the same mounting method as a car, you might be able to use one.

Here is a link to a Dakota Digital unit from Summit Racing:

http://store.summitracing.com/partde...5&autoview=sku

I changed my then statement to read d+1, it counts, except the condition is maintained as true when I have the photointerrupter interrupted, so the counter just keeps counting as the timer loops.... Is there a way to have it count ONCE per condition? Or say, every time the voltage changes by a range of 3 volts or more, add 1 to the counter variable?

Thanks.

Dan thanks for the link, that might be useful if I can't manage to do it this way...

Originally Posted by keyvan

I changed my then statement to read d+1, it counts, except the condition is maintained as true when I have the photointerrupter interrupted, so the counter just keeps counting as the timer loops.... Is there a way to have it count ONCE per condition? Or say, every time the voltage changes by a range of 3 volts or more, add 1 to the counter variable?

Thanks.

Dan thanks for the link, that might be useful if I can't manage to do it this way...

need more logic then.

easiest is like this...

logic 1:
if input > value then variable++ else variable=0

logic 2:
if variable == 1 then count_variable++ else nothing

without thinking all the way through this I think that does what you want. Still on vacation mode

hey thanks nick, ill try it when i get home and let you know

EDIT:

I tried that. set up another variable, so to restate, this is what i did:

Logic 1: If Input > 1 then x++ (Vote Opinion: d+1), else x=0 (VO: 0)
That works, if the input is 5v (Sensor blocked), x keeps increasing, when I unblock the sensor, x returns to 0.

Logic 2: If x=1, then y++ (VO: d+1), else nothing.

Here's what happens when I test:
Interrupted: x increases constantly, and y increases constantly as well! Doesn't follow the logic!
Uninterrupted: x reverts to 0, y stays at whatever value it was at last (this is fine).

Why does y continue to increase even though x is no longer equal to zero and is continuing to increase? The state of x=1 should be false as soon as x no longer equals 1 and continues to climb, thus y should not increase anymore, it should only have increased one time.

EDIT: Got it working, see my next post.

Found a fix.

I changed logic 2, it is now the following:

When x is greater than 0 and less than 2 (so when x=1), then do y++.

Works now, attached logic diagram (I'm trying to be as thorough as possible to help others )

Nick, why didn't the first way work? Is the "==" module bugged?


So I tried testing this by running a comb through the photointerrupter... It fails to count every tooth... And about 30% of the time, it counts it twice... even if I run it through pretty slowly. If you care, I can take a video of the screen and the comb and the values of the variables. For my purposes I might just have to use a different method altogether. Would have been nice to use the photointerrupter though since I've now got it working in fusion brain (for the most part.)


Right now the logic function is not between 0 and 2, it's between 0.9 and 1.1, i thought that might decrease the likelyhood of error, but doesn't seem to have made a difference.

Originally Posted by 2k1Toaster

Thanks for the praise!
In one of the earlier versions there is a gtr inspired skin that is ina folder in the MDX source directory or maybe the bin/debug area with the name of gtr or str or something like that. If you cant find it I will see if Tim has a copy he can post up.

There was no rotating image in there that I could find, only static, multi, and variable-location. I'll dig deeper and see if at least the settings are there....

But that's fine because the skin just showed me the idea of having a gauge within which a bar fills up, which is actually a lot cooler to me than an arrow pointing to a value like a conventional gauge.

Originally Posted by RonS

If you do a search in google for freq to voltage you will find a few million links. Or do a search for LM2907. That will get you what you want.

Thanks, this thread has become a very good reference for me. I'll look into this if my microcontroller route doesnt work out. Not sure if I mentioned this already, but I'm just going to program a microcontroller to do this job.. you can see my AVRFreaks forum post here: (some good advice there too, and another world for those that want to try something a little bit more in-depth than the fusion brain, although I'm going to interface my MCU back into the fusion brain for displaying everything): http://www.avrfreaks.net/index.php?n...=528752#528752

NICK, I have another question for ya:

If my signal is about 5.10v, will it register on the FB? Will it fry it?

When my fuel gauge is empty, and the engine is on, the voltage sits between 5.02v and 5.09v..... I am hoping I don't have to use a voltage divider for this. Else, I would just make my "empty" occur one notch sooner on the fusion brain, right before I get to 5 volts.. I just don't want to end up riding it all the way to empty empty one day and fry my FB in the meantime.

Thanks

Anything above 5v is not good for the FB and you risk damage. You arent over that much so the microchip itself should be ok (no guarentees) but it will only read in 5v, it will not read in 5.xx.