Moving Faders in timer() or tick()

[ThomasT]

Hi,

I'm just debugging an update of my software.

I wanted to delay the fader movement so I tried to move them (after timing mechanism)

in main::tick() or main::timer().

But this do not work correctly.

Before I do further debugging I just want to asks if this can causes problems.

Sometimes the fader moves, sometimes they don't. And there seems to be no rule.

So I suspect a problem with interupt handling or something like this.

Normal direct fader movment works perfectly.

What's this for you my asks...

I have 4 midiboxes with 8 faders each. Don't know why, but my ALPS faders take

more current that Thorsten descriped. I think up to 700mA accourding datasheet.

The problem is that my power supply offers only 5A on 12V.  So I have only 150mA

per faders. Thats not enough so movement of all faders together will not work properly.

My idea was to delay the movement depending on the midibox id.

midibox 4 moves directly, the next 8 faders of midibox 3 1s later, midibox 2 2s later

midibox 1 3s later. Maybe the times need improvment. Why, midibox 1 as last and midibox 4

as first? The faders of midibox 4 moves faster. The ones of midibox 1 slowest. Don't know why.

My be an problem of usage. (lower channels vs. higher channels)

Only on events that causes movements of all faders. These are, reset (per menu or startup)

and snap shot recall. In all other cases the faders move directly of cause.

Thanks for any ideas.

Thomas

If this will work I will publish my whole code. But not before.

[cinhcet]

Hello Thomas,

what kind of Alps Motorfaders do you use? With how much voltage do you supply them?(should about 8V)

My MFs need only 1A if all move.

bye

Edit:

By the way, what are you going to build?

[ThomasT]

Hello Thomas,

what kind of Alps Motorfaders do you use?

Puh...I don't remember the number. But they are on Thorsten's list.

By the way, what are you going to build?

I have already built...I just wnat to do some improvement because I had some other

things to fix, so I wanted to update the software as well.

Just as an importent tipp: never combine midiboxes as I did. Chain them as single

*independent* devices. -> debug horror.

http://www.krachwerk.de/projekte.html

http://www.krachwerk.de/midibox/midibox.html

[cinhcet]

your midibox very impressive!!!

[stryd_one]

The problem is that my power supply offers only 5A on 12V.

...

My idea was to delay the movement depending on the midibox id.

Sounds like you should fix your PSU first..........

The faders of midibox 4 moves faster. The ones of midibox 1 slowest. Don't know why.

Sounds like you have the power wired in serial.

[ThomasT]

Sounds like you should fix your PSU first..........

What do you mean with "fix"?

Do you have an idea what a PSU for 22A looks like?

Its not worth the efford, in normal operating it needs 2A or so.

Sounds like you have the power wired in serial.

How should this be?

No I havent.

[TK.]

I don't see a reason why MIOS_MF_FaderMove() should behave different if called from another hook, it should even work from an interrupt service routine.

But there could be an issue with the "manual move detection", because your faders are not moved precisely enough, so that the driver "assumes" that they are manually moved. In such a case, MIOS_MF_FaderMove() positions will be ignored for a short timespan.

In order to overcome this, just call MIOS_MF_TouchDetectionReset(<fader-number>) before calling MIOS_MF_FaderMove(<fader-number>, <new-position>)

Best Regards, Thorsten.

[ThomasT]

I don't see a reason why MIOS_MF_FaderMove() should behave different if called from another hook, it should even work from an interrupt service routine.

Thanks. Good to know.

MF_TouchDetectionReset(<fader-number>) before calling MIOS_MF_FaderMove(<fader-number>, <new-position>)

I'll try that.