• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About roberto

  • Rank
    MIDIbox Newbie

Profile Information

  • Gender
  • Location switzerland
  1. How to connect Common Anode RGB LEDs

    ...just for the record. im slowly slowly get into the deep sea of MIOS... i managed to map the RGB buttons with the multicolour test mentioned in TK's post above. everything's fine... (although magenta is missing in the map, i added it at the end after red...) back to construction 
  2. How to connect Common Anode RGB LEDs

    switched back to first comuter, and there it is again... button behaviour inversed again, damned...
  3. How to connect Common Anode RGB LEDs

    strange... i booted the whole thing on a second computer and now it's working as expected...  will investigate...
  4. How to connect Common Anode RGB LEDs

    yes, those are nice buttons, rugged, but 10 bucks each...  well, before fiddling with RGB hue, i have to solve following by inverting i turn off the RGBLEDs on startup: # Common Anode RGB LEDs EVENT_LED id=1 inverted=1 type=NoteOn key=36 # Red LED EVENT_LED id=2 inverted=1 type=NoteOn key=37 # Green LED EVENT_LED id=3 inverted=1 type=NoteOn key=38 # Blue Led by sending a NoteOn 36/37/38 and Off from the MIOS Keyboard i can light and turn off the 3 LEDs. Fine.   Now, when i define a button the behaviour is reversed EVENT_BUTTON id=81 fwd_id=LED:1 type=NoteOn key=36 range=0:127 button_mode=Toggle EVENT_BUTTON id=82 fwd_id=LED:2 type=NoteOn key=37 range=0:127 button_mode=Toggle EVENT_BUTTON id=83 fwd_id=LED:3 type=NoteOn key=38 range=0:127 button_mode=Toggle will say, the LEDs are OFF when the button sends a NoteOn and ON by a NoteOff... i tried to inverse also the EVENT_BUTTON and the range (127:0) but nothing helps... is there something else i need to invert? i don't get it.
  5. How to connect Common Anode RGB LEDs

    cool, thanks latigit, works... as i understand following code inverts the output: EVENT_LED id=0 inverted=1 EVENT_LED id=1 inverted=1 EVENT_LED id=2 inverted=1 etc. now i have to figure out how to assign the RGB LEDs to different velocities on the same note... phew, this coding is a big book to get into it...    the RGB button has internal resistors, so i think it's not necessary to match the color brightness...  
  6. Hi   After testing the functionality of the CORE, DINs and DOUTs it’s time to layout the Controller.   I want to use (among others) 16 RGB Buttons and im unsure how to connect it to the DOUT’s. I read some threads about it but didn’t found the answer that satisfied me.     The RGB Buttons are COMMON ANODE. One possibility is to attach it to a 6 *8 LED Matrix with the drawback to loose brightness. I don’t want that, I have enough DOUTs to connect the LEDs directly, so I would like to go the direct way.   Is it possible to do that without using additional ULN Arrays? As I understand it is possible to drive one RGB LED with one Midi Note and make the color with different velocities right?   And since I am at the very beginning of everything I don’t understand how the code should look for that...      
  7. yesss, the right chip arrived. all works fine now! thank you guys for your help... now it's time to to build the machine! 
  8. ur welcome. Reichelt... correct, the outs are inverted. i'm confident it will work after. whoohooo :-)
  9. you got a beer latigit. cheers!
  10. RC 1 instead of 2 - no change of behaviour... and still no shorts at any of your mentioned pins... grrmpf RC and SC are correct, tried it with different ribbons and straight jumpers... just to mention, IC 1 on the CORE is a 74 HCT 540 instead a 541... ordered a 541 - they sent me a 540. looking at the specs, it doesn't matter. right? i'm getting fuzzy :-(
  11. damned, i measure and measure, check and check, over and over, i can't find it. so thank you latigid for the advice... RC1 and 2 are NOT conected together. there's continuity from SI to pin PB14, no shorts anywhere to SC, RC, +5V, 0V, pins 9 and 10 are like expected and also 10k pullups are there... but yes, the crank has to be there somwhere. i measure 4.9V on the DIN, i think this is ok? im sure it is something really dumb. maybe something with the configuration? because i get some invalid infos like: ((don't know what tokens and .NGR and .NGC are for)) [8346.901] show ngr_tokens [8346.903] Token processing is: enabled [8346.903] Token memory allocation: 0 of 16384 bytes [8346.903] .NGR file is: invalid [8346.903] Tokens are: invalid attached is the whole config file and at the end the midi routings and the reset info. there is no source port set ON. is this intended like that? or do i have to change that? Snapshot #0 not stored in /DEFAULT.NGS yet.. how to store ??? config.rtf
  12. ok, card reader finally arrived... it's recognized it seems: [3381.877] sdcard [3381.879] SD Card Informations [3381.879] ==================== [3381.879] -------------------- [3381.879] CID: [3381.879] - ManufacturerID: [3381.879] - OEM AppliID: [3381.879] - ProdName:     [3381.879] - ProdRev: 133 [3381.879] - ProdSN: 0x00000707 [3381.879] - Reserved1: 193 [3381.880] - ManufactDate: 135 [3381.880] - msd_CRC: 0x29 [3381.880] - Reserved2: 1 [3381.880] -------------------- [3381.880] -------------------- [3381.880] - CSDStruct: 0 [3381.880] - SysSpecVersion: 0 [3381.880] - Reserved1: 0 [3381.880] - TAAC: 62 [3381.880] - NSAC: 0 [3381.880] - MaxBusClkFrec: 50 [3381.880] - CardComdClasses: 1461 [3381.880] - RdBlockLen: 10 [3381.880] - PartBlockRead: 1 [3381.880] - WrBlockMisalign: 0 [3381.880] - RdBlockMisalign: 0 [3381.880] - DSRImpl: 0 [3381.880] - Reserved2: 0 [3381.880] - DeviceSize: 3779 [3381.880] - MaxRdCurrentVDDMin: 4 [3381.881] - MaxRdCurrentVDDMax: 5 [3381.881] - MaxWrCurrentVDDMin: 4 [3381.881] - MaxWrCurrentVDDMax: 5 [3381.881] - DeviceSizeMul: 7 [3381.881] - EraseGrSize: 31 [3381.881] - EraseGrMul: 31 [3381.881] - WrProtectGrSize: 31 [3381.881] - WrProtectGrEnable: 0 [3381.881] - ManDeflECC: 0 [3381.881] - WrSpeedFact: 4 [3381.881] - MaxWrBlockLen: 10 [3381.881] - WriteBlockPaPartial: 0 [3381.881] - Reserved3: 0 [3381.881] - ContentProtectAppli: 0 [3381.881] - FileFormatGrouop: 0 [3381.881] - CopyFlag: 0 [3381.881] - PermWrProtect: 0 [3381.881] - TempWrProtect: 0 [3381.881] - FileFormat: 0 [3381.881] - ECC: 0 [3381.881] - msd_CRC: 0x7c [3381.882] - Reserved4: 1 [3381.882] -------------------- [3381.882]  [3381.882] Reading Root Directory [3382.057] ====================== [3382.057] Retrieving SD Card informations - please wait! [3382.058] SD Card: '': 990 of 990 MB free [3382.058] [......a] 00/00/-20  00:00:00 AM     43432 DEFAULT.NGC [3382.058] [......a] 00/00/-20  00:00:00 AM     584 DEFAULT.NGL [3382.058] [......a] 00/00/-20  00:00:00 AM     251 DEFAULT.BIN [3382.058] [......a] 00/00/-20  00:00:00 AM     520 DEFAULT.NGS [3382.058] [......a] 00/00/-20  00:00:00 AM     3124 DEFAULT.NGK [3382.058] [......a] 00/00/-20  00:00:00 AM     43432 TEST.NGC [3382.059] [......a] 00/00/-20  00:00:00 AM     3124 TEST.NGK [3382.059] done. i can save and load from card. i resoldered all boards again (DIN's, CORE), checked for shorts again and changed the IC's on the CORE (74HCT541 + 74HC595) still no luck... the DOUT's are working perfectly, the DIN's don't. all i get is the attached debug infos when i short VS and D7 on the first Header J3 on the DIN. it sends 64 note-on's on close and 64 note-off's at open. i get this on all DIN boards but ONLY on the first header (J3). all other headers (J4-J6) and pins (D0-D7) don't react...    debug.rtf
  13. thank you Gerald, i think i'll wait until the card reader is here. I'm away the next few days so it's worth waiting. i dort see any button presses with the default NG configuration. but i can send messages from MIOS to DOUT. i will recheck the DIO boards again, but im shure they are ok, because all 3 of them do the same error... cheers
  14. sorry man, thank you million for your help but you are going into the wrong direction. lets forget the rgb button! i managed to get the leds work, i'm aware about the common anode... lets keep it simple. if I'm doing a short between Vs and D0-D7 of J3 on the DIN then i should get a message in the MIOS right? it's not happening...