VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- Springboard Modules (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=10)
-- Glenayre/Handspring Possible Coverup (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=8300)

Why is it that the Activelink is only available bundled with a new Visor? What about us poor shmoes that bought early with no modules (to speak of)? What are they hiding? I can't imagine why they wouldn't want to tap the existing market of Visor owners at the same time as bundling them with new visors. I for one am very very upset about this. Am I the only one? Are you guys at Visor Central going to get to the bottom of this? Thanks!

You can read all about the issue in this thread:
http://discussion.visorcentral.com/...p?threadid=7899

The upshot is that the glenayre pager module emits so much RF that it can negatively affect the visor's operation. Therefore, the @ccesslink module is only available bundled with a specially shielded version of the visor. Note that neither the infomitt 1-way pager or the recently announced visorphone require this extra shielding (no news about the minstrel S module yet, but it may only be a glenayre issue).

My question is:

What's the difference between a shield in the visor and a shield on the Activelink? I can't imagine that the entire interior of the Activelink version visor is shielded(if that really IS the reason why you have to get the bundled visor). I'd bet that it only shields around the springboard slot. Why can't the SB have this built in?

There's gotta be more to it than just the shielding issue...

From the other thread:

I spoke earlier today to Allen Bush, a Handspring spokesman, about the @ctivelink interference issue.

When the standard version of the Visor is used with the @ctivelink
module, the @ctivelink may not perform optimally and could emit higher than normal RF interference that may disturb the @ctivelink's transmission. The module is completely functional in all standard Visor models, however, the Visor and @ctivelink may not perform optimally when used together and, it is likely, a user may not even notice that the issue exists at all.

We have not received information regarding how this issue came about; it might be a one-time issue since no other wireless modules appear to have this problem.

After realizing this issue, Handspring, "as a good development partner," decided to make a special version of the Visor to meet Glenayre's needs.

Today this Visor model is only bundled with the @ctivelink; it is unknown and cannot be determined whether it will replace the existing Visor line or be built in to future products. Handspring cannot comment on future products.

I have an interview scheduled with Glenayre's CEO next week, and will have a chance to ask him why the decision was made not to redesign the module to work with existing Visors (if it is technically possible).

Handspring acknowledged that a major reason why the Visor was optimized rather the @ctivelink stems from the fact that Glenayre, from a business standpoint, has decided to sell the bundle in different sales channels in order to appeal to new type of customer. This decision was made due to large commitments of the @ctivelink which will appeal to these new users who do not currently have Visor units. A bundle with an optimized Visor made sense to quickly get the product to the market to meet the business needs of Glenayre and its partners.

However, it doesn't make much sense for the existing Visor owners.

If Glenayre decides to release the @ctivelink as a standalone module
(Handspring indicates they may sometime into the future and the decision lies with Glenayre), users who are unhappy with the performance of their @ctivelink (due to the interference) may be able to trade-in their Visor for an optimized version. We have no information about when or how this trade in would work.

I will have more information next Wednesday, including Glenayre's take
On the issue) after the PCIA convention.

__________________
<B>Marcus Adolfsson</B>
Editor

Handspring's Customer Support site now has a page on the @ctiveLink. It basically states most of what marcus' post above does.

__________________

God bless America, my home sweet home...