OneLittleFonzie

nederlander - check actief - check MB64, nog niet helemaal af. Controller voor Arturia Prophet V en Jupiter V.

Hi All I have made a nice controller for the Arturia Prophet 5 but now I want to make something new. My son would like to make a robot that can be controlled by midi (dancing is his idea). Now I would like to attach a infra red transmitter to the MIOS32 based box (I prefer I2C but not necessary). Has anyone any idea, experience how to do this? I know the Lego IR Powerfuntions protocol: http://www.happybricks.com/TBs%20Media/TBs_20091029_1/LEGO%20Power%20Functions%20RC%20v110.pdf Thanks in advance Take care Ron

So my plan is to make a sort of Midibox 64 with Core32 bit a bit bigger. First I want to make a Jupiter 8V and a Prophet 5V controller with one midibox 64x. The next project will be a controller for the Arturia Moog Modular V. The first one I can make with the supported 64 analog inputs and the 128 binary inputs. I'm already going to use NRPN messages. For the modular I would need more inputs. So, I'm considering using lines for the multiplexer for analog inputs. I'm surprised this is not standard as you would double the number. Is there something I don't know? If there is a reason not to do so I would like to hear that. For the multi position switches I was thinking about using analog inputs and a few resistors with the switch to get like 3 postions. Or would it be "cheaper" to use 2 binary lines? I'm really existed about this :-) I've made a controller for the JV1080 10 years ago; Only using I2C. 128 pots :-) Regards Ron

Excellent. Everything works fine except for the LCD. It's an old Hitachi HLM 2041. Need to check whether it's compatible. Otherwise I have a smaller one too. Going to start programming now :-) Thanks for all the help Ron

Wow Thorsten, you are the best. I quickly wanted to check because you responded so fast. It works after I deleted the miosstudio.xml file. Still not sure why it didn't work at some point. I guess the default connection from the menu doesn't do the same as removing the file. Anyway Thanks very much Ron

Well, the jumpers were the problem. Now it seems uploading is suddenly a problem :-) Received Checksum: 00 - OK Received Checksum: 00 - OK Received Checksum: 00 - OK Starting upload of project.hex Requesting reboot... Waiting for upload request... Received Checksum: 00 - OK Received Checksum: 00 - OK Received Checksum: 00 - OK Received Checksum: 00 - OK Received Checksum: 00 - OK Received Checksum: 00 - OK Received Checksum: 00 - OK Received Checksum: 00 - OK Received Checksum: 00 - OK Received Checksum: 00 - OK Received Checksum: 00 - OK Received Checksum: 00 - OK Received Checksum: 00 - OK Received Checksum: 00 - OK Received Checksum: 00 - OK Received Checksum: 00 - OK Received Checksum: 00 - OK Received Checksum: 00 - OK Received Upload Request Received Checksum: 00 - OK Received Checksum: 00 - OK Sending block #1 08004000-080040FF Received Checksum: 00 - Error Sending block #1 08004000-080040FF Received Checksum: 00 - Error Sending block #1 08004000-080040FF Received Checksum: 00 - Error Sending block #1 08004000-080040FF Received Checksum: 00 - Error Sending block #1 08004000-080040FF Received Checksum: 00 - Error Sending block #1 08004000-080040FF Received Checksum: 00 - Error Sending block #1 08004000-080040FF Received Checksum: 00 - Error Sending block #1 08004000-080040FF Received Checksum: 00 - Error Sending block #1 08004000-080040FF Received Checksum: 00 - Error Sending block #1 08004000-080040FF Received Checksum: 00 - Error Sending block #1 08004000-080040FF Received Checksum: 00 - Error Sending block #1 08004000-080040FF Received Checksum: 00 - Error Sending block #1 08004000-080040FF Received Checksum: 00 - Error Sending block #1 08004000-080040FF Received Checksum: 00 - Error Sending block #1 08004000-080040FF Received Checksum: 00 - Error Sending block #1 08004000-080040FF Received error code 01: Less bytes than expected have been received Aborting after 16 errors

Wow That's very impressing so much service :-) I guess it's because I missed the 3.3/5 volt selector I missed (J24/J25/J26) Going to try tomorrow morning Thanks very much Ron

I quickly tried that yesterday evening. I'll read the documentation of MIOS studio and try again. Thanks very much for your time. I'll come back on this. Regards Ron

It sure is strange. It's exactly like on the diagram I'm going to buy a LCD 4*20 this afternoon. This way I can check what the MIOS32_DOUT_PinSet method returns. I can imagine that I did something wrong but I'm more surprised about the activity led on the board. It does exactly what is needs to do but it doesn't toggle when I receive incoming midi data. The handler works because I can return midi messages which I see in the midi monitor strange, strange, strange Thanks Ron

Thanks for the quick reply So, I've used the example "apps\tutorials\009_dout" should work. In my case it doesn. I've connected 1 led for now and nothing happens. When it starts up the led lits while booting as well as the activity led on the board. I've added this piece in de APP_Init and the APP_MIDI_NotifyPackage event handler u8 i; for i = 0 ; i < 127 ; i++ ) { MIOS32_DOUT_PinSet(i, 1); } Nothing happens when I press a button, also the activity led doesn't flip while MIOS32_BOARD_LED_Set(1, ~MIOS32_BOARD_LED_Get()); is in the handler body. When I add: if( midi_package.type == NoteOn && midi_package.chn == Chn1 && midi_package.velocity > 0 ) MIOS32_MIDI_SendCC(port, Chn1, 1, midi_package.velocity); I receive something back from the MIOS32 in my midi monitor so that handler is activited. What is happening (or not). Thanks very much Ron

I just started building Midibox stuff. The MIOS32 version Midibox 64 is my goal. Now that I'm testing a bit with programming I realize that for instance DOUT doesn't work. Is that right? How far is the STM32 version project. If necessary I could contribute. Thanks Ron