More about those buttons

[Ian_Hurlock]

Ok thanks for the help with the last post TK

That helped a bit.

I ended by pasting the notify toggle goodies out of the 128 ain din etc example.

;)

The buttons now work on individual pins straight after my last encoder.

Now here's the RUB

I have a button connected to din 48 , as shown on the lcd when the button is pushed.

However the information it transmits to midi is found at MT_ ENTRY number 53.

That is the  5th entry in the 0x30-0x3f sr range.

I can edit this entry and the value is sent by midi as edited when the button is pushed.

I don't know why the the button I push says 48 on lcd but is really 53. ???

Thnks again for your help

Ian

[TK.]

Hi Ian,

is this entry located to the correct address? Maybe it has been changed during your modifications. Just take a look into the main.lst file, search for "MIOS_MPROC_EVENT_TABLE" and ensure that it is located at 0x003080:

003080                00063 MIOS_MPROC_EVENT_TABLE

The entry for button #48 (==0x30 hexadecimal) should be located at 0x0030E0:

                      00118         ;; entry 0x30-0x3f
                      00119         MT_ENTRY        0xb0, 0x30
0030E0 30B0               M         dw      (0x30    << 8) | 0xb0

Best Regards, Thorsten.

[Ian_Hurlock]

Thank you TK for your reply.

The entry was in the right place as you pointed out.

What bothered me was that I could not add my button parameters as the next entry in the list under the last encoder.

I now realise that the total din inputs for the 24 encoders used adds up to 48 so the next entry had to be after that, so I counted down the list and put it at number 48 in the list. ;)

Took me 3 days but I tell you what when you've sorted it out you give praise to MIOS and to TK for the wonderous toy he has made for all 8) 8) 8) 8) 8)

Tip for others that may suffer as I have :

I typed the numbers of the din inputs next to the list in the MIOS_MPROC_EVENT_TABLE from 0 to 127 and all my worries were over.

Later

Ian

PS. And you thought only Steve C answered his own posts ;) ;)