VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- How To / Troubleshooting (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=2)
-- beam troubleshooting (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=20612)

beam troubleshooting

My beam is weak at best. I substantiated that my VDX is the culprit, I was in a co-worker's office and between his VDX, my VDX and another guy's M505 I figured out that I can't receive for squat. I beam okay, not well -- just okay.

I tinkered w/ all the hacks (afterburn, easylock, mcphling, find) and it was the same all around.

Looking for a little troubleshooting assistance before I go swap out the unit for a new one. I have the Fry's (I know, I know) 2 year performance gaurantee and I'm only 3 months into it.

/s/MTM

I've had occasional beam receive problems with a few apps. In all cases, it seemed that having the app under/overclocked with Afterburner was causing the problem. After restoring the speed setting of the app to Default, everything went ok.

__________________
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GS d-(+) s: a C++ UX++++V++S++ P+>+++ L>+++ E+>++ W++ N++(+++) o? K? w !O !M V-- PS PE Y+ PGP++ t++ 5++ X++ R+ tv++ b++(+++) DI++++ D+ G++ e+++>++++ h--- r+++ y?
-----END GEEK CODE BLOCK-----

Color me a bit confused. How could you have an app overclocked if it has not been received? Are you talking about tweaking afterburn and it helping beam transmit? Receive? Both?

I can handle afterburn messing up the works and tinkered (disabled it, using hackmaster) w/ it and I could still not receive.

I bought a factory refurb @ Fry's 3 months ago w/ the 2 year instant exchange warranty figuring that I could end up w/ a good one after the 2 year deal expires. By that time, VDX will probably cost about $29 and be outdated anyway.

I just did another sync and am going to go swap. Should only wait a couple of hours in the Fry's line.

/s/MTM

ahh, didn't realize you were referring to beaming apps. Most of the time i'm beaming stuff like calendar or phone book entries, which is when I usually discover i have a problem.

I've not spent much time trying to diagnose or troubleshoot the problem since restoring the app speed back to default usually fixes it. have you tried checking the Adjust Ticks box?

__________________
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GS d-(+) s: a C++ UX++++V++S++ P+>+++ L>+++ E+>++ W++ N++(+++) o? K? w !O !M V-- PS PE Y+ PGP++ t++ 5++ X++ R+ tv++ b++(+++) DI++++ D+ G++ e+++>++++ h--- r+++ y?
-----END GEEK CODE BLOCK-----

No, I have not done any tick adjusting. Just disabled the hack is about the extent. Beaming is buggered up w/ or w/o afterburn.

When I beam, it will xmit a bit and stop. If I move the unit it picks the process back up and beams for a while then will stop and I move the unit it starts and ...

If whatever is being beamed is small, it goes without problem.

Receive is another story altogether. It just don't work.

Now that I think about it, problems began when I made a Handsrping dude jump around inside a boihazard symbol. It works okay as my easylock graphic but the problems really got bad when I started using that symbol as an avetar here. Hmmmm

quote:

---

Originally posted by mdatl
Just disabled the hack is about the extent. Beaming is buggered up w/ or w/o afterburn.

---

__________________

God bless America, my home sweet home...

I just had your problem the other day. For me nothing to do with hacks. Here goes:

Are you beaming two handhelds lying flat on a table? When I tried that, they would start but stop. Then, I put little post-it pads under both, then tried beaming, and it worked fine. Try it out.

__________________
-Bernie

"One word sums up probably the responsibility of any vice president, and that one word is 'to be prepared'.
-Dan Quayle

Yup, tried it. No workie. That's what helped me figure out that a little movement would revive the transmit beam link.