[Maurice Calvert]

Hi Anders,
thanks for taking the time to followup, indeed I was a bit confused initially.
In the meantime I’ve figured out how to communicate between a .Net program running on the brick with your firmware and another .Net program running on my PC, over wifi. Two-way communication is possible, initiated on either side, simply by setting up sockets to listen for the other program.

Amazing job you’ve done here, congratulations and Thanks.
Maurice

[Maurice Calvert]

I have a WiFi stick now and things are better.
I boot up the monobrick firmware off the SD card, wifi works on 192.168.1.115 and when I connect with winscp I see the wifi startup in the startuplog:

Starting process: killall with arguments: wpa_supplicant
killall: wpa_supplicant: no process killed
Starting process: ip with arguments: link show wlan0
Starting process: ip with arguments: link show wlan0
Starting process: ip with arguments: link show wlan0
Starting process: rm with arguments: /mnt/bootpar/wpa_supplicant.conf
Starting process: /home/root/lejos/bin/startwlan
Start WiFi…
Check configuration…
hostname is EV3
searching for wlan
wpa_state=DISCONNECTED
Searching for AP…
wpa_state=ASSOCIATING
Searching for AP…
wpa_state=COMPLETED
bssid=84:26:15:5c:b1:49
ssid=CalvertWireless
Request IP address…
udhcpc (v1.13.2) started
Sending discover…
Sending select for 192.168.1.115…
Lease of 192.168.1.115 obtained, lease time 86400
adding dns 192.168.1.1
Starting process: ip with arguments: link show wlan0

When I try and connect from VS2015

       _EV3 = New Brick(Of Sensor, Sensor, Sensor, Sensor)("wifi")
        _EV3.Connection.Open()

I get a ConnectionException with innerexception of “Failed to find EV3”

If you have any ideas I’d be most grateful 🙂

[Maurice Calvert]

Thanks for the follow-up.

My local network is 192.168.1.* so even if I set the EV3 IP address to 10.0.1.1 I can’t ping it because 10.*.*.* isn’t my local network.

When I set the Ev3 to 192.168.1.13 (accessible on my local network) I can ping it.
When I try and connect with SFTP it says “Server rejected SFTP but it listens for FTP connections”.
When I try and connect with FTP it says “No connection could be made because the target machine actively rejected it”.
When I try and connect with SCP it says “Connection to 192.168.1.13 refused”.
So: It’s definitely there and listening.
It seems that the network setup is correct but the brick is refusing to talk.

Seeing as it’s listening, why would 10.0.1.1 be any different to 192.168.1.13?

[Author]

Posts