Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

CTRL:R encoder only sends a value of +1/-1

An unused (NOS) unit is sending only +1/-1 value on one of the encoders. I did a full reset both using the editor as well as the sysex file. Used an external MIDI monitor as well as the one included on the editor, but it seems it is a hardware problem

Which is the specific part for the encoders? I am able to service the unit myself but opening it is not worth if I don't have the exact pot I need to replace it

Comments

  • Hi there bichuelo,

    I don't think it's a hardware problem. If its successfully sending +1/-1, then the encoder is physically working, but the firmware has stored the wrong mode for it. It's more likely a problem with the settings. Are you using it in conjunction with a script at any point? Which encoder is giving you the issue?

  • Hi, thanks for your help!

    The encoder is the lower, leftmost. CC 50 [ID: 8]
    It shows mode CC both in the encoders section as well as send MIDI under Inspector, identical to the rest of the encoders

    No custom script, I tried both sending a .syx file to reset it as well as recalling Defaults (reset) from the Livid Editor online, several times. but the results are the same

  • I noticed the send MIDI section says Note. I changed it manually but it seems all of them are set like this, after resetting again

  • can you show me a Midi stream coming from it, into say, MIDI Monitor? Just curious exactly what it's sending.....

  • Here you are. I included the movement of the enconder to its right. Of course all resets have been done previously including a factory reset

    Both encoders are moved to the left and right during the test

  • Ok, yeah that seems like a bad pot. If it were sending inc/dec it would be different values.

    I'll look around and see if I can find the right specs for those, I had to replace one on my Code a long time ago, but I got them direct from Livid. Still, I know that the info exists somewhere, because I had it at the time.

    Might be a minute before I get back to you, super busy atm....apologies in advance ;)

  • Thank you!

    Hope you are able to find the model easily so I can service it and have that controller on full throttle again

  • edited February 2021

    There are two types of encoders that were used for CNTRLR. One sends a reversed signal, so it's important to get the right one. I looked through the forums and my emails and couldn't find the right information, and unfortunately the ones that I have are for Code, not CNTRLR, so they aren't necessarily the same.

    Do you have any way of knowing the production date of the CNTRLR you have? Or which firmware was installed? There were two, one for the reversed encoders and one for the regular ones...if you can determine that, I can probably narrow it down for you a bit.

    a

  • Thanks!

    I can get the serial number, the number of the service tags in the boards inside the unit and the date the unit was exported from Austin.

    Which information could help to find the production date of the unit?

  • The date of export is probably the only useful thing, but I don't know how accurate it will be. The best way to find out is to try both versions of the firmware, see which one works right (either will work, but for one version the encoder direction will be reversed), and then we would know for sure.

  • It says the 0.1.2.3 firmware is installed on the editor and the encoder direction is clockwise, as expected.

    I found both firmwares (including 1.27) at this thread: https://aumhaa.com/forum/discussion/20/does-anybody-have-cntrl-r-version-1-27-firmware#latest

    But I can't find the bootloader and the link on the wiki is broken

  • Sorry, missed this post and have been really busy.

    Here's a link to the firmware updater, which I think is what you're looking for:

    http://www.aumhaa.com/livid_archive/FirmwareUpdater/Livid_Firmware_Update_117_osx.zip

    Does that get you up and running? I'll be unavailable for the next week-ish, apologize for getting back to you a bit late....

    a

  • @amounra said:
    The date of export is probably the only useful thing, but I don't know how accurate it will be. The best way to find out is to try both versions of the firmware, see which one works right (either will work, but for one version the encoder direction will be reversed), and then we would know for sure.

    I was able to load both firmware files but for some reason both behave the same, none of them reversed. Don't know if I made it properly, the updater reported success both times

    It would be great to confirm what the controller reports using the editor, but the page has been down for some days. Using the Wayback Machine I was able to find the wiki in order to put it in bootloader mode, but the editor is not there :/

  • I’m away from home atm, but there are two different editor links that you can still find via google....one works and one doesn’t. Maybe search for the one that does (sorry I have no way to check at the moment)....I’ll be home next week and I can try to help more then. There’s also an editor app that will work on older OSs but again, I have no access to any resources right now, I’m posting this from my phone ;)
  • the domain was down for several days and now that it's back I can get to the editor at https://lividinstruments.com/editor_2017/
    And even though the main site works, the wiki is down as I'm typing

    Fortunately I remember how to put it in bootloader mode and I was able to successfully load both firmware 0.1.2.7 and 0.1.2.3
    But, all of the controls move in the same direction on the two versions

    What else can be done to find out which is the correct part to replace? I can disassemble the unit and take pictures

  • So sorry that I haven't gotten back to you about this, I have actually looked for the information but couldn't find anything useful. I'll try to email someone that knows more than I do, no promises.....

    a

  • Thank you!

Sign In or Register to comment.