I have a Raspberry PI with Win 10 IoT installed.
The device is connected through Ethernet, I can ping it
I've connected through Powershell, changed admin password. Followed instructions here: http://ms-iot.github.io/content/en-US/win10/samples/PowerShell.htm
I can connect to the device's web based interface http://ip:8080
However, WindowsIoTCoreWatcher.exe does not show or list my device. I tried Refresh button, run as admin. Still no result.
How can I fix the issue?
Thank you,
WindowsIoTCoreWatcher listens for UDP broadcasts that are sent every five seconds by a process running on the device: C:\Windows\System32\ebootpinger.exe. It appears that this process occasionally dies or stops broadcasting, particularly if the device has not been rebooted in several days. It can be restarted with the PowerShell command (e.g. in a remote interactive session):
Start-Process ebootpinger.exe
Related
I have a Raspberry Pi with a 4G USB dongle connected to it for internet access. Everything works on power-up, everything auto-connects and connectivity is established.
In fact if I leave the Raspberry Pi on my desk powered up it stays connected through the 4G dongle for weeks without any issues.
As soon as I leave my mobile cell area, connectivity drops out and does not recover. I also want to be able to unplug the USB 4G dongle and reconnect it and have the cell link auto recover. I am using USB-Modeswitch and wvdial.
Is there anyway I can get the 4G dongle to auto recover?
Thanks for reading.
Brodes.
OK I think I have found the solution I was looking for....
I created this script that sends 5 pings to the other end of a VPN tunnel. If the pings fail then the Raspberry Pi reboots.
#!/bin/bash
# This script checks for an active Internet connection by pinging.
# If the pings fail, it will reset the USB modem dongle.
ping -c5 10.8.0.1
let a=$?
if [ "$a" != "0" ]; then
/sbin/shutdown -r now Connection lost, rebooting...
fi
Then I created a cronjob to run this script every 2 minutes.
If anyone has a better idea please let me know.
Cheers,
Brodes.
I am running into an issue connecting to a wifi AP using Windows 10 PC.
The AP is located on an embedded device, amd uses WPA2-personal security. The AP can be enabled by our testsetup for certain testcases. The idea is to let Windows connect to the AP in these tests.
I am able to manually connect to the AP when it is active. However, when I try it when there is no active user (e.g. headless/CI setup), I get an error.
The command and reply I use when manually connecting (using a saved WiFi profile named "Test_AP.xml"):
PS C:\projects> netsh wlan add profile user=current filename=Test_AP.xml; netsh wlan connect name=Test_AP interface="Wi-Fi"
Profile Test_AP is added on interface Wi-Fi.
Connection request was completed successfully.
When I try with no activ user (e.g. headless/CI setup), the reply is:
Profile Test_AP is added on interface Wi-Fi.
The network specified by profile "Test_AP" is not available to connect.
I was able to reproduce it, by adding a sleep command before executing the powershell commands, and immediatelly disconnecting my remote session to the PC. When I reconnect after a while, I see this error.
I already tried adding to profile to all users, but to no avail.
Does anybody know why Windows is not able to connect to a wireless network in this case? Or any inspiration what I can improve?
Kind regards
I have Windows 10 IoT installed on a Raspberry PI 3 B, and I am trying to connect to it via the Windows IoT Remote Client running on my laptop. (+)
As it mentioned here and here, there is a related known issue in Windows 10 IoT on build number 16299.
Consequently, when I try to connect my Raspberry PI via the Remote Client, it shows me only a white screen. However, it makes me able to use the mouse and keyboard connected to my laptop to control the Raspberry Pi.
In the description of the known issue, it says: "Drivers must be manually copied and registered on the device.".
Then my question is what do you know about the drivers that should be copied manually?
And is there any way except than waiting for next release of windows 10 IoT?
Let me explain my problem: I have a raspberry Pi with Kodi installed and I use it with a IPTV service. This service only allow me to use it in one device at a time and sometimes I want to use it on my phone.
I'd like to be able to turn off my raspberry remotely so I can watch it in my phone whenever I want. I tried to create a web server that would allow me to run a script that would turn off the device but I can't access it because the raspberry IP takes me to some kodi stuff.
So to sum up, I'd like to go to my raspberry IP with Kodi installed, press a button and turn off the device. The web stuff I can take care of.
Any thoughts?
The only safe way to do this is to have a VPN tunnel that lets you access your internal network. This is much safer than opening up a port to Kodi on your router. It would just attract every bot and hacker out there.
Once you have a working VPN tunnel between your home network and your smartphone, just use a Remote Control App to shut Kodi down cleanly.
You can use a Kodi remote app for your mobile device. E.g. Kore (official remote app for Android) does have a shutdown button.
I think the best and easy way is to install dataplicity in your Raspberry Pi and access via dataplicity web or the app (Android or iOS) to the Terminal and use the command: sudo shutdown -h now or sudo poweroff
I am trying to establish a serial connection between the RPI3 and an Arduino. Because that wasn't working I connected a USB to TTY cable from my laptop to the Rx/Tx pins of RPI. I was eventually able to use PuTTy to connect to it.
I am running Android Things on the RPI and the android code I have running is supposed to be a loopback (reading from UART and writing back what was read).
Here is where I am confused....
When PuTTy connected I was presented with a command line console on the RPI.
How do I get the Rx/Tx pins on the RPI to just be serial connections into and from my application and NOT a way to log into the console?
Is that a bad idea? I suppose if I ever needed to log into the RPI this would make it more difficult...
I figured out what I was doing wrong...
When following the setup directions at the below site I was using the Bluetooth mode instead of the Application mode. When I followed the directions for Application mode I was able to start using UART0 for serial comms
Set the console attribute to the following in cmdline.txt:
console=tty0
Add the following line in config.txt:
dtoverlay=pi3-disable-bt
Remove the following lines from config.txt:
enabled_uart=1
core_freq=400
https://developer.android.com/things/hardware/raspberrypi.html#disabling_the_console
Beginning with Developer Preview 3, in which USB-Serial devices support added, You can use external USB-UART dongles like this instead of UART of Raspberry Pi 3.