[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4756: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3891)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4758: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3891)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4759: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3891)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4760: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3891)
fingerfans.dreamhosters.com • View topic - Fruitful TouchStream Repair Tactics

Fruitful TouchStream Repair Tactics

Comments specifically about the keyboard devices.

Moderator: The00Dustin

Fruitful TouchStream Repair Tactics

Postby pythagoras » 16 Mar 2006, 08:01

pythagoras
Hang-around
 
Posts: 3
Joined: 16 Mar 2006, 06:18

Postby ivanw » 16 Mar 2006, 11:23

This is nice. This is understandable. Anyone could have guessed that something simple happened to explain the end of an episode. At last we know that this is not one of those damned profit motive again. It's just that it would have been comforting to know that sooner. I know, there has been so many good reasons why no one could talk by then.

Now for the repair advices. Thanks, whomever you are :wink:. Maybe we won't worship you for this but it will help the community in its contribution to make it happen again. As I said before, we had to work hard too. Keeping the spirit alive is our task in the process.
Image

Ivan
User avatar
ivanw
Zealot
 
Posts: 390
Joined: 29 Jul 2005, 12:32
Location: Paris, France

Postby nomaded » 16 Mar 2006, 21:37

I think "Prometheus" would have been a better pseudo than "pythagoras". :wink:

Thank you very much for some of those insights are what to look for, for future repairs. I really hope you will be able to stay and participate in this little community - your experience is invaluable.
nomaded
Smarty Pants
 
Posts: 131
Joined: 27 Apr 2005, 04:11
Location: MA

Postby The00Dustin » 17 Mar 2006, 03:27

The00Dustin
Grizzled Veteran
 
Posts: 183
Joined: 28 Apr 2005, 22:07

Postby ivanw » 17 Mar 2006, 12:21

Worshiped? :roll: I would just say that some genuine experienced fellow would be appreciated to say the least. There must be some still alive I think. Is that truly not feasible? If so, could anyone explain why?

Any suggestion about coming up with someone that could build up the required skills and equipment? These are typical symptoms analysis that should be written down into some repair procedure. More information has to be collected as well, like schematics, test points and their typical readout: voltages, frequencies, wave shape. In fact, all this is the matter of a specialized organization. And I know that efficient servicing facility can only be achieved by someone close enough from the repair activity.

If one of us is ready to put his/her hand on a and manage to know how to , then I will be confident in our ability to repair a damaged device. All this talking comes from my previous life experience of the field. That's why I can tell that I am not able to do it myself.
- I know that I don't know what has to be known to do a good job.
- Does anyone knows/wants us to know he/she knows?
User avatar
ivanw
Zealot
 
Posts: 390
Joined: 29 Jul 2005, 12:32
Location: Paris, France

Postby pythagoras » 18 Mar 2006, 19:22

pythagoras
Hang-around
 
Posts: 3
Joined: 16 Mar 2006, 06:18

Postby ivanw » 18 Mar 2006, 21:07

User avatar
ivanw
Zealot
 
Posts: 390
Joined: 29 Jul 2005, 12:32
Location: Paris, France

Postby aat0995 » 19 Mar 2006, 19:44

aat0995
Hang-around
 
Posts: 8
Joined: 07 Mar 2006, 16:55

Postby ibrandt » 28 Mar 2006, 05:50

ibrandt
Hang-around
 
Posts: 8
Joined: 09 Jul 2005, 17:20

Postby Michael.Massing » 07 Apr 2006, 03:06

Michael.Massing
Hang-around
 
Posts: 5
Joined: 07 Apr 2006, 02:33

Postby ivanw » 07 Apr 2006, 09:27

User avatar
ivanw
Zealot
 
Posts: 390
Joined: 29 Jul 2005, 12:32
Location: Paris, France

Postby Rqyteqto » 07 Apr 2006, 18:58

Invent the Future
Rqyteqto
Grizzled Veteran
 
Posts: 201
Joined: 13 Jun 2005, 01:40
Location: Kahalu'u, Oahu, Hawaii

Postby Michael.Massing » 07 Apr 2006, 19:47

Michael.Massing
Hang-around
 
Posts: 5
Joined: 07 Apr 2006, 02:33

Postby Rqyteqto » 08 Apr 2006, 20:43

Invent the Future
Rqyteqto
Grizzled Veteran
 
Posts: 201
Joined: 13 Jun 2005, 01:40
Location: Kahalu'u, Oahu, Hawaii

Re: Fruitful TouchStream Repair Tactics

Postby -jeffB » 03 May 2006, 19:22

-jeffB (Jeff Brandenburg, Durham, NC, USA)
-jeffB
Regular
 
Posts: 41
Joined: 26 Apr 2005, 17:46
Location: Durham, NC, USA

Postby Michael.Massing » 04 May 2006, 00:30

Michael.Massing
Hang-around
 
Posts: 5
Joined: 07 Apr 2006, 02:33

Making progress...

Postby jwr » 25 Sep 2006, 11:30

Hey, some news on the repair front. The right half of my failed TouchStream has been opened and boards desoldered. Several components have been replaced, but it seems that indeed the problem is with one of the Xilinx FPGAs.

Many thanks to pythagoras for the tips, they are extremely helpful.

Next things to try will be to read the programming off the JTAG vias for the FPGA, so that it can be replaced and reprogrammed. Hopefully Fingerworks did not protect the software from being read. If they did, I hope some good soul has the binary lying around on the hard drive somewhere.

I'll be posting new pictures of the processor board soon (probably tomorrow).
--J.
jwr
Familiar
 
Posts: 18
Joined: 09 Aug 2005, 11:06

Wow!

Postby goldfish » 27 Sep 2006, 06:24

Wow! I missed this thread. Good stuff, many thanks to Pythagoras for the excellent info.

Great to know in case my iGesture breaks down. Makes me wish I was an electrical engineer.

The FingerWorks technology really was innovative and superior--which of course was why the company was bought out. Regardless, the market for products which minimize RSI will only grow, and grow immensely.

Were "history" to restart, I think the market would definitely still be there. With a big marketing machine raising sales, and economies of scale lowering costs, the future for this technology would be very bright, and would benefit many more thousands--in addition to the thousands already helped.

Regardless, thanks again to Pythagoras for the repair tips, and as well to the creators of FW for the superb products.
goldfish
Familiar
 
Posts: 18
Joined: 05 Jun 2005, 07:45

Postby Michael.Massing » 04 Oct 2006, 06:43

As a quick update, I think I have narrowed my particular problem down to the ribbon cable. With this (apparent) knowledge, I've been taking steps to minimize cable strain and shock, both for home use and traveling.

A neoprene pad - custom cut from a spent wetsuit - was devised to both cushion and stabilize the ribbon connectors when I fold the kb for travel: keying surface out, since it is relatively indestructable. To my pleasant surprise, I discovered that deploying the pad under the keyboard during use at home made a significant improvement in "deadening" the previously imperceptible bounce of the metal tent, and made the keyboard as a whole much closer to the "zero-force" ideal.

I still have a bit of a potential issue with increasing the angle between the halves of the kb (I use the right half more perpendicular to my body's center line and closer to the body, to compensate for trackpad use), since that torques the connectors more than they were designed for, but so far so good.

Best to all,
M.
Michael.Massing
Hang-around
 
Posts: 5
Joined: 07 Apr 2006, 02:33

Pictures of the right half

Postby jwr » 08 Oct 2006, 14:47

For all those interested, I've posted pictures of the right half of the keyboard, at . You can see how the board with the CPU looks like :-)

It seems that indeed one of the Xilinx FPGAs has failed in my keyboard. We'll have a try at it with a programmer using the JTAG interface. I hope to high heaven that the code in the Xilinx does not have the protect flag set! If it does, there is little else I can do unless a kind soul sends me the code or makes it available on P2P somewhere.

More to come.
--J.
jwr
Familiar
 
Posts: 18
Joined: 09 Aug 2005, 11:06

Xilinx FPGA codes

Postby jwr » 10 Nov 2006, 15:33

--J.
jwr
Familiar
 
Posts: 18
Joined: 09 Aug 2005, 11:06

Re: Fruitful TouchStream Repair Tactics

Postby ahales » 24 Apr 2011, 22:48

ahales
Hang-around
 
Posts: 9
Joined: 24 Apr 2011, 22:14

Re: Fruitful TouchStream Repair Tactics

Postby TorbenGB » 25 Apr 2011, 13:25

User avatar
TorbenGB
Site Admin
 
Posts: 528
Joined: 26 Apr 2005, 00:07
Location: Vienna, Austria

Re: Fruitful TouchStream Repair Tactics

Postby ahales » 01 May 2011, 07:15

Thanks a lot man !!!
ahales
Hang-around
 
Posts: 9
Joined: 24 Apr 2011, 22:14

Re: Fruitful TouchStream Repair Tactics

Postby jwr » 02 May 2011, 11:16

…and let us all know if the repairs were successful! :-)
--J.
jwr
Familiar
 
Posts: 18
Joined: 09 Aug 2005, 11:06

Next

Return to Keyboards: TouchStream, MacNTouch, Digitouch, Mini

Who is online

Users browsing this forum: No registered users and 0 guests

cron