Is switch 4 momentary or latching? The idea is to add resistance where each switch adds its value to all of the resistors before it. If the value is dropping, then the last two must be in parallel with the previous four resistors. If switch four is latching , then I would expect that behavior.
The resistor ladder is meant to replace an expression pedal with several fixed and repeatable settings.
They’re all momentary and all wired the same way. But maybe there’s some issue or short happening somewhere.
Check it with an ohm meter.
Good idea. Mind saying a word more about what to look for, and what different readings might suggest?
We’re still working on the guide but here’s the gist.
- After setting Omniport1 to Resistor Ladder, save and restart the controller.
- Click on Calibrate, which will bring up the calibration menu in the controller.
- Press a switch, and you’ll see a value reflected
- Use that value and then assign it to a function in the editor
- Save your settings again.
For example, if I press a switch and it shows 4, and I want to map that switch to Tap Tempo, here’s what it’ll look like:
Thanks for that explanation James. I was able to calibrate and set it up that way, and amazingly, it seems to work (amazing because it means I soldered up the switch correctly, not because I was expecting any issues with the software end of things).
So for anyone else who tries this, I don’t know if I wired it up “incorrectly” or not, causing some of the later switches to be lower in value than the previous switches, but since they all have separate values, I was able to calibrate just fine and it all seems to work as I was hoping it would.
glad to see it working. I was under the mistaken assumption that it was for preset expression settings. It appears from James’ post that it’s a way to get multiple switches on an omniport . Cool!!! I might have to try this.
For those not well versed in electonics… the resistors in the diagram are the little zig-zag lines. When you put them end-to-end the way they are they are in series. In series, the total resistance of the string is just the sum of each of the individual resistors.
The switches (normally open) basically don’t exist in the circuit until they’re pressed. When they’re pressed they “close” and they create a path to ground. The MCx then measures the amount of resistance between the tip and ground. The further down the circuit the switch that’s pressed is, the higher the resistance it sees. That’s how it knows which button is pressed.
Be aware that if you press multiple buttons at the same time it will only detect the one the produces the lowest resistance (the closest to the top in the diagram).
If you’re looking to test your build, put an ohm meter across the tip and sleeve of the connector. When no buttons are pressed you should get infinite resistance, no reading, or whatever your meter shows for an open circuit. If you start pressing buttons from first to last you should see the resistance go up for each successive one. If you use 1.5K resistors, like in the diagram, your first button should read 1.5K ohms. The second 3K ohms. The third 4.5K ohms. etc.
@james I want to expend the number of switches of my MC8 with a “Ladder aux switch”, with 6 switches for exemple, connected to omniport 1. I’m wondering if it’s possible to assign all press types to each switch of the 6 : “Press, release, double press, long press, etc.” and assign a midi message to each type as for the 8 built-in MC8 switches? Or is it only one midi message per switch?
In the video on adding a 3-button “standard aux switch” (“https://youtu.be/IYEjrzsaSbc?si=4VslnWlKLym9sszD”), assigning the “aux switch” function allows the switch to be used with all press types. I’d like to know if the same applies to auxiliary ladder switches. I ask because on the screenshot with your explanations, it seems there’s only one function per switch.
I try to understand the limitation (if limitation) of the ladder aux switch.
Question I’m hoping someone can help with.
Jason from Pedalnetics built me a 7 switch resistor ladder aux switch.
(Why 7? Well, it really had to do with space on my board)
Was hoping to use the buttons for dedicated functions. For example:
- Toggle page
- Bank up
- Bank down
- MIDI clock tap tempo
- Loop start/stop (controls boss rc-5)
- Undo/redo loop (controls boss rc-5)
- Clear loop (controls boss rc-5)
I haven’t received the pedal yet so admittedly I haven’t really messed around with this yet but I did look around in the editor. Functions controlling the Morningstar (Toggle page, bank up, bank down, and tap tempo) seem pretty straight forward. But I think I’m not understanding the preset part. Can I have dedicated buttons on aux switch to send messages another pedal?
If assigned to preset A, then does that change with the bank?
I guess I don’t understand why one would not just press the switch on the Morningstar vs on the aux switch.
Maybe how I intend to use the aux switch is not correct, but that’s what I was hoping for.
Can someone clarify how I would do it? Or if it can be done.
Thanks!
Hello @timhongx2
It’s easy, just assign one of the switch letters you’re not using with the controller to a switch on the auxiliary ladder footswitch. In the case of the MC8, for example, you can directly use the letters A (1) @ P (16). In other words, the 2 available banks. On the editor, you’ll see that letters 17 (Q) to 22 (V) is there and are free to assign. These 6 letters can be assigned to your auxiliary ladder switches and programmed with midi messages like those of the controller, for press, double press, long press and so on, just like the original controller switches. You can also assign functions like “bank up”, but when you assign “bank up”, for example, you can only do “bank up” with this switch and won’t be able to assign any other midi message.
Hope it help
Hello @james ,
I have a bug with the ladder switches and my MC8. I purchased 8 ladders aux switch pedal from a professional company and confirmed that everything is working before shipping. I was able to assign the omniport #1 to the Laderswitch type, calibrate it, and do whatever I wanted with the web editor (assign letters to the switch or predefined functions bank up, down and so on), without any problem, but the recording/uploading is not done in the MC8. When I go to the MC8 “inboard” menu, for omniports, the transfer is not done because the “omniport” type equals “error”. This seems to be the case for other assignment options (3@4). The expression and midi In,Out options and the classic aux switches are correct.
I updated my MC8 to firmware 3.12.5.240131400 “before starting”. After finding the issue in the inboard menu I try a “reset” with the inboard menu. Try reinstall the firmware 3.12.5, but nothing is working the omniport still show error.
Finally, I’m pretty sure you will fix it shortly or let me know what I’m doing wrong. Then, if I could request a new feature, if it’s possible for the MC8 to add a “W and X” switch name, that would be great! Because it limits the possibilities of implementation to have only 6 midi programmable switches when you have 8 ladder switches. In addition it will give us 3 full 8 switches bank available.
UPDATE :
I try the firmware version 3.12.5 with NO keyboard key. Same result, inboard menu say omniport = error. I try the 3.12.4 down to the 3.12.2, same behavior and result.
Ah. Didn’t realize there are more preset options than whats in the banks.
Thanks. Will try it soon.
No problemo, I hope @james can add 2 more 
. That way, we’ll have 8 available for my new 8-ladder switch pedal.
Can confirm this behaviour but it’s not an urgent issue. We’ll fix this in the next update. The resistor ladder data is stored correctly in the MC8 and can be edited correctly on the Editor, but it shows up as “Error” in the omniport settings if you view it on the device itself.
We can’t add additional presets for the MC8, but I think what we can possibly do (I’m not sure yet) is give the option to the user to change 2 of the expression presets to normal presets. Because very seldom do people use 4 expression presets (with 4 expression pedals) together.
Yes! This would be a very welcomed feature especially if the new presets can operate independently of the letter presets (A-X) like the Exp. presets do. This would avoid things like disengaging a preset when using CCs for tap tempo and disengaging with other actions/messages as well. I’m currently using a Disaster Area MIDI Baby 3 to access the 3 Exp. presets that I never use for an exp. pedal. I assign each button on the MIDI Baby to one Exp. preset, giving me essentially a “smart” aux switch in which I can also use the “Hold” button action on the Baby to access other functions on the MC6 Pro as well without disengaging any presets or toggling states that are currently engaged.
I’ve just recently started doing this and it works well but it’s limited to PC/CC. Your idea of giving the user the option to change 2 of the exp. presets would be a game changer as long as the new presets operate independently like the exp. presets but with all the button actions and message types of the letter presets (A-X).
Hello @james
Thanks for your reply, the problem I’m having with the ladder switch is “it doesn’t work” 
. I realized I wasn’t explaining it in my post. All settings are made with the web editor, it seems to save on the controller (with the “error” display bug) by always show on the controller they have been updated. I assigned the first switch “Bank up (MC8-utility function)” to another “Bank jump to bank #1” and a third as Switch Q with “bank down midi msg”. In the editor when I trigger the switch, the midi monitor show nothing. After disconnecting the editor, when press no switch responds/reacts by sending a midi message, nothing works 
. The only time the switch work is during the calibration process. The last thing I can specify is that the company that built the pedal tested it on an MC6-Pro (3.12.6), everything works correctly and they sent me the calibration value obtained. I didn’t use these values, I redid the calibration with the MC8… All the values are different, for example the first switch is 15 on the MC6Pro and 7 on the MC8. This is probably linked to the omniport electrical circuits, which are probably different in amperage or voltage on the 2 controllers. You can see the result of my calibration below. In addition, I’ve tried with firmware version 3.12.4 and the scaling switches don’t work either.
It’s a good idea to give the choice between expression and standard button! I noticed that you already have 26 memory slots (A-Z), considering the 4 expressions as W,X,Y & Z. If it’s not possible to have an AA and BB like 27 and 28, it seems to me an excellent idea to give the choice.
Hi @timhongx2,
I don’t have an MC6-Pro, I have the MC8 and I work under Windows.
UPDATE: After writing a reply to help you, I looked on the Morningstar website at the demo mode of the MC6-MKII and MC6-Pro editor. What you have on your screenshot is the capacity of the MC6-MKII (the original MC6), not the MC6Pro.
Two possibilities, as I understand it :.
-
You have installed the MC6-MKII firmware accidentally on your MC6Pro instead of the latest firmware version of the MC6Pro (3.12.6). (https://manuals.morningstar.io/mc-midi-controller/MC6-PRO.986611713.html#MC6PRO-UpdatingtheFirmware) or this step-by-step reference may not be up to date (https://manuals.morningstar.io/mc-midi-controller/updating-your-firmware) or you need to update your firmware.
-
You have an MC6-MKII, not an MC6-Pro. If this is the case, you have a limitation due to the power of the controller and its memory. If you want to see the possibility of the MC6-Pro go to this page https://editor-beta.morningstar.io/mcgen2 at the bottom open the MC6Pro « Demo mode » you will see the difference from your screenshot.
This is the best I can do for you, sorry, I don’t have the MC6Pro I can’t test nothing.