nILS

Och... Echt jetzt? Nein. Falsch. Richtig. Ich formulier Dir das gerne auch nochmal in Deinen Text um, dann kommt's vielleicht an.

I think you should ask around if some midiboxer is willing to forward you a crystal oscillator.

Nö. Genau andersrum. Mehr Widerstand zwischen Basis und 5V macht weniger Strom, und damit weniger Hintergrundbeleuchtung.

If at any point you need real-time support for some coding issues it might be quicker to drop by the chat - just saying ;)

Na wenn Du doch aus irgendeinem irrigen Grund annimst, "links" sei der Widerstand am geringsten - was wäre, wenn der Designer der Platine den Poti so verdrahtet hätte dass genau das gegenteil der Fall ist? Dann wär's genau andersum. Wenn es DIch tatsächlich interessiert schau mal hier rein: http://ucapps.de/mbhp/mbhp_core_v3.pdf Schau mal was der "Luminance" Poti da eigentlich macht und wie der angeschlossen ist.

No. It proves that the things relevant to burning them are still working, nothing else.

Moved from "Design Concepts" to "Miscellaneous".

Your function will work this way, as "sendProgramChange()" is sth different than "sendProgramChange". I typically prefer naming the parameters differently though. Doesn't seem to make a lot of sense to me to call the parameter "sendProgramChange". I'd go with just "program" as this describes best what the parameter is - the desired program. Is this difficult to code? Any functions I should be looking into? No. It's a bit more code than using all the premade stuff of course ;) I would suggest using J5 for the inputs - there's a neat driver already written for just that purpose. Look in mios\modules\j5_io there's a readme that explains the usage. I'd suggest using that for the inputs as it handles the debouncing etc iirc. That leaves you with having to find 6 unused pins for the LEDs. Since you are not using an LCD, I'd simply suggest using PortB for that - 8 pins, all physically adjacent, too. To set up PortB as an output port, you'll need to write 0x00 into the TRISB register (each bit corresponds to one pin, 0 = output, 1 = input). From that point on you can write to PortB using either PORTB directly, overwriting all 8 pins at once or the PORTBBits struct to write individual pins easily. Here's a quick example: void Init(void) __wparam { TRISB = 0x00; // set Port B as output PORTB = 0x00; // turn off all LEDs // some doodling with the pins PORTB = 0x0A // 0x0A = 10d = 00001010b which means the 2nd and 4th pin are set high (LED on) PORTBBits.RB0 = 1; // set 1st pin high PORTBBits.RB7 = 0; // set 8th pin low PORTBBits.RB3 = 1; // set 4th pin high PORTBBits.RB2 = 0; // set 3rd pin low }[/code] I am not at home atm, and I have no way of testing the code I write, so don't expect it to work, this is from the top of my head, so for instance the capitalization of PORTBBits might be wrong :)

Und was ist wenn der Poti einfach andersum angeschlossen ist? :rolleyes:

MIOS_MIDI_BeginStream(); MIOS_MIDI_TxBufferPut(0xC0); // Program Change, Channel #1 MIOS_MIDI_TxBufferPut(0x12); // Program Number 12 MIOS_MIDI_EndStream(); [/code] That's 18 (1 * 16^1 + 2 * 16^0). You know, you can just use decimal numbers as well ;) [code] MIOS_MIDI_BeginStream(); MIOS_MIDI_TxBufferPut(0xC0); // Program Change, Channel #1 MIOS_MIDI_TxBufferPut(12); // Program Number 12 MIOS_MIDI_EndStream(); Question 2: You can do that. When a button gets pressed MIOS calls DIN_NotifyToggle and passes the pin state and number. const unsigned char pc[4] = {0, 6, 12, 18}; void DIN_NotifyToggle(unsigned char pin, unsigned char pin_value) { if (pin_value) return; // ignore button up if (pin < 4) sendProgramChange(pc[pin]); else // other buttons }[/code] sendProgramChange would be a function that does the stuff at the start of the post. Doing it this way, you introduce a pretty static connection between hard and software though. I usually use defines to map pins to button names. That allows changing pins/functions on the fly. [code] #define BUTTON_PC0 0 #define BUTTON_PC6 1 #define BUTTON_PC12 2 #define BUTTON_PC18 3 void DIN_NotifyToggle(unsigned char pin, unsigned char pin_value) { if (pin_value) return; // ignore button up switch (pin) { case BUTTON_PC0: sendProgramChange(0); break; case BUTTON_PC6: sendProgramChange(6); break; // and so on } } Also, if you only need a total of 12 IOs you can easily use pic pins instead of DIN/DOUT modules. J5 for instance offers you 8 pins and if you don't have any other modules attached you can basically use any free pin.

Ganz gegen den Uhrzeigersinn = minimum, wie an jedem handelsüblichen Gerät. Sicherheitshalber fängt man alles immer am Minimum an :)

When it's time. There'll be an announcement on the forum, no worries, you won't miss it.

:frantics:

Well that explains it. There's only one audio output socket and that's stereo. The other socket is an audio in (also stereo).

Since you haven't mentioned it - are you using a cable with stereo plug? What SIDs are you using?

It takes Note Events as well (actually that's the main thing it does).

No. It means there's one of four cores, which is correct. No. You have 4 banks for patches (A-D) and one bank for Ensembles (H).

That's because you shouldn't use 8-bit mode. Two of the pins are used for the CAN bus.

Das Multimeter reicht für den Anfang auf jeden Fall. Jeder anständige Lötzinn hat schon Flußmittel drin. Extra "flux" brauchst Du nur bei SMD.

Ooh, that is a good point!

Moved to "Parts Questions".

Judging by the amount of traces on the top layer it seems rather unlikely that this is a multi-layer board, then again it's mass-produced with lotsa smd... Either way, all 3 pins of an encoder need to be connected for it to work. 2 data lines and one ground or pullup line will be needed.

The analog and digital grounds are connected on the AOUT_NG modules. There can only be one ground. If you have more, how on earth would the voltages be referenced towards each other? Without having seen some pics of the board and your wiring it's really kinda hard to give you any further hints - make sure you have the wiring correct (between core and aout) and you've jumpered the AOUT_NG board correctly. Check if all the parts are correct, report back :)

I'm not really sure if cross-posting that was necessary... Anyways, here's my answer again. Woot? Made by DOS? With a really weird date code? "Just promise me you'll be careful..." Make damn sure you have a way of getting your money back. Most of what I read on other forums recently points towards most "SID"s being around in larger quantities being either remarked (not necessarily an issue) or just random chips that happen to have the same pin count ;)

It shouldn't matter how you ground things, as long as there's only ONE ground and that's going everywhere you need it. Are you using the bipolar option? What PSU are you using? An shorts/bridges on the AOUT_NG? Got some high-res pics?