Jump to content

latigid on

Frequent Writer
  • Posts

    2,516
  • Joined

  • Last visited

  • Days Won

    147

Everything posted by latigid on

  1. No worries! I know Peter and a few others ran a mixed colour scheme and it seemed to work out well, though the current drive through the LEDs might get a bit non-linear I think. Stress test is currently running with the "worst-case" matrix fully on, so no multiplexing. Half an hour in and nothings burned out yet. What do you think is a fair test time?
  2. If you're concerned with the LED lifetime then simply increase the values of the RJ resistors to a current you are comfortable with. I would consider the probability of an LED matrix "freezing" in the way you describe as a low risk though.
  3. Not sure if this is a grumbling post about schematics not being supplied? You bought the PCBs, so you are welcome to the schematics if you send an email in reply to your order confirmation. Snippets of the schematics are supplied in part throughout the troubleshooting thread. This is generally a better way to provide targeted help to builders and I'm very responsive in that regard. So, rant over! :-) If that wasn't your intention, then I'm sorry. The LEDs are indeed multiplexed as is typical for MIDIbox projects and driven through bipolar transistors. The key datum is actually the peak forward current per chip, listed as 100mA. True, our multiplexing speed and fraction is slower and larger than the given conditions. All of the LEDs have been put through a burn-in test using the same circuit as the one in the SEQ, so we know that they are good. Also, these are superflux LEDs with much higher current-carrying capacity than your typical LEDs. Have fun building!
  4. Hi, We currently use this one from Reichelt: https://www.reichelt.de/d-sub-kabel-1-1-25-pol-stecker-stecker-1-8-m-2-0-m-ak-4010-p3997.html?&trstct=pos_0 TK. suggests up to five metres would work. So I guess that means 16 feet in Freedom Units. Unfortunately I couldn't find a decent one from Mouser but if you need to get all of your parts there, 571-1658613-2 plus 26-way ribbon could do the job (and would be less bulky than a cable). Another famous sequencer does it that way :).
  5. It's getting there! Next in the pipeline is the LoopA, then the BLM.
  6. The J16 port is physically the same on the wCore, the E part just breaks out the LEDs (GPIO) and reset switch to the panel. The Waveshare board of course might have layout differences compared to the Discovery. The pull-up resistors for the J15 display port required changes that I didn't fully investigate, but it works so I'm happy :).
  7. I've reached the end of where I could offer help. If it was working before, switch back to a previous firmware version? I think TK. modified _NG to accommodate mixtures of AIN ports as inputs and outputs, so maybe something to do with that! Best of luck, Andy
  8. Sorry, I see F4 in the title now. What version of _NG? If it's a recent version try an old one and vice versa. Could be a software bug. From a hardware perspective it might be that your analogue voltages are out of range? I.e., greater than 3V? If the MCU freezes it might have run out of memory and needs a hard reset. But reset from MIOS Studio typically doesn't work especially on Windows, or at least a restart of MIOS Studio is required. Personally I don't see the merit in using AINSER and AIN (MCU). The offboard ADCs are much better with far less jitter than the onboard ones.
  9. F1 or F4 Core? AIN (MCU pins) or AINSER8 or AINSER64? I presume MCU. ?? What build version of _NG are you running?
  10. If you didn't already, add jumpers to the CAN pins in case the buss is used in the conventional manner (CV/gate). Putting a high-speed digital signal on the power cable might introduce some crosstalk and should be tested.
  11. Hello, Glad it worked out better this time :). I personally don't use the min/mid/max calibrations but rather the 0V--10V. If you switch the channel back to off and then try another does the issue remain? Could be a software bug perhaps, but if you can calibrate I think it's fine. Best, Andy
  12. Now we just need to do black panels to match the case
  13. Nice! If you like it's also no issue to cancel the PCB order. But more DACs might be useful in the future. You can have up to 32 AOUT channels, so maybe a second A1 module set dedicated to CCs/LFOs? (I'm not 100% sure on the configuration.) So we can conclude from this that the DAC is at least somewhat resilient to reflow/extra heating?
  14. I also remember a problem like this. But somehow I was able to get around it as I even made a video where I could vary the NRPN to access all 360 hues of a WS2812. I had a look at my NGC and could see nothing special configured. So please follow Bruno's advice, maybe he has found the problem.
  15. I don't have a solution ready for this, so you should try out with Bruno's. Consider also using the Euroceiver and a desktop device where power requirements and space for displays/controls is not an issue. Such discussion would be better suited to a private channel or at least in a dedicated topic.
  16. Sure, most skiff cases are much shallower than this. I built my own cases with probably >100mm depth, because a lot of the DIY modules from years ago were much deeper :). wCore has all of the expected ports and could be mounted "straight on" like is done for the SEQ. This would have a shallower depth but a wider panel of course. It's a compromise of using pre-fabbed MCU breakouts and avoiding fine-pitch SMT, as it can be difficult sometimes as we've seen! You could also panel-mount a Discovery board Core in the same way. You'd miss panel-mounted SD access and a USB cable, but it's very doable.
  17. The wCore currently available could also be used as an F4 Core variant mounted in a Eurorack system. Depth would be the PCB length, so 77.5mm. The idea was to USB/SD PCBs mounted on the front panel, plus any MIDI DIN etc. as needed. I think the next ProgrammA iteration would be a fine controller for MBCV and would use the same Line Driver/Euroceiver combo :).
  18. @TK. looks awesome and I'm glad it fits! Will you fill the rest with more CV modules or get a nice filter or VCO? :) @enveevee don't worry, we'll send some replacement boards and you can try again :).
  19. Hi Niels, Thanks for the update and details. I'm sorry that you had trouble with the soldering but maybe something was learned along the way. On the upside, the PCB can be easily replaced and because it's modular you don't have to throw away the rest :). Best, Andy
  20. You're able to control the SO/SC/RC1 pins on and off? And they make it all the way to the superDAC board? You can also measure on the DAC SI (Rx) and SO (Tx), pins 9 and 12, respectively. Even better if you have a scope, but the pins should show some voltage depending on the speed of your multimeter. Pin 7 should be at about +5V. The previous troubleshooting was in another thread, but the -5V state and red LEDs are normal if the DAC channel doesn't deliver any voltage. In your case it seems like no channels are providing voltage. Did you try the drag soldering method Peter suggested? Personally I prefer to use a chisel iron tip and just do a few pads at a time, then use desoldering braid to remove the shorts after.
  21. On IC2, pins 2,3,4,5, the pads look quite different, did something happen to them? Also check that the pads make contact with the IC pins (power off). So test on the pad and the top of the IC pin just to make sure that there is a good connection. Test that no pads are shorted together, except for the channel outputs as indicated earlier.
  22. No worries! For the cables, it is correct if the red stripe always ends up on the left of the notch. But always check the voltage: the red striped side should be -12V. The 11 pin header (J3) connects the superDAC board to the transmute8 board. The pin outputs are channels 1,2,3,4 0V NC 0V 5,6,7,8 (0V=ground, NC= no connection). Pin 1 is square shaped. You can "calibrate" all channels to Max and see if you get any output. If you're viewing the board from the top and with the J19 side up and the DACs showing, you have channel one closest to IC1 on the left of J3 and channel 8 on the right side. For testing the pins, start with J19 on the Euroceiver with the IDC cable unplugged; i.e. measure from the topside of the J19 shrouded header. Once a cable is connected to superDAC, just use empty top pins of J19A. This will work at least for SC and RC1. You could also measure on the DAC pins but be careful not to slip with the probes.
  23. Use the MIOS terminal command "testaoutpin" and ensure that you can control each of SO SC RC1 (maybe SI but it isn't used for AOUT). The issue could be further up the line.
×
×
  • Create New...