Jump to content

latigid on

Frequent Writer
  • Posts

    2,516
  • Joined

  • Last visited

  • Days Won

    147

Posts posted by latigid on

  1. 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.

  2. 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.

  3. 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.

  4. 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 :).

  5. 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.

     

     

     

     

  6. 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.

     

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

    J19.GIF.c785b2daf68377186a9eda82f2fd2afb

  8. Hi,

    For IDC cables, the most important thing is that the red stripe or pin-1 marker is on the same side for both ends of the cable. It doesn't matter if the cables loop back around using the strain resistance or not, or in other words if the ribbon enters from the top or the bottom of the connector.

    Shrouded headers on the bus boards will force the connection orientation though, so if the cables are "twisted" with the red stripe on different sides, the power polarity will be reversed. Maybe your power distribution has non-standard female headers? Pictures would help.

    I don't think it's related to this though for the A1 module. Red lights on mean the op amps are correctly powered and with the -5V offset.

    For the superDAC board, I hope that you didn't plug in the Eurorack power there? Pictures of the murder scene? Overheating is possible; what soldering temperature did you use? Having no output would be unexpected. I know that sometimes channels just become less linear. 

    max525-5500.thumb.GIF.0e2e3cbbd96a043b2f

     

    You should have +5V on the red pins, 2.048V on the blue pins. Yellow should be the DAC output. You should be able to measure this voltage or on the 11-pin header.

    Check the cables as usual.

     

  9. 1 hour ago, enveevee said:

    I installed all the modules and like to calibrate but when i power on the a1cv board all leds are all lighted red and when meassuring voltage all inputs have 5v. Do you know in what way to look? 

    +5V or -5V? Inputs or outputs? You mean you can't change the voltage of the outputs?

     If you followed the tutorial, the LEDs should glow red with negative voltage. Or did you use different LEDs?

    How are you sourcing the +5V on the Euroceiver? Still over USB or with the regulator/jumper?

     

    From the description, I think the DAC is not outputting any voltage, so the transmute8 board defaults to the -5V offset. This could be caused by 

    • no +5V power
    • AOUT not configured (select module type AOUT)
    • cables/improper board-to-board connections/cable in wrong J19
    • missing RC1 jumpers

    Even without any transmute8 board connected, you should be able to measure voltage from 0-2.048V from the output header when running through the calibration procedure.

     

    1 hour ago, enveevee said:

    Gates board is working fine, only my first channel 1 led is always burning (only when connected with my midibox) but you can see it's triggering. All other channels are working like a charm.

    Can you measure a voltage on the jack output? Maybe the gate output is configured as inverted on the AOUT SEQ menu? You can try another octal board. Check the soldering around R1/LED1/IC1.

     

     

  10. The SRIO (J8/9) and J19 SPI require some sort of +5V, the source of which is selected by J5 (or SJ5). So the USB (power only) can be one of those sources, otherwise it can be regulated down from the Eurorack +12V or passed through the DB-25 cable, though I don't recommend the latter as the wires are quite thin and there will probably be a voltage drop.

    • Like 1
  11. @Cow_Patty ah, I see that I misinterpreted your post, I figured that you wanted to bolt on displays to a BCR2000, now I read that you want to replicate/extend it. I think your idea is feasible and it looks quite similar to what is planned for v2. By all means, go for it as this is what MIDIbox is all about.

    The limit of banks is 255 I think, just they need a method of selecting them.

    @FantomXR no firm release date yet, anything in mind from your side?

  12. Alright, I'll bite :)

    Just now, Cow_Patty said:

    My very first post and I already have two MIDIbox Gurus here. But still no answers! Instead, it was hijacked for ads. Basically.

    From personal experience, these sort of retrofits to existing hardware never lead anywhere. In fact I have had a BCR2000 in pieces for many years. It is possible to hack it and turn it into a MIDIbox but you will have to understand the layout, connections and so on. It sounds like you don't really have the skills for that, hence I recommended an alternative that would probably accomplish what you are after. If you do have the skills, then I apologise in advance, but it doesn't sound like it from your post.

     

    Just now, Cow_Patty said:

    Are my questions so unintelligent that don't even deserve an answer?!

    Many of your questions demonstrate a lack of understanding on basic MIDI protocol. Most of the others could be answered by working through the MB_NG pages: http://ucapps.de/midibox_ng_manual_fs.html

     

    Just now, Cow_Patty said:

    Do you guys just don't like newbies?! Aren't forums not only to share ideas but also to provide info?!

    Well you got an extra response out of me, but please be patient when starting out. I know you're probably eager to get started. 

     

    Just now, Cow_Patty said:

    I still have my idea, that's been cooking for ages in this dense head of mine. I'm still game, even if that project comes and I change my mind, I'm not worried. I'll still do it.

    History shows that if an idea is too difficult to follow through on (hacking a controller, overly ambitious project etc.), 99% of the time the person doesn't complete the build and never comes back.

     

    Just now, Cow_Patty said:

    Again, what I asked for is just to know if its possible. So I can start making preparations.

    Anything is possible if you have the skill and patience to do it.

     

    Just now, Cow_Patty said:

    I hope I didn't came as a rude, but I think it was necessary.

    You could refine your questions. It is a big block of text to read through straight out of the blocks.

    Here are answers to your questions:

    1.1 NRPN
    1.2 Incremental encoders
    1.3 http://ucapps.de/midibox_ng_manual_ngl.html
    2.0 Yes
    3.1 http://ucapps.de/midibox_ng_manual_ngr.html
    3.2 Yes
    4.0 Yes
    5.0 Not sure, but ProgrammA will use a concept of superbanks

  13. 10 minutes ago, Cow_Patty said:

    Humm... is that so?

    And if there is some design thing I would like to be different, will I be able to change?

    You could get the PCBs you want and incorporate them into your own controller. Everything will keep the typical compatibility. 

     

    10 minutes ago, Cow_Patty said:

    And what modules will be secure to go ahead and get for now?

    midiphy stuff is not final yet, but should be an encoder board and core. 

     

    10 minutes ago, Cow_Patty said:

    I'm still very tempted to do my own...

    Go for it! 

  14. 22 minutes ago, Cow_Patty said:

    For now there is no need to be technical, I haven't started the project, so I don't have any hardware, nor do I know programming. When the time to go more in depth arrives I will ask. So bear with me. :rolleyes:

    IMO just wait for ProgrammA v2, it will be awesome :).

  15. You need to assign the shift register to the triggers in the HWCFG. Then the triggers should work on AOUT channel 16.

    Quote

    DOUT drum gates/triggers
    Notes to AOUT Channel #16 (C-1, C#1, D-1, ... upwards) will be redirected to up to 64 digital outputs of the DOUT chain. Each key number triggers an individual gate for 1 mS, accordingly this mode is predestinated for drum triggers. The used shift registers have to be defined in the MBSEQ_HW.V4 file (DOUT_GATE_SR1..8)
     

    With the new firmware version you can adjust the pulse time of the triggers.

×
×
  • Create New...