TK.

I don't know SmashTV's variant so good, therefore I cannot help here so much. But you could just compare your wiring with the original schematic. You can follow the tracks from the 74HC165 to the terminals of your board in order to find out the right pinning Best Regards, Thorsten.

http://www.farnell.de for 8.10 EUR Best Regards, Thorsten.

In the other lines it's 1, 2, 3 - it just selects the output channel I must say, in the meantime I find it funny which details can be discussed on a code I hacked in within 10 minutes ;-) Most of this stuff is just "standard programming". Some lines might look strange when they are out of context, but they make sense when you see the whole code and compare it with the MAX525 datasheet. Best Regards, Thorsten.

I think this was a typing error - Altitude is right, R1 is connected correctly to the LM317, but it's hard to see it without eagle. Best Regards, Thorsten.

It's the *_plus.brd file - Mike will send me a fixed version in the next days Best Regards, Thorsten.

Wow! What a great price! How to highlight this posting? Because some people asked for faders in the past and found much more expensive offerings - they could be saved from paying too much money Best Regards, Thorsten.

In my oppinion it makes sense to talk about a single board solution again after the first release. Who knows what will change until then... as mentioned several times before: I can only guarantee, that with the modular concept you will have the highest flexibility. Best Regards, Thorsten.

I deleted most of the old releases since I feel a bit sheepish when everybody is able to find the bugs I made in the past... ;-) What is so interesting on the old stuff in particular? Best Regards, Thorsten.

I still don't get it... You are selecting one of the drivers (they don't run in parallel) The clock line is always connected to pin RD5 The data line is always connected to pin RC4 The CS/RCLK line is always connected to pin RC5 in these two configurations. Of course, you can connect the modules to other pins if they are free or if they are allowed to be shared, in this case you only need to change the constant values of the #define's Best Regards, Thorsten.

The PGA2311 provides a serial interface with Chip Select, SDI and SCLK line - so it's very similar to the MAX525, which means, that there are assembly and C based drivers available which you could use as a template. From the MB side you only need a core module... Best Regards, Thorsten.

I don't understand this question - why shouldn't it be possible? Best Regards, Thorsten.

Yes, this DIN mapping works with the first 8 shift registers. Each encoder entry just overrules two DIN pins, so no problem here Best Regards, Thorsten.

After the protection buffer is an offset of ca. 4V, so yes: it's possible to use a LM324, but I'm not sure if it gives you the same results like a LF353 Best Regards, Thorsten.

As Stryd_one mentioned, the purpose of the "Register Clock" is different than the purpose of a "Chip Select" line. At the end it doesn't much matter, to which pins these signals are assigned, you just only have to take care, that a chip select line is active during the whole transfer (AOUT module), and a register clock is triggered after a transfer (AOUT_LC module) You could even call the "RCLK" pin still "CS" pin - the name is not important (it could only confuse others if they read the code) Stryd_One's code is correct, but you have to take care, that only the 16 bits of sr1_value are shifted out Why different defines? Because for different MIDIbox variation, where pins are sometimes allocated by other functions... Best Regards, Thorsten.

1) detented sind mit Rasterung, non-detented ohne - die Rasterung ist hilfreich, wenn man Werte exakt einstellen moechte, aber hinderlich beim sweepen. 2) nein 3) gar nicht Gruss, Thorsten.

Hallo, bei einem Drum Clone kommt es ja nicht so sehr auf Genauigkeit an, oder? Dann koenntest Du alternativ auch einen Spannungsteiler als Referenz hernehmen. Bspw.: [tt] 5V |----/\/\/\/\/\----*----/\/\/\/\/\----| GND 1k | 470 | Vref = ca. 2.35V [/tt] Gruss, Thorsten. P.S.: ich glaube, es ist wirklich Zeit, eine Alternative zum MAX525/MAX6007B zu bieten...

Did you try it? Best Regards, Thorsten.

This is my personal macro to do something if a bit is set or cleared - it improves the readability. The macros are defined in macros.h the difference between IFSET and BIFSET is, that BIFSET works also with BANKED registers >= 0x80 <= 0xf7f It leftshifts the constant n times. e.g., "0x01 << 3" results into 0x08" - this is also to improve the readability yes, I cannot say, where changes have to be made - there might be different places. Better not to change the pin layout of the GP buttons, especially if you want to keep it compatible to MBSEQ V3 You can change the mapping in main.asm, USER_ENC_NotifyChange you can achieve the same (and more) in the song menu, when song mode is turned off (press song button twice). You can predefine pattern sets and chains at different "song offsets" (A1, C1, E1, ...), and select the offsets with the 16 GP buttons during the sequencer is playing. I think that I've described this mechanism in the ChangeLog Best Regards, Thorsten.

Moxi, I don't understand why you are not using the original code of aout.c and doing the changes there? AOUT_Load2SR() has to transfer 16 bits instead of 32, it has to service the RCLK pin instead of the CS pin (compare with aout_lc driver) AOUT_Update() has to select the values which should be uploaded to the shift registers... and thats all! Best Regards, Thorsten. Best Regards, Thorsten.

You have to ensure, that no unused encoder entry overrules the pins, which are connected to buttons (if you are unsure: remove all ENC_ENTRY lines of encoders that are not connected to your box), and you propably have to adapt the DEFAULT_DIN_SR_PIN_* settings, if you have changed them in the meantime Best Regards, Thorsten.

This is not possible with MBSID V1, it will be possible with MBSID V2... Best Regards, Thorsten.

Please read the wishlist, it's everything in there! Best Regards, Thorsten.,

You are using macros, which are not defined, and which do mostly not run on gpasm anyhow. Replace "rgoto" by "bra" IFSET by "btfsc ..." (see macros.h of a common assembly based application) IFCLR by "btfss ..." (see macros.h of a common assembly based application) and if there are still errors, search for other macros I forgot here. In general, the savest thing when using inline assembly functions is not to use macros at all Best Regards, Thorsten.

thats the reason why I will wait at least for one month before ordering samples ;-) Best Regards, Thorsten.

When you are starting the "make" file from the command shell, you will see the errors on screen. In addition, they can be found within the listings, which are located in the _output directory Best Regards, Thorsten.