There are several files that I routinely transfer to another device
using Bluetooth.

Is there a way to automate the process for the file? Something like a
Batch file that would automate the activation and transfer of the file?

If there is what commands would you use to activate the Bluetooth routine?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 9/24/2023 8:36 AM, knuttle wrote:

There are several files that I routinely transfer to another device using Bluetooth.

Is there a way to automate the process for the file?   Something like a Batch file that would automate the activation and transfer of the file?

If there is what commands would you use to activate the Bluetooth routine?

Research

fsquirt.exe

fsquirt -send # Tool offers no help. Someone "guessed" at the option :-)
fsquirt -receive # Possibly a file transfer protocol, making use of SPP or RFCOMM

which is the root of point to point transfer.

Requires pairing and so forth. Requires the
receiver "being in the mood for it", as it were.

It is not like file sharing, exactly.

*******

In theory, mind you, it is possible to have an IP stack
on top of Bluetooth (via PAN), and file sharing would then work.

And I just got it working :-) So something has changed since
the last experiment (two years ago for broken PAN attempt).

The next puzzler ? What's with the transfer rate ?

2:02 for 20,375,552 or 167,012 bytes/sec

FSquirt for the same file took:

3:39 for 20,375,552 or 97,026 bytes/sec

The network cable was unplugged on the Test Machine for the test,
so it couldn't cheat.

The test was done with Asus Bluetooth 4 adapters. My BT 5 hardware
is more of a nuisance.

Part of the reason it worked, is I did a clean install of Win10 Pro 22H2 for the Test Machine. And the other end was my Daily Driver Win11 Home 22H2.

The RFCOMM protocol originally showed up on only one end of the test.
Device Manager showed it, on the clean install machine. It was only
after fiddling with it, and "making a Direct Connection", that, eventually, Device Manager admitted it had been flirting with RFCOMM on the Win11 machine. This means the opportunity to do this experiment, is "not discoverable", since you can easily be in a state, where neither Device Manager shows the RFCOMM row.

[Picture]

https://i.postimg.cc/G2sGJq7g/Windows-BT-PAN-finally-works.gif

By using addresses within the LAN subnet mask of the other hardware,
I could do some pings. Doing a ping from one BT to the other, was
something like 27 milliseconds. Whereas normal Ethernet GbE ping time
is around 1 millisecond or so.

Sadly, none of this is particularly useful. You are unlikely
to be doing any of this stuff. Lashing this up is silly and
just a bar bet. I could copy from //LEVERAGE/LEVShare if I wanted,
to make a command line of it, assuming (hah!) the networking was alive for it.

FSquirt is the closed thing to the right tool for the job,
except the interface sucks. No scripting.

I think someone could write some code for this. It might
be some obscure Powershell, or it might take some C# and .NET
for somebody. You know the drill by now.

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 9/24/2023 8:36 AM, knuttle wrote:

There are several files that I routinely transfer to another device using Bluetooth.

Is there a way to automate the process for the file?   Something like a Batch file that would automate the activation and transfer of the file?

If there is what commands would you use to activate the Bluetooth routine?

One other background point.

The "fsquirt.exe" thing you will see running in Task Manager,
that is a response to using "Send To --> Bluetooth" in
a context menu.

It's basically a kind of FTP transfer. You start the FTP server
on the receiving end running, so the receiver is ready for it.
The FTP server is not left "running" all the time, and is
only running until the transfer is completed.

The receiving end is started graphically, by accessing the Bluetooth
icon in the tray area, and selecting a Receive function in there.

And as far as I know, none of this works without Pairing.

There is also a tick box for Authentication, but I don't
know the logic tree for that.

Using fsquirt -receive (on the Receiving end) and using
fsquirt -send (On the Transmitting end), are the command
line equivalents, of the GUI functions described above.

*******

Other than that, maybe some kind of syncing software
could be used for passing a file on a regular basis.

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)