More Video-IO Expander

[XORadmin]

I am experiencing some very wonky behavior with USB keyboard functionality.

The issues I mentioned previously with the keyboard timing out after a while are still happening. I tried three different keyboards with and without a USB hub.

But now I am having worse issues as well:

1. The cursor will no longer scroll at all when a direction arrow is held down. Also there seems to be a lag when pressing the cursor keys repeatedly.

2. Shift functions seem to not be working properly.

3. Chaotic inputs are happening occasionally as though other keys are getting pressed - while using nothing but the arrow keys to try and scroll around.

I am on the newest proper firmware 2.02 and absolutely love all the new things that came with it.. but my USB keyboard is currently unusable. Starting to think I may have a hardware issue unfortunately.

Could be a cable issue. And maybe check your key delay and repeat settings.

[spilthyfred]

I am experiencing some very wonky behavior with USB keyboard functionality.

The issues I mentioned previously with the keyboard timing out after a while are still happening. I tried three different keyboards with and without a USB hub.

But now I am having worse issues as well:

1. The cursor will no longer scroll at all when a direction arrow is held down. Also there seems to be a lag when pressing the cursor keys repeatedly.

2. Shift functions seem to not be working properly.

3. Chaotic inputs are happening occasionally as though other keys are getting pressed - while using nothing but the arrow keys to try and scroll around.

I am on the newest proper firmware 2.02 and absolutely love all the new things that came with it.. but my USB keyboard is currently unusable. Starting to think I may have a hardware issue unfortunately.

Could be a cable issue. And maybe check your key delay and repeat settings.

I tried multiple cables and also tried using a hub in between. The other keyboards I tried had the cable attached. I also tried with and without the midi expander, and swapping ports too. I even made sure the microSD was formatted correctly and that it had the proper files on it.

Key delay is set at 200ms and repeat at 50ms... pretty sure they were never changed.

All keyboards and cables work just fine when I plug into my actual desktop computer for what its worth.

[XORadmin]

I am experiencing some very wonky behavior with USB keyboard functionality.

The issues I mentioned previously with the keyboard timing out after a while are still happening. I tried three different keyboards with and without a USB hub.

But now I am having worse issues as well:

1. The cursor will no longer scroll at all when a direction arrow is held down. Also there seems to be a lag when pressing the cursor keys repeatedly.

2. Shift functions seem to not be working properly.

3. Chaotic inputs are happening occasionally as though other keys are getting pressed - while using nothing but the arrow keys to try and scroll around.

I am on the newest proper firmware 2.02 and absolutely love all the new things that came with it.. but my USB keyboard is currently unusable. Starting to think I may have a hardware issue unfortunately.

Could be a cable issue. And maybe check your key delay and repeat settings.

I tried multiple cables and also tried using a hub in between. The other keyboards I tried had the cable attached. I also tried with and without the midi expander, and swapping ports too. I even made sure the microSD was formatted correctly and that it had the proper files on it.

Key delay is set at 200ms and repeat at 50ms... pretty sure they were never changed.

All keyboards and cables work just fine when I plug into my actual desktop computer for what its worth.

Inside cable connections. Especially the ribbon cable to the Midi port.

[spilthyfred]

I just tried multiple different ribbon cables for both the NSA and MIDI. For a moment after switching the NSA cable to a shorter one it would scroll again, but only for 5-6 steps, sometimes only 1 or none at all. Then it just stopped working again. Shift functions still do not work correctly either.

Are the ribbon cable connections super sensitive? I was using longer ribbon cables due to routing in my case (the more video expander is mounted on the back). Everything was working before until recently. Now, even when testing with shorter cables it is still not functioning properly. Would more robust ribbon cables do the trick?

[spilthyfred]

I am experiencing some very wonky behavior with USB keyboard functionality.

The issues I mentioned previously with the keyboard timing out after a while are still happening. I tried three different keyboards with and without a USB hub.

But now I am having worse issues as well:

1. The cursor will no longer scroll at all when a direction arrow is held down. Also there seems to be a lag when pressing the cursor keys repeatedly.

2. Shift functions seem to not be working properly.

3. Chaotic inputs are happening occasionally as though other keys are getting pressed - while using nothing but the arrow keys to try and scroll around.

I am on the newest proper firmware 2.02 and absolutely love all the new things that came with it.. but my USB keyboard is currently unusable. Starting to think I may have a hardware issue unfortunately.

Could be a cable issue. And maybe check your key delay and repeat settings.

I tried multiple cables and also tried using a hub in between. The other keyboards I tried had the cable attached. I also tried with and without the midi expander, and swapping ports too. I even made sure the microSD was formatted correctly and that it had the proper files on it.

Key delay is set at 200ms and repeat at 50ms... pretty sure they were never changed.

All keyboards and cables work just fine when I plug into my actual desktop computer for what its worth.

Inside cable connections. Especially the ribbon cable to the Midi port.

I just tried multiple different ribbon cables for both the NSA and MIDI. For a moment after switching the NSA cable to a shorter one it would scroll again, but only for 5-6 steps, sometimes only 1 or none at all. Then it just stopped working again. Shift functions still do not work correctly either.

Are the ribbon cable connections super sensitive? I was using longer ribbon cables due to routing in my case (the more video expander is mounted on the back). Everything was working before until recently. Now, even when testing with shorter cables it is still not functioning properly. Would more robust ribbon cables do the trick?

Tried rolling back to Firmware 1.27, and suddenly everything seemed to go back to normal. Scrolling was fine. Shift functions worked.

Then everything started misbehaving again, only this time it is registering keys as being held down even after I let go. Scrolling wont stop. CTRL, ALT, and SHIFT being registered at random - giving random inputs all over.

So on the newer firmware it wont register any held down keys - and the timeout issue seemed far less frequent.
While on the older firmware held keys remain registered for too long and the timeout issue came back.

HDMI has always worked flawlessly, but the USB connection has remained problematic for me. I really want to get the USB keyboard set up so it just works and stays connected as it makes the Nerdseq so much better to use.

[XORadmin]

I am experiencing some very wonky behavior with USB keyboard functionality.

The issues I mentioned previously with the keyboard timing out after a while are still happening. I tried three different keyboards with and without a USB hub.

But now I am having worse issues as well:

1. The cursor will no longer scroll at all when a direction arrow is held down. Also there seems to be a lag when pressing the cursor keys repeatedly.

2. Shift functions seem to not be working properly.

3. Chaotic inputs are happening occasionally as though other keys are getting pressed - while using nothing but the arrow keys to try and scroll around.

I am on the newest proper firmware 2.02 and absolutely love all the new things that came with it.. but my USB keyboard is currently unusable. Starting to think I may have a hardware issue unfortunately.

Could be a cable issue. And maybe check your key delay and repeat settings.

I tried multiple cables and also tried using a hub in between. The other keyboards I tried had the cable attached. I also tried with and without the midi expander, and swapping ports too. I even made sure the microSD was formatted correctly and that it had the proper files on it.

Key delay is set at 200ms and repeat at 50ms... pretty sure they were never changed.

All keyboards and cables work just fine when I plug into my actual desktop computer for what its worth.

Inside cable connections. Especially the ribbon cable to the Midi port.

I just tried multiple different ribbon cables for both the NSA and MIDI. For a moment after switching the NSA cable to a shorter one it would scroll again, but only for 5-6 steps, sometimes only 1 or none at all. Then it just stopped working again. Shift functions still do not work correctly either.

Are the ribbon cable connections super sensitive? I was using longer ribbon cables due to routing in my case (the more video expander is mounted on the back). Everything was working before until recently. Now, even when testing with shorter cables it is still not functioning properly. Would more robust ribbon cables do the trick?

Tried rolling back to Firmware 1.27, and suddenly everything seemed to go back to normal. Scrolling was fine. Shift functions worked.

Then everything started misbehaving again, only this time it is registering keys as being held down even after I let go. Scrolling wont stop. CTRL, ALT, and SHIFT being registered at random - giving random inputs all over.

So on the newer firmware it wont register any held down keys - and the timeout issue seemed far less frequent.
While on the older firmware held keys remain registered for too long and the timeout issue came back.

HDMI has always worked flawlessly, but the USB connection has remained problematic for me. I really want to get the USB keyboard set up so it just works and stays connected as it makes the Nerdseq so much better to use.

In the past except for some types of USB keyboards, the stability relied always on the ribbon cable.
Maybe it does get any interference from the surroundings somehow? 

The communication never changed in earlier versions so I guess if it is just a 'feeling' that it is fine.
I can always send up some new 14 pin ribbon cables if needed.
Also the upcoming version will do have a difference in communication and maybe that helps.

[spilthyfred]

Could be a cable issue. And maybe check your key delay and repeat settings.

I tried multiple cables and also tried using a hub in between. The other keyboards I tried had the cable attached. I also tried with and without the midi expander, and swapping ports too. I even made sure the microSD was formatted correctly and that it had the proper files on it.

Key delay is set at 200ms and repeat at 50ms... pretty sure they were never changed.

All keyboards and cables work just fine when I plug into my actual desktop computer for what its worth.

Inside cable connections. Especially the ribbon cable to the Midi port.

I just tried multiple different ribbon cables for both the NSA and MIDI. For a moment after switching the NSA cable to a shorter one it would scroll again, but only for 5-6 steps, sometimes only 1 or none at all. Then it just stopped working again. Shift functions still do not work correctly either.

Are the ribbon cable connections super sensitive? I was using longer ribbon cables due to routing in my case (the more video expander is mounted on the back). Everything was working before until recently. Now, even when testing with shorter cables it is still not functioning properly. Would more robust ribbon cables do the trick?

Tried rolling back to Firmware 1.27, and suddenly everything seemed to go back to normal. Scrolling was fine. Shift functions worked.

Then everything started misbehaving again, only this time it is registering keys as being held down even after I let go. Scrolling wont stop. CTRL, ALT, and SHIFT being registered at random - giving random inputs all over.

So on the newer firmware it wont register any held down keys - and the timeout issue seemed far less frequent.
While on the older firmware held keys remain registered for too long and the timeout issue came back.

HDMI has always worked flawlessly, but the USB connection has remained problematic for me. I really want to get the USB keyboard set up so it just works and stays connected as it makes the Nerdseq so much better to use.

In the past except for some types of USB keyboards, the stability relied always on the ribbon cable.
Maybe it does get any interference from the surroundings somehow? 

The communication never changed in earlier versions so I guess if it is just a 'feeling' that it is fine.
I can always send up some new 14 pin ribbon cables if needed.
Also the upcoming version will do have a difference in communication and maybe that helps.

Thanks for the reply, hope you had a good superbooth!

Still trying to troubleshoot this. Let me know if you would like me to start a different thread or to email.

Currently I have tried 3 keyboards; 7 usb cables with and without hub; 6 different 12-pin ribbon cables short and long; 3 different 14-pin ribbon cables; different power bus boards; current and previous firmware versions... In every situation my keyboard is unusable for me. Glitches all over even though it used to 'mostly' work To be honest its never worked 100% for me. Is it possible that it could be an actual issue with the expander??


I would be willing to try some new ribbon cables to see if that helps. I do need them a little longer than usual with the way my case is set up - and hope that isn't an issue.
(I did just put in an order for the Multi-IO expander a couple days ago so maybe the cables could just go out with that order to save on shipping...)

Only other thing I could think of would be to try out even more keyboards and/or order some 26awg wire and a crimper tool and make my own more robust ribbon cables - but this is starting to feel excessive to troubleshoot. If that didn't work I would have to assume the issue lies elsewhere.