mikee

Members
  • Content count

    84
  • Joined

  • Last visited

Everything posted by mikee

  1. thanks a lot TK all is now clear. no ref to menu buttons as there are none supported. all 128 dins are available. no menu button support therefore no toggle or indeed anything. finally: no, I have not found a reference which describes that ain64_din128_dout128 supports a menu. Thanks also to janis1279 for your input. Indeed thanks for the speedy response kind fellows.
  2. Hi all. I have already posted this in testing and trouble-shooting but on reflection I think that was wrong forum.  I hope therefore this is a more sutable place for my questions. I therefore aplologise in advance. There does not seem to be a ''technical questions' place. Ref the application: ain64_din128_dout128_v2... Does anyone know where is there a reference to the four lcd menu buttons: exec, right, left and snapshot? If this app has no such menu buttons, does it mean that mean there is a total of 128 buttons available for MIDI note-on offs, without altering code? Also:  (unlike the MB64 app) I cannot locate any reference to the menu buttons - are they toggle types or what? Perhaps I am not looking in the correct places. Any ideas or help would be greatly apprecated folks. regards
  3. Hi all. Ref the application: ain64_din128_dout128_v2... This might sound like stupid, but where is there a reference to the four lcd menu buttons: exec, right, left and snapshot? If this app has no such buttons, does it mean that there are 128 buttons available for MIDI note-on offs? Also  (unlike the MB64 app) I cannot locate any reference to the buttons - are they toggle types or what? Any ideas or help greatly apprecated folks. regards
  4. BrennerNG weird error reports

    thanks for the reply analogue_mo stupid as it might sound, i had not provided power and the leds seemed to say all was well, but thanks anyway mate.
  5. hi all Im using BrennerNG44 to burn pic16f48a. Using Brenner, I get these results:- PIC16F84 in database:   Vpp : 13V  (12 .. 14V) CP-Blocksize : 0800 Panelgröße : 0000 HEX-file-name : picF84a_test.HEX -- HEX-file loaded -- 1 k FLASH needed -- 0 Byte EEPROM needed -- HEX-file contains Config-data Chip erased Start to program Flash ##-->7 errors in PROGRAM      ************* note Start to program ID -- no ID to burn -- ID o.k. Start write Configuration ##-->1 errors in Config    ************* note -- finished config used:          __CONFIG _CP_OFF & _XT_OSC & _PWRTE_ON & _WDT_OFF include used: "P16F84A.INC" ** Ref notes: Does anyone know why Brenner detects program errors and config error when MPLAB asm says all is fine? Cheers everyone
  6. Why is it called FM synthesis?

    just enjoy neb. By the way, I thought you said it only took 10 mins to get the sound you want? It seems to me that you start with a mental sound but end with something entirely different. Twiddle and learn.... the maths are far too complex and restrict the music juices. regards
  7. Thanks for help. If by start -> run -> cmd you mean the Windows Run command, then I cannot get that to work - does not recognise 'Copy' !!!  ??? Anyway, I will read all response tonite and try again.  Thanks again Podewski.
  8. Carefully following procedures in [[windows_toolchain_core]] I was successful up to the message: "Please answer the following in the form of c:/foo/bar. Where is your MinGW installation? c:/MinGW" The only file in c:/MinGW/bin/ is mingw32-make.exe, and no such file as gcc.exe exists there. Also, according to [[windows_toolchain_core]], "make upgrade" it says; "Unfortunately there is currently no installer for the required version of make (v3.81). It is downloaded in the MinGW setup above, but we must copy it to the correct location." Click 'Start… Run'. Paste in the following command: copy c:\MinGW\bin\mingw32-make.exe c:\msys\1.0\bin\make.exe /y Click 'OK'. But this command in Windows is invalid, (message returned is: "Windows cannot find copy") and copying across by hand only results in the complaint that the file 'make.exe' already exists (which is very true. Below is a copy of the Console window during the procedure: C:\msys\1.0\postinstall>PATH ..\bin;C:\Perl\site\bin;C:\Perl\bin;C:\WINDOWS\syst em32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI C ontrol Panel;C:\Program Files\Microchip\MPLAB C32 Suite\bin;C:\Program Files\Mic rochip\MPLAB IDE\VDI;C:\Program Files\Microsoft Visual Studio\Common\Tools\WinNT ;C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin;C:\Program Files\Mi crosoft Visual Studio\Common\Tools;C:\Program Files\Microsoft Visual Studio\VC98 \bin;C:\Program Files\SDCC\bin C:\msys\1.0\postinstall>..\bin\sh.exe pi.sh This is a post install process that will try to normalize between your MinGW install if any as well as your previous MSYS installs if any.  I don't have any traps as aborts will not hurt anything. Do you wish to continue with the post install? [yn ] y Do you have MinGW installed? [yn ] y Please answer the following in the form of c:/foo/bar. Where is your MinGW installation? c:/MinGW I could not find c:/MinGW/bin/gcc.exe. You must have given an invalid path to your MinGW environment. I am reversing to no MinGW installation. If you do have MinGW installed then you can manually bind the mount point /mingw to C:/mingw (replace C: with the drive of your choice) by creating an /etc/fstab file with a line that has a value similar to: C:/mingw /mingw Press ENTER to continue         Normalizing your MSYS environment. You have script /bin/awk You have script /bin/cmd You have script /bin/echo You have script /bin/egrep You have script /bin/ex You have script /bin/fgrep You have script /bin/printf You have script /bin/pwd You have script /bin/rvi You have script /bin/rview You have script /bin/rvim You have script /bin/vi You have script /bin/view MinGW-1.1 has a version of make.exe within it's bin/ directory. Please be sure to rename this file to mingw32-make.exe once youve     echo installed MinGW-1.1 because it\s very deficient in function. Press ENTER to continue. C:\msys\1.0\postinstall>pause Press any key to continue . . . ================================================================= I gave up at this point, thinking that I must be too dense to grasp something fundamental, which I cannot see.  :( If I start again, do I need to uninstall everything?  ??? Do the letters Ming perhaps have some deep esoteric C++ meaning? It seems to me that there's a great deal of effort just to change a couple of lines of code, and I wonder if it cannot be more readily achieved using Assembler? cheers all.
  9. If the toolchain involves those unix files etc, then I cannot install it as yet, a lot of problems trying. thanks for reply  :)
  10. Hi all, I urgently need to look at V1.3 (not any higher) of the above file. I tried a download from http://www.ucapps.de/mios/ain64_din128_dout128_v1_3.zip but I get Error 404. Anyone help me find this zipped pack please?? If not does anyone know of another source? thank you forum.
  11. thanks for the quick reply TK. Yes I get you. MPLAB goes in the bin then?  As for those Unix-system files etc, I tried but failed to install all of them, and have posted elsewhere with my experiences. Thanks again TX and to all who have spent so much time coding the apps: THANK YOU VERY MUCH ... Powered up my MB lash-up for first time 20 minutes ago, and it is up and running, and I am a very happy giraffe, the results are excellent!!! :) regards all
  12. Hi all, I want to get into PIC assembler MB-wise, and wondered what is the minimum set-up needed to change code and upload via MIDI. A few years ago there was a kind of Virtual MidiBox and a method of uploading sysex commands etc. Is this method still used? Can someone give a brief run down? Or is there some stuff already hiding somewhere? Have all the software zips been 'upgraded' to C only? All the best folks
  13. MB64 Lash-up

    Hi folks, got my first MB app off the ground at last. Threw my stuff together, dying to do a few pot-tests and play around with Ableton. Expected many hours of tracing obscure dry joints and dead mice in the works as i never used a fancy printed board - just a plain non-copper perf board, but all worked extremely well indeed. My compliments to the Main Man. I intend to throw many more switches onto the board, 32 are too few. I will go up to 128 switches. Don't need leds - i can see what's happening on my monitor. Cannot increase pot above 64 without second 16f452, but 64 is loads for now. I burnt the chip, then uploaded setup hex file then after that i uploaded Mios, all via MIDI of course. I expected it to fail beacuse the write-ups say Mios first, then app setup second. Anyway, it worked a treat!!! Sitting at my desk surrounded by a huge rat's nest, feeling good. Psu runs stone cold. Its an old 12V supply from a PC100, and I whacked a couple of op-amps and a few power transistors to give me 5V. I really should reduce the initial supply to about 7v. But what can one do? I liked the little pot-levels on the display! See ya all again folks - keep on boxin'
  14. Sorry folks, I just cannot see any voltage coming into the 7805, where is it please? Can someone else not see it too?  ;) cheers Johnh
  15. programming a pic16f84a

    in case you r still unsure: Download BrennerNG as per Thorsten's advice. A zipped bundle, and when undone you will find the file: PBrennerNG44.exe. This is the one which burns the Pic16F84 etc. The main text is in German ltongue but the actual burner is in English - weird. Just click on the file to run - it needs no installing on Windows. It will recognise your programmer if it works and is properly connected. It has option to check out the Pic in your programmer, so if you put a Pic16F84 in the socket, and click on 'identify PIC in Programmer', it will do exactly that. Next, click on 'seclect HEX-file as source', and (assuming you have a hex file, and know where you stored it) the file is loaded ready to be burned in. Finally, click on 'write HEX file into PIC' which begins burning process. You see the progress and get a nice big OK,OK,OK if all went well. as for that hex file: Download MPLAB from Microdigital, install it, then run it. You have before you a nice assembler with some port bit stimulus and general debugging stuff. Do you thing with the PIC16F84 there, then, when your asm file is ready, click on Project/Quickbuild (filename.asm) and a hex file is generated (if all went well). Now you can burn it in with the Brenner. Its very good for learning PIC assembler, but no good for much of Midibox stuff, because C is the thing now. But I play around with generating music stuff, and C just won't do when your shaving single instruction cycles of a project. Also, C uses more memory than asembler, and that's in short supply in a PIC16F84. If you want to burn PIC18F452 later in your studies, you might use my mod, which saves adjusting programming voltages each time you change processors. A tip here: only a few pins are used when burning, so what good are DIL sockets with lots of surplus pins? By removing the pins, and leaving just those required for the burner, means that the process of plugging chips in and out is made very easy, almost zero-insertion force. NOTE: do not use turned pin sockets, or you could easily end up with broken-legged PICs. Just use the cheaper stamped pin sockets. (and here's a little parting tip: PIC16F84 without crystal and capacitors: just connect a resistor from +5V to pin 16, leave pin 15 unconnected, and change the assembler _config to include  RC_OSC. If you are just learning, this saves time, effort and money.) Hope this helps, regards
  16. BUTT_ON or BUTTON off?

    Thanks for the reply TK. I understand therefore that on off refers to midi on off, and if no 'off velocity' is sent then this accounts for on-only. I can see where such a case might be required. Thanks for that one. As for the second question, I understand that nothing at all happens until button is released. As the logic state has already changed from 1 to 0 on the down stroke, I assume you are referring to the logic state of 0 to 1 on the release. Thanks for that also. I have made no experiments so far (gthus theoretical questions) as I am still throwing chips on my board (core and all modules on same matrix board) but come unstuck when I bought a picf425 which refused to change condition of a few port pins. But its hard to convince a seller that it was treated with correct care, and must have been a dud one. But there you go. Sorry I did not reply sooner, my IP connection failed for a day or so. By coincidence it happened just as i had downloaded some stuff. (Active Perl site, mingw etc). Thanks agin for the fast response and valuable info regards
  17. BUTT_ON or BUTTON off?

    Hi all, I previously posted this same article in Midibox HUIs, but having recieved no replies I thought perhaps I was in the wrong form, so I am posting the same questions here. Please forgive me if I have made a blunder folks. Here is the post: I read somewhere in Midibox HUIs that @ononly behaviour is "like a one-shot", does this mean that when a switch is pressed the software turns off by itself after a certain time? Anyone add clarity? If a led (via dinout) is used to indicate the state of the button, would that also turn off after a certain time? I fully understand @onoff and @toggle behaviours but @ononly? ??? Also: If a latched switch is used rather than a press to make switch, so that once pressed that Dinx4 input in held at logic 0, does the software consider it to be pressed only one time, or does it consider it is a new press on each serial scan?  In other words what is the end effect of keeping a button pressed down? Hope this makes sense folks Regards.
  18. Make Arcade Controller from PC Keyboard

    I stand corrected aristidesfl thanks for that. Its been some years since I played with keyboard signals, but you are correct. I should have explained that I was using VBasic at the time, and thats why I could not turn off the repeat. The pc keyboard does send a continuous stream of data, as yo say. I humbly bow out
  19. Button behaviours

    Hi all I read somewhere in this forum that @ononly behaviour is "like a one-shot", does this mean that when pressed it turns off by itself after a certain time? If a led (via dinout) is used to indicate the state of the button, would it also turn off after a certain time? I fully understand @onoff and @toggle behaviours but @ononly???? Also: If a latched switch is used rather than a momentary switch, so that once pressed that Dinx4 input in held at logic 0, does the software consider it to be pressed only one time, or does it consider it is a new press on each serial scan?  In other words what is the end effect of keeping a finger on a button? Hope this makes sense folks Regards.
  20. Using 5V and J2 pin

    Regards using fuses to protect core etc: I would suggest you add a diode to each of your boards, so that if you do reverse the connections the fuse will conk out. Hope this helps regards diode_protect.JPG diode_protect.JPG
  21. Are you feeding actual audio through this patching system? If so, I have a large quantity of 1/4 inch professional jack sockets which are surplus to requirements.  (Might also have 16 100mm log faders, but not sure as yet.) If you are looking for audio-mixer bits I might be able to help, perhaps a swap in payment? regards and best of luck with your patch-bay.
  22. Cheers for the reply. It makes sense to me: use the least to get the same (or better) result. Its surprising how many think the opto-isolator is there to protect expensive chips. Interesting project you have there Thorsten, thanks a lot.
  23. PC owners have to use a MIDI interface cable so that they can interface to a MIDI machine such as MBox64. The core must therefore have a complimentary MIDI interface including an opto-isolator etc etc. But as the opto-isolator is only present to prevent ground loops (which usually only occours when lots of gear is used) and affords no so-called 'protection' for the core pic, I wonder why on earth spend out on the things which are not required? Surely a simple buffer between Pic and Games port would suffice??? Cheers all  :) MIDI_mod.JPG MIDI_mod.JPG
  24. I put conpoments on boord and swicht the mains on. Many wigglys come down wire anto my core boord. then big light come flashing one time, i got  abit scared an went to switch off, but too late!!!!! bigger light get me right in the eye, an thats not a joke, it hurt mee big time folks. So i looked where the big light comming from an seen it com from lcd back of it, this is the biggest light i never saw, i was so flummexed. So i put a meeter on the lcd and guess what? bigger light went smaller as my meeter went to the right side, an i say to my self "gosh! what is going down here babe" an start to sweet a bit under my collar. Anyway I fix it by gluing meeter to side of box. if anyone else has same problem, just let me know an i will fix yours as well. all the best frends
  25. Hi all. In my local council recycling center, I found a 16 channel pro mixer desk in a bad state of repair. Noting that it had lots of excellent Alps 100mm 10K Ohm Log faders, (plus lots of 100K Lin center-detented pots etc etc) I thought they might be good in a Mbox64. Problem is that they are Log law tapers, and it seems that Mboxes don't like log pots. (What is the effect by the way?) As I had at least 18 faders, I decided to use two faders arranged in parallel, with one fader inverted. The end result is a fader of 5K Ohm with what seems to be a pseudo-linear taper. I know this is awfully wasteful, and I also end up with 5K pots rather than the standard MB 10K, but what the hell, and my power supply (being from a pc, minus noisy fan) can handle the extra bit of current easily. Anyway, they work for me  ;) I hope this input is helpful in showing what might be possible when faced with difficult situations. Cheers all Here's how they are wired up: pots.JPG pots.JPG