gm02froe

Hi Getting slowly into the simple test applications I struggle at the moment with a rather strange effect. I ajusted the ain64_din128_dout128_v1_3.zip application (see topic: http://69.56.171.55/~midibox/forum/index.php?topic=5034.0) to my own needs and I am able to - build a main.hex file without any errors and upload it with MIOS Studio onto my core and/or - build a main.syx file with perl and upload it with midiox onto my core in both cases the application runs just as intended. but when I power off the core and plug in the power again, it wont react on incomming MIDI signals anymore. any hints? cheers martin

Hi everybody it finally works. thank you LX for the files and TK for the code. there is still an open issue though, but I will start another thread for this one... cheers martin

Hi LX and all you did was changing mios_tables.inc, compiled the application again and uploaded the HEX? Or did you make the additional changes TX suggested (USER_MPROC_NotifyFoundEvent) inside the main.asm? Because as far as I can see I dont make any mistakes in this process. best regards martin

Hi I am testing my first AOUT module with aout_example_v1_4 - application and dont get the expected results: Sending midi notes (with the help of MIOS Studio MIDI Keyboard Controller)signals doesnt change the voltage on pin #0 and #1 as expected after reading the aout_midi.inc. The LCD Display shows the correct note pitch and veolicity. The LED on the AOUT board is on. The power connections are done according to http://www.ucapps.de/mbhp/mbhp_shx8_interconnections.pdf (without the SHX8 module of course, which would be the next step) I test with help of a voltage-meter connect between v1 resp. v2 and (J2-)Vs any hints or ideas are very welcome thanks martin ** ADDITIONAL INFO ** I was able to run MidiBox CV, so the hardware works fine. But I am still not able to run the AOUT testapplication on my setup. Since I plan to run the AOUT with a SHX8 module, myissue is resolved. SO up to the next challenge.. (However, there is a little itch)

Thanks LX but this not the case. I had the mentioned errormessage of a path longer than 62(?I think) charakters and resolved this. As far as I can say, I dont have any problem with the compiler. all is green. can you control the DOUT's with midi? best regards martin

Additional information There might be an issue with the "USER_MPROC_NotifyFoundEvent" function playing around with lcd_print I figured out the following: - once the application is uploaded and a button is pressed, the function is called, even though NO midisignal was sent to the midibox. (according to the doc it only reacts on received midisignals that are mapped in the CONFIG_MIDI_IN table) I print out the entrynumber with "call MIOS_LCD_PrintBCD3". no matter which button is pressed (see above) or which midisignal I send the number is "55" (Assuming this method displays the content of WREG). However, the proper LED is switched on and off - so I obviously dont grasp the whole thing... - after a (power off/on)-Mios boot, the USER_MPROC_NotifyFoundEvent is not called anymore (the display doesnt show any reaction), not even by a button. best regards martin

Hi Thorsten no errors at all. The only message during build that doesnt look kosher is: Make: The target "C:/..../ain64_din128_dout128_v1_3/main.o" is out of date. kind regards martin

Hi Thorsten Thank you very much for your quick reply. I successfully implemented the MIDI controllable code for DOUT. Though deleting the code inside the "USER_DIN_NotifyToggle" function doesnt do the trick. The button still toggles the corresponding LED. However, when I plug off/on the powersupply to the core, the Button doesnt toggle the LED anymore. Only.. nor can I control the LED via MIDI anymore. The button still sends its MIDI signal though. As soon as I upload the new main.hex (I work with MIOS studio) I have the same effects again as I described above. I made the following test: When I simply delete the code-snipplet inside "USER_DIN_NotifyToggle" without adding the code for "USER_MPROC_NotifyFoundEvent", it works as expected: The button doesnt toggle the LED anymore (and the LED doesnt react on MIDI signals of course). ....Its still pretty dark in this black box, and I just lost my lighter...anybody got a match? cheers martin P.S. ... in order to understand your stroke of genius from last month again! :-)

??? In order to get my head around the AIN64DIN128DOUT128 application and the mios_tables.inc: The first 128 entries define the midi-events sent in case of a DIN-event. The next 64 entries define the midi-events sent in case of a AIN-event. Where are the events defined that control the 128 DOUT? Do they correspond with the 128 entries for DIN? That would mean If I send back the same midi-event received for a DIN-event, the corresponding DOUT LED will be set on/off, like with MIDIO128, right? (my tests showed this doesnt happen, but maybe I made a mistake?). When a DIN-event occours, the corresponding DOUT LED lights up. Is it possible to turn this off? thanks for any hints martin

Hi LX funny that you just have the same problem as I wanted to post now. I noticed the same effect, compared to the midio128 application where it is possible to trigger the led with midi. as far as I can see the ain64_din128_dout128_v1_3 - application is only a test application, and will lack the functionalities of midio128 (the amount of code speaks for this). to get to the required result we either have to expand the midio128 application so that it can handle AIN as well, or if the ain64_din128_dout128 can be expanded so the DOUT reacts on midi-events. Maybe some of the experts can give us a hint or two? however, I am not familiar with PIC programming or assembler, so for the moment I cant give any help, but we might join forces... ;-) so long martin

Thanks for your replys! I will go for a second core then, cause I need these 128 dins. And I will post the result of this work. It wount be a synth though... cheers martin

Hi I am planning to build a midibox64 and need 64 AINs 64 AOUTs and 128 DINs What is the easiest way to add those additional 64 DINs? cheers martin

Hi All My current project asks for a solution that allows me to control many analog inputs and outputs (reading different kinds of sensors and controlling different kind of devices - from 12V up to 240V), and my idea is to do this via midi. midibox64 together with the MBHP_SHX8 module seems the right joice to start. MidiIO is no good because it only supports digital IO (right?). Instead of pots, faders and buttons I would like to use simple interfaces to connect cables (plugs). In order to control devices that work with more than 5V (which I believe the CV In's and Out's operate on) I attach another external device that translates between those voltages. Is this the right approach? are there any details to consider? I appreciate any reply and hint. kind regards martin froehlich PS. I am really a newbee, I have never done a job like this, but I have professional support, at least on the electronics side. But I do not have (or have available) any experience in porgramming MIOS or assembler.