Windows IoT + Pi3
3852 Views - Created 06/02/2017
I was originally using this card: Link to competitor (hope that's OK) however, I found them to be a little unreliable and was hoping to use the AB Electronics UK card instead. Unfortunately, I can't get the card to work. The 'competitor' card linked above works perfectly, serial data is fine but with the AB card I can't get any comms at all. I'm putting this down to the Pi 3 issues discussed here: https://www.abelectronics.co.uk/kb/article/1035/raspberry-pi-3-serial-port-usage It seems the solution to this problem always discusses the changes required for Linux builds.
Ultimately, I have 3 questions:
1. Has anyone had any success with these boards using a Raspberry Pi 3 running Windows IoT?
2. Does anyone know of a way to apply the 'Linux fixes' linked above to Windows IoT?
3. Does AB Electronics have any plans to revise the board so it becomes compatible (out of the box) for Pi 3s (as per the 485 competitor board linked above)?
Many thanks in advance.
P.S. Apologies in advance if discussing other Pi card vendors isn't allowed.
We have not tried using the RS485 Pi with Windows 10 on a Raspberry Pi 3 yet but I am currently setting up a fresh IOT image on a Pi 3 so I can check whether or not it works. In theory, as long as the UART pins are working on the Raspberry Pi then the RS485 Pi should work as well.
The schematic for the LinkSprite board is similar to our RS485 Pi board so if the LinkSprite board works ours should too. Comparing the two boards the main differences apart from using a different RS485 transceiver is their board has LEDs to show when data is being sent and received and our board has voltage spike protection on the inputs. The wiring on the DB9 connectors is different so if you are using a cable designed for the LinkSprite board you will need to rewire it to use our RS485 board.
I will let you know if I manage to get Windows 10 working with the RS485 Pi.
The RS485 Pi was connected to another RS485 Pi on a Raspberry Pi 2 running Linux which is configured to use the UART port as a terminal. When I started the SerialUART app and then powered up the second Raspberry Pi I received the normal Linux bootup text in the received data box on the Windows app and once booted I could send data to the second Raspberry Pi from the app and have it echo the text back so two-way communication appears to be working.
Can you try downloading the modified SerialUART app and see if it works on your Raspberry Pi? It may be worth double-checking your wiring as well just to make sure everything is connected correctly.
Note: documents in Portable Document Format (PDF) require Adobe Acrobat Reader 5.0 or higher to view, download Adobe Acrobat Reader or other PDF reading software for your computer or mobile device.