protofuse

hum... of course. I didn't succeed in asking, sorry. ok to close the circuit, of course. BUT, on this schematics, there is a big short circuit, for my opinion ... but indeed, I have to understand something that seem to be hard to explain. the circuit will be close by putting the 5V to the 5V input on the core, and the gnd of the core to the gnd of the psu. right? so, why should I put closer to the psu a line between 5v and gnd ????? maybe, it could be ONLY to light a pretty led .... I thought this line had a specific function...

no problem with all of that (current, voltage, ohm's law etc) , but... why do I have to link +5v to Gnd before my whole circuit? I mean, if I have to do that, I guess the specifications of my psu are involved ...?! right ?

I did the trick aout transistor and 1-3 bridge on my two cores as seen here: http://www.ucapps.de/midibox_lc/midibox_ng_switching_psu.pdf how can I calculate the resistor to put in serial with the led between the ground and the 5V ??? any ideas or explanations could be fine and I'd increase my knowledge too :) all the best, protofuse

thanks a lot lylehaze. it will be a common cathode led matrix. I did the calculation: 150, 100, 100 seems to be fine indeed! I'll buy my resistors :) thanks a lot!

hi experts, before to finish soldering my DOUTx4 modules w/ ULN to drive my rgb matrixes, I have to choose resistors values. The rgb leds I got are those : http://www.sparkfun.com/datasheets/Components/YSL-R596CR3G4B5C-C10.pdf Vred = 2V Vgreen= 3.2V Vblue= 3.2V all for I=20mA so I guess: Rred = 100 ohms Rgreen = 160 ohms Rblue = 160 ohms am I right ?? the fact I use ULN, the fact I use DOUT modules would alter these values ??? I guess, no. But I'd prefer to ask before, if anyone has experiences with that all the best, protofuse

hello, you can check the noofny project here: http://noofny.blogspot.com/ or mine here: http://www.julienbayle.net/diy/protodeck/blog/ mine is not finished, but I tweaked the code to fit my hardware. feel free to send me an email :)

Hi thorsten did! it works. pic18F4620.lkr & pic18F4620.lib are correctly placed now ;) I plan to upload asap thanks a lot !! protofuse

Hello, I read that: http://www.midibox.org/dokuwiki/doku.php?id=using_pic18f4620 (it seems to be obsolete, but...) I read that too: http://www.midibox.org/dokuwiki/doku.php?id=mios_pic18f4620 I tried to change pic18F452 by pic18F4620 in makefile.orig in order to compile the code especially for the pic18F4620. here is the complain (I also enabled the warning): H:\MIDIBOX\protodeck\_Code\protodeck\protodeck_CORE_1>make rm -rf _output/* rm -rf _output rm -rf *.cod *.map *.lst rm -rf *.hex mkdir -p _output sh ./bin/mios-gpasm -c -p p18f4620 -I./src -I ./include/asm -I ./include/share -I ./modules/app_lcd/dummy -DDEBUG_MODE=0 -DSTACK_HEAD=0x37f -DSTACK_IRQ_ HEAD=0x33f -I ./modules/mios_wrapper modules/mios_wrapper/mios_wrapper.asm -o _output/mios_wrapper.o sh ./bin/mios-gpasm -c -p p18f4620 -I./src -I ./include/asm -I ./include/share -I ./modules/app_lcd/dummy -DDEBUG_MODE=0 modules/app_lcd/dummy/app_lcd. asm -o _output/app_lcd.o sh ./bin/mios-sdcc -c -mpic16 -p18f4620 --fommit-frame-pointer --optimize-goto --optimize-cmp --obanksel=2 -I./src -I ./include/c -I ./include/share - DDEBUG_MODE=0 main.c -o _output/main.o main.c:227: warning 85: in function MPROC_NotifyFoundEvent unreferenced function argument : 'entry' main.c:227: warning 85: in function MPROC_NotifyFoundEvent unreferenced function argument : 'evnt0' main.c:227: warning 85: in function MPROC_NotifyFoundEvent unreferenced function argument : 'evnt1' main.c:227: warning 85: in function MPROC_NotifyFoundEvent unreferenced function argument : 'evnt2' main.c:242: warning 85: in function MPROC_NotifyReceivedByte unreferenced function argument : 'byte' main.c:309: warning 85: in function ENC_NotifyChange unreferenced function argument : 'encoder' main.c:309: warning 85: in function ENC_NotifyChange unreferenced function argument : 'incrementer' main.c:331: warning 85: in function AIN_NotifyChange unreferenced function argument : 'pin_value' ./bin/mios-gpasm modifies _output/main.asm, result in _output/main__mios-gpasm-tmp.asm gplink -s ./etc/lkr/p18f4620.lkr -m -o project.hex ./lib/libsdcc.lib ./lib/pic18f4620.lib _output/mios_wrapper.o _output/app_lcd.o _output/main.o ./lib/pic18f4620.lib: No such file or directory make: *** [project.hex] Error 1 indeed ./lib/pic18f4620.lib doesn't exist. should I forget the specific compilation and use all the pic18f452 libs as usual? should I dig further and make my compilation for my p18f4620 ? any ideas would be welcome :)

probably, I found something, and obviously, I share it: http://www.harmony-central.com/MIDI/Doc/table1.html could help. but, should I use note-on byte status? or note off? or both of them in another const ? I'm lost :-(

I'm looking informations about the const: button_event_map I understood basically what it involves, but what kind of data to put into ?? { byte1, byte2 } for pot_event_map, byte1 = midi status and byte2 = midi data what do I have to do with button_event_map ? (I really looked for about that, sorry if I missed something )

Hello experts and the others, I'd like to use a real IDE in order to code my midibox app. This one could be eclipse as I already use it for java and python programming. I read carefully: - http://www.midibox.org/dokuwiki/doku.php?id=windows_toolchain_quickstart - http://www.midibox.org/dokuwiki/doku.php?id=howto_app_dev_eclipse_ide But I'm a little bit stuck. How could I do for using it for programming my app? Eclipse IDE fits my needs, but I can change for another IDE if another one fits better with mios programming... cheers and regards!

thanks a lot :)

hello experts, I made a little mistake by ordering a nice (& expensive) PSU with 2 outputs: 12v/2A & 5v/6A so, I understood I could use it without the 7805 and with a bridge between pin 1 & pin 3 of the 7805 is it right? I understand that 2 capacitors + Rectifier aren't useful too , but should I keep them? drop them? any idea/tips would be appreciated :)

hi experts :) I'm looking for potentiometers for my deck project.. I checked on radiospares, mouser, alpha taiwan, farnell etc there is always a required feature missing required feature (ideally !) - linear & 10K (especially required, of course) - knurled & 6mm diameter shaft - with solder lug (=not for pcb) Basic!! But I don't find them :( I need them for them for those: http://fr.farnell.com/jsp/search/productcompare.jsp?SKUS=1440013,1440005,1440004,1440003,1440002 so the "knurled shaft" feature seems to be necessary! and this is the feature that stuck me in my research! I mean, I found a lot with plain shaft or D shaft ! so the question is, do you think I can use them with my knobs + glue (or else) ??? your help would be appreciated!

indeed... the loard resistor are already on the lines ("before" the leds..) so ... it doesn't require another one I'll use a 2803 (18 pins..) so I have to re-check that to directly put it on the DOUTx4 module.. I think I'll do a thing like mike/noofny: not sure yet :)

any ideas about resistors value for the darlington array legs ??? for the leds, I guess it can be calculated easily by hand or by this kind of tool: http://led.linear1.org/led.wiz by putting 1 as the led number and 5V as source voltage... and the datasheet value for I values... but for the transistor array ?????

yeah! it is a great news noofny. my contribution doesn't deserve a beer (or a coca cola) bugfight did the trick :) thanks to him too! I just hope to test all of that ASAP!

hello, As I'll need around 100 buttons, 100 rgb leds, and 100 pots + 1 LCD, I began to design an architecture with 2 cores. after reading about multiple core hardware, some question remains. I understood that there are (at least) 2 kind of method to use multiple core when it is required: - via LTC module (here) - via midibox link (here) but... in my case, with 2 cores, I'm a little bit stuck. )) I'll use the LTC for midi in & out led purpose only )) I'll put 2 DINx4 + 2 AINx4 + 2 DOUTx4 on each core )) I'll use a character LCD handled by one core what is the more efficient link I can do between my two cores ? I'm able to read.. so if a link I didn't check is available, I just ... run to it :) thanks a lot for this site... and for the GREAT midibox framework!

hi stryd_one, sorry, I didn't check this thread and see your answer. thanks for your answer. I'll get 2 pic 4620! the project involves a rgb led matrix we're discussing here, if you're interested too: http://www.midibox.org/forum/index.php/topic,12786.30.html cheers!

bugfight, noofny, any infos about all of that? I'll probably work on the code asap (this day... in the next hours as here: it is 11AM! cheers

bugfight, USER_SR_Service_Prepare is an ISR too... (sorrrrrry!) so probably, your code works like that and works with efficiency ... :) noofny, I guess it could be useful to make one core drives one matrix, and the other one the other matrix because of overloading risk of ISR.. experts, what do you think about that?

as I'm just as the beginning of my project, I cannot test it by myself, but... I almost understood how it can work.. the schematic of noofny, with the verification and eventually fixed thing about the ground of pin 9 (or pin 10 with ULN28003) may work fine! in order to avoid flickering, I guess we have to use an interrupt service routine. it is a process called periodically AND independently of the main routine. I read this a long time ago about interrupt and timer of arduino board (atmega8 controller) As described here, we have to use the timer2 and a particular interrupt. indeed, the timer 0 is the clock reference timer1, timer2 takes timer0 as a reference so, we can "hijack" timer2 for our use ///////////////////////////////////////////////////////////////////////////// // This function is periodically called by MIOS. The frequency has to be // initialized with MIOS_Timer_Set ///////////////////////////////////////////////////////////////////////////// void Timer(void) __wparam { } I'd like to put inside this Timer(void) function the cycle we talked about above. pratically, it should work like that: main functions => handle button (via DIN SRs) + handle pots (via AIN SRs) interrupt called functions => handle RGB Leds matrix (called via an interrupt) why shouldn't we OVERload the Timer(void) function ? it is easy: when it will be called, the system ONLY care of what it will be inside this function.. it means: no functions from the main thread works!! ...thus it is called i n t e r r u p t... pretty and cool name and ... indeed the appropriated name ;) basically, it means: no pots handling, no buttons handling during the interrupt time (= the driving leds matrix time) I'll code something asap. but as I said, I cannot test it. so, probably, we'll work with noofny (one in France, the other in Australia...!) but the solution is near... and others had done it before (example: the monodeck II)

bugfight, the code you made is to use with the first schematic from noofny or another (one of those in my link) ?? I found a mistake in the schematic, hope noofny didn't make it in the real world. the "common" pin (pin 9 for the ULN2003 and 10 for the ULN2803) isn't linked to ... ground in our case. personally, and probably, I'll do that: bugfight? what do you think about that and about the code we can use for it ? by sending bytes from the CORE to the DOUTx4, we successively commute the rows of the matrix to the ground and light up colors in the line successively: for line for color light up all led in the line with current color the only question I have: does it flicker......................? indeed, at a time, one color of a led in one line is up... I'm afraid about that. I have to dive more inside the midibox framework in order to figure out how timers are used .. because: handle pots, buttons, and ... making so quick needed cycles... I guess it requires asynchronous stuff.. (thread..) but i'm sure it already exists in this powerful framework

I complete my previous post by this: with this, we can see that with one Darlington array + 3 SR, we could easily drive a 8x8 RGB Leds matrix :D so... I'm going to drink a cocaCola to celebrate! I'll post more from my schematics work asap!

hello, I contribute here as I worked on rgb led matrix too. The only "problem" is the fact the cathods are linked... ground is common and if I sink the current on a line, it sinks from each cathode and blip blip blip: the three colors are light up together. so transistors are here only for avoiding that! but I guess everyone understood that, if it wasn't the case, I hope it is clearer for several I just add it several links that could help: 1/ led spi interface from sparkfun http://www.sparkfun.com/commerce/product_info.php?products_id=760 => especially the firmware code. even if it is a spi between your core and the led driver, the matrix is connected via SR + a pretty ULN darlington arrays watch this pdf it shows a correct rgb led driver wired! but this is incomplete without the wiring of the RGB led matrix involved ATTENTION: the matrix is " as if it was" a common anode in this sparkfun example ! all the examples here are common cathode! but the philosophy is the same watch it: currents have to be sinked by the darlington. you saturate one transitor by sending +v to it it closes the circuit between the corresponding line and the ground ... so yes: the current gets out the led cathode to the ... commuted ground :) and you do it on a cycle. so now, it is complete ;) 2/ unsped & Devon Jones/Octinct (+ ) for those who don't know the octinct, it is a NICE and WORKING full* rgb monome clone arduino based. http://unsped.blogspot.com/ Check the code it uses. no darlington, ok, but 3 transistors: one for each color. the cycle is: for all lines for all color light up this led the first link about that, that talks about darlington is : http://www.upwardnotnorthward.com/2008/01/my-first-project-full-colour-rgb-monome.html 3/ arduinome's playground about LEDs http://www.arduino.cc/playground/Main/InterfacingWithHardware#Output => LEDS & Display (just added the unsped link, it hasn't been added ... what a omission!!!) BTW, I began a project like noofny, I only designed things on visio and ordered 2 midibox 64 kits at Mike's shop. If I can help about that, I could easily debug when I'll wire my matrixes...but I'm sure above links provide solutions, especially the first link that shows how the hardware has to be wired! If you need help, just ask!!