moxi

hi, yes you can and the mods are really easy to do (only one file to mod, see the one named "mios_tables.inc" ,all is well documented)

hi, i'm voting for the solution C.. cause there is just two parameter to setup and then we just have to try many combination just moving an encoder...that's seems to be the more fun for "live" modifications of the track...

it's exactly why i've tested many bit manipulation! i will try this tonight...your code is more clear!

:), thanks again for your hint TK. now the code is working for my four cv output: the define in aout.h: the new code for the file aout.c: AOUT Update of the gate is missing, as i won't use them. my two aout_lc modules are set in 8/8bit configuration, my map.c file is configured to load 8 bit value in aout_value[x] : example, for my first CV: there is probably useless code in the AOUT_Update function...but i've make it working doing a lot of hardware testing, and as i'm a beginner ,i'm not sure that i understood all things fine... thanks you all..

...no sorry, it's from the code i give you.. :-X thanks

it's good, i've removed the second from your code and that works.. 1 get the right pattern for the two values...

ok, i don't know why , but the banked was causing the error "symbol not previously defined", so i've replaced by 0 in my first file, now i've corrected that (i've replaced the banked by "1"). the pattern i get now (with 0x8080,0x8080): 76543210 76543210 76543210 76543210 00000000 11000000 00000000 11000000

With 0x8080,0x8080: first sr: O7=0 O6=0 O5=0 O4=0 O3=0 O2=0 O1=0 O 0=0 second 74hc595 O7=1 O6=1 O5=0 O4=0 O3=0 O2=0 O1=0 O 0=0 third same as first, fourth same as second. with 0x4040,0x4040: first: O7=0 O6=0 O5=0 O4=0 O3=0 O2=0 O1=0 O 0=0 second: O7=0 O6=0 O5=1 O4=1 O3=0 O2=0 O1=0 O 0=0 third same as first, fourth same as second. i shift the registers 16 times

hi, no, with 0x8080 i get 0V on output 1 and 3, and 7.5V on 2 and 4 with 0x4040 i get 0V on output 1 and 3, and 1,50 on 2 and 4 my outputs are 8/8 bit and 8/8bit, range from oV to 10v

what i've understood from the datasheet of max525 and 74hc595( if i'm right), it's that the 74hc595 need 8 bit value and the max525 need 16bit value, but in the 16 bit , only 12 are used to hold the value... but i'm still lost...

yes...

i'm definitively out... :( if someone want to do the job, explaining how and why...that will be a great lesson...

salut, pour les circuits, encoders, kits de composants: http://mbhp.coinoptech.com/ Mikes PCB shop sinon, cherche pour CONRAD.fr , mouser (usa), reichelt (allemagne) pour les boutons: http://www.midibox.org/forum/index.php?topic=7242.0 c'est de l'artisanal, mais ça coûte moins cher, sinon d'une manière générale pour les boutons , il t'en faut de type "momentané"

hi, i get mine from mouser...

hi, i'm ok with the operators, but (excuse me if i'm not enough clever) when i read: (aout_value[0] | (0x3000 i understand that aout_value is ored with 0x3000 but when i read: (0 << 14) first i don't understand first where come from this "0", secondly, i don't understand why we are bitschifting "0" i'm learning, feel free to don't reply if you think it's obvious...

does that mean that the result of "aout_value[0] | (0x3000" is shifted?

ok, so "AOUT_Load2SR(aout_value[0] | (0x3000" set to 1 the bits 15 and 16 now ,what mean the "0" in the next expression "(0 << 14)) (to what is applied the << ?

btw: now my aout_lc output value, not the good ones ,but it's already a good things ... :)

hi, another (stupid) question: could you explain what mean "AOUT_Load2SR(aout_value[0] | (0x3000 | (0 << 14)), aout_value[4] | (0x3000 | (0 << 14)));" (i've learn how work the "if" fonction, what means " ll " and "<<") ; i know that "AOUT_Load2SR(aout_value[0]" call AOUT_Load2SR, that's ok, but i can't find any information about the symbol "|" ...

ok, it's the purpose of the CS/RCLK line that change.. i will go on....

in the aout_lc driver, there is this code: and in the aout driver : for me,reading this code, that are the same pins that are defined for the two modules (c5,c4 and d5), but in fact the module are NOT connected to the same pins.. so i suppose there is something i'm understanding wrong..

ok, but what about my question: you wrote two time the same code for defining pins (in aout_lc and aout driver of mbCV app) but at this end the modules are connected to diferent pins..how it's possible?

it's ok for the understanding of the asm code... but to say that in other words: 1.how to define that there is the RCLK pin that is used instead of the CS pin? are changes to be done in the aout.h file? 2.why defines of pins are the same in the two drivers (in midibox CV app) and hardware pining is different? ==> i'm missing something...

i've tried to change the hardware pinning...no success in fact , i need more explanation about when i compare the defines in aout.h and the ones at the beginning of the LC driver, i see the same thing but with two different names...changing the name of the defines (eg replacing "#define AOUT_LAT_CS" by "#define CV_AOUT_LC_LAT_RCLK" and doing the same replacement in the prog won't lead to any changes...the app is still adressing the same pins...and if i'm right , i've to adress different pins to adress the LC module... as i don't understand how pin are serviced, it don't mean a thing of trying many combination of prog'.. it's what i'm doing since 3 day's...and even if i make it work, i won't understand why.. i'm using two LC module, but just making the first one working would be enough in a first time...