Jump to content

latigid on

Frequent Writer
  • Posts

    2,516
  • Joined

  • Last visited

  • Days Won

    147

Posts posted by latigid on

  1. Okay, so the Nixie takes normal 5V logic signals and is powered separately with higher voltage?

    If it is just a binary coded decimal, MB_NG can do that:

    http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fleddig1.ngc

    led_matrix_pattern=<pattern-number>	LED patterns can be specified if an event should forward its value to a LED_MATRIX element:
    1: the first LED pattern specified with LED_MATRIX_PATTERN n=1 commands
    2: the second LED pattern specified with LED_MATRIX_PATTERN n=2 commands
    3: the third LED pattern specified with LED_MATRIX_PATTERN n=3 commands
    4: the fourth LED pattern specified with LED_MATRIX_PATTERN n=4 commands
    Digit1: outputs the first (rightmost) BCD digit of the value. See also cfg/test/leddig1.ngc
    Digit2: outputs the second BCD digit of the value: (value / 10) % 10
    Digit3: outputs the third BCD digit of the value: (value / 100) % 10
    Digit4: outputs the fourth BCD digit of the value: (value / 1000) % 10
    Digit5: outputs the fith BCD digit of the value: (value / 10000) % 10
    LcDigit: converts the value directly into a BCD digit as used for the Logic Control protocol. See also cfg/test/leddig2.ngc
    LcAuto: to handle the Logic Control protocol correctly, this pattern type will set the pattern number (1..4) according bit 5..4 of the received MIDI event value. Bit 3..0 will select the pattern position, and the 6th bit will set the "Center LED". See also cfg/test/logictrl.ngc for the usage

     

  2.  

    Quote

    the RGB button has internal resistors, so i think it's not necessary to match the color brightness...

     

    Perfect, even easier then! Good choice on the buttons.

     

    6 hours ago, roberto said:

    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... :cry:

    It does take a while to understand the coding, but just go through the many examples. Notice in the "RGB hue sweep" thread, TK. has basically what you need. He uses a map to define the LED colour based on an incoming CC, so change that to notes over the range you require. The velocity should change the dim level, at least this is one way to work with "smart" LEDs.

     

     

  3. For common anode, wire the anode to +5V or your supply voltage (possibly through a resistor) and connect your cathodes to DOUT pins. If the light output is different for each die, you may want three resistors on the cathode side instead. E.g. red has a lower Vf, so may end up brighter, often green is too bright etc., so control the current with the resistors.

    595s can sink current, meaning they "can provide ground/0V." So the output is "inverted" for common anode parts. This can be specified in MB_NG. When the 595 output is high, the LED is off. When it's low, the LED is on.

    You shouldn't need any transistors if the current is nominally around 20mA or so. 

    I haven't tried with the dim levels of normal RGB LEDs, but TK. has in your second link above.

  4. Ah the fun of early release designs! 

    That would be something to discuss with Adrian H. I believe that he's working on including a panel to blank out the unused holes. It should be cheaper (from the supplier end) to keep track of just one design, and I think the price will be more than acceptable for end users.

  5. Many thanks Bruno! :cheers:

    Just to note, there will be some PCB revisions for version 1.1. In general, you can consider to start getting parts together, but I would recommend waiting until the spec is validated.

    Also, some of the non-Mouser parts will be offered along with PCBs. So hopefully that's only two parcels needed to ship.

  6. As the DOUT can be correctly addressed. this means the SC and RC lines are okay. I assume that RC1 and RC2 are connected together on the PCB? 

    This gives me the impression that the problem is the SI pin (pin 5 on J8/9). With the ribbon cable connected to the DIN, is there continuity between this pin and PB14 on the Core? Is this pin shorted to anything else, such as SC, RC1/2, +5V, 0V?  Are any of pins 9 and 10 on the 74HC165s shorted? From pin 10 IC1 onwards, the signal should see a 10k pullup resistor. 

  7. Adrian is finalising the case design, hopefully he doesn't mind me teasing a few pics. Note that these are not final and will probably change.

     

    Adrian_concept.png.8d61c64665e10bd57bcf8

    Concept, shown as the left-handed design. The PCBs will work both ways, but you have to choose a left- or right-handed front panel.

     

    Adrian.thumb.png.e0acc77b01bfda68dafc829

    This one has too-high caps around the wheel. Originally the wheel PCB was mounted at a different height, but now everything mounts on a (very clever) interior shelf. Only one sort of round cap required.

     

    Adrian2.png.58938b7bdf7ea757a5b9780a38e1

    Many things will change: circular holes for the MIDI DINs, different knob choice, maybe coloured windows.

     

    Adrian_rear.thumb.png.67f94c23dac9e388a7

    The IO can be mounted either at the back or bottom. This means the unit can be either desktop or 19" mount :).

     

    More info as I receive it.

     

     

    • Like 9
×
×
  • Create New...