[SOLVED] Midi settings missing and no external clock

edited November 2015 in Troubleshooting
Hi all,
I'd like my LXR synced to my Midirex. In the settings menu I"ve set BPM to 0 but then I've noticed I'm missing some settings options, namely the Midi txf and rxf. My settings options goes like this;

bpm, ch, fet, flw, qnt, ss

That's it. I'm missing mrt, txf and rxf.

I assume this is why external sync isn't working.

Comments

  • youre missing more than that. what firmware version is this? sounds like you might be on a very old one.
  • I was on the firmware linked in the assembly instructions. I've since upgraded to the latest one on github and the Midi and Trigger settings have appeared. I can now get clock over USB but still nothing over the Midi socket.
  • do you get notes or any other data from the midi output? make sure 'txf' is set to 'all', or at least something with 'R' in it.
  • Done a bunch of testing tonight. Midi-out does indeed work perfectly.

    I've printed out the schematics and tested continuity in all points between the Midi-in jack and the ARM Cortex header. Everything checks out fine. Doing voltage tests when powered up and receiving I get 5 volts between pin 4 and the midi-in on the Cortex header. Interestingly I get a drop down to 0.74 volts after the 220ohm R3 where it hits the 6N138 on pins 2&3. Not sure if this is normal or not.

    I've tried older firmwares, including your own Brendan, but get hit by the OLED display bug so they aren't usable for testing.

    I don't know how I else I can test with a multimeter. I was suspicious of the display being mounted without tape under it but it doesn't appear that anythings shorted out there (I can lever it up a little and slide paper in).
  • SUCCESS! I've resoldered (reflow?) the joints of the midi-jack from the top underside, the 220 ohm and the diode and its come good!

    Also fixed my dodgy snare LED by doing the same thing. Win! Perfectly functioning LXR.

    :D
  • Glad to hear things are working! Can you clarify - what is the 'oled display bug'? I use an oled display and have never seen a display-specific issue with my firmware. If there is something preventing it from working on certain displays, I'd sure like to know about it!
  • I was referring to the problem in this thread. I may not have described it correctly but I can't run anything earlier than v37 without getting a corrupted display on boot.
  • edited November 2015
    ah! ok - I just rolled the .37 changes into my firmware mod. Let me know if that works for you!
Sign In or Register to comment.