-
Posts
2,524 -
Joined
-
Last visited
-
Days Won
149
Content Type
Profiles
Forums
Blogs
Gallery
Posts posted by latigid on
-
-
Or did you mean the larger 17x17 BLM? For that one we are working on a new version. All going well it should be available later in the year.
-
Cheers!
I'm not 100% sure what you mean with very long lengths. Does it remain when the gate length is set to glide? Video?
-
Is the external PSU actually +5/-5V? So a 10V supply?
The 0V should be common rather than 0V to -12V. I think that's what your diagram shows, but the 0V of the PSU should connect to the yellowish wire on your diagram, not the black -12V
-
Everything sounds correct.
7 hours ago, rbv2 said:so the connection underneath the DAC is not sufficient then?
Yes and no? Try to have the 0V common to both PSUs, i.e. at the source of the power.
-
On 5/23/2019 at 6:22 PM, rbv2 said:
hi all,
after testing i found an minor issue with my breakout-box. everything is working as intended but i get annoying double triggers on some modules. when i connect the same modules to my robokop sequencer or other trigger source everything is fine. could it be a grounding issue?
the +/-12V for the AOUT NG is coming from my eurorack and the +5V for AOUT NG and the LineDriver Receiver from an additional psu. the external psu (5v) is in the middle of the ribbon cable between AOUT NG and the receiver as suggested by latigid on. i also enabled the 1ms trigger but it makes no difference.
when using the same trigger on another module it works so i guess i can rule out the double trigger is coming from the sequencer itself.
please help
rbv2
I repeat my advice from the other thread:
Could it be the HW config settings or an issue with midi loops feeding back in? More than one track assigned to AOUT?
The perennial IDC cabling issue would also be worth checking.
You could also test with _NG again and in MIOS terminal
set dout x 1
to check if the problem is replicated. For x you have to count the number of shift register outputss in the chain, starting from 0-7 for the first one. Or simply replace x with 'all'.
21 hours ago, Hawkeye said:Therefore, I would also expect maybe a common ground problem on your side? Have you grounded the external PSU and the LineDriver Receiver to the modular/rack common ground?
Check the resistance of your 0V from the Eurorack to somewhere on the SEQ e.g. pin 2 on a MIDI out (the one at 6 o'clock).
In the line receiver, is jumper J3 closed? This could cause interference on the +5V line if there are two PSUs fighting.
12 hours ago, rbv2 said:at the moment i have wired 12V+/- and GND directly from a doepfer bus board to J3 of the AOUT NG the external psu is in the middle of the cable from JAOUT of the receiver to J1 of the AOUT NG. (Vs & Vd) . by common ground do you mean i should connect the Vs line of 5V PSU to the GND of J3 at the AOUT NG? all the jacks (gate, trigger, cv) are connected to ground and since the panel is made of aluminium the gnd of both psu's is connected.
If you use an external PSU you must connect the 0V together with the +/-12V PSU 0V common line. A metal panel is not a good (and some would say unsafe) method of achieving common 0V.
12 hours ago, rbv2 said:i have also learned that the 5v on the doepfer boards are not there at all although it is written on it
I guess you are not using the +5V on the bussboard? But if you are, maybe you don't have +5V connected and the modules are being parasitically powered from the digital signals? (This is not good for CMOS btw.) Did you measure correct +5V on the modules?
9 hours ago, Hawkeye said:Probably @latigid on can help you out way more than i can... but i just looked up the AOUT_NG schem and it seems analog ground can be tied to digital ground (see middle of the schem), maybe by a jumper? If that is the case, i think the grounds should be all tied down together and nothing is floating, which might cause problems. We are using the AOUT (not NG) module, so i don't really know much about the NG.
There is only one "ground" and the separation of analogue/digital 0V is a complex and often misunderstood topic. On AOUT_NG the two are connected underneath the DAC chip; there is no jumper etc.
9 hours ago, rbv2 said:a friend of mine will lend me his scope. but i don't have one right now.
A scope might be useful to see what's going on.
-
The JA matrix is driven by the extra ICs on lemec_R. The fact a whole row is missing points to an issue on the sink side.
Check continuity (also for cold solder joints and faulty cables) from the following pins
lemec_R:
IC17 pin 1 :: IC18 pin 7
IC 18 pin 12 :: J5 pin 8
J5 pin 8 ::IDC cable to JA:: J2 pin 8JA:
J2 pin 8:: MATRIX pin 14.The matrix pins are labelled like an IC, so anticlockwise from the bottom-left dot.
-
- Do the DIN tests work? I.e. do you see button events in MIOS Studio?
-
The problem is isolated to one LED, not a whole row-of-four or column?
- Then the issue is soldering to that particular part
- All LED anodes/SJ of a column will be common, test continuity
- You have multiple colours configured? Check the RJs.
Provide a few good-quality photos to make troubleshooting easier.
-
Maybe create another post as it's not really a v4+ problem?
Could it be the HW config settings or an issue with midi loops feeding back in? More than one track assigned to AOUT?
The perennial IDC cabling issue would also be worth checking.
-
@TK. thanks for the coding efforts! This will be very helpful in other projects too.
The rainbow rings look very pretty :)
-
9 hours ago, jaytee said:
Any updates on the AOUT/DOUT eurorack modules? Just curious :)
We should get panel samples in a week or two, then do a PCB run. Still a wee way off.
-
2
-
-
The caps are not to my taste, but good for you if you are happy with that look :).
-
5 hours ago, otropom said:
everything is running great now, you were right about IC2 cold joint. I just have the matrix that display "mirrored" text can it come from a backward cable or something like that. ?
The activity matrix? Check the HW config file as you need:
# set to 1 or 2 to enable the relative track position display # 0: TPD disabled # 1: TPD enabled - columns are cathodes, rows are anodes # 2: TPD enabled - columns are anodes, rows are cathodes # 3: TPD for midiphy frontpanel enabled - columns are anodes, rows are cathodes, inversion TPD_ENABLED 3
Quotein any case merci beaucoup for your kindness and your advices, i will finally be able to enjoy the midibox seq ! and it wasn't that easy for noob (second diy project) that was not comfortable with English language :) learnt lot of things !
De rien! You had a great attitude and provided the right info (pictures). It's really great work if it's just your second project! Félicitations!
-
Each display gives this output when only one is plugged in? Then the cables are okay, or at least have the same issue :).
At a guess, probably the register data is corrupted, so look again on IC2 for cold joints or shorts. Make sure the power is jumpered to 3v3 (it was before I know).
Check that the 407v board is correctly inserted into the 2x 2x25 header pins. You may have bent the connectors by inserting/removing the 407v a lot. Reference the schematic here and check for continuity back to the top of the 407v header pins PD7, PD6 etc.
Check that the E (enable) lines of the displays are not connected together.
-
Make sure you clean up all of the pads (with desoldering braid) before resoldering IC2. Pin 16 can be bridged directly to C2, no problem.
-
The soldering on the OLED headers could be better, try to rework. If the fillet looks like a teardrop, it might not be contacting the PTH properly. Try to get the heat into the pad and the solder will flow there.
Soldering could be better on IC2, pin 8. Recheck R33abcd.
Try swapping the OLED cabling to the other J15 port. Could be bad cables again, could also be that some pins on the cable short out components on the OLED, so isolate with even a scrap piece of plastic or card on the OLED PCB right under the connector.
-
That might be a hard combination to tune. But yes, normally blue should have a lower-value resistor as it's typically dimmer.
At least on the older SEQ firmware, the measure LED was not "XORed" i.e. beat and measure would trigger at the same time. That might be a way to get all three going at once for white-ish, though I can't remember if it's still part of the current firmware.
-
Sometimes I feel like there can be oxidation or other crap on the pins that prevents good contact and messes up the data transfer.
-
-
If _NG is flashed and JA is working it's a good sign. The _l and _r .NGC files specify the position of JA. You can use _r to test lemec_L. It's possible to test lemec_R as the first board in the chain, but you need to reconfigure the file.
The boards are chained JA-lemec_L-lemecR, correct?
You should measure +5V on the 74HC165 input pins and 74HC595 outputs should go to +5V with set dout all 1. Check the preceding pages of this thread or the datasheets for pin assignments. You can follow the SRIO chain (especially the SO signal) to see how far the data gets.
Seeing as you have some DIN activity, consider replacing IC2/IC4, which were reversed and then heated up probably quite a lot during rework.
-
Just check first that the MB_NG app is flashed and you have loaded the correct seq_l or seq_r.ngc. Was testing of the JA board okay?
To simulate DOUT behaviour you can try
set dout all 1
Or go through and count the dout pins (8 per chip) until you get to the correct IC -> replace all with the one you want to toggle. DOUT rows/cathode sink rows are given in previous pages.
The matrix is controlled by ICs 2 (cathodes) and 3 (DIN).
Having spare parts is always useful and could be used in future projects. I typically get 100 shift registers at a time.
-
1
-
-
No worries.
It might be that IC2 was damaged by being reversed. Did you use new chips or the same?
I was troubleshooting with @niles the past weeks on a similar problem. The same advice applies, so check cables, resolder IC2 and IC3. Many solder joints look "cold" Any MIOS output with
set debug on
?
-
When you say the "kernel" doesn't boot, do you mean the waveshare MCU breakout board? If this is the case, a typical cause is a short between 0V/+5V.
Please check the orientation of all ICs. At least IC4 is in backwards! (The stripe on the IC should go towards pin 1).
-
1
-
-
Glad you got it working. Interesting solution, as R33A is more associated with the OLEDs.
-
Frequency is controlled by the CPU, I'd say if you see the clocks at all it's good. It might be that RC is 1 kHz.
How's your DIN matrix looking?
Troubleshooting midiphy SEQ v4+
in MIDIbox SEQ
Posted
R5 just applies a bit of protection for a CV input (as yet unmapped in software). It's not necessary for running anything. You could also bridge the 3.5mm socket pad to the diode cathode with a resistor.