Ergodox freezes/bricks (solved)

[Zutatensuppe]

Hello,

I just got my ergodox the other day and assembled it and at my pc at home it works fine, though i have not used it very long hours.

The last 2 days i brought it to my workplace and after some time input freezes and can only be "unfrozen" by removing usb cable from ergodox.
Input freezes means that i cant move the mouse and cant get input from ergodox, but another keyboard that is connected to the pc at the same time keeps working.
When i reconnect the usb cable, the input freezes again. When i wait long enough before reconnecting the cable, input is again possible. It seems that the more often i reconnect, the longer i have to wait the next time.

I use Windows 10 both at work and at home.
Firmwares i tested already:
- Original massdrop firmware (https://www.dropbox.com/sh/8bbol6fkvydmtmg/QLudrdEyc9)
- Unmodified, but self compiled version of TMK Cub (https://github.com/cub-uanic/tmk_keyboard.git)
- Modified version of TMK Cub (added 2 layers and moved some keys)

Has anyone experienced a similar problem? Does this sound like a hardware issue or rather software/firmware/driver?
I cant use the ergodox at work if it keeps freezing like this

Help is much appreciated! If you need any more info, let me know.

I ll keep updates coming whenever I know something more.

Edit1:
Additional Information: This happens also if i just connect the ergodox and do not type on it. At some point the mouse freezes until ergodox is disconnected from usb again.
Edit2:
Have connected Ergodox with both halves, stayed ok for about 24 minutes, then froze.
I now try to connect only 1 half. By the way, is it normal that when only 1 half of the ergodox is connected, i cant type anything at all (even when not frozen)?
Edit3:
I got the ergodox from falbatech.pl if that matters.
Edit4:
Still ok with only one half connected for about 1h, mouse does not freeze, but as statet above, i can not type anything either with only one half connected. I will try at home with both halves and leave them connected as long as possible to see if i can reproduce the problem with a different pc.
Edit5:
Updated info about what firmware i tried already.

[suicidal_orange]

The Ergodox is known for using a lot of power, could that be relevent?  Front ports often supply less than ones on the motherboard, and if the mouse is connected to the same block that could be sharing the same rail and stop with it.

I would take it home and see if it works there - if it does the problem is not the keyboard...

[yinzer]

I've experienced a similar problem. However, it may not be software or hardware (per say).

If you ordered one of the cheaper two piece cases from Falbatec and, depending on how you installed your teensy, it's unlikely, but possible, that your case is putting pressure on the Teensy reset button.

If you have one of these two piece cases, you could take off the top half and see if the problem persists.

Alternately, if you have a reset button mapped to your top layer, that would have the same effect.

[tp4tissue]

I think -Yinzer- may be onto something.. I hadn't seen the 2 piece case myself.. but that does sound like it would cause the intermittent issues.


Overall more diagnostics is required to determine the at-fault..


The freezing problems I've encountered personally was always due to the trrs cable going loose, and eventually my trrs port broke, so I just soldered directly to the pcb. No more issues after that. (only left side would freeze)


If your whole board is freezing up,   First try the massdrop firmware to rule out software issue..

and if it's still freezing, then check your soldering..

[b0f0]

I have Ergodox frim Falbatech. It works fine. Did you play with the firmware ?
I have this https://github.com/benblazak/ergodox-firmware the "partial-rewrite" branch.

[Zutatensuppe]

First of all, thank you all for your responses.
Ergodox is now up and running for about 1h at home. No issues at all so far. Ill do some coding now to emulate working environment as best as possible (maybe some specific key combinations cause the issue?). I won't try anything here if no freeze happens, but i will take your advices to work tomorrow and when i have time try everything out. 

@suicidal_orange: I'm not sure if that could be a problem, but i'll check. I have connected to the hub of the monitor most of the time, but i tried with the rear usb ports of the pc tower too with the same results. Maybe i didnt connect it to usb3, but usb2? I can check that tomorrow. The mouse was always connected to rear usb ports of pc.

@yinzer: I think it is one of the cheapest cases (just acrylic). However, the reset button is free, there is a hole in the case so the button can be clicked from outside with a long pointed object. it is definately not in a clicked or near clicked state, so i'd rule that out. Doesnt hurt to test with top off though, so i guess i might give it a go anyway.  About the button mapped in layer: i have certainly mapped a button in layer 2 (where all but two buttons are transparent) that corresponds to the teensy button. I might just remove that layer alltogether, if that can be a possible culprit. but then again, why would the keyboard freeze? its not like i have that button pressed down all time. can you explain?

@tp4issue: Ok, i will check if the trrs cables are ok (they seem tightly fitted in the port, and i dont really move the keyboard). Original massdrop software was already tested, sorry i didnt mention it. How can i best check the soldering, and what parts? Sorry, i have not done such project or worked with electronics very much.. definately will check again though. might it be that if some specific buttons are pressed, the teensy goes in some kind of loop, when something was wrongly connected, was my first thought  yesterday, so i resoldered the usb cables from teensy to external usb already. i also checked all diodes directions, but thats about it.

@b0f0: Yes, i have added a 2 layers, one to move cursors and one to move mouse. but i have also tried ben blazak precompiled binary and also "default" tmk cub firmware. ill try the branch u mentioned.

[Zutatensuppe]

Small update:

I have done two things:
1. removed the layer with the mapped teensy button
2. connected the ergodox to a usb 2 port instead of usb 3 (i looked again and it was previously either connected to usb 3 port or monitor usb hub)

the results after about 2h: no problems at all.
As i have done the two at the same time, i dont know which of the two was causing the freeze, but by what you said i guess it is the usb port.

I hope this continues to go well. 

Update: whole day without freeze. seems like one of the 2 was really the problem. i will try to verify that tomorrow by plugging into the other usb port again. but im glad its working now

[tp4tissue]

Small update:

I have done two things:
1. removed the layer with the mapped teensy button
2. connected the ergodox to a usb 2 port instead of usb 3 (i looked again and it was previously either connected to usb 3 port or monitor usb hub)

the results after about 2h: no problems at all.
As i have done the two at the same time, i dont know which of the two was causing the freeze, but by what you said i guess it is the usb port.

I hope this continues to go well. 

Update: whole day without freeze. seems like one of the 2 was really the problem. i will try to verify that tomorrow by plugging into the other usb port again. but im glad its working now

my guess..  xhci is messing with it..

[Zutatensuppe]

does that mean, with another firmware it could work on usb 3 too? anyway, on usb2 no problems for 2 consecutive days 

[tp4tissue]

does that mean, with another firmware it could work on usb 3 too? anyway, on usb2 no problems for 2 consecutive days 

um... you can try.. this thing...



Install RWeverything 64bit..

Run the command     WPCI32 00h 14h 00h D0h 00h; RwExit

Check that the line to the right of D0 is all zeros