Hi,
I just finished (badly, SMD sucks so hard) soldering up a Beamspring -USB-5251 Rev 4. When I plug it into my computer (win 10), it says "USB device not recognized) and when I try to start up the capsense utility it says "No Controller found"
I'd really like to convert this thing...but I dunno what to do here.
Oh not to mention not only is it not working, but the DAC101S101 (U2) is sparking/crackling
One other note: I'm testing the controller completely disconnected from my actual beamspring. Just plugging the converter alone into my computer. Don't know if that matters.
As I am using the same parts as you are, I can give an update as soon as my PCBs have arrived.
Attaching the controller without keyboard attached should work without issues and I am worried about the sparking/crackling
This can be caused by shortening something, like the USB connector itself or other parts. The 0.1uF condensators shouldn't care about the polarity but I am not so sure about C5. As I am not an expert, I have only wild guesses here.
Why would you do that in 2019? CY8CKIT-059 is 5x cheaper and supports literally everything (except parts of macro engine which didn't strictly work anyway).
"USB device not recognized" is "it's powered on, but something strange comes off data pins". Check the signal train from USB socket to the main chip.
If things spark - you are definitely blowing the resettable fuse in your USB port. Not sure after how many cycles they become blown fuses, so you want to avoid plugging things that short-circuit USB power pins
It means understandable by curious but not-that-curious nincompoops, like the rest of us! So you spell out things really explicitly. Do not assume knowledge. Everything relevant should be laid out so clearly, it strikes you as insulting to the reader. It isn’t. We need that!
Oh, and everything that is not directly relevant to the reader's needs should be ruthlessly cut. It’s really all about giving us the direct how-to we need.
Xwhatsit’s docs were pretty good that way. I remember finding them a bit of a stretch in places but mostly reassuring.
DMA wrote: 16 Jul 2019, 18:49
I'm all ears. What does it mean to have a "particularly clear guide"?
Something that answers the following questions:
This device supports many different keyboards, here's how you determine how to wire it up. E.g. this is how you determine rows and columns, logical way of wiring these pins to the microcontroller, etc. Example(s) provided.
Ok now you've wired it up, here's the steps you need to take to program it, outlined, start to finish. Starting from necessary software installation on applicable operating systems to programming individual keys. Example(s) provided.
First part is also kind of there - it tells you about where rows and columns are by default. If you go remapping - you must understand the dev environment and I'm not making that readme "teach yourself PSoC Creator in 21 days".
Not convinced whether "how to figure out your PCB interface" should be in this README or not - if you're into esoteric hardware, you should know about those things.
The difference between xwhatsit docs and CS docs is that the former didn't have any choice/options. It was made for 4x23 or 8x16 matrix, and it was preprogrammed - which took care of switch type, too. So you had a physical board which defined _everything_. Simplifies instructions, but good luck if you have a displaywriter, because nobody makes xwhatsit for displaywriter as there are not many of those.
DMA wrote: 16 Jul 2019, 19:37
if you're into esoteric hardware, you should know about those things.
Dude, no. That is an unacceptable attitude, and you are not going to be well liked if you carry on that way. The saying about making assumptions comes to mind.
You may be some great expert, and were sorry that we aren't as brilliant as you are, but we still want to convert out keyboards and still want help doing so and aren't really interested in being condescended towards in the process.
I strongly suggest you reassess your attitude on this matter.
I am not a "great expert", neither I play one on TV.
It's just I mostly know when I don't know things - and PCB mapping without PCB in hand is one of those.
I literally can't know all the variants (or even technologies) of all the keyboards CS _may_ support (see, for example, Sandgrax's foam-and-foil conversions).
PS: f you think xwhatsit manual is authoritative on the layout of IBM keyboards from 70s so everything must "just work" - well, it's the other way around.
_your_ 3278 may have different layout and different matrix - because it's of some rare batch or something.
DMA wrote: 16 Jul 2019, 20:53
I am not a "great expert", neither I play one on TV.
It's just I mostly know when I don't know things - and PCB mapping without PCB in hand is one of those.
I literally can't know all the variants (or even technologies) of all the keyboards CS _may_ support (see, for example, Sandgrax's foam-and-foil conversions).
PS: f you think xwhatsit manual is authoritative on the layout of IBM keyboards from 70s so everything must "just work" - well, it's the other way around.
_your_ 3278 may have different layout and different matrix - because it's of some rare batch or something.
The point here is that if you were given a capacitive switch keyboard, you could probably make it work. Try to put the process that you would apply down in words so that others may learn from it.
I don't think xwhatsit's manual is authoritative, in fact he's lacking massively in particularly annoying ways, not to mention I can't even get mine to work (although that's probably down to bad soldering, but who knows, you know?)
PancakeMSTR wrote: 16 Jul 2019, 23:00(although that's probably down to bad soldering, but who knows, you know?)
Oh, don't worry. If you pass the "solder it correctly" part - you'll just unlock level 2.
The boss on level 2 is "find a threshold which reliably registers keypresses and yet doesn't spuriously fire when I don't press anything".
As for "lacking in annoying ways" - I fail to see any publicly-accessible documents from you which would describe your findings and how you overcame those. You're blaming me for not providing you with pictured step by step guide - yet I don't see any produced by you. Do unto others, y'know.
DMA wrote: 16 Jul 2019, 23:58
Oh, don't worry. If you pass the "solder it correctly" part - you'll just unlock level 2.
The boss on level 2 is "find a threshold which reliably registers keypresses and yet doesn't spuriously fire when I don't press anything".
PancakeMSTR wrote: 16 Jul 2019, 23:00(although that's probably down to bad soldering, but who knows, you know?)
Oh, don't worry. If you pass the "solder it correctly" part - you'll just unlock level 2.
The boss on level 2 is "find a threshold which reliably registers keypresses and yet doesn't spuriously fire when I don't press anything".
As for "lacking in annoying ways" - I fail to see any publicly-accessible documents from you which would describe your findings and how you overcame those. You're blaming me for not providing you with pictured step by step guide - yet I don't see any produced by you. Do unto others, y'know.
Look, I get that the xwhatsit is apparently not the optimal solution, even though some people seem to be using it just fine. To me, it just seems like the easiest approach to converting a beamspring, while your method does not. That was what factored into my decision making process.
Nonetheless, I'm planning on trying to get both the xwhatsit and your commonsense converter working.
As for "documents describing my findings," I don't have any because I haven't successfully gotten either the xwhatsit or
the commonsense converters working, though I might write up my experience if I ever do. At a minimum, though, I at least put together a parts list for the xwhatsit beamspring-usb pcb, which I consider a start.
Hi,
I just finished (badly, SMD sucks so hard) soldering up a Beamspring -USB-5251 Rev 4. When I plug it into my computer (win 10), it says "USB device not recognized) and when I try to start up the capsense utility it says "No Controller found"
I'd really like to convert this thing...but I dunno what to do here.
Oh not to mention not only is it not working, but the DAC101S101 (U2) is sparking/crackling
One other note: I'm testing the controller completely disconnected from my actual beamspring. Just plugging the converter alone into my computer. Don't know if that matters.
It's almost certainly the soldering. I too am bad at SMD soldering but practice makes perfect. Maybe try to take a few photos, especially of the MCU. It might be something that can be reworked.
When you plug it into the computer for the first time, it should show up as "Atmel USB Device" > "ATmega32U4" if I'm not mistaken.
I'm sorry I'm not very familiar with xwhatsit but it sounds like you want to validate:
You used the right components
Your soldering is fine
There's certainly people here who can help answer those questions.
Oh and my guess is that, if parts were sparking, those parts (and possibly others) may be toast. This is just a guess though. Unfortunately a fried component doesn't always show visible signs of brokenness.
Hi,
I just finished (badly, SMD sucks so hard) soldering up a Beamspring -USB-5251 Rev 4. When I plug it into my computer (win 10), it says "USB device not recognized) and when I try to start up the capsense utility it says "No Controller found"
I'd really like to convert this thing...but I dunno what to do here.
Oh not to mention not only is it not working, but the DAC101S101 (U2) is sparking/crackling
One other note: I'm testing the controller completely disconnected from my actual beamspring. Just plugging the converter alone into my computer. Don't know if that matters.
It's almost certainly the soldering. I too am bad at SMD soldering but practice makes perfect. Maybe try to take a few photos, especially of the MCU. It might be something that can be reworked.
When you plug it into the computer for the first time, it should show up as "Atmel USB Device" > "ATmega32U4" if I'm not mistaken.
I'm sorry I'm not very familiar with xwhatsit but it sounds like you want to validate:
You used the right components
Your soldering is fine
There's certainly people here who can help answer those questions.
Oh and my guess is that, if parts were sparking, those parts (and possibly others) may be toast. This is just a guess though. Unfortunately a fried component doesn't always show visible signs of brokenness.
Yeah I probably screwed something up with the soldering. I've ordered parts to try again, and also am planning on ordering parts to try one of Commonsense's converters. I'll come back here with the results, but it'll prolly be a week or two.
Oh and the major thing I want to validate is that I have the right parts, I know my soldering is terrible and probably the reason I fried parts. I'll only start to reconsider that if I feel like I soldered everything absolutely perfectly and it's still not working.
