lcpr

That's very simple and what I assumed. Just didn't know it was taken care of automatically. Great thanks!

Stupid newbee questions - I don't understand how to use the DOUT in Midibox64. I see what you can select, but what doe it mean, what does it do? All I want is to be able to assign an LED (DOUT) to a button when the button is defined as a "toggle" type. How / can / \where do I do that? Are they 'already mapped' ? What is the "shift register"? ################################################################################ # LED Map: assignes the LED shift registers to the Button Shift # registers or special values # Currently following values are supported: # 0 Default Setting (see Map below) # 1 Button Shift Register 1 (Button ID #1-#8) # 2 Button Shift Register 2 (Button ID #9-#16)

Thanks TK.

Thanks TK. Sounds like NG would be great. Can you point me to the information on how the NG hooks up to the analog / DIN / DOUT. Would I need a MBHP_AINSER64 if I want to use only 8 analog inputs?

Midibox with analog potentiometers AND encoders, and buttons? Is there a way to do it? Seems like the encoders are just 'buttons' - right? I have a xy joystick that is analog (potentiometer) and I would like to use it along with some encoders for other functions. Is there any Midibox applilcation for encoders and analog? Can I just use Midibox64 and connect and encoder to DIN and use it like an incremental 'button' switch???

Ok - I *think* I get it. There is the bootloader and operating system (which I have loaded), then there are applications like the Midibox64, Midibox64e, etc like this one (latest?) zipfile: midibox64_v2_4f.zip midibox64_v2_4f\setup_midibox64.hex <--- is this the right file to upload? then a setupfile (bank?) like zipfile: midibox64_v2_4f.zip midibox64_v2_4f\tools\mk_syx\midibox64_generic.syx -OR- the output from Serge's wonderful Midibox64 configurator. Is the above right?

I know this is a newbee question - I'm just confused by the process on setting up Midibox64. I have the V1.2 bootloader and V1.9 MIOS on my chip. Sometime in the past (forgot how etc) I configured it for a Midibox64e. I'm reconfiguring my hardware for a Midibox64 to use analog pots etc, and want to replace the Midibox64e (application?) with Midibox64 (application). What 'pieces' do I have upload to the chip? I see the midibox64_v2_4f.zip file has "setup_midibox.hex". Is THAT the code? And/or what about Serge's http://miostools.midibox.org vMidibox64 application? That contains "midibox64.syx" files..... Do I upload BOTH the setup_midibox.hex and then a *.syx file? Or just the syx? Confused....

Thanks Electruck - I figured there had to be something set to tell the core that what mux to use. I may try messing with the software, or just get an AIN module (and future expansion capability) and use the prebuilt Midibox64 sysex. BTY - is there any documentation that describes the way the DOUT works? I'm having trouble finding how all the options are set. I did build a successful Midibox64e a few years back but have purged my memory of all the setup I did to get it working!! I'm converting over to Midibox64 form "e" since I have a XY joystick (analog pots) that I want to use for Wavestation controller.

Stupid question maybe... I want to build a midibox with only 8 analog pots (and a bunch of switches). What do I do software-wise ? Do I need an AIN module or can I just go direct to the mainboard (core) pins WITHOUT COMPILING another hex file? Or is it just easier to use an AIN and use the MidiBox64 premade app? Or can I modify the ini file where is shows, then convert to syx using the perl script??? [TYPE] midibox64 [bANKNAME] "Generic Bank " [CONNECTED_POTS] 64 I have the Serge Midibox editor and it doesn't seem to have anywhere to say how many pots there are connected.