|
|
|
The following page was printed from RemoteCentral.com:
Topic: | Ipaq 3955 setup This thread has 14 replies. Displaying all posts. |
|
Post 1 made on Tuesday December 31, 2002 at 11:39 |
3ems Founding Member |
Joined: Posts: | February 2002 29 |
|
|
I just a the iPAQ 3955 was wondering what software you are using with it. Last night I setup my entire system with Nevo but I have the Pronto 2000 and like its setup instead. I also download the trial version of Padwin and will try it later today. I found the remote not as responsive as the pronto. I found that I have to pretty much point it at the equipment. The pronto signal bounces off any wall in the room and works. The color on the ipaq is a definate plus but I'm not satisfied with the signal strenth on the ipaq. Thanks Michael [Link: luciancarnival.com]
|
|
Post 2 made on Tuesday December 31, 2002 at 13:17 |
XRay Long Time Member |
Joined: Posts: | November 2002 45 |
|
|
Yeah, the IR range and directivity is not good. You'll need some kind of IR extender to make it work. I use a PDA-ir CF extender. It works great from anywhere in my 12'x35' room.
Unfortunately, the PDA-ir has some issue with the 3955. It's only compatible with 38xx and below. You might be able to find some other solution, though.
Regards. Jay.
|
|
Post 3 made on Tuesday December 31, 2002 at 16:24 |
Dave Houston RF Expert |
Joined: Posts: | October 2001 1,521 |
|
|
On 12/31/02 13:17.55, XRay said...
Unfortunately, the PDA-ir has some issue with the 3955. It's only compatible with 38xx and below. PDA-ir is not the source of the problem. The compatibility problem is in TV Remote Control software.
|
|
Post 4 made on Thursday January 2, 2003 at 07:51 |
Wilhelm Founding Member |
Joined: Posts: | November 2001 119 |
|
|
You can say what you want, but the problem is, that the IR-Extender doesn't comply to CF-Standard, otherwise it would work on every PDA that has this interface. That is the pupose of defining interfaces, you know. Wilhelm
|
|
Post 5 made on Thursday January 2, 2003 at 09:44 |
Dave Houston RF Expert |
Joined: Posts: | October 2001 1,521 |
|
|
On 01/02/03 07:51.41, Wilhelm said...
You can say what you want, but the problem is, that the IR-Extender doesn't comply to CF-Standard, otherwise it would work on every PDA that has this interface. Which would require totally different software and cost far more than anybody would be willing to pay, let alone someone like you who has whined continually that you should get a custom piece of software with lifetime upgrades for the $15 you paid for TV Remote. That is the pupose of defining interfaces, you know. Yes, I know well. How many interfaces or pieces of hardware have you actually designed? Have you actually read the CF specification? Do you have even a glimmer of a clue as to the costs involved? As soon as you incorporate an MCU you have to comply with FCC and CE regulations which add even more cost. We looked at that first and decided there would be no way to recover the development costs. The market is miniscule. It's proven to be less than 1/3 of what PDAwin predicted and their prediction was quite modest. With Philips planning PDA based software (they've already released a beta Pronto Lite for the PalmOS) and Harmony Remote planning a PDA version of their software, the market is likely to shrink even more. Eventually, Dell or someone will realize that all that's needed is a higher power IR emitter and decent learning software (e.g. TV Remote Control). The emitter would add about $0.06 to the cost of the PDA. At that time, the market (and need) for an add-on IR extender evaporates. If Dell succeeds with the Axim, the entire PDA market will likely shift to lower cost PDAs. They are likely to cut corners on things like the quality of the audio circuitry. You can say what you want but everything you have said indicates you don't have a clue.
|
|
Post 6 made on Thursday January 2, 2003 at 13:42 |
westmetro Founding Member |
Joined: Posts: | December 2001 63 |
|
|
When Intel released the XScale, they also changed the low-level method of talking to memory address lines and the system memory. On top of that, Compaq changed the memory map of the iPaq too. PocketPC 2002 deals with this via a HAL-style hardware layer but any software that talks directly to the hardware (like PDAWin) needs to be far more intelligent than they have been up to now.
The *real* problem is that the people at PDAWin seem to be unable to grasp this concept. There are probably less than 10 lines of assy code that need to be modified. What needs to happen is first of all run a simple test (two lines of code) to detect StrongArm or XScale processor, then set the memory map address for the expansion slot (3 lines of code) as appropo. Compaq has gone so far as to release sample code that accomplishes this along with a document that talks about specific code adjustments that have to be made for expansion pack and CF card communications to work corectly on the H39xx and H54xx series. But as I said PDAWin appears to be unable to deal with this.
This message was edited by westmetro on 01/02/03 13:49.58.
|
|
Post 7 made on Thursday January 2, 2003 at 14:30 |
Dave Houston RF Expert |
Joined: Posts: | October 2001 1,521 |
|
|
On 01/02/03 13:42.48, westmetro said...
When Intel released the XScale, they also changed the low-level method of talking to memory address lines and the system memory. On top of that, Compaq changed the memory map of the iPaq too. PocketPC 2002 deals with this via a HAL-style hardware layer but any software that talks directly to the hardware (like PDAWin) needs to be far more intelligent than they have been up to now. The problem predates the XScale processors. There doesn't appear to be any standard that is adhered to as to which CPU extended ports map to which physical pins in the CF slot. Even each StrongArm model iPAQ did it differently. PDAwin understands this while you obviously do not. They detect the difference between H36xx, H37xx, and H38xx iPAQs and set things up as is appropos but have not found documentation for the other PDAs and do not know how to detect other PDAs. I know for a fact that they've explored this because we sent them an e-740 before they became available in Slovakia. The *real* problem is that the people at PDAWin seem to be unable to grasp this concept. There are probably less than 10 lines of assy code that need to be modified. What needs to happen is first of all run a simple test (two lines of code) to detect StrongArm or XScale processor, then set the memory map address for the expansion slot (3 lines of code) as appropo. Compaq has gone so far as to release sample code that accomplishes this along with a document that talks about specific code adjustments that have to be made for expansion pack and CF card communications to work corectly on the H39xx and H54xx series. But as I said PDAWin appears to be unable to deal with this. How about a URL to this document? How about one for the Audiovox Maestro, the Toshiba e-740, the Dell Axim? I don't think you understand the issue.
|
|
Post 8 made on Thursday January 2, 2003 at 15:54 |
westmetro Founding Member |
Joined: Posts: | December 2001 63 |
|
|
|
Post 9 made on Thursday January 2, 2003 at 16:07 |
Dave Houston RF Expert |
Joined: Posts: | October 2001 1,521 |
|
|
On 01/02/03 15:54.24, westmetro said...
Sure I understand the issue. And the solution. It took me all of five minutes with google to find these PDFs (which have been available since around the first of September last year). Like I said, you don't understand the issue. You're not even in the ballpark. Aren't you the same guy who thought that ALL of the downloads on Handango represent a sale? This message was edited by Dave Houston on 01/02/03 16:13.55.
|
|
Post 10 made on Thursday January 2, 2003 at 16:14 |
westmetro Founding Member |
Joined: Posts: | December 2001 63 |
|
|
Nope, the core issue is one of customer service. So far PDAWin is silent on the issue, a lesson you might care to emulate.
Or by your 'tude are you begging for everyone to send their IR cards back for a refund?
|
|
Post 11 made on Thursday January 2, 2003 at 17:54 |
Dave Houston RF Expert |
Joined: Posts: | October 2001 1,521 |
|
|
On 01/02/03 16:14.30, westmetro said...
Nope, the core issue is one of customer service. So far PDAWin is silent on the issue, a lesson you might care to emulate. You have absolutely no idea what you are talking about. Or by your 'tude are you begging for everyone to send their IR cards back for a refund? On what basis? They do exactly what they are advertised to do. They work with the PDAs listed on both the EDV web page and on the PDAwin web page as many posters to this forum have attested. I'm not involved in the manufacturing or marketing but to the best of my knowledge there is no one who actually has one who is unhappy with it. In a few instances people ordered them without reading what PDAs they work with. Both EDV and Laser have offered refunds in those instances. A couple of those people have held on to them in the hope that PDAwin will find a way to support them on their particular PDA.
|
|
Post 12 made on Friday January 3, 2003 at 06:30 |
Wilhelm Founding Member |
Joined: Posts: | November 2001 119 |
|
|
On 01/02/03 09:44.28, Dave Houston said...
Which would require totally different software and cost far more than anybody would be willing to pay, let alone someone like you who has whined continually that you should get a custom piece of software with lifetime upgrades for the $15 you paid for TV Remote.
Hi Dave, seems I hit a nerve. Why would you otherwise begin to try to insult me with your answer? I have never complained about anything like you said, I even promoted TVRemote, because I think it's the best software so far. You developed a hardware for which you are neither willing to provide a proper interface nor device drivers and are furious defending this concept and even blaming it on the software application developers that this only works on some PDA's. The times of Peek and Poke are over! Yes, I know well. How many interfaces or pieces of hardware have you actually designed? Have you actually read the CF specification? More than you know. Fortunately I am not one of your potential customers, because I designed an internal transmitter which works perfectly for me and my needs. Probably you might be surprised how many people would pay for well designed hardware. But trying to make the "quick dollar" with this may not work on a community of users who share their experiences, sorry. The market is miniscule. Just out of curiosity: What do you define as miniscule? Eventually, Dell or someone will realize that all that's needed is a higher power IR emitter and decent learning software (e.g. TV Remote Control). Well obviously even you anticipate things could be developed a lot better. As I have seen you also keep insulting others who are criticizing your product. With this attitude it perhaps would be better for your business to keep quiet. Sincerly Wilhelm
|
|
Post 13 made on Friday January 3, 2003 at 08:26 |
Dave Houston RF Expert |
Joined: Posts: | October 2001 1,521 |
|
|
On 01/03/03 06:30.59, Wilhelm said...
I haven't seen anybody who actually has the product criticize it. I've seen one anonymous troll who does not have the product and has displayed no technical knowledge whatsoever make unfounded claims and then resort to threats when his claims were refuted. You, by your own admission, do not have any add-on product and have never seen the product, never-the-less feel its your right to make false statements about it.
|
|
OP | Post 14 made on Friday January 3, 2003 at 11:39 |
3ems Founding Member |
Joined: Posts: | February 2002 29 |
|
|
Can we PLEASE get back on track.
|
|
Post 15 made on Friday January 3, 2003 at 13:06 |
Dave Houston RF Expert |
Joined: Posts: | October 2001 1,521 |
|
|
On 01/03/03 11:39.06, 3ems said...
Can we PLEASE get back on track. To the best of my knowledge there is no third party software that works with the Nevo hardware. The PDAwin software will work with the IrDA emitter but you will find the range disappointing. PDAwin has not found a way to support the PDA-ir CF extender on the H39xx or later iPAQs. The only other choice I know of at this time is TotalRemote. I'm not familiar with their software but believe they have a demo version you can try using the IrDA emitter. I do not think their software will work with the Nevo hardware either but their little emitter should work with your iPAQ.
|
|
|
Before you can reply to a message... |
You must first register for a Remote Central user account - it's fast and free! Or, if you already have an account, please login now. |
Please read the following: Unsolicited commercial advertisements are absolutely not permitted on this forum. Other private buy & sell messages should be posted to our Marketplace. For information on how to advertise your service or product click here. Remote Central reserves the right to remove or modify any post that is deemed inappropriate.
|
|