Wifi with raspberry Pi 4

[billko]

---

@taestygecko wrote:

I will have to try this out and see if it works or not

---

I forgot all about the Hobbyist Toolkit forum!!!

[taestygecko]

Yeah this is the page I have studied and have been trying to work from. I will give another RPI a go

[billko]

Did you try the Digilent Maker Hub?

[rolfk]

Last time I checked the Linx chroot environment did not exist in its own partition but simply in a subdirectory tree on the main filesystem. Not even sure if chroot could operate with separate partiions. The idea is that the chroot environment redirects specific configured device entries in its own filesystem to according device entries in the host OS. What is configured to be redirected works as if it is present in the chroot environment rather than in the host, what is not configured to be allowed to go through simply doesn't seem to exist in the chroot. That's for a large part how chroot isolates the guest OS from the host. Only things explicitly allowed to pass through can be accessed in the guest, everything else is simply not there. This can and often does break when something in the guest wants to do direct hardware access rather than going through device inodes.

[billko]

Here's something from the LINX makerhub FAQ:

When adding a new target in my LabVIEW project, my BBB/RPi2 isn't detected. What's wrong?

---

The LabVIEW project uses mDNS to detect available BBB/RPi2 targets on the network. Some network routers don't correctly forward mDNS traffic which can make targets undetectable in the LabVIEW traffic. This happens most commonly when the development PC is connected to the network via ethernet and the target is connected to the network via Wifi, or vice versa. When this happens you will need to add the target to your project by specifying the IP address.

[taestygecko]

Does it matter if the RPI OS is 32Bit or 64Bit

[billko]

---

@taestygecko wrote:

Does it matter if the RPI OS is 32Bit or 64Bit

---

I don't know the answer to this, unfortunately.

[rolfk]

@taestygecko wrote:

Does it matter if the RPI OS is 32Bit or 64Bit.

Why would that be? LabVIEW installs it’s own Linux based OS in a chroot environment to run in. This is a lightweight VM and isolates it entirely from the host OS, except communication through explicitly configured device entries in the filesystem and network communication.

[taestygecko]

Ok it has taken me some time, as I needed to find a Raspberry Pi that worked as well as figuring out how to set up the router...

I have got it all working and functioning through the way NI has instructed me and I have now got labVIEW controlling my RPI.

So now I can get back to my original post which is "can I remove the Ethernet cable form my target and the router and have labVIEW command my RPI vi the targets Wi-Fi?"

[wiebe@CARYA]

If you have a connection, it shouldn't matter to LabVIEW (neither the PC not the RPi code) if the connection is a using a cable or WIFI.