Jump to content

superdavies

Members
  • Posts

    41
  • Joined

  • Last visited

    Never

Everything posted by superdavies

  1. Hi I'm using a custom version of the app called ain64_din128_dout128_v2_0.zip written in C; I'm not very practical in the apps development but I only want to know what's the default configuration for the digital out of this app. because I Need that every single led connected to the board via the dout module will light up when the corresponding din will be pressed: is this the default config. or not? If not any suggestion to how (and where) I must modify the code? Thank you! Andrea
  2. Ok all works well, we only had some problems with the organizations of the values because we ordered them as matrix of 9x8, in the preset.asm, and after the recompiling, the running app reading from the eeprom always add a 0 value on every lines of the matrix and the values was not right: we solved the problem changing the matrix from a base 9 to a base 8 thinking about multiple of 2 is better: now the app read the value from the eeprom in the right way! Thank you for the help, very useful, if someone of you would like to have a copy of the code with the implemention for ther eeprom reading, just ask! Bye Andrea
  3. Thank you Thorsten! This sound really good for me and I understand 100% of what you tell me. So this evening, when I'll come home I'll try to do what you suggest me and after I can tell you and all community the result of my work. This is really what I needed, good explanation, in a clear way, very direct, You're the best! Also for people like me, not really good in program languages, this sound to me like a really good thing! Thank you very much!!! Andrea
  4. Hi Thorsten, No, I don't find the forum via google, I'm only a newbie midiboxer with some question! ??? Maybe it's better for me to explain all the stuffs and all my midibox "story" I build up my hardware MBHP some months ago for trying to control some "software synths" like from native instruments or other and I used some "pre-built" apps like mb64 or midio and I find them very interesting; I started build another one 1 months ago with the proposal to start to understand more and think about midibox in a new way expecially about the understanding of the language, not really for writing a new one (it's really much for me) but to understand C and the world of Midibox including the microcontroller world and so on. I find very soon that this is really difficult, so I ask a friend of mine ( person that know C language ) to help me with some things and here we are! Maybe for me it will be more confortable to use apps like mb64 v2.4 and use an external eeprom for store the data but In this way iwon't understand nothing...I need to try myself! THIS IS THE REASON OF MY QUESTION: starting from ain64_din128_dout128_v2_0.zip we made some custom modification to that app for match our project that will include some kind of "presets" for the pots, I mean 20 "user value" that we can call by pressing 10 din, every din will call 10 pots value (and the pots connected to the ain will be "by-passed") , so you have a total of 200 fixed value; I think we call call this a kind of "banks". My friend told me that there's not enough space in the PIC for specify 200 values one by one and he suggested the possibility of store these values in the eeprom, one value for every byte, ( and so i'm asking if this is possible and how...) Also if this friend of mine know C language, there's something that he can't do and he's not very expert in PIC programming. Excuse me for the strange question and the disturb, hope you can understand what I mean, because I really want to know much about the world of programming and the world of microchip, but it's hard and I'm doing it step by step. Thank you very much for your reply. Andrea
  5. still have confusion about it 1) I need to write the eeprom 2) I don't want to do this with MIOS because i'm not a programmer, so it wouldn't be easy for me 3) Maybe it's better to write the eeprom from outside the MIOS 4) I think I have two ways: first using software like midiox ecc and upload the data to the eeprom via midi, second using a programmer like MBHP PIC burner or others. Are these things right? if so, that's my problems: In the eeprom I really don't have to put application or programs files, but only "numbers" banks values and things like these. So with software like midiox or mios studio how can I do this if I only can upload .hex or .syx? Is there the possibility to convert numbers or simply data file to .hex or .syx and upload them? How can I decide to put them to eeprom and not to flash? And how about a picburner? I'm using MBHP PIC burner and p18 but seems to me that I can't write datas to eeprom and I have the same problem like before, the fact that I can only upload .hex files. Is there other software that can do this using MBHP PIC burner? Do you know if there's instruction for p18 in english? I know...lot of questions, but I really can't understand the right way...please help me! :) Bye Andrea
  6. Ok Only one thing: I want be able to write bank datas on the eeprom using my MBHP PIC burner. Is it possible with the p18 software? the program is in German and I really can't understand nothing! Is it possible to use other software for write the eeprom of the pic18f (instead of P18) but using the same hardware (MBHP)? Thank you very much! Andrea
  7. Hi Maybe now I can understand! I want to write banks data on the pic's eeprom, so I have to write an application (.hex) with the data I want to store and then I have to upload it with mios studio or with other software that support .syx; I must specify the address of the eeprom to make sure every byte go to the right place (eeprom). It is right? Thank you
  8. Not out of PIC! You can use an application running on the core to write the eeprom (f.e. MIDOBOX64) or you can use an external software that can write the pic's eeprom from outside ( PC running a software able to do so via midi - midi cable - core stuffed with pic ). As for upload an application without remove the pic from the core using the bootstrap loader, I'm searching for the possibility to do same thing with the writing of the eeprom. possible? Thanks Andrea
  9. Ok I know that the writing of th eeprom is included in the mios features, but I would like to know if there's the possibility of writing on eeprom using software like mios studio or other software "out of pic", software running on PC and capable of doing the upload via midi (like the uploading of mios or other apps) this is for avoid of using a standard pic flashing utility like PIC burner. Is it possible? If so, what is the software and how? Thank you!!! Andrea
  10. Ok, I understand... But which software do I need for writing the eeprom? Thank you! Andrea
  11. Hi These are the PIC18f452 specs: Program Memory Type Standard Flash Program Memory Size (Kbytes) 32 RAM (bytes) 1536 Data EEPROM (bytes) 256 I/O 34 I know the MIOS+Bootstrap+Apps are on the Flash program memory, but what about the RAM and the EEPROM? Are they useful for something? This is my question: is it possible to access the EEPROM of the pic for writing something on it ?(I'm thinking about banks and things like these) How to do? Thank you for your help!!! Andrea
  12. Hi I Red many topics regarding the use of ATX power supply for using with midibox but I think that maybe there's the needing of make something clear! I'm not sure about the things I understand, but I think that +5v out of a standard PC PSU is good for some projects (midio, midibox64 ecc) and not good for others (sid ) that's because ATX is switched and this carry noise in the audio line. Is it right? Maybe is a good things to explain the problem in a definitive way because I think many midiboxer would like to use this kind of PSU. What's the pros of using it? what's the reason for not suggesting its usage? if is it possible to use, how many cores it can supply? For what project it's good? Thank to anyone who want to contribute! Andrea
  13. Thank you very much! I understand, I think the best way for me is using the midimerger with another PIC. Bye Andrea
  14. I have a question regarding an additional midi in port: I have seen the midimerger project and also the IIC midi that provide additional midi in for the midibox and I have seen that both use the RA4 port of the PIC...this is my question: If I use this port of my midibox64 for driving a 6n138 ecc connected to another midiin port, does it works or I need another PIC for doing this? Bye Andrea
  15. Ok, I understand! Now it's clear...it's a sort of simulaton of a pot but done with resistors! Thank you very much, another time!!! I have another question regarding an additional midi in port: I have seen the midimerger project and also the IIC midi that provide additional midi in for the midibox and I have seen that both use the RA4 port of the PIC...this is my question: If I use this port of my midibox64 for driving a 6n138 ecc connected to another midiin port does it work or I need another PIC for doing this? Bye Andrea
  16. Hi For my project I need to use a 6 way position curson for driving an ain. All AIN input need to have a pot and a pot is a variable resistor so I thought that if I put 6 resistors in the 6 pin of the curson with value 0,2.2k,3,9k,5,6k,8,2k,10k I i'll obtain my result. But my problem is with the connection. Pots have 3 pin and my "modified 6 position curson have 2 pin, the first is the common, and the second is the other pin connected to all resistors that can be selected with the cursor; what about the third pin? Help's useful! Thank you! Andrea
  17. Hi :) I find the the ASM apps for midibox are quite easier for a newbie as the C ones! That's why the configuration of the files named XXXX.ini ad the making of syx files for sending to core are very very simple! But, in my opinion, as I red in many messages, if you want to modify something or to write your own apps, C is better because is simple, but the modification of an existing apps in C is more difficult than ASM ones (like Mk_syx). After this prefaction...that's my problem. After many days of studying, trying with asm apps and C apps, I realize that for my own midibox project The MK_Syx files are the best, it have comments and there's a file named Generic.ini that is just perfect! Now I want to add some simple things to my box: pushing a DIN, some controller must go to a specific Value ex: I push a button and 10 controllers values go to 60 in a classic 0-127 range, I push another one and the same 10 controllers values must go to 20 and so on...a kind of "Memory" or "snapshot" function... Have you go some advices for how to do this ? In which way, modifying asm program, adding somethings or with a C programs is association with the original MK_Syx? Can someone please give me some help? Thank you! Andrea
  18. Yes In my thought, meta events stands for many midi events by pressing a button or turning just one pot. Ok, I'm learning C but for me it's a little bit difficult, I try so many times also with differents apps in asm, in c and so on but, also for the english language that is not mine, it's not so easy for me! Many people tell me just a couple of days, just a week and things like these but it's three months and still can't understand so many things!!! Ok, just tryin' another time understanding C but I'm a bit demoralized... No problems with electronics but BIG probles with programming!!! Thank for your help. Andrea
  19. ok Let's talk for real. I have seen all your links ( just seen so much times...) and I probably understand that for things I have to do it's better another application coded in C, so I choose ain64_din128_dout128_v2_0 . ( also for the reason that I don't need the lcd) So I need to assign a "metaevent" to some of my dins for doing things I told yesterday ( pressing a din cause some controller to go to a specific value ) How can I start? suggestions? Thank you very much!!! Andrea
  20. Hi to everyone For my midibox64 project i'm using the mk_sys and the file in it called "midibox64.ini"; I made some changes in the .ini file and all works for my needing; but I have some question, because I need more. Is it coded in C? If so why I can't see files like main.C ecc? I need to make up other changes but I can't understand where I have to made them and how: These are my needs: I would like to assign some metaevent to some dins...very easy messages like this:"when you push the button assigned to din number 1, the value of controller assign to pot 2 must go to 40, the value of controller assign to pot 5 must go to 0, and so on; in other words, a single din "telling" to all the value of some controllers to go to a specific value from 0 to 127. is it possible? Second question: there's the possibily, as I can understand with metaevent too, to choose beetween the pots rows? I try to explain: we have two dins with metaevent and two potrows of 15 pot each, by pressing the first din only must work the first row, by pressing the second din only must work the second row possibly making snapshot like on startup. Is it possible? Anyone would like to help me with coding? :) Thank you very very much!!! Superdavies
  21. Hi to everyone Can you please direct me where I can read something about the difference beetween the buttons behaviours for the config. of mb64 ( meaning @onoff @ononly @toggle)? Or please can someone explain? I really can't find nothing about! Thank you very much! Andrea
  22. Yes This is my opinion too! It is digital so it's not important if the circuitry is open or close, the only thing that matter is the changing of the state; but my real problem is after the start-up! What I have to do? Think about the hammond organ and think about the NI b4...think about the percussion on-off button: in the hammond you have a switch (like the one for turn up the light in your home) maybe a 2 way switch so you have the circuit open or close...it's analog In the NI b4 as for other "Midi" apps for doing this function you have a push button: first push=perc on, second push=perc off it doesn't matter the circuit-state open or close, just the function sending. Now I really want to use the hammond consolle I have here at home so I don't have push buttons, I have only switches: I think I have two possibilities... I can make a little modification to the firmware so it would recognize that it must send control change message when switch turns from open to close and the same control change when it turns from close to open, I think it's possible, this possibility use only one pin of the din but have the problem that ,for instance ,if I turn off the midibox with the percussion switch in position ON and I move the switch to OFF while the midibox still off, when I power the midibox on (assuming that the midibox can recognize the last value ofter poweron ) I have the percussion switch to OFF but the percussion on NIb4 in on. Second possibility: using 2 din and a 2 way switch: if the circuit is close in the first din= control change message for percussion, if the circuit is close in the secong din= the same control change message for percussion, thinking it has the advantage that maybe can recognize the value at startup. Is it possible? What's the "yes and no" of this configuration? Please, please help! Andrea
  23. Yes, I'm talking about switches instead of momentary buttons! Any suggestion for how to modify the firmware named ain64_din128_dout128_v1_3 apps ( the asm one) for acting with switches? Thank you very very much!!! ;)
  24. HI! :) This is my question and it is regarding the configuration of the buttons on midio or in mb64, so we are talking about the DIN module. As most of you already know, I'm midifying an old hammond organ for use it to control VST as B4...I'm probably at the end of my project: the keyboards works, the drawbars and the other pots works...so maybe this is my last problem :-\ I have the mb64 core using for the pots and for some other buttons ( the hammond classic controls ) such as the VIBRATO ON-OF, PERCUSSION ON-OFF VOLUME NORM-SOFT and so on. My problem is that all these controls are two way selectors or three way (deviator ) in a on-off mode not as push button; so for instance, if I take the percussion on-off selector when I turn ON it can send midi on signal but how to made it do the midi OFF signal if the another position is from on to off (from close to open)? If it were a push button just first push and it send On signal, another push and it send off signal, but it isn't...and i really want to maintain the original layout of the hammond organ console. Is there a possibility for doing this working on the firmware? My mb64 is working with the ain64_din128_dout128_v1_3 apps ( the asm one) Another question: Is there the possibility that ( as we can do with the pots ) for example I have percussion ON activated and when I turn off and on the midibox it recognise the last value before the rebooting? Thank you very very much!!! Andrea
×
×
  • Create New...