robinfawell

I have nearly finished my FATAR based digital piano. It is working with the code kindly written by TK with some minor work by me with on the soft and sustain pedals. The case and stand are complete. The piano works well with two exceptions. 1) As suggested by TK, I want the Keyboard Max and Min delay variables to be defined by two Hex switches. There is an unused section of the scan matrix that I have used successfully to control the pedals referred to above. I have also tried to use the "empty" switch positions of the matrix with the hex switches and although it works to some extent, it is not convenient. I want to program to read the two hex switches immediately after switch-on. I don't need them to be variable during normal operation. Is it feasible to incorporate the relevant code into the initialisation section where it can be read and used by the system.? Incidentally it is very difficult to decide on suitable values. At present I am using a fast delay of 4 and a slow delay of 60. My current thinking is that I may need to reduce the latter(perhaps to 30). I am thinking of using the IO's of J5B and J5C for the 2 X 4 inputs from the hex switches. I believe that the main problem in trying to use the scan matrix is that that the switches are only read when the values change. 2) System speed. The resolution of the delay referred to in 1) above is 1 mS. I would like reduce this value progressively. I have looked in the repository to find where the frequency is pre-scaled without success. There may be several other changes needed to speed up the application. Any pointers would be appreciated. Regards Robin

John My project is working in terms of generating the 88 piano notes. I have also made some (minor) code changes to enable the use of the sustain and soft pedal. I am using the midibox based on MIOS32 to generate midi which then passes to a PC running Pianoteq which is a piano softsynth. I have not had the time recently to complete the case woodwork and to box in the pedals. There is more work to do on the resolution/ accuracy of the time delay. It is this delay that is used to determine the velocity (loudness) of each note. Your project is an organ project which may not need the velocity sensing. The C code for generating midi is much simpler in that case. In my organ project I used an obsolete Roland Synth. If I was starting today I would use a PC organ synth. However my knowledge of these synths is very small. The later MIOS32 system is ready made for USB interfacing. However you could use the older hardware if you want. There is no need to use the QBas matrix. Modify TK's fast scan example. You will find this in the Repository. To do this you will need to learn some C programming. Look at the information in the doc folder in fastscan_button_matrix_16x16 and in the app file. The latter contains the C code. At this stage do not be put off by the code. Most of the difficult code was programmed by TK for the velocity sensing aspects. I will try to help you if I can. Dealing with note generation is not that difficult. I am guessing that the stops should also be achievable. Let me know which system you will use. Robin

There is a strong recommendation not to exceed the 16 bit Shift Register Max. See Tutorial 009. There are two possibilities that occur. Use line drivers between the core and the SR's. See Duggle's work. Use 2 cores and split the matrix. Regards Robin

Thanks very much Thorsten I will try this approach. It is much better to use the existing Example Fast Scan Matrix rather than introducing myJ5 method. Regards Robin

Thanks Thorsten It was useful to have the confirmation that J5 could have a mix of inputs and outputs. I looked at the connections again and found that I had transposed 2 of the 3 cables to the small J5 diode matrix board. Silly me! At this point in time I have proved that MIOS32_BOARD_J5_PinSet works for both pins 8 and 9. Now I need to program these operations sequentially. Once this task is completed I need to integrate the modified 006 RTOS tutorial into the Fast Matrix Scan Example. You will recall that I initially tried to use the Fast Scan Matrix Example with the 2 Pedals and 3 hex switches. The Pedals are made by the keyboard manufacturer, Fatar. They seem to be using the same type of switch for the pedal as they use for the keys ie a membrane switch; this type seems to have little or no bounce. It worked fine with the Pedals but gave unpredictable results with both types of hex switch. The Midi Channel switch will be fitted on the small console is a Cherry type Series E (0-9, A-F). The other type will be used to control the Delay variables to alter the velocity response. These will not be on show, They are a small pcb type and are are mounted on the J5 Diode Matrix board. The problem I think is that the Fast Matrix scan program deals with detecting 1-0 transitions. The hex switches rely on 4 wipers making contact with pcb tracks arranged to produce a parallel 4 output Hex code. There is an inherent lack of precision whereby the final contact should produce a 1 but is preceded by a 1-0 transition. The 1 state will not be detected. Hence an error is made. For these reasons I decided to opt for the J5 matrix approach. Many thanks again. Robin

I sent this message before. After sending it, I thought that I could program the input to the input using "J5 set" It may well have this effect, internally but it will not drive my diode matrix.I need a Digital output. Have a look at the initialisation code. I have progressed a little using Tutorial 006 RTOS and have programmed the behaviour of the hex and other switches to J5 inputs. I used a lead connected to OV as the ""row enable" for my 2 X 8 matrix using J5. I then tried to use pin 8 and 9 of J5 as outputs. I have initialised the pins as follows MIOS32_BOARD_LED_Init(0xffffffff); // initialize pins 0 - 7 of J5A, J5B and J5C as inputs with internal Pull-Up int pin; for(pin=0; pin<8; ++pin)// only 8 Inputs - leaves 4 Outputs MIOS32_BOARD_J5_PinInit(pin, MIOS32_BOARD_PIN_MODE_INPUT_PU); for (pin=8; pin <12; ++pin) MIOS32_BOARD_J5_PinInit(pin, MIOS32_BOARD_PIN_MODE_OUTPUT_PP); and have programmed the output pin to be 0V as follows. //s32 MIOS32_BOARD_J5_PinSet ( u8 pin, u8 value) //set J5 pin 8 to 0 MIOS32_BOARD_J5_PinSet (8, 0); I have checked all 4 output pins they are all 3v. I have looked at the code on MIOS32_BOARD .c but can not see that I have overlooked anything. I have tried many variations but I cannot manage to change the state of the the output pins 8 and 9. I'm very frustrated! I will appreciate any help. Robin

I should point out that Thorsten, with some donkey work from me, has completed the program code in C for an 88 key Fatar velocity scanned keybed. This is based on MIOS32. You will see it in the examples. To see this you you will need to download the MIOS32 repository. I'm trying at the moment to add a Midi Channel switch, a Sustain and Soft pedal switches to complete the project. You will see that currently I'm having some difficulties in trying to use the J5 pins for that purpose. I am delighted with the results. The softsynth I'm using is from Pianissimo which is one of the cheapest. Providing the Fatar switching is the same, it will be easy to adapt Thorsten's work for a smaller keybed (keyboard). If you want any help let me know. Robin

I have progressed a little using Tutorial 006 RTOS and have programmed the behaviour of the hex and other switches to J5 inputs. I used a lead connected to OV as the ""row enable" for my 2 X 8 matrix using J5. I then tried to use pin 8 and 9 of J5 as outputs. I have initialised the pins as follows MIOS32_BOARD_LED_Init(0xffffffff); // initialize pins 0 - 7 of J5A, J5B and J5C as inputs with internal Pull-Up int pin; for(pin=0; pin<8; ++pin)// only 8 Inputs - leaves 4 Outputs MIOS32_BOARD_J5_PinInit(pin, MIOS32_BOARD_PIN_MODE_INPUT_PU); for (pin=8; pin <12; ++pin) MIOS32_BOARD_J5_PinInit(pin, MIOS32_BOARD_PIN_MODE_OUTPUT_PP); and have programmed the output pin to be 0V as follows. //s32 MIOS32_BOARD_J5_PinSet ( u8 pin, u8 value) //set J5 pin 8 to 0 MIOS32_BOARD_J5_PinSet (8, 0); I have checked all 4 output pins they are all 3v. I have looked at the code on MIOS32_BOARD .c but can not see that I have overlooked anything. Please help. Robin

Dear All I have moved on a little since the previous message. One thought is to use J5 A,B and C pins. It seems possible to use the 12 pins, 8 pins could be configured as digital inputs and up to 4 pins as digital output. The combination could be used with diodes to provide a 4 X 8 diode matrix. This would provide more than enough scanned pins for my current needs needs. I will use Tutorial 5 and 6 as a starting point. I'm not too sure about the integration with Thorsten's Fast Scan Matrix example and the RTOS aspects. More later. Robin

I'm having some problems in trying to use a rotary switch to change the the Midi Channel. There are some unused Shift Registers locations that I refer to as BANK 0 and BANK 1. See attached Table I have allocated pins 80, 81, 82, 83 to the pins of the the HEX switch and had hoped to generate values (1 - 9) and (a - f). I have used pins 84 and 85 to connect to the soft pedal and the sustain pedal switches. The code for both is shown //non-key switches if((column >=0 && column <=7 ) && (row >= 10 && row <= 11)){ pin = 8* row + column; if(pin == 84 && pin_value == 0) { // send soft pedal CC MIOS32_MIDI_SendCC (KEYBOARD_MIDI_PORT,KEYBOARD_MIDI_CHN, 67, 127 ) ;} if(pin == 84 && pin_value == 1) { MIOS32_MIDI_SendCC (KEYBOARD_MIDI_PORT, KEYBOARD_MIDI_CHN, 67, 0 );} if(pin == 85 && pin_value == 0) {// send sustain pedal CC MIOS32_MIDI_SendCC (KEYBOARD_MIDI_PORT,KEYBOARD_MIDI_CHN , 64, 127 );} if(pin == 85 && pin_value == 1) { MIOS32_MIDI_SendCC (KEYBOARD_MIDI_PORT,KEYBOARD_MIDI_CHN , 64, 0 );} //channel select //uses pins (80 - 83) with 16 bit rotary Switch to give (0 - 9, a - f) "Red Code" if (pin == 80 && pin_value == 0) { w = 1;} //lsd bit if (pin == 80 && pin_value == 1) { w = 0;} //lsd bit if (pin == 81 && pin_value == 0) { x = 2;} if (pin == 81 && pin_value == 1) { x = 0;} if (pin == 82 && pin_value == 0) { y = 4;} if (pin == 82 && pin_value == 1) { y = 0;} if (pin == 83 && pin_value == 0) { z = 8;} //msd bit if (pin == 83 && pin_value == 1) { z = 0;} //msd bit //Chn = (w + x + y + z); "End of Red Code" MIOS32_MIDI_SendCC (KEYBOARD_MIDI_PORT,(w + x + y + z) , 30 , 0);// 30 (0x1e)undefined, 0 arbitrary } //right hand keys The system does change the midi channel but the code in red does not work. I get only get a few channel values. Is this suspicion correct? Does this make sense. Thanks Robin After I sent the above I read about the use of encoders with J5. These inputs configured as digital inputs will hopefully allow me to use three rotary hex switches without any more SR's. Three such switches will allow me to control the Midi Channel No and the other two will be used to adjust the keyboard_delay_fastest and keyboard_delay_slowest variables. Connectin Diagram MIOS 32 Fast Scan with extra switches.doc

Dear Thorsten The latest code is functioning properly for Debug verbose levels 1 and 2. I'm not sure about level 3. Verbose level 1 No debug messages. Midi On/Off Verbose level 2 Debug messages as below. Midi On/Off [4480.781] row=0x08, column=0x07, pin_value=0 -> pin=78, timestamp=10894 -> IGNORE [4480.795] row=0x09, column=0x07, pin_value=0 -> pin=79, timestamp=10908 -> NOTE ON (delay=14); velocity=121 [4480.900] row=0x09, column=0x07, pin_value=1 -> pin=79, timestamp=11013 -> IGNORE [4480.918] row=0x08, column=0x07, pin_value=1 -> pin=78, timestamp=11031 -> NOTE OFF Verbose level 3 Debug messages as below. Midi On/ Off OK. [3934.484] row=0x08, column=0x07, pin_value=0 [3934.484] row=0x08, column=0x07, pin_value=0 -> pin=78, timestamp=113654 -> IGNORE [3934.499] row=0x09, column=0x07, pin_value=0 [3934.500] row=0x09, column=0x07, pin_value=0 -> pin=79, timestamp=113668 -> NOTE ON (delay=14); velocity=121 [3934.622] row=0x09, column=0x07, pin_value=1 [3934.623] row=0x09, column=0x07, pin_value=1 -> pin=79, timestamp=113791 -> IGNORE [3934.640] row=0x08, column=0x07, pin_value=1 [3934.640] row=0x08, column=0x07, pin_value=1 -> pin=78, timestamp=113812 -> NOTE OFF Note generation is working. Thanks again! Robin

Dear Thorsten No errors detected. All is fine. Do you mean using a pot or Thumbwheel switch to control both variables? Additional Interconnection Table It may be useful to include in the docs for this examples a table showing more clearly the connections between the LH and the RH Keyboard and the DOUT / DIN IC Pins. This would be for your present version. I have attached the diagram sse below. It would also be helpful to others to include the 88 note Fatar circuit diagram in the example docs. I hope I have the ability to complete the project on my own. Thank you once again for your time and trouble in developing the keyboard fast matrix velocity scan system. There are always queries on the midibox forum for keyboard scanning systems. Your solution using time measurement is elegant and probably unique. Best Wishes Robin Keyboard to Shift Register Connections.doc

Hi Thorsten I think that I had two app.c in the folder. The latest has been tested with MIOS STUDIO and is AOK!. See the result of pressing A0. I also played all the notes with the softsynth. Future Work I need to dismantle the keyboard to a add few diodes to my adaptor board. Maybe I should allow a couple of switches for enabling one or two velocity curves? MIOS STUDIO.txt

Dear Thorsten Same as last time. Is the latest version 1107? Robin

Dear Thorsten Here are the Delays that I measured in mS. Hard 4, Normal 10, Semi 40, Soft 65, Very Soft 200 - 300 even 400 The last measurement is very contrived. It is based on achieving a velocity of 1. Latest program There seem to be a problem with first 8 notes. ie Note A0 to E1. I show the A0 the others are similar. [32731.500] row=0xff, column=0x00, pin_value=0 -> pin=0, timestamp=1055233 -> IGNORE [32731.500] row=0x00, column=0x00, pin_value=0 -> pin=0, timestamp=1055233 -> IGNORE [32731.500] row=0x01, column=0x00, pin_value=0 -> pin=1, timestamp=1055240 -> NOTE ON (delay=7); velocity=122 [32733.263] row=0x01, column=0x00, pin_value=1 -> pin=1, timestamp=1056996 -> IGNORE [32733.281] row=0xff, column=0x00, pin_value=1 -> pin=0, timestamp=1057014 -> NOTE OFF [32733.281] row=0x00, column=0x00, pin_value=1 -> pin=0, timestamp=1057014 -> NOTE OFF Note that there are 3 0's and 3 1's Extra Switches I have modified the code and the table to allow for 16 switches in the empty part of the Table. I think that the system should have some extra switches that can be scanned. My requirement is deliberately basic. At present I can think of 10 essential ones at present. Please let me know if I should send the latest version. The table will make this clearer. I have not coded the new functions only made allowances. Regards Robin Connectin Diagram MIOS 32 Fast Scan with extra switches.doc

Dear Thorsten I have checked the DOUT connections using a combination of MIOS STUDIO and a meter on the "diode" setting. MIOS STUDIO was very useful in showing when the depressing of the key made only the 1st switch close . I used weights from the kitchen to rest on the first key (A0) to make only the the 1st switch close. I have shown that J3 DIN IC pin 11 (D0) equiv to T0 (Fatar)is connected to J3 DOUT IC pin15 (D0) equiv to BR0 (Fatar) (via a diode) when the key is depressed making the 1st switch of the pair close only. In this state there is no connection to pin 1 to J3 DOUT IC pin 1 (D1) equiv to MK0 (Fatar). When the key is fully depressed then J3 DIN pin 11 (D0) is connected to both DOUT pins ie D0 (BR0 and D1 (MK0) I believe that this shows that the first row is row 0 and that my wiring is OK. By the way the expression row -= 1; corrects the pin No(s) to agree with my table. In trying the find out the reason I wondered about void BUTTON_NotifyToggle(u8 row, u8 column, u8 pin_value, u32 timestamp) { // determine pin number based on row/column // based on pin map for fadar keyboard provided by Robin (see doc/ directory) // tested with utils/test_pinmap.pl int pin = -1; I could not understand why the variable pin was given a value of -1. I tried int pin; and there seems be be no difference to the system. If I am right the it follows that something else is wrong. I know that it doesn't matter because the piano can be made to work.. Maybe it is something to do with the operation of DIN/DOUT in latching the previous DIN inputs. Code alternative I don't understand // pin number (counted from 0) consists of: // bit #0 if row -> pin bit #0 int bit0 = row & 1; // bit #2..0 of column -> pin bit #3..1 int bit3to1 = column & 0x7; // bit #3..1 of row -> pin bit #6..4 int bit6to4 = (row & 0xe) >> 1; // combine to pin value if( column < 8 ) { // left half if( row >= 0 && row <= 0x9 ) { pin = bit0 | (bit6to4 << 4) | (bit3to1 << 1); } } else { // right half if( row >= 0 && row <= 0xb ) { pin = 80 + (bit0 | (bit6to4 << 4) | (bit3to1 As an exercise I have worked out an alternative that I understand. // for the left hand, pin = 8 * row + 2* column when row even, pin = 8 *(row - 1) + 2 * column +1 when row odd // if ( row % 2 == 0 ) { it's even} else{ it's odd} //left half, column < 8, row 0-9), pin even if ((column <0x8) && ( row >= 0 && row <= 0x9 ) && (row % 2 == 0)) {pin = 8 * row + 2* column;} else{ if ((column < 8) && ( row >= 0 && row <= 0x9 ) && (row % 2 == 1))//is odd pin = 8 *(row - 1) + (2 * column) +1;} // right half,(column (8-F),row (0-b), pin even, in the right half need to add 80 (even)or 81 (odd) //and subtract 8 from column value to get correct pin nos if((column >= 0x8 && column <= 0xf) && (row >=0 && row <= 0xb) && (row % 2 == 0)) {pin = 80 + 8 * row + 2* (column - 8);}else{//row is odd if((column >= 0x8 && column <= 0xf) && (row >=0 && row <= 0xb) && (row % 2 == 1))//even rows Touch experiment You asked me to undertake an experiment with various degrees of touch to the keys. Here are the results , highly subjective of course! Hard 126 Normal 100 - 105 Semi 80 - 90 soft 50-60 very soft 1 Finally, having thought about the scan speed issue, the only in advantage in increasing speed would be that of time accuracy. ie from a 1mS accuracy to 0.5mS accuracy. I doubt whether the switch contacts are mechanically displaced all that accurately. Best Wishes Robin

Dear Thosten We may be at cross purposes here. First of all let us agree some terminology. Let us agree that all pins, rows, columns and SR pins (bit x) begin at 0. My hardware is currently connected as follows:- J3 DIN (bit 0 of SR) to Col 0, J3 DIN (bit 1 of SR) to Col 1, etc, ending with J3 DIN (bit 7 of SR) to Col 7 J4 DIN (bit 0 of SR) to Col 8, J4 DIN (bit 1 of SR) to Col 9, etc, ending with J4 DIN (bit 7 of SR) to Col F J3 DOUT (bit 0 of SR) to Row 0, J3 DOUT (bit 1 of SR) to Row 1, etc, ending with J3 DOUT (bit 7 of SR) to Row 7 J4 DOUT (bit 0 of SR) to Row 8, J3 DOUT (bit 1 of SR) to Row 9, etc, ending with J3 DOUT (bit 3 of SR) to Row B My rows do start at 0 (not1) Originally I think that I referred to J3 DOUT bit 0 as Row 1. This I'm sure is the cause of confusion. I'm sorry to be a nuisance. Robin

Dear Thorsten There is an error. Here are the first few notes. [2864.223] row=0x01, column=0x00, pin_value=0 -> pin=1, timestamp=12411 -> IGNORE [2864.230] row=0x02, column=0x00, pin_value=0 -> pin=16, timestamp=12418 -> IGNORE [2864.356] row=0x02, column=0x00, pin_value=1 -> pin=16, timestamp=12544 -> NOTE OFF [2864.373] row=0x01, column=0x00, pin_value=1 -> pin=1, timestamp=12561 -> IGNORE [2870.294] row=0x01, column=0x01, pin_value=0 -> pin=3, timestamp=18481 -> IGNORE [2870.303] row=0x02, column=0x01, pin_value=0 -> pin=18, timestamp=18490 -> IGNORE [2870.415] row=0x02, column=0x01, pin_value=1 -> pin=18, timestamp=18602 -> NOTE OFF [2870.429] row=0x01, column=0x01, pin_value=1 -> pin=3, timestamp=18616 -> IGNORE [2879.430] row=0x01, column=0x02, pin_value=0 -> pin=5, timestamp=27616 -> IGNORE [2879.435] row=0x02, column=0x02, pin_value=0 -> pin=20, timestamp=27621 -> IGNORE [2879.540] row=0x02, column=0x02, pin_value=1 -> pin=20, timestamp=27726 -> NOTE OFF [2879.552] row=0x01, column=0x02, pin_value=1 -> pin=5, timestamp=27738 -> IGNORE [2884.359] row=0x01, column=0x04, pin_value=0 -> pin=9, timestamp=32544 -> IGNORE [2884.367] row=0x02, column=0x04, pin_value=0 -> pin=24, timestamp=32552 -> IGNORE [2884.479] row=0x02, column=0x04, pin_value=1 -> pin=24, timestamp=32664 -> NOTE OFF [2884.494] row=0x01, column=0x04, pin_value=1 -> pin=9, timestamp=32679 -> IGNORE I have also looked at the util doc file, this starts with pin = 1 Also look at my table it starts with Pin No = 0. I can do this again but I thought this is what you wanted. Row, Column, Pin No all starting with "0". There is a less important comments error, referring to BLM. ///////////////////////////////////////////////////////////////////////////// // This task is called each mS to scan the button matrix ///////////////////////////////////////////////////////////////////////////// // will be called on BLM pin changes (see TASK_BLM_Check) void BUTTON_NotifyToggle(u8 row, u8 column, u8 pin_value, u32 timestamp) I will run the key touch tests later today. Robin

Thanks Thorsten I accept your points regarding speed. I suppose when you think about some musical instruments, there are always delays eg on an acoustic piano: fingers to keys, keys to hammers, hammers to strings. With light touch notes the hammer and key action is of course slower. It could be regarded as more realistic having longer delays. The table is already revised . It seemed better to use a generally accepted rule regarding bits, pins, SR pins. I have expanded the document to include more details of the Fatar connections. See below. Regarding different responses eg logarithmic. Come soft synth pianos have different curves built in. The one I'm using "Pianissimo" has several curves from very light to very heavy. I have just found this out! Best Regards Robin Row Col Fast Scan pin from 0.doc

Duggle I must admit that the general impression of the sound and playability is good. Actually getting a velocity of 1 needs great attention. Not much force is needed to achieve a velocity of 100. The may be some scope for greater resolution above this level. A light touch can easily produce a velocity of 40 - 60. It is very subjective! Robin

Dear Thorsten I did try the last version of fast scan last night and I now have the Midi On and Midi Off working. I have tried it out with 2 soft synths that I have. It works fine. Thank you again. My Table with Pin No, Rows, Columns It is inconsistent. I think that both rows and columns should start with 0. It will be more understandable to anyone else who uses the program. A new version is attached below. Please modify the code. Start Note A0 This should be Decimal 21 ie 0x15. This was found out using the piano synth. Scan Speed I appreciate that have taken up a lot of your time recently. But I would like to see whether the scan speed could be increased. I believe that we may have reached the limit using portTICK rate of 1mS. Can the 1mS portTICK parameter be reduced? This also raises the subject of DMA. I think that it would be interesting to see what is possible and would add to Duggle's work on this subject. I also need to incorporate a Midi Channel switch into the piano system and incorporate the two foot pedals (Midi Control Nos 64 and 67). I will utilise the unused Left Hand Bytes Rows B and C for this. I would like to see if I can deal with this on my own. Regards Robin PS Rather than being very generous with your time maybe you could give me a few pointers on how to use SRIO. Row Col Fast Scan B.doc

Thorsten, The system is now generating both Midi On with velocity and Midi Off with zero velocity. I need to go to bed now but will check on delays tomorrow. What measurements would you like? There seems to be a delay of 226 with a velocity of 1. That's the slowest I can get! Would that be 226 mS? Thanks again Robin

I forgot to look for them. Here they are! 5187.328] 90 21 7a [5188.828] 90 22 7c [5190.468] 90 23 7c [5191.531] 90 24 7a [5192.288] 90 25 7c [5193.347] 90 26 7a [5194.240] 90 27 7a [5194.903] 90 28 7c [5195.515] 90 29 7c I have played the first few notes at roughly the same velocity. However No Midi Off Codes are generated. I'll check all the notes but I thought you would be pleased with an early reply. Robin

Thorsten Here is the latest result from MIOS STUDIO. [4032.078] [BUTTON_NotifyToggle] XXX 38533 0 0 0 [4032.078] [BUTTON_NotifyToggle] row=0x01, column=0x00, pin_value=0 -> pin=1, timestamp=38533 -> IGNORE [4032.084] [BUTTON_NotifyToggle] XXX 38539 1 0 1 [4032.084] (ERROR: string passed to MIOS32_MIDI_SendDebugMessage() is longer than 100 chars! [4032.202] [BUTTON_NotifyToggle] XXX 38657 1 1 1 [4032.202] [BUTTON_NotifyToggle] row=0x02, column=0x00, pin_value=1 -> pin=2, timestamp=38657 -> IGNORE [4032.218] [BUTTON_NotifyToggle] XXX 38676 0 1 0 [4032.218] [BUTTON_NotifyToggle] row=0x01, column=0x00, pin_value=1 -> pin=1, timestamp=38676 -> IGNORE Robin

Hi Thorsten I have tried out the new code. There seems to be a problem. See the MIOS STUDIO Debug message for Key 1 (A0) I've checked a few other keys the results are similar. Robin