kapser

Thank you for the fast answers. So if I understand it all well, its better to start with programming the PIC from scratch and not using the MIOS software (IRS?) at all ? I wanted to use some midi control of the POV and doing some stuff on the BPM. It seemed to my it was easier to take the MIOS platform as basis ( as it already implements a lot of midi stuff of course ). Any resources on programming assembly ?

I want program a POV ( spinning leds ) application with MIOS_C. So I need to switch leds on/off with a very high speed. What kind of speeds can I achieve ? Does it depend on the amount of outputs ( I want to use all the 128 pins ). I calculated that I need a refreshrate of about 25kHz ( 38 us ). Any tips or things people experienced. Or do I just have to start programming and measuring the outputs with a scope ?

I'm building some application for an interaction project at my university. I want to use the midibox64 configuration, but don't want to use the menu, page and other option because I don't have an LCD. With mk_sys I've configured the pots, but how do I configure to DIN's to send a note on. In the midibox64.ini file, is written that I should disable the buttons in the asm file. How can I do that ? I've looked in different files, but it's not exactly clear to me how everyting is organised. Also the question how I can let a led ( on the DOUT ) burn on ( for 500ms or something ) : - an incoming sysex string - if a specific DIN is triggered and it should stop burning if I trigger another DIN I don't have I clue how to do someting like this ( change the asm file ? ) Thank you in advance.

My problem is also fixed, it was a bad solder connection from one of the resistors to the optocoupler.

Yep, and others to try if that might work.

Well, I also tried to upload mios with another interface ( emagic unitor8 ) and did the last send/receive test. Again the bytes are changed :-( Is there a way to upload mios without midi ?

Well, I did ALL the debugging ( optocoupler test etc. ), but nothing seems wrong with the hardware. If I receive sysex I get a feedback string everytime a string of 1024 bytes is send. Everytime this string : SYSX: F0 00 00 7E 40 00 01 F0 What does this mean ??? Because it's different then F7, but I couldn't find it in the error codes table. If the sysex "uploading" is done, I'll get the 2 second message ( F0 00 00 7E 40 00 01 F7 ) Again.

Well, I use a midiman midisport 2x2. Thought it was a pretty realiable device, but I could try another one of course.

Well, now I've connected Tx to Rx without the microprocessor. If I send a lot of bytes ( 1024/512/64) at the same time, I get other messages at the input ( like pitchbend ). Now I send bytes with this configuration : This are the first hex numbers I've send : F0 00 00 7E 40 00 02 00 00 01 00 40 3B 62 3F 04 03 5E 13 But I receive this in the sysex scratch pad: F0 00 00 7E 40 00 02 00 00 00 00 00 3B 62 3E 00 03 1C 02 70 It goes wrong after 9 numbers. I suppose that I should receive the same value's as I'm sending.

Well I have the same problem. I passed check number 6. I get a response from the device every 2 seconds ( SYSX: F0 00 00 7E 40 00 01 F7 ) If I upload the mios_v1_7.syx with midiox ( i tried low level output buffer from 64 bytes ) and a delay of 1000 ms. I get a response on the input. Everytime this string ( F0 00 00 7E 40 00 01 F0 ) a lot of times ( seems like a reaction of the pic on the incoming data ). After my "upload" is finished, I keep getting the 2 second message's. I've read every item on your site and tried different thing, but nothing seems to work.

Well, mine voltage regulator was also very hot ( not normal hot ). Problem was that a placed some IC's on the DIN en DOUT board in the wrong way :-( So they seem the work as a diode or something. So unplug everthing on your CORE module ( all the external modules voltage lines ) and check if that solves your problem. If it is, then there is certainly something wrong with the external modules.

Well, mine voltage regulator was also very hot ( not normal hot ). Problem was that a placed some IC's on the DIN en DOUT board in the wrong way :-( So they seem the work as a diode or something. So unplug everthing on your CORE module ( all the external modules voltage lines ) and check if that solves your problem. If it is, then there is certainly something wrong with the external modules.