Round the clock

[camerart]

Have you tried it?

Using your numbers with 3580 ticks around the circle:

If you're moving from 0 to 11 distance is +11.
If you're moving from 11 to 0 distance is -11.
In both cases the ABSolute value of distance is 11. If you have deadband set to 1 then you'll move because distance is larger than deadband.

If you're moving from 11 to 12 distance is +1.
If you're moving from 12 to 11 distance is -1.
In both cases the ABSolute value of distance is 1. If you have deadband set to 1 then you won't move because distance is not larger than deadband.

/Henrik.

Hi Henrik,

My system is actually 0 to 3581, so 3582 ticks/circle. I used the 0 to 11 clock face to simplify my question, so actually 11 to 0 is similar to 3283 to 0.

This is an interesting solution, if I can use it. At the moment I'm trying to unravel a pile if spaghetti with my existing program.

I have to convert it for use with the Oshonsoft system, while learning about ABS, and the ????????.15 variable. I'm not sure if Oshonsoft supports ABS, but I assume it can be got round in some way.

I'll let you know once I get it running, thanks.

C.

[HenrikOlsson]

PBP doesn't have signed 16-bit (WORD) variables so the distance.15 is simply a way to determine if the value is negative. The equivalent code, if you have signed variables, would be:

    Distance = Target - Position

    IF Distance > 1790 THEN
       Distance = Distance - 3580
    Endif

    IF Distance < -1790 THEN
       Distance = Distance + 3580
    ENDIF

/Henrik.

[camerart]

Hi Henrik,

As mentioned my system has 3582 tick/rev, so is the 3580 in the last post correct?

I don't think Oshonsoft supports negative values, but I'll check.

Thanks, C.

[HenrikOlsson]

Oh come on, think or at least do some trial and error your self now! ;-)

The ABS and Distance.15 is some "trickery" to make it work with PBP but the "clean" formulas shuld work fine with pen and paper. Try it out, make it work with the 12 hour clock example you actually asked for first. Then try wth the larger numbers, I'm sure you'll be able to figure out what needs tweaking for any number of ticks around the circle.

You were interested in the logic. This, I think, is one way of doing it but I'm sure there are others. As for how to actually implement it on Oshonshoft you're on your own or at least in the hands of someone else.

/Henrik.

[camerart]

Oh come on, think or at least do some trial and error your self now! ;-)

The ABS and Distance.15 is some "trickery" to make it work with PBP but the "clean" formulas shuld work fine with pen and paper. Try it out, make it work with the 12 hour clock example you actually asked for first. Then try wth the larger numbers, I'm sure you'll be able to figure out what needs tweaking for any number of ticks around the circle.

You were interested in the logic. This, I think, is one way of doing it but I'm sure there are others. As for how to actually implement it on Oshonshoft you're on your own or at least in the hands of someone else.

/Henrik.

Hi Henrik,

I can assure you that I'm not simply asking questions and waiting for help, as I am working hard at this end

As I'm better at visual than pen and paper, I'm trying to get it to work in Oshonsoft, which causes extra problems.

In the larger program that this code is intended to go into, I have use another way, but it doesn't lend itself to adding DEADBAND easily around the 11 to 0 jump.

I asked someone to help me convert your code to Oshonsoft, and they 'jumped the gun' and are trying to add it into my larger program. This is good if I like your code, but a waste of time if I don't!!!

C.

[camerart]

Hi,

I just got a message from the other forum, helping me to get your code working in Oshonsoft: [Testing 'distance.15' in the program will not make any difference to the Dead band angle detection, its just another way of doing what we have already done.]

So it looks to me that I have to simply keep working on my program, till I come up with a solution for adding the DEADBAND.

Thanks to all that helped me.

Camerart.