-
Posts
2,516 -
Joined
-
Last visited
-
Days Won
147
Content Type
Profiles
Forums
Blogs
Gallery
Posts posted by latigid on
-
-
Looks ace, thanks for your work Bruno.
-
What is the pinout of a Nixie tube adaptor? It would depend on the interface: SPI, I2C, parallel etc. as how you might connect everything.
I think Nixies use voltage that can kill you, so it's not for the light-hearted.
-
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...
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.
-
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.
-
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.
-
The aim is for spring, I can't promise anything definite though.
-
-
Many thanks Bruno!
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.
-
I'm not sure if software debounce affects encoder events? We've heard a lot of stories about low-quality Bourns encoders. Better seem to be ALPS EC12.
-
Hey, wait until it works first! But prost/santé/cincin!
Where did you get your chip? The DOUT probably works because all outputs are inverted, whereas the SI will be out of phase with the rest (at a guess).
-
That'll do it, you need the non-inverting 541
-
The DIN should show +5V as there's a 10k pullup attached. You could try connecting RC1 instead of RC2, as they pulse at the same time anyway.
The incremental behaviour is weird, it's like the data is being latched on every clock. You're sure you've got RC and SC correct? No shorts, including any of pins PB15, PB13, PB12, PD10 on the Discovery board?
-
Even though some of the other breakouts are more ideal in terms of form, they don't always include every pin. You should take care with the particular MCU used as it may have reduced performance. The Waveshare stuff looks fairly trustworthy with regards to quality, documentation, support, etc.
-
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.
-
I was wondering the same. Switching with the left hand also leaves the right hand free for playing (e.g. a keyboard). For those using the Wilba SEQ for years, that's also a learned "home" location on the left.
Best,
Andy -
Hey, really nice job! I love how many different textures and patterns are happening.
-
Are you sure that PICkit 3 supports the chips you have? I have a vague idea that some of these are supported on PICkit 2 or clones, not completely sure.
-
I think everything is 1.5mm aluminium. The colour will probably change too :).
-
The SEQ uses new designs of Core/MIDI boards, so save those for other projects :)
-
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.
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.
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.
Many things will change: circular holes for the MIDI DINs, different knob choice, maybe coloured windows.
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.
-
9
-
-
-
Sorry to see you go! It's good practise to put your location and prices for the items.
-
Thanks for reporting back, I'm glad you got it sorted.
-
As shown in the above image, the C+ pin is not connected to the switch and the other two terminals (left and right, between C+/B and R/G respectively). should be used. But try with jumpers directly on the pinheader too.
Chronulator (cool meter clock kit)
in Miscellaneous
Posted
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