开云体育

OK, getting off subject after I said it is too early to start talking abut software....

However, I do have reason to ask about configuring the I/O pins.
I am still thinking about hooking up HC-05 to MY nanoVNA which does not have dedicated P3 pins.
To do that I need some room to add wires directly to the CPU and if such room is not available near CPU pins 30/31 I'll will be looking for other pins.

BTW
I agree that EIA can be intimidating , but after all it is all about options, no magic involved.

I am not sure I share concerns about I/O speed, my first encounter with the EIA was @ whopping 110 bauds.

Years ago I got professionally involved communicating with a device of unknown options - so one of my "for hire " C code was to
run thru all of the options until intelligent / readable response was received

..and if the communication is too slow , then there is more time for cup of coffee...

Personally I wouldn't risk trying to solder wires directly to the CPU. It looks like you have one of the older units (not necessarily a clone). I believe the P3 connector was added on the 3.4 revision of the PCB. I have the 3.3 and it doesn't have the port either. The version number is printed underneath the battery on mine. You are probably better off getting the H4 unit which will make life a lot easier to add the bluetooth module to it as there will be more room to work with as well.

You do not have to talk me out of soldering to the CPU.
I am really not trilled to do that anyway.
As far as model number - the battery seem to be "superguled" with sticky tape ( ?) so I did no attempt to
remove it. But the model # is irrelevant at this point anyway.

Being a coding geek I just got this "brilliant " idea.
The nanoVNA communicate with PC using USB - we have working nanoVNA-saver -
so why not
add another USB device - USB works in parallel - sort off - that device being ordinarily
Bluetooth adapter ( USB to Bluetooth )
and add this adapter as another means of communication

Or even better - replace the USB cable connection with such external ( no soldering to CPU ) USB - Bluetooth adapter .
All done in software...

PS anybody ported Python to C /C++ ?

On 7/22/21 9:39 AM, Anne Ranch wrote:

You do not have to talk me out of soldering to the CPU.
I am really not trilled to do that anyway.
As far as model number - the battery seem to be "superguled" with sticky tape ( ?) so I did no attempt to
remove it. But the model # is irrelevant at this point anyway.

Being a coding geek I just got this "brilliant " idea.
The nanoVNA communicate with PC using USB - we have working nanoVNA-saver -
so why not
add another USB device - USB works in parallel - sort off - that device being ordinarily
Bluetooth adapter ( USB to Bluetooth )
and add this adapter as another means of communication

Or even better - replace the USB cable connection with such external ( no soldering to CPU ) USB - Bluetooth adapter .
All done in software...

PS anybody ported Python to C /C++ ?

If you're going to do that, why not just slap a RPi on the back of the NanoVNA.? Then you can use any wireless interface available on the Pi - I've used VNC over WiFi to run NanoVNA-saver on the Pi talking to the NanoVNA.? $50 and a battery for the Pi and you're done.


I have done some limited recoding of algorithms originally in Python to C, but one comes up against the question of "why?"? - For all the things one might do with a NanoVNA, none are particularly compute intensive, so as long as Python runs on your chosen platform, there's not much need to move to C to get better performance.

If you wanted to try and write a C "interface handler", I'd just start with something like nanovna.py (which is basically a command line interface to the nanovna, with more sophistication than the native USB serial interface) and write the code in C to do the same things as you need.

Another possibility is to use a Pi (or something cheaper/smaller) to just be a RFC2217 server for the USB/Serial port, and then run whatever you want, with the "serial" connection over the wireless interface of choice.

On Thu, Jul 22, 2021 at 09:55 AM, Jim Lux wrote:

Then you can use any wireless interface available on the Pi

Funny you posted that.
I am up to my eyeballs in playing with Bluetooth and just found out that NOBODY can tell me what is the passcodde to get into RPi.
My OS identifies two HC_05 and I can get in one with 1234 passcode.

It does identify my RPi with name, but I do not know the passcode .
Tried 0000 and it did not work.

Well I got RPi few inches next to nanoVNA but I think just replacing the USB cable with Bluetooth would be more KISS.
I think if you "warm-up / /charge" the nanoVNA first then replace the cable with Bluetooth would be slick.

Raspberry Pi wants to be a Bluetooth host, not a Bluetooth client.

I’m sure there are ways to do it the other way around, but it doesn’t work that way out of the box.

73, Willie N1JBJ

It does identify my RPi with name, but I do not know the passcode .

I am still learning about Bluetooth - especially how it is initialized on power-up.
Now I am comparing behavior of HC-05 , got two of them powered up, and RPi as far as OS goes accessing them.

That is the key - how OS responds to available commands.
Long time ago I started with Bluetooth by studding "BlueZ" library and using some software examples.
Then I learn that Linux uses "BlueZ" as standard to work with Bluetooth technology.
From there I know , for sure, that Bluetooth device has an option "to be discoverable" which means the device will
allow / respond to inquiry passed over the RF, NOT via physical I/O connection .
Now this all sounds to convoluted , but if one keeps in mind that communication is BETWEEN two points , it is not that hard to visualize.

Ok, end of sermon.
These are the facts
1. OS , irregardless what mechanism is used , "finds" all nearby Bluetooth devices and identifies them by name
2. I have "boom box", two HC-05 , my FT857 CAT and ONE "ARM" , and which is the name I have given to my RPi
when I had setup to work with it directly.
3. My RPi is now powered only, no mouse , no keyboard , no monitor. But I forgot the IP and having a heck of a time
identified it so I can SSH to it when I need it.

From all this - I am having a hard time accepting ( because how it is setup internally as client /server ) that I cannot access the RPi same as the other Bluetooth devices and pass a code to the it - if I know what it is.

I guess I need to find the IP address and SSH to the RPi and work on the Bluetooth from RPi direction .

73 Vaclav AA7EJ

The "Talking BT to a Pi" thing is out of my experience, so I can't help you there. Never heard of anyone doing "ssh to Pi over BT", and I'm not even sure that is a thing, so I'll stop. 8*)

Finding the Pi on the LAN is pretty easy, as I believe you have Linux.

nmap -sn 192.168.0.* | grep Raspberry -B2

[Use your LAN numbers above. You might have to install nmap, but that appears to be widely available.]

Alternately, if it's on the LAN and you have a Linux or macOS machine, and (I think you said) your device is named "ARM", you should be able to just:

ssh pi@...
though depending on how you changed the name, the default:
ssh pi@...
might (still) work.

73, Willie N1JBJ

After few detours I can SSH to my RPi.
Now I have to re-learn now to navigate RPi using commands. Interesting how one forgets stuff after not using RPi for over a year.
The Bluetooth "manager" on Ubuntu is pretty flaky, hope upgraded / updated OS on RPi will work better.
I am sorry I took this detour discussing my RPi bluez - pun not intended.

IMHO this is the most intelligent , no nonsense article about "how to Bluetooth" .
Do not let "raspberry " distract you and SKIP all the GUI stuff , go down to command line.



PS
It is little vague describing "pairing " and its result as "connected" - then it goes on to how to connect.
( My attempt to "connect" failed - assuming because to do not have no serial I/O hooked up.
I wonder if I physically connect the TX /RX between the HC-05's - sort of "loopback " ? )
Somebody in this thread mention term "coupled " as a result of pairing. Seems more fitting.

On 7/23/2021 6:11 PM, Anne Ranch wrote:

IMHO this is the most intelligent , no nonsense article about "how to Bluetooth" .
Do not let "raspberry " distract you and SKIP all the GUI stuff , go down to command line.



PS
It is little vague describing "pairing " and its result as "connected" - then it goes on to how to connect.
( My attempt to "connect" failed - assuming because to do not have no serial I/O hooked up.
I wonder if I physically connect the TX /RX between the HC-05's - sort of "loopback " ? )
Somebody in this thread mention term "coupled " as a result of pairing. Seems more fitting.

Anne, you can have a remote desktop experience if you prefer using either RealVNC or NoMachine

<>

<>

RealVNC works with Raspberry Pi if you enable it using Raspberry Pi Configuration app then you can just connect to it via IP Address, so long as the Pi is on the same subnet. You can also use it outside of your LAN via creating an account and registering the Pi on your account.

NoMachine has a Raspberry Pi downloads on there website. I've not tried using NoMachine outside of my LAN, so not sure how simple it is to use that way.



--
All the Best & 7 3s
Dale Miller, KC2CBD
Cookeville, Tennessee
Putnam County TN ARES
Emergency Coordinator
Vice President Cookeville Repeater Association
Ham Operator since 1997 (Extra)

stpatrick2@...
Registered Linux User: #317401
Linux since June 2003
Registered Ubuntu User #26423

--

Looks as NoMachine would allow access to RPI desktop , if I can get it installed.... wants to install package but does not tell you
have to change folder....
However, I do not want to overstate my welcome here , I made a reference to RPi as BTW there is another way to skin a cat.
Let's not turn this into RPi discussion.