> Unfortunately Stephen already unsubscribed. I reached out to him, but got no response.
You know, I'm actually saddened by this. He clearly didn't have appropriate expectations in the first place. But I guess I was hoping with the slight reset on his expectations, he'd see the light and become a happy member of this member-supported small community that we have. He could have fallen on his sword with an apology and saved face and been redeemed among his "new" peers he has here. Plus I think most of us are tolerant enough for giving people second chances. Oh well. You can't please everybody all of the time. And those that are not pleased and have already put a foot in their mouth (so to speak) don't always recover from that enough to feel comfortable among their (now former) peers. On Sun, Feb 10, 2019 at 10:17 PM John R. Hogerhuis <[email protected]> wrote: > Hello Greg, > > Unfortunately Stephen already unsubscribed. I reached out to him, but got > no response. > > As to the pin alignment, I'm glad you got it working. > > Sometimes debugging issues is a matter of faith. If you aren't sure what > part to trust, you end up chasing your tail. > > I have a strong level of confidence in REX at this point given Stephen > Adolph's design, firmware and software, and it's unlikely any of the people > currently shipping them would ship them untested. > > So I think the #1 default culprit is going to be pin contact since that's > the random variable. Even if it leaves the fabricator's workbench fully > tested, which I fully expect they all do (since who would want to deal with > tech support issues) they can't know what condition the customer's option > ROM socket is going to be in. > > And it has proven in practice to be a common issue in installing REX. I > had the same problem installing my units. > > Luckily it's not too hard to bend the pins back out a bit to make contact. > > -- John. > -- Gary Weber [email protected]
