Jump to content

robinfawell

Programmer
  • Posts

    292
  • Joined

  • Last visited

About robinfawell

  • Birthday 05/23/1940

Profile Information

  • Gender
    Male
  • Location
    UK

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

robinfawell's Achievements

MIDIbox Tweaker

MIDIbox Tweaker (3/4)

0

Reputation

  1. I agree with a previous suggestion to make an adaptor board as I have done. Don't cut any Fatar circuit boards. This means that you can plug the 40 pin Fatar connector by flat cable into a 40pin connectors on the adapter board. Or maybe to split the cable into two and have more easily obtainable 20 pin connectors (X2). Then using small dia cable make the appropriate connection to two 16 pin connectors. Therefore the adaptor will have a 40pin connector (or 2X 20 pin connectors)and two 16 pin connectors. The latter will connect by two flat cables to the Dio- Matrix Board. The 40 (or 2X20) pin flat cable(s) will connect to the Fatar Keybed. My keybed has two 20 pin Micromatch Connectors. You will of course need to source a tool to assemble the flat cable to the cable. I use a cheap tool and a little ingenuity. You also need to source the mating half of the Fatar connector. A tip. Don't fit this board under the keyboard as I did. It sounds a good idea but you will likely need to remove it for fault finding. I haven't studied the NG module enough.The following might not be practical. I have on the adapter board 16 extra diodes which connect to the switches of soft pedal, sustain pedal, transpose, midi channel, presets, panic button and a few others. I have a Fatar 88 note keybed. I use a 12 X 16 matrix. For a velocity sensitive 88 note keybed you need a 176 position matrix ie 11 X 16, To scan 16 diodes requires as well you need 12 X 16 matrix. The Dio-Matrix board will accommodate the 88 note keybed needs plus 80 Diode/ Switch combinations if required. I use TK's Programming Example 29 with my own program modifications. (Helped a lot by Thorsten) Robin I should have mentioned that I am using the STM32F40 module. The redesign has just been completed.
  2. Here are a couple of ideas. Most of my work concerns digital piano. In addition to scanning the keys for switch changes . I scan 16 extra switches for changes. You could use J5 to to the same. I use a membrane momentary action switch.made by MEC with low bounce characteristics. Here is some code for a 2 switch solution. This enables the user to to decrement and increment the value. You will need to declare the transpose variable as a global variable. //transpose buttons if(pin == 95 && pin_value == 0){//pin 95 is RH Transpose Button ie + Transpose (Higher Note) transpose = transpose +1;} if(pin == 94 && pin_value == 0){//pin 94 is LH Transpose Button ie + Transpose (Lower Note) transpose = transpose -1;} if(transpose > 9){ transpose = 9;} if(transpose < -9){transpose = -9;} You need only one switch, but you can only advance if(pin == 95 && pin_value == 0){//pin 95 is Transpose Button transpose = transpose +1;} if(transpose > 9){ transpose = 0;} In the latter case pressing the button after 9 is reached, returns the variable to 0 Later in the program you will add the transpose value to the note number.. For octave shifts you will use multiples of 12 notes Robin
  3. I have solved my problem. Setting up LCD type is done with the bootloader not with the app. Robin
  4. My rebuild of my digital piano has progressed to incorporating my DOG display. I recall that last time, over a year ago, I used the Mios Studio app to enter the LCD parameters. The program is my version of Thorsten's example, Fast Scan Matrix. I cannot get the commands to work. I notice that the app is showing Unnamed App in the parameters panel. Am I missing something? Robin
  5. Thorsten Thanks for your reply. I persisted mainly to improve my knowledge of Linux. Robin
  6. I have to report a complete failure in trying to follow the linux gcc toolchain download and file setup. specifically sudo wget http://www.//www.midibox org/mios32_toolchain/gcc-arm-none-eabi-xxxxxx.tar.bz2 and the next line sudo tar zxvf-gcc-arm-none-eabi-xxxxxx.tar.bz2 The text asks for xxxxxx to be replaced by the date of the latest tool chain. I have tried 4_7-2013q3 2013q3 20130619 I have tried adding "linux" after the date. Nothing seems to work. I'm obviously missing something important. However, I've gone back to Win 7 where I can compile correctly. I have used tutorial 005 and can generate Midi events using shorting links on J5A/B If anybody can suggest a solution for the linux problems, I will appreciate the help. Robin
  7. Thorsten It works! The pin voltages on J5 are about 3V and I have received an event. My toolchain file /usr/local/mios32_toolchain/bin consists of 27 arm_none_eabi files each with different endings Robin Here is the result after compile using my data not yours. I have now changed the Board env variable to that shown below But this doesn't work! No events - J5 pins at 0.3V Here is a svn update
  8. Hello Thorsten I used Linux. Here is part of the profile file where I set the Env Variables permanently. I realise that you want me to use your project hex file. I'll check it out. Robin
  9. Tonedef I happened to read your August post. I can let you know how I achieved this if you need some ideas. I use two membrane momentary switches. Transpose+ and Transpose-. If you want to see the code let me know. Robin
  10. Hi Thorsten Yes the pin voltages are correct. On J5B pins A4,A5,A6 and A7 all measure approx .3 V to ground. Robin They are all connected to the correct STM Discovery Pins Pin A3 is lower , 0.2V PS This morning I got quite excited. I thought I had discovered the problem. In looking at the makefile list after compiling I found that there was no reference to the BOARD variable. Unfortunately correcting this has made no difference to the voltages on J5
  11. Thorsten Thanks for the confirmation. The Query button causes code in both monitor displays. Yes I can select MIOS32 and Juce ports. However I cannot trigger Note Events on J5a for some reason. I have measured the input voltage of J5B pins with a multimeter, they are about 0.3 volts. Robin
  12. Thorsten I have been re-reading the bootloader articles. I note that the LED on the STM device has to flash twice when the bootloader is installed. I would say that that it is flashing three times. What does this mean? The reason for this query is that there is no response to MIOS STUDIO after installing Tutorial 5 with shorting pins to ground on J5A. This makes me doubt whether the bootloader is installed. The ST utility seems to load the bootloader and shows verification. Can I use MIOS Studio to show if the Bootloader is installed? I am getting nowhere fast. Thanks for your help. Robin
  13. TK Yes It downloads OK. It shows as follows. Parent Directory README.txt gcc-arm-none-eabi-4_7-2013q3-20130916-linux.tar.bz2 gcc-arm-none-eabi-4_7-2013q3-20130916-mac.tar.bz2 gcc-arm-none-eabi-4_7-2013q3-20130916-win32.zip Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.3.20 Server at www.midibox.org Port 80 Robin Today's Comment. I have used the linux link above to download the GCC file and constructed the Toolchain manually by creating a directory and transferring files into usr/local. I believe that I have done this properly.
  14. Thanks Thorsten I today have spent a fair amount of time today reading anything referring to STM32F4 and reread the README on the Tutorials. They, as you confirm refer specifically to the STM32F4 core. This is very reassuring to me as I would like to be able to use my digital piano again. I mentioned earlier in my recent posts that I could not download the MIOS32_toolchain as described in Core Toolchain Setup. I have tried many times using linux to use the following code cd/usr/local sudo get wget http;// www.org/mios32_toolchain/gcc-arm-none-xxxxxx.tar.bz2 sudo tar zxvf gcc-arm-none-eabi-xxxxxx.tar.bz2 Each time I receive Error 403 I have tried xxxxxx as 2013q3, 20130916, -4_7-2013q3-20130916-linux all with the same result. (error 403) I am concerned that my ad hoc method to get the same result may have caused a corrupted hex file. Your guidance will be much appreciated. Robin PS I believe have been using the correct toolchain but perhaps not correctly.
  15. Having given up on using Windows 7 with MIOS STUDIO I have switched to a PC running LINUX (Mint). MIOS STUDIO seems to work properly. I have managed to download hex files using MIOS STUDIO, it would seem. However I would like proceed slowly and looked for an application that I could use to check that the STM32F4 core is OK. Tutorial 5 seemed to be the ideal candidate as it only needs shorting links to be applied to J5 connector. I am not sure whether this APP is ready for STM32F4. I get no response Please let me know if this is the case and if not let me know if there is another application that would be suitable. Or, whether I am likely to have a fault on the hardware. Thanks Robin
×
×
  • Create New...