Jump to content

Troubleshooting midiphy SEQ v4+


latigid on
 Share

Recommended Posts

No shorts found on between any of those resistors, and on the IC4 pins.

Checked the values of R14 / R15 and theyre correct - 1K.

I reflowed the pins of IC4 and no luck.


This issue doesn't seem to be an obvious one whatever it is!

Link to comment
Share on other sites

Very tricky!

To check: it does the same thing if you change the the sequence of boards and load the respective .NGC _R / _L? 

You could try to modify the .NGC file by commenting out the DIN matrix

DOUT_MATRIX n=1  rows=8 inverted_sel=1 inverted_row=1  sr_dout_sel1=3  sr_dout_r1=4  led_emu_id_offset=1001
DIN_MATRIX  n=1  rows=8 inverted_sel=1 inverted_row=0  sr_dout_sel1=3  sr_din1=3     button_emu_id_offset=1001

That might help to narrow down where to look.

Link to comment
Share on other sites

I set it up in RH mode (from left to right: Core -> LE MEC -> LE MEC RH -> JA PCB )
and loaded up seq_r and the issue remained.
I commented out the DIN MATRIX line in seq_r.ngc for the RH PCB and this is the result of turning ENCSW4 clockwise one detent with set debug on:

[ 657.687] MBNG_DIN_NotifyToggle(36, 0)
[ 657.688] No event assigned to BUTTON hw_id=36
[ 657.702] MBNG_ENC_NotifyChange(12, 1)
[ 657.703] [EVENT] id=ENC:12 hw_id=ENC:12 bank=0 fwd_id=DISABLED:0 type=CC value=0 label=
[ 657.708] MBNG_DIN_NotifyToggle(36, 1)
[ 657.709] No event assigned to BUTTON hw_id=36

 

I noticed SW20 did not light up this time when turning. The Mattias LEDs Common Cathode are still desoldered, so not sure if these would light up in this column with DIN commented out.

I presume I was not meant to comment out DOUT_MATRIX?

Thanks!

Edited by Smithy
Link to comment
Share on other sites

hw_id=36 means that it is the 36th DIN input. I think the DINs are counted backwards, so that corresponds to IC3, pin 14. That pin is connected in parallel to J2, pin 6 and RN2, pin 5, along with the diode anodes of that column. (If they are counted forwards, then it is IC3 pin 3 and J2/RN2 pin 7 and the 5th column of diodes.)

Logically, the only way that you can trigger that DIN pin by turning EN4 is if there is some connection between the encoder pins and that pin. It could also be the diodes in the 4th column of switches.

With the plate board connected, see if you get any shorts between the encoder legs and all pins of J2.

Disconnect the plate and try the same debug test by shorting J1 pins 9/10 to 0V. If you get the same hw_id=36, then your issue is on lemec_R. If the issue disappears when disconnecting, then there is some unintentional contact made when stacking the boards together.

Edited by latigid on
Link to comment
Share on other sites

On 6/10/2021 at 11:30 PM, latigid on said:

hw_id=36 means that it is the 36th DIN input. I think the DINs are counted backwards, so that corresponds to IC3, pin 14. That pin is connected in parallel to J2, pin 6 and RN2, pin 5, along with the diode anodes of that column. (If they are counted forwards, then it is IC3 pin 3 and J2/RN2 pin 7 and the 5th column of diodes.)

Logically, the only way that you can trigger that DIN pin by turning EN4 is if there is some connection between the encoder pins and that pin. It could also be the diodes in the 4th column of switches.

With the plate board connected, see if you get any shorts between the encoder legs and all pins of J2.

Disconnect the plate and try the same debug test by shorting J1 pins 9/10 to 0V. If you get the same hw_id=36, then your issue is on lemec_R. If the issue disappears when disconnecting, then there is some unintentional contact made when stacking the boards together.

So i tested for shorts between all encoder legs of ENSW4 and the pins of J2 - nothing.
Disconnected the plate PCB and shorted pins 9 and then 10 of J1 to GND. Nothing comes up on Debug.  (I even removed the comment # character from the DIN line in seq_r.ngc and tried a second time just in case.

 

Link to comment
Share on other sites

I still think if you have a short between the encoder pins and J2, pin 6, that would probably explain your issue.

Try shorting J1 pins 8/9 to 0V, (not 10). That's where that encoder ends up. You should see DIN events corresponding to the encoder if SEQ_L/R is loaded. See if enabling the DIN matrix brings back the LED storm too.

Another weird thing that sometimes happens is that your MEC switches have broken LEDs. 

 

Link to comment
Share on other sites

On 6/15/2021 at 5:44 PM, latigid on said:

I still think if you have a short between the encoder pins and J2, pin 6, that would probably explain your issue.

Try shorting J1 pins 8/9 to 0V, (not 10). That's where that encoder ends up. You should see DIN events corresponding to the encoder if SEQ_L/R is loaded. See if enabling the DIN matrix brings back the LED storm too.

Another weird thing that sometimes happens is that your MEC switches have broken LEDs. 

 

Still no short between ENC4 pins and J2 Pin 6.

With the ENC Plate PCB installed when I short J1 pin 8 to GND the SW20 LED lights up  and I get the following in debug, it includes touching the pin and releasing from it:

[1036341.011] MBNG_MATRIX_NotifyToggle(1, 28, 0)
[1036341.011] MBNG_DIN_NotifyToggle(2028, 0)
[1036341.012] [EVENT] id=BUTTON:2028 hw_id=BUTTON:2028 bank=0 fwd_id=LED:2031 type=NoteOn value=0 label=
[1036341.013] MBNG_DOUT_NotifyReceivedValue(2031, 127)
[1036341.014] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 31, 127)
[1036341.015] MBNG_MATRIX_NotifyToggle(1, 44, 0)
[1036341.016] MBNG_DIN_NotifyToggle(2044, 0)
[1036341.016] No event assigned to BUTTON hw_id=2044
[1036341.020] MBNG_MATRIX_NotifyToggle(1, 60, 0)
[1036341.021] MBNG_DIN_NotifyToggle(2060, 0)
[1036341.021] No event assigned to BUTTON hw_id=2060
[1036341.024] MBNG_MATRIX_NotifyToggle(1, 12, 0)
[1036341.024] MBNG_DIN_NotifyToggle(2012, 0)
[1036341.025] [EVENT] id=BUTTON:2012 hw_id=BUTTON:2012 bank=0 fwd_id=LED:2016 type=NoteOn value=0 label=
[1036341.026] MBNG_DOUT_NotifyReceivedValue(2016, 127)
[1036341.027] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 16, 127)
[1036341.029] MBNG_MATRIX_NotifyToggle(1, 36, 0)
[1036341.030] MBNG_DIN_NotifyToggle(2036, 0)
[1036341.030] No event assigned to BUTTON hw_id=2036
[1036341.033] MBNG_MATRIX_NotifyToggle(1, 52, 0)
[1036341.034] MBNG_DIN_NotifyToggle(2052, 0)
[1036341.034] No event assigned to BUTTON hw_id=2052
[1036341.038] MBNG_MATRIX_NotifyToggle(1, 4, 0)
[1036341.038] MBNG_DIN_NotifyToggle(2004, 0)
[1036341.039] [EVENT] id=BUTTON:2004 hw_id=BUTTON:2004 bank=0 fwd_id=LED:2015 type=NoteOn value=0 label=
[1036341.040] MBNG_DOUT_NotifyReceivedValue(2015, 127)
[1036341.041] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 15, 127)
[1036341.042] MBNG_MATRIX_NotifyToggle(1, 20, 0)
[1036341.042] MBNG_DIN_NotifyToggle(2020, 0)
[1036341.043] [EVENT] id=BUTTON:2020 hw_id=BUTTON:2020 bank=0 fwd_id=LED:2024 type=NoteOn value=0 label=
[1036341.044] MBNG_DOUT_NotifyReceivedValue(2024, 127)
[1036341.045] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 24, 127)
[1036341.060] MBNG_MATRIX_NotifyToggle(1, 20, 1)
[1036341.060] MBNG_DIN_NotifyToggle(2020, 1)
[1036341.062] [EVENT] id=BUTTON:2020 hw_id=BUTTON:2020 bank=0 fwd_id=LED:2024 type=NoteOn value=127 label=
[1036341.062] MBNG_DOUT_NotifyReceivedValue(2024, 0)
[1036341.063] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 24, 0)
[1036341.070] MBNG_MATRIX_NotifyToggle(1, 20, 0)
[1036341.070] MBNG_DIN_NotifyToggle(2020, 0)
[1036341.071] [EVENT] id=BUTTON:2020 hw_id=BUTTON:2020 bank=0 fwd_id=LED:2024 type=NoteOn value=0 label=
[1036341.072] MBNG_DOUT_NotifyReceivedValue(2024, 127)
[1036341.073] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 24, 127)
[1036341.080] MBNG_MATRIX_NotifyToggle(1, 12, 1)
[1036341.080] MBNG_DIN_NotifyToggle(2012, 1)
[1036341.082] [EVENT] id=BUTTON:2012 hw_id=BUTTON:2012 bank=0 fwd_id=LED:2016 type=NoteOn value=127 label=
[1036341.082] MBNG_DOUT_NotifyReceivedValue(2016, 0)
[1036341.083] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 16, 0)
[1036341.088] MBNG_MATRIX_NotifyToggle(1, 12, 0)
[1036341.088] MBNG_DIN_NotifyToggle(2012, 0)
[1036341.089] [EVENT] id=BUTTON:2012 hw_id=BUTTON:2012 bank=0 fwd_id=LED:2016 type=NoteOn value=0 label=
[1036341.090] MBNG_DOUT_NotifyReceivedValue(2016, 127)
[1036341.091] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 16, 127)
[1036341.186] MBNG_MATRIX_NotifyToggle(1, 44, 1)
[1036341.186] MBNG_DIN_NotifyToggle(2044, 1)
[1036341.186] No event assigned to BUTTON hw_id=2044
[1036341.192] MBNG_MATRIX_NotifyToggle(1, 52, 1)
[1036341.193] MBNG_DIN_NotifyToggle(2052, 1)
[1036341.193] No event assigned to BUTTON hw_id=2052
[1036341.197] MBNG_MATRIX_NotifyToggle(1, 4, 1)
[1036341.197] MBNG_DIN_NotifyToggle(2004, 1)
[1036341.198] [EVENT] id=BUTTON:2004 hw_id=BUTTON:2004 bank=0 fwd_id=LED:2015 type=NoteOn value=127 label=
[1036341.199] MBNG_DOUT_NotifyReceivedValue(2015, 0)
[1036341.200] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 15, 0)
[1036341.201] MBNG_MATRIX_NotifyToggle(1, 20, 1)
[1036341.201] MBNG_DIN_NotifyToggle(2020, 1)
[1036341.203] [EVENT] id=BUTTON:2020 hw_id=BUTTON:2020 bank=0 fwd_id=LED:2024 type=NoteOn value=127 label=
[1036341.203] MBNG_DOUT_NotifyReceivedValue(2024, 0)
[1036341.204] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 24, 0)
[1036341.205] MBNG_MATRIX_NotifyToggle(1, 36, 1)
[1036341.206] MBNG_DIN_NotifyToggle(2036, 1)
[1036341.206] No event assigned to BUTTON hw_id=2036
[1036341.210] MBNG_MATRIX_NotifyToggle(1, 60, 1)
[1036341.211] MBNG_DIN_NotifyToggle(2060, 1)
[1036341.211] No event assigned to BUTTON hw_id=2060
[1036341.215] MBNG_MATRIX_NotifyToggle(1, 12, 1)
[1036341.215] MBNG_DIN_NotifyToggle(2012, 1)
[1036341.217] [EVENT] id=BUTTON:2012 hw_id=BUTTON:2012 bank=0 fwd_id=LED:2016 type=NoteOn value=127 label=
[1036341.217] MBNG_DOUT_NotifyReceivedValue(2016, 0)
[1036341.218] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 16, 0)
[1036341.219] MBNG_MATRIX_NotifyToggle(1, 28, 1)
[1036341.219] MBNG_DIN_NotifyToggle(2028, 1)
[1036341.221] [EVENT] id=BUTTON:2028 hw_id=BUTTON:2028 bank=0 fwd_id=LED:2031 type=NoteOn value=127 label=
[1036341.221] MBNG_DOUT_NotifyReceivedValue(2031, 0)
[1036341.222] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 31, 0)

This does not happen without the Enc plate PCB installed / connected.

I also tried doing it with the arduino headers installed to separate the PCBs further like in the photo below, and I do get the events and SW20's LED lighting up still.


IMG_20210621_224057.thumb.jpg.e09f737d60ae738fb8f6787dc462eb07.jpg

 

So this should rule out a short between components touching on both boards.

Shorting J1 Pin 9 to GND has no effect.

Would I be right in thinking there's a short somewhere on the ENC Plate PCB?

Edited by Smithy
Link to comment
Share on other sites

7 minutes ago, Smithy said:

Still no short between ENC4 pins and J2 Pin 6.

With the ENC Plate PCB installed when I short J1 pin 8 to GND the SW20 LED lights up  and I get the following in debug, it includes touching the pin and releasing from it:


[1036341.011] MBNG_MATRIX_NotifyToggle(1, 28, 0)
[1036341.011] MBNG_DIN_NotifyToggle(2028, 0)
[1036341.012] [EVENT] id=BUTTON:2028 hw_id=BUTTON:2028 bank=0 fwd_id=LED:2031 type=NoteOn value=0 label=
[1036341.013] MBNG_DOUT_NotifyReceivedValue(2031, 127)
[1036341.014] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 31, 127)
[1036341.015] MBNG_MATRIX_NotifyToggle(1, 44, 0)
[1036341.016] MBNG_DIN_NotifyToggle(2044, 0)
[1036341.016] No event assigned to BUTTON hw_id=2044
[1036341.020] MBNG_MATRIX_NotifyToggle(1, 60, 0)
[1036341.021] MBNG_DIN_NotifyToggle(2060, 0)
[1036341.021] No event assigned to BUTTON hw_id=2060
[1036341.024] MBNG_MATRIX_NotifyToggle(1, 12, 0)
[1036341.024] MBNG_DIN_NotifyToggle(2012, 0)
[1036341.025] [EVENT] id=BUTTON:2012 hw_id=BUTTON:2012 bank=0 fwd_id=LED:2016 type=NoteOn value=0 label=
[1036341.026] MBNG_DOUT_NotifyReceivedValue(2016, 127)
[1036341.027] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 16, 127)
[1036341.029] MBNG_MATRIX_NotifyToggle(1, 36, 0)
[1036341.030] MBNG_DIN_NotifyToggle(2036, 0)
[1036341.030] No event assigned to BUTTON hw_id=2036
[1036341.033] MBNG_MATRIX_NotifyToggle(1, 52, 0)
[1036341.034] MBNG_DIN_NotifyToggle(2052, 0)
[1036341.034] No event assigned to BUTTON hw_id=2052
[1036341.038] MBNG_MATRIX_NotifyToggle(1, 4, 0)
[1036341.038] MBNG_DIN_NotifyToggle(2004, 0)
[1036341.039] [EVENT] id=BUTTON:2004 hw_id=BUTTON:2004 bank=0 fwd_id=LED:2015 type=NoteOn value=0 label=
[1036341.040] MBNG_DOUT_NotifyReceivedValue(2015, 127)
[1036341.041] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 15, 127)
[1036341.042] MBNG_MATRIX_NotifyToggle(1, 20, 0)
[1036341.042] MBNG_DIN_NotifyToggle(2020, 0)
[1036341.043] [EVENT] id=BUTTON:2020 hw_id=BUTTON:2020 bank=0 fwd_id=LED:2024 type=NoteOn value=0 label=
[1036341.044] MBNG_DOUT_NotifyReceivedValue(2024, 127)
[1036341.045] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 24, 127)
[1036341.060] MBNG_MATRIX_NotifyToggle(1, 20, 1)
[1036341.060] MBNG_DIN_NotifyToggle(2020, 1)
[1036341.062] [EVENT] id=BUTTON:2020 hw_id=BUTTON:2020 bank=0 fwd_id=LED:2024 type=NoteOn value=127 label=
[1036341.062] MBNG_DOUT_NotifyReceivedValue(2024, 0)
[1036341.063] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 24, 0)
[1036341.070] MBNG_MATRIX_NotifyToggle(1, 20, 0)
[1036341.070] MBNG_DIN_NotifyToggle(2020, 0)
[1036341.071] [EVENT] id=BUTTON:2020 hw_id=BUTTON:2020 bank=0 fwd_id=LED:2024 type=NoteOn value=0 label=
[1036341.072] MBNG_DOUT_NotifyReceivedValue(2024, 127)
[1036341.073] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 24, 127)
[1036341.080] MBNG_MATRIX_NotifyToggle(1, 12, 1)
[1036341.080] MBNG_DIN_NotifyToggle(2012, 1)
[1036341.082] [EVENT] id=BUTTON:2012 hw_id=BUTTON:2012 bank=0 fwd_id=LED:2016 type=NoteOn value=127 label=
[1036341.082] MBNG_DOUT_NotifyReceivedValue(2016, 0)
[1036341.083] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 16, 0)
[1036341.088] MBNG_MATRIX_NotifyToggle(1, 12, 0)
[1036341.088] MBNG_DIN_NotifyToggle(2012, 0)
[1036341.089] [EVENT] id=BUTTON:2012 hw_id=BUTTON:2012 bank=0 fwd_id=LED:2016 type=NoteOn value=0 label=
[1036341.090] MBNG_DOUT_NotifyReceivedValue(2016, 127)
[1036341.091] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 16, 127)
[1036341.186] MBNG_MATRIX_NotifyToggle(1, 44, 1)
[1036341.186] MBNG_DIN_NotifyToggle(2044, 1)
[1036341.186] No event assigned to BUTTON hw_id=2044
[1036341.192] MBNG_MATRIX_NotifyToggle(1, 52, 1)
[1036341.193] MBNG_DIN_NotifyToggle(2052, 1)
[1036341.193] No event assigned to BUTTON hw_id=2052
[1036341.197] MBNG_MATRIX_NotifyToggle(1, 4, 1)
[1036341.197] MBNG_DIN_NotifyToggle(2004, 1)
[1036341.198] [EVENT] id=BUTTON:2004 hw_id=BUTTON:2004 bank=0 fwd_id=LED:2015 type=NoteOn value=127 label=
[1036341.199] MBNG_DOUT_NotifyReceivedValue(2015, 0)
[1036341.200] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 15, 0)
[1036341.201] MBNG_MATRIX_NotifyToggle(1, 20, 1)
[1036341.201] MBNG_DIN_NotifyToggle(2020, 1)
[1036341.203] [EVENT] id=BUTTON:2020 hw_id=BUTTON:2020 bank=0 fwd_id=LED:2024 type=NoteOn value=127 label=
[1036341.203] MBNG_DOUT_NotifyReceivedValue(2024, 0)
[1036341.204] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 24, 0)
[1036341.205] MBNG_MATRIX_NotifyToggle(1, 36, 1)
[1036341.206] MBNG_DIN_NotifyToggle(2036, 1)
[1036341.206] No event assigned to BUTTON hw_id=2036
[1036341.210] MBNG_MATRIX_NotifyToggle(1, 60, 1)
[1036341.211] MBNG_DIN_NotifyToggle(2060, 1)
[1036341.211] No event assigned to BUTTON hw_id=2060
[1036341.215] MBNG_MATRIX_NotifyToggle(1, 12, 1)
[1036341.215] MBNG_DIN_NotifyToggle(2012, 1)
[1036341.217] [EVENT] id=BUTTON:2012 hw_id=BUTTON:2012 bank=0 fwd_id=LED:2016 type=NoteOn value=127 label=
[1036341.217] MBNG_DOUT_NotifyReceivedValue(2016, 0)
[1036341.218] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 16, 0)
[1036341.219] MBNG_MATRIX_NotifyToggle(1, 28, 1)
[1036341.219] MBNG_DIN_NotifyToggle(2028, 1)
[1036341.221] [EVENT] id=BUTTON:2028 hw_id=BUTTON:2028 bank=0 fwd_id=LED:2031 type=NoteOn value=127 label=
[1036341.221] MBNG_DOUT_NotifyReceivedValue(2031, 0)
[1036341.222] MBNG_MATRIX_DOUT_NotifyReceivedValue(2, 31, 0)

This does not happen without the Enc plate PCB installed.

I also tried doing it with the arduino headers installed to separate the PCBs further like in the photo below, and I do get the events and SW20's LED lighting up still.


IMG_20210621_224057.thumb.jpg.e09f737d60ae738fb8f6787dc462eb07.jpg

 

So this should rule out a short between components touching on both boards.

Would I be right in thinking there's a short somewhere on the ENC Plate PCB?

If you essentially trigger the encoder pins with the plate PCB disconnected and there is no spurious matrix event, then I agree that there is a short somewhere on the plate board. It is really puzzling that you don't see any short to J2 from the encoder. 

Check again that all RNs are cut flush, even with stacking headers maybe the pins are too long?

The encplate PCB is fairly simple and just connects the encoders to J1/3 and the diode columns to J2.

Link to comment
Share on other sites

11 minutes ago, latigid on said:

If you essentially trigger the encoder pins with the plate PCB disconnected and there is no spurious matrix event, then I agree that there is a short somewhere on the plate board. It is really puzzling that you don't see any short to J2 from the encoder. 

Check again that all RNs are cut flush, even with stacking headers maybe the pins are too long?

The encplate PCB is fairly simple and just connects the encoders to J1/3 and the diode columns to J2.

The RN pins are definitely not touching, here's a photo showing how far the PCBs are apart from each other with the headers:

IMG_20210621_232005.thumb.jpg.28d361b6bd95c9c99f7976acdbdce130.jpg

 

Shorting J1 Pin 8 to GND even at that distance causes SW20 to illuminate.
Any advice or images of traces to help me find the short on the Enc Plate PCB?

On the underside of the PCB there is quite a few spots where the silkscreen has been marked and copper is showing. No traces seem to be exposed however.


 

Link to comment
Share on other sites

You could try to bodge it by connecting the cathode end of the diode directly to the encoder switch pin. It is the one closer to the middle of the board (the one closer to the edge is the row sink and is common to the three preceding encoders). It would probably help to remove the encoder switch pin from the PCB totally and find some way to insulate it.

Connecting directly from encoder switch pin to J2 pin 6 is also an option.

 

Link to comment
Share on other sites

1 hour ago, latigid on said:

You could try to bodge it by connecting the cathode end of the diode directly to the encoder switch pin. It is the one closer to the middle of the board (the one closer to the edge is the row sink and is common to the three preceding encoders). It would probably help to remove the encoder switch pin from the PCB totally and find some way to insulate it.

Connecting directly from encoder switch pin to J2 pin 6 is also an option.

 

Connecting the diode from the Encoder Switch pin to J2 pin 6 solved the issue!
There must be a short on the top side of the board under or near ENC4!

Thanks so much for the help, and enjoy a beer on me! Must have been the longest troubleshooting effort ever! :)

Link to comment
Share on other sites

  • 3 weeks later...

Hello,

I am in the middle of building my Midiphy SEQ v4+ and things are going well for the most part.

Unfortunately, I realise that I made a mistake in assembling the USB PCB.

I seem to not to have properly put the metal parts that screw into the case so that they are flush with the PCB - instead, they stick up about 3mm.

I have tried to desolder using a wick/pump but no luck - they are solidly in there.

Everything works on the USB PCB and I'm able to upload the firmware to the core, but I'm aware I will now have a problem when assembling the case of my Seq V4+

Any ideas, or will I have to buy and reassemble the PCB?

 

 

Link to comment
Share on other sites

It would be difficult to desolder these parts as the metal acts as a big heatsink. An option I can see is to somehow cut the metal apart, even so there are just the pins left, then order new brackets. 

3mm is probably too much to get the rear-panel components to align properly. In the end maybe you have to reorder the PCB and/or parts but it is worth a go to get them off. 

  • Like 1
Link to comment
Share on other sites

Thank you very much - cutting them off with some flush cutters and pumping away the solder eventually worked!

I have connected the USB board up to the computer and confirmed that MIOS Studio can communicate with the board. 

Are there any other tests I should run to ensure that I haven't damaged the USB board in the process through heat, or is it safe to say it's fine?

Link to comment
Share on other sites

Hello - now I am testing the JA PCB and having 2 problems:

1. All switches show activity in MIOS Studio except for SW 12, which gives no response.

2. None of my LEDs light up when the switch is pressed.

I triple checked LED polarity, part numbers, IC orientation and reflowed everything - still no luck.

Any idea what to look for next?

All the best,

Jeremy

Link to comment
Share on other sites

There are some joints that don't look to be properly formed e.g. the top row of the LED matrixes, fifth pin from the left viewed from the rear of the board. It could be a similar cold joint for your SW12.

Were you testing with SEQ_L.NGC? Because if you have the switch matrix going, there is no reason why the LEDs should not light up, unless they all have reversed polarity. Test with your multimeter, diode mode, red probe on the circle, black probe on the flat.

If you haven't loaded SEQ_L.NGC, then I wouldn't expect any LEDs to light up.

Looks like the resistor network is the right part.

Cables can also be at fault, or even the soldering of the buffer chips or the headers on the Core board.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...