NI Linux Real-Time Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

[SOLVED] myRIO-1950 - Wifi dongle driver compilation

It worked.

I installed and replaced the old non working rtl8192cu modules.

I then had to blacklist rtlwifi that was blocking rtl8192cu from working properly

(At this point, wlan0 was finally discovered by the OS)

I then I had to build up a wpa_supplicant.conf  with

wpa_supplicant -B -iwlan0 -c/etc/wpa_supplicant.conf -Dwext && dhclient wlan0

and then ifconfig wlan0 up and got internet on the myRIO

Thank you very much for your help

0 Kudos
Message 11 of 40
(2,369 Views)

Hey, glad to see you ignored my nay-saying and got it working anyway

0 Kudos
Message 12 of 40
(2,369 Views)

Hey am trying to do what you did, i have the same problem of installing the edimax  drivers on the NI myrio 1950..please am requesting you to take me through the entire procedure, i downloaded the drivers for the edimax..but i have issues compiling them

Thanks

0 Kudos
Message 13 of 40
(2,369 Views)

What issues are you seeing? What steps did you do up to this point?

0 Kudos
Message 14 of 40
(2,369 Views)

I tried to follow the tutorial you made but got stuck on stage 3of running the makefile.

On entering: source/ use/local/natinst/tools/versioning_utils.sh

I get this response: no such file or directory

And still, what does source refer to in that line

0 Kudos
Message 15 of 40
(2,369 Views)

First, let's check that you're using a version of the software that supports the functionality that you need. Post the result of running "uname -a"

Secondly, it should be "source[space]/usr/local/natinst/tools/versioning_utils.sh". " Source " basically tells the shell to use a shell script to modify the environment of the currently running shell (set environment variables, define new functions, etc)

0 Kudos
Message 16 of 40
(2,369 Views)

The result of uname -a

admin@NI-myRIO-1950-03047863:/rtl8192CU_linux_v2.0.939.20100726# uname -a

Linux NI-myRIO-1950-03047863 3.2.35-rt52-1.0.0f1 #1 SMP PREEMPT RT Wed Jun 12 09:57:26 CDT 2013 armv7l GNU/Linux

Result of source /usr/local/natinst/tools/versioning_utils.sh

admin@NI-myRIO-1950-03047863:/rtl8192CU_linux_v2.0.939.20100726# source /usr/local/natinst/tools/versioning_utils.sh

-bash: /usr/local/natinst/tools/versioning_utils.sh: No such file or directory

0 Kudos
Message 17 of 40
(2,369 Views)

You do not have the needed version of the OS that has support for the needed functionality. That script does not exist in the 13.0 version of the OS.

You can update to a 14.0+ RIO on your development machine, format and reinstall with the newer RIO (choose a Custom Installation), and that will give you an OS with the needed functionality.

0 Kudos
Message 18 of 40
(2,369 Views)

Hi, I have a question related with this thread.

I am trying to use USB wifi dongle with Linux RT device (myRIO-1950).

It seems that you could communicate with myRIO through the dongle,

I want to ask you some question.

 

- Is the device able to be recognized on MAX as network device like myRIO-1900?

- Do you have some following files?

+- dmesg log

+- boot log

+- lsmod log

we want to check by reading these files whether our device is working correctly.

 

Best,

0 Kudos
Message 19 of 40
(2,369 Views)

Hi,

  • When you connect through a Wifi connection (ad-hoc or internet router) myRIO1950 get a DNS Name and MAX is able to see the device as the myRIO1900. You should always use the DNS Name and never the IP address to access the myRIO through Wifi though (it can be variable).
  • I got an output for dmesg log not for the two other commands. (See attached file)
  • You can also check if your device is working by simply ping the host router/computer or google
    • ping google.com
    • ping the local router

~# ping google.com

PING google.com (216.58.209.238): 56 data bytes

64 bytes from 216.58.209.238: seq=0 ttl=56 time=40.002 ms

64 bytes from 216.58.209.238: seq=1 ttl=56 time=33.925 ms

64 bytes from 216.58.209.238: seq=2 ttl=56 time=39.490 ms

~# ping 192.168.0.1

PING 192.168.0.1 (192.168.0.1): 56 data bytes

64 bytes from 192.168.0.1: seq=0 ttl=64 time=68.425 ms

64 bytes from 192.168.0.1: seq=1 ttl=64 time=9.296 ms

64 bytes from 192.168.0.1: seq=2 ttl=64 time=8.793 ms

0 Kudos
Message 20 of 40
(2,369 Views)