Podcast #128: We chat with Kent C Dodds about why he loves React and discuss what life was like in the dark days before Git. Listen now.
2

Did you try: [System.IO.Ports.SerialPort]::getportnames() COM1 $port= new-Object System.IO.Ports.SerialPort COM1,9600,None,8,one $port.open() $port.WriteLine("Hello world") $port.Close() And reading from a Serial Port $port= new-Object System.IO.Ports.SerialPort COM1,9600,None,8,one $port.Open() $port.ReadLine() Edit: I found out on this site: https://...


2

I had the same problem. I visited this link - Setting up Windows 10 for IoT on your Raspberry Pi 2 - and cut/paste code to connect from there on to the powershell - it connected fine. net start WinRM Set-Item WSMan:\localhost\Client\TrustedHosts -Value MINWINPC remove-module psreadline -force Enter-PsSession -ComputerName MINWINPC -Credential MINWINPC\...


1

If you setup /etc/network/interfaces as in How to set up networking/WiFi then you can see if it has connected (and the IP) with ip a. route -vn will show if there is an entry in the routing table (and the metric). Both eth0 and wlan0 should have entries.


1

I think Alex is Correct I closed and start power shell again and only difference I did was set the PC name all lower case (as its actual named) net start WinRM Set-Item WSMan:\localhost\Client\TrustedHosts -Value minwinpc Enter-PsSession -ComputerName minwinpc -Credential minwinpc\Administrator Did not use this line remove-module psreadline -force


Only top voted, non community-wiki answers of a minimum length are eligible