Zori

Has anyone solve the Bluetooth transfer limit? I have read others having the same problem as I do when trying to send files that are over 40kb from PC to x50v.

I did a search but can't find any solutions, does anyone know hot to get pass that?

zim2dive

I am seeing similar issues, but had not tried smaller files to see what would be successful.

http://www.aximsite.com/boards/showthread.php?t=66562

perhaps I'll give that a shot and see.

Mike

Zaventh

That's strange. Is it limited to just the x50v? I have an x50 and I transfer 2-10mb files frequently via Bluetooth.

zim2dive

I show

BT-PPC Version 1.5.0 Build 2600, with module versions 1.5.0.2 under the "advanced" box.

Heh, and I am finally struck by the Insufficent memory bug when trying to turn on BT.

Mike

transcout

I can transfer ~8mb mp3 files easily on my x30
BT-PPC Version 1.5.0 Build 0801, module versions 1.5.0.801

krogh

After a bunch of testing between my Axim X50 and a Mac and a PC, I've found that BlueTooth 'File Transfers' work fine always from either the Mac or the PC. Unfortunately, they need to be initiated from the computer and not the Axim. BlueTooth OBEX pushes or pulls only work for small files (<100K or so). The PC doesn't seem to support these and the Mac does this by default. These sorts of transfers can be initiated from either the Mac or the Axim.

Since the BlueTooth File Transfer protocol is the only reliable method and can only be initiated from the computer, I've abandon this and switch to using only WiFi for moving files.

To initiate a File Transfer on the Mac, you need to 'browse' the Axim and then either send or get a file. Other approaches use the OBEX push/pull protocol.

Anyone have different observations?

zim2dive

Originally Posted by krogh

After a bunch of testing between my Axim X50 and a Mac and a PC, I've found that BlueTooth 'File Transfers' work fine always from either the Mac or the PC. Unfortunately, they need to be initiated from the computer and not the Axim. BlueTooth OBEX pushes or pulls only work for small files (<100K or so). The PC doesn't seem to support these and the Mac does this by default. These sorts of transfers can be initiated from either the Mac or the Axim. Since the BlueTooth File Transfer protocol is the only reliable method and can only be initiated from the computer, I've abandon this and switch to using only WiFi for moving files. To initiate a File Transfer on the Mac, you need to 'browse' the Axim and then either send or get a file. Other approaches use the OBEX push/pull protocol. Anyone have different observations?

a) if this is somehow an x50v issue... then you may have an advantage over us :)

b) I did try to "push" a file from my Mac to the Axim, and that failed in the same fashion as the "get" that I initiated from the Axim (and left the Mac BT file xfer process very hung).

Cheers,
Mike

Zaventh

Originally Posted by zim2dive

Ooooh... excellent catch!!!! Yes, looking over all the threads I can find, everyone seems to have an x50v. How can we make this a sticky so we can combine the threads into one? I wonder if there are different drivers from the x50 to x50v... I show BT-PPC Version 1.5.0 Build 2600, with module versions 1.5.0.2 under the "advanced" box. Heh, and I am finally struck by the Insufficent memory bug when trying to turn on BT. Mike

Are you trying to push files?

My Axim x50 has BT-PPC Version 1.5.0 Build 2600
Module versions are 1.5.0.2600

zim2dive

Originally Posted by Zaventh

Are you trying to push files? My Axim x50 has BT-PPC Version 1.5.0 Build 2600 Module versions are 1.5.0.2600

My problem is in the xfer of a file TO the Axim. The xfer fails regardless of where I initiate the xfer.

Most/all of the problems reported seem to be in the TO-Axim direction.

Copying FROM the axim seems to work just dandy.

Mike

Zaventh

Originally Posted by zim2dive

My problem is in the xfer of a file TO the Axim. The xfer fails regardless of where I initiate the xfer. Most/all of the problems reported seem to be in the TO-Axim direction. Copying FROM the axim seems to work just dandy. Mike

Yeah, definately works for me no matter what way I do it. :)

Did you note the difference in the module versions?

krogh

If you're still having problems, complain to Dell for a replacement. That's what I had to do with my first X50. Although, it wasn't easy. I had to wait for a while to get a support person overseas. Then had to do the rounds with her as she tried to convince me that the device didn't have a problem. Finally, I told her that I do network support and none of my company's other BT devices had this sort of problem. Finally, they sent me a replacement and it works. Unfortunately, the only thing she (and the follow up person) seemed to care about was how I'd rate the call.

Good luck.

zim2dive

Originally Posted by krogh

If you're still having problems, complain to Dell for a replacement. That's what I had to do with my first X50. Although, it wasn't easy. I had to wait for a while to get a support person overseas. Then had to do the rounds with her as she tried to convince me that the device didn't have a problem. Finally, I told her that I do network support and none of my company's other BT devices had this sort of problem. Finally, they sent me a replacement and it works. Unfortunately, the only thing she (and the follow up person) seemed to care about was how I'd rate the call. Good luck.

Ok, as it was I found I could xfer a 116k file, but dumped on a 3M file. Size does matter :)

Did a hard reset, and the large file still bombs.

Will follow up with tech support.

Very worrisome, the idea of a unit that can do a small file but not a larger one.. that is not the kind of hardware failure that makes me feel good about a replacement (I've done embedded HW design for 11 years) being reliably better. Much better when something is completely broken...

Mike

zim2dive

Email back from Dell support this AM which authorized an "exchange"... which I take it to mean they are shipping me a new one, and then I ship back the 1st one... I think ;) ... at least that's what I infer, but did not find clearly explained :)

Still bothers me to think of this as a HW problem... sniff sniff... it *smells* like driver, not HW... too much _works_.. its more like a buffer allocation/overflow problem for incoming files. When HW is broken, well, it more often just doesn't work at all ;)

Sigh... still waiting for the raincheck on the Best Buy 1G SD card before I committed to the unit 100% anyway, but geez, I'm glad I didn't wait to test this for 3 months....

Mike

zim2dive

To their credit Dell overnighted me a replacement... but of course I had to charge the battery, taking an extra half day :)

This device has the same problem with my laptop.

Out of the box... nothing added, no mem cards, nothing configured (other than the screen alignment taps)... file xfer from my laptop from at 415.2k... approx the same place that it died before.

Since I had both Axims (original and replacement), I thought I'd test that.

I discovered one seemingly very ugly default.. when I tried to "send" a file from my original Axim (loaded up with trial version of everything under the sun), the send menu decided to LIST EVERY @#%@#% FILE on the device in one flat AND VERY LENGTHY listing.... man that took a while to finish listing itself... egads.

I was able to xfer files from Axim to Axim without a prohlem. Paired and not paired.

So it seems like the problem is Axim to non-Axim now, with plenty of other reports of partial file timeouts. Dell, is anyone listening on your end for some cross-vendor testing????

Mike

zim2dive

In case there are any enterprising folks with the problem that are willing to hack around, I found this set of OBEX docs on msdn

http://msdn.microsoft.com/library/de...rysettings.asp

I don't immediately see any setting to tweak, but maybe someone else will.

Mike