Data Encoder not working

  • I've scoped across the pins.. The encoder push changes the state on each output whereas turning the encoder seems to do nothing. I'm guessing that means the encoder is faulty?
  • Dicky wrote:I've scoped across the pins.. The encoder push changes the state on each output whereas turning the encoder seems to do nothing. I'm guessing that means the encoder is faulty?
    No, your encoder is working fine. It's a software problem. You need to reflash the Atmega1284p. The only way doing this is by using a chip programmer.

    Check this thread:

    viewtopic.php?f=28&t=1847&p=11528&hilit ... mer#p11528
  • Please try this beta update it should fix the encoder issue
    download/file.php?id=118
    Best regards,
    e-licktronic
  • I can confirm that the v2.003beta firmware solved this problem for me. Before that, I tried reflashing both v2.003 and v2.002 without success.

    Thanks for the fix!

    I reflashed the chip using an Arduino, following the instructions in this thread: viewtopic.php?f=17&t=436. No need to pull the chip, the interface is built right into the motherboard.
  • After finishing the YOCTO2, I realized that the DATA-KNOB did not work.
    I checked the DATA KNOB. He seemed to work.
    I checked the connections from the DATA-KNOB to the ATmega1284P. Was OK.
    I wrote a message to e-licktronic.com in the contact form.
    Vincent replied, "Update the firmware with the 2.003beta fixed the issue."

    When asked how to do that, he replied, "There is a process to upload the firmware available in the forum via SYSEX."

    I wrote to him that I had not read anything about it, but that some used the programmer WINGONEER TTL866II.
    His answer: The sysex firmware is available in the forum. Then you need a midi interface connected to your computer. Download a Sysex loader like midiox or C6. Then connect your midi out interface to the midi in of the yocto. Power up your yocto while holding 1,3,5 steps button, all leds wants to flash then send the sysex via the software. Wait until your yocto reboot. Your done.

    I bought a midi interface, installed midi-ox, downloaded the sysex firmware and connected PC and yocto via the midi interface. But powering up my yocto while holding 1,3,5 steps button had no effect.
    I wrote that to Vincent and have not got an answer since ...

    Solving:
    I bought the XGecu TTL866II plus universal programmer, saved the Atmega contents (2.003) on the PC and flashed 2.003beta.
    When I turned on my yocto2 all LED lit up. The yocto2 responded to no input while terrible sounds came from the speakers. :o
    I flashed the original 2.003. The same lights and noises. :shock:
    Maybe the fuse bits are wrong. I needed information. I found two Fusebit calculators.
    https://eleccelerator.com/fusecalc/fuse ... tmega1284p and
    http://www.engbedded.com/fusecalc/
    I played around a bit and flashed 2.003beta, leaving all fusebits unchecked.
    The Yocto2 works, even the DATA KNOB. Yippee !!!
    I played around a bit again and flashed 2.003, leaving all fusebits unchecked.
    Guess what? The Yocto2 works as well. Yay!

    There is obviously no problem with the software, but with the fusebits!
  • Rumpel wrote:After finishing the YOCTO2, I realized that the DATA-KNOB did not work.
    Solving:
    I bought the XGecu TTL866II plus universal programmer, saved the Atmega contents (2.003) on the PC and flashed 2.003beta.
    When I turned on my yocto2 all LED lit up. The yocto2 responded to no input while terrible sounds came from the speakers. :o
    I flashed the original 2.003. The same lights and noises. :shock:
    Maybe the fuse bits are wrong. I needed information. I found two Fusebit calculators.
    https://eleccelerator.com/fusecalc/fuse ... tmega1284p and
    http://www.engbedded.com/fusecalc/
    I played around a bit and flashed 2.003beta, leaving all fusebits unchecked.
    The Yocto2 works, even the DATA KNOB. Yippee !!!
    I played around a bit again and flashed 2.003, leaving all fusebits unchecked.
    Guess what? The Yocto2 works as well. Yay!

    There is obviously no problem with the software, but with the fusebits!
    I have done exactly the same with the same programmer and using your configuration and it works for me too!! Thank you for the instructions and thanks e-licktronic for the firmware.
    It is probably already mentioned but a stepless encoder is probably better for this project since the firmware seems to read out the values of the encoder in between the physical steps. Maybe an idea for the next version of firmware?
  • Same problem, reflashing with 2.003beta helped but the encoder is not precise as it should.