Testing AIN board

Testing/Troubleshooting
1

I want to test my AIN however I only have a couple of pots i purchased simply for this reason, to test my AIN board before buying all 32 pots.

Smash told me to use jumpers to clamp inputs A4 through A7 to ground on J5B of the core. It’s done. So J5 of the AIN is connected to J5A of my Core and 3 pins of J6 to the other J6.

I have +5 getting to pins 1 and 3 of the pot and ive moved pin 2 around on diff. inputs of the first multiplexer and i dont get any MIDI Out messages  ??? Do I have to connect all 4 multiplexers and have all pots ocnnected in order to get to output something? My DIN board works fine!

2

To only know if the multiplexer works out fine, I used this here: Clamp all analog input pins to ground except one “measuring” pin. This has to be left open up! If you now power on the MB should be sending Midi messages all the time. If you touch it with your finger (as you are yourself an antenna) it should even send much more!

This way you don´t need the pots connected to get a first “functional” test up and running.

If this test fails, something with your AIN or the interconnection to the core should be wrong.

No, you don´t need all the multiplexer IC´s inserted. btw: Normally you want to have the pot connected like that: Pin1 - GND, Pin2 - AIN connection, Pin3 - 5 Volt (why? So at least some current is flowing and the Voltage is divided smoothly in the pot itself. If you have 5 volts on P1 and P3 there´s no current flowing and so you have two parallel 5kOhm resistances in front of your AIN input); but I think you already knew, right? :wink:

Greetz!

3

I read in the other thread regarding pots that, in order to use one or two pots for testing, the application has to be re compiled.

Is this true? I have the MB64E application installed…

4

Is this true? I have the MB64E application installed…

did you enable the AIN in the application? MB64E is made for encoders; the pots are an option and have to be enabled in the main.asm file of the MB64E app.

cheers

5

I have set:

#define DEFAULT_NUMBER_AIN 32

and

#define DEFAULT_ENABLE_AIN_MUX 1

recombined with Convertall.bat and re-uploaded the updated main.syx with the MB64E sysexbox GUI.

I still dont get anything. Am i forgetting to edit something in the main.asm ?

6

this is ok;

just to be sure; you do press “build”/“make” in the MPLAB right? just saving the main.asm won’t work.

if it’s not this, it’s probably some bad connections (and did you wire your pots like pay_c said; +5V, Ain, Ground?)

good luck, marcel

7

http://www.midibox.org/forum/index.php?topic=6212.0

I’m a total newb and have already been moaned at for not reading enough but i do remember Thorsten saying in the thread above that

#define DEFAULT_ENABLE_AIN_MUX      1

should be

#define DEFAULT_ENABLE_AIN_MUX      0

Don’t kick off if this is something entirely different though, It just looked similar to me :slight_smile:

8

The MUX=multiplexer has to be turned of if motorfaders are connected and *can* be turned of if less than 8 analoge inputs are used. So MUX=1 is ok.

I agree with illogik. To go *really* sure, check both last edit dates (in Windows you´ve got to enable the details view for that) of both main.asm and the .syx files sended to the MB. If both is newer date (near to your edit  :wink: ) it´s your stuff normally. FIRST you have to save the main.asm BEFORE compiling it! Sometimes this is overseen, too. If you don´t you´ll compile the old stuff within MPLAB.

Greetz!

9

thanks a lot guys. I wasn’t proceding the right way. All I had done was edit the main.asm file and ran the convertall batch file but the new program never worked so I downloaded the MPLAB IDE program and simply BUILT the edited asm file and uploaded the new hex file. It works!

I finally get all the super fast retarded AIN output messages. Now i see what the fuss was about  8)

10

If you didn’t know about compiling the app… Time to read ucapps.de some more!!! Much more! :slight_smile: