Forum - Recent Threads

Using as a firewall

Mekon256 — Sat, 26 Mar 2022 20:47:48 GMT

I have an NVidia Jetson device, and want to connect it through the Guardian 100 to the internet; can the Guardian do this out of the box, or do I need a custom application deployed on the Guardian to do this?

Can the Avnet Guardian interface to or support BACNET and/or RS485?

pjschoenke — Thu, 01 Jul 2021 19:35:51 GMT

Hello!

I have a building automation customer that is interested in this product.

Can the Avnet Guardian interface to or support BACNET and/or RS485?

Any feedback or input is welcomed and appreciated!

Thank you!

Paul

Guardian 100 iPerf3 Wi-Fi Data Rate and Test Application Tests

BigG — Tue, 14 Jul 2020 21:41:52 GMT

I am referring to Section 14 (and Section 15) of the Azure Sphere Guardian 100 Hardware User Guide (v1.4).

In section 14 it states " This uses a pre-compiled, production-signed application that is side-loaded into the MT3620 device from the azsphere command window."

Whoever created this pre-compiled program without any transparency on the code is asking the user to take a huge risk side-loading this onto the Guardian 100. Legal matters aside (production signed? where's the proof) this makes it rather difficult to troubleshoot when it does not work as described.

The instructions go on to say:

The Guardian iPerf3 application is preconfigured to connect to an iPerf3 server at a specific static address. It is therefore necessary to set the computer’s ethernet adaptor to have a static IP address of 192.168.1.35 (plus the other highlighted settings shown below...)

Unfortunately my LAN does not make use of 192.168.1.... as an option. How can you expect such rigidity?

Hence the need to check what's going on and maybe have an option to compile my own customised test code. So, what's the reason for hiding this code? Where's the transparency?

The same can also be said for section 15.1 Guardian: Test Application Installation.

EDIT: PS. The user guide also does not provide instructions on how to remove the side-loaded images, meaning they remain on the device until manually removed. So, how is this best done?

RE: Guardian 100 iPerf3 Wi-Fi Data Rate and Test Application Tests

BigG — Wed, 15 Jul 2020 17:32:25 GMT

I decided to take a leap of faith and try out the test using the compiled program as described in Section 15. Unfortunately, the document content for this section is littered with error but I eventually found the image package as described on the element14 website (required a search). However when attempting to load it fails as shown below.

Is there a Linux version of the Guardian 100 WiFi Manager software

BigG — Mon, 13 Jul 2020 16:11:21 GMT

Section 7.3 of the latest User Manual (v 1.4) for the AVNET Azure Sphere Guardian 100 covers Wi-Fi Setup using a WiFi Manager Windows Application.

Assuming that there is no Linux option, has anyone attempted to use this utility using say Linux WINE or equivalent (Virtual Machine?).

I've only just swapped my 12 year old desktop, which had Windows 10 (prior was Windows 7 and Vista), over to Linux OS. It was a clean install as this gave me 64bit on Linux. After more than 25 years of using Windows it's actually not that hard to pick up Linux OS, but I'm still very much finding my feet. Hence the sometimes obvious to an experienced Linux user is not so obvious to me at this stage.

Cannot get the Guardian100 to connect to my PC via USB (suspect driver issue)

BigG — Wed, 29 Jan 2020 11:08:10 GMT

As title suggests, I am having trouble with connecting to Guardian100 via USB cable.

Setup so far (as per users guide):

1. Windows10 [tick]

2.Version later than 1607 [tick]

3. Install Azure Sphere SDK [tick]

3.1 The version reported should be 19.09 [tick]

Then I had followed this step in the Quick Start Guide:

STEP 3:

Connect the provided cables and power-up Guardian:

- Connect the Ethernet cable from Guardian to the equipment

- Connect USB cable type-A connector to the on-site equipment

- Connect USB cable type-B connector to Guardian

Then went onto

STEP 4:

Complete the Microsoft installation instructions to:

- Set up an Azure Sphere account (and subscribe to notiﬁcations)

- Claim your device

- Conﬁgure Wi-Fi settings of your device

I was unable to Claim my device.

Within the instructions it informed me that I should have 4 ports showing. I only have 1. I tried installing FTDI drivers directly and tried uninstalling but to no avail. Same thing.

Now while writing this query I do note a discrepancy with the Users Guide and the Getting Started guide.

I see in the user guide this instruction, which is not in the quick start guide (hence did not follow)

8.4 Debug/Programmer FTDI USB Interface Access

1) Disconnect all cables from Guardian, unscrew the four screws and remove the enclosure lid

2) Plug-in a USB cable (type-A to MicroUSB) from the vertically oriented MicroUSB connector on the Guardian PCB, to a spare USB port on the Windows 10 development computer

Then in 8.4.1 Windows FTDI USB Driver Installation

1) On first-time connection of Guardian to the development computer, the USB drivers should automatically download and install (this can be slow). If drivers do not install automatically, right-click on the device name in Windows Device Manager and select Update driver. Alternatively, download the drivers from Future Technology Devices International (FTDI), - choose the driver that matches your Windows 10 installation (32- or 64-bit). Additional assistance on this aspect is available at: https://docs.microsoft.com/en-us/azure-sphere/install/install#connect-the-Secure Edge Module

The link above returns page not found (404)

Finally, 8.4.2 Windows FTDI Interface Verification

2) Open Windows Device Manager and confirm the following are listed: - three new COM ports (under Ports COM & LPT) - a TAP-Windows Adaptor V9 (under Network Adaptors)

[View:/resized-image/__size/555x493/__key/communityserver-discussions-components-files/262/contentimage_5F00_129018.png:555:493]

I am not able to get these 3 showing.

Any advice welcomed.

RE: Cannot get the Guardian100 to connect to my PC via USB (suspect driver issue)

BigG — Thu, 30 Jan 2020 13:04:27 GMT

I did not pick that up. Nice to know that. Still, you have to be able to communicate with the device via USB in order to upload the WiFi credentials as well. So, not being able to do that was the issue I needed solving.

RE: Cannot get the Guardian100 to connect to my PC via USB (suspect driver issue)

clem57 — Thu, 30 Jan 2020 12:14:11 GMT

Actually in the MS doc for Azure Sphere they mention a switch that allows creating the tenant without the device. Later the device can update over the air...

RE: Cannot get the Guardian100 to connect to my PC via USB (suspect driver issue)

BigG — Thu, 30 Jan 2020 09:18:53 GMT

So, as I suspected (although not initially assumed), the quick start guide is incorrect - I suggest this quick start guide (and probably the user manual too) needs amending

You need to follow these instructions given in the user manual to create a tenant.

As per section 8.4 (Debug/Programmer FTDI USB Interface Access):

1) Disconnect all cables from Guardian, unscrew the four screws and remove the enclosure lid

2) Plug-in a USB cable (type-A to MicroUSB) from the vertically oriented MicroUSB connector on the Guardian PCB, to a spare USB port on the Windows 10 development computer

When I followed this step and it gave me the 3 USB ports and allowed me to create my Azure tenant etc.

This all makes sense as you wouldn't normally want this feature accessible from outside the enclosure.

So, it turns out it was not a driver issue, after all.

RE: Cannot get the Guardian100 to connect to my PC via USB (suspect driver issue)

BigG — Wed, 29 Jan 2020 13:55:42 GMT

Yes I am. I cannot get to Step 5 as it fails with a message in the Azure CMD tool telling me that it cannot connect to device as cannot find it.

This is when I am first creating the tenant as per these instructions: https://docs.microsoft.com/en-us/azure-sphere/deployment/create-tenant

RE: Cannot get the Guardian100 to connect to my PC via USB (suspect driver issue)

Fred27 — Wed, 29 Jan 2020 13:33:58 GMT

Are you familiar with the process of claiming your device when using the Azure Sphere development board? I assume this will be fairly similar. You need to log into Azure and to use the azsphere command line tool.

This is the relevant part of the guide for claiming the development kit: https://docs.microsoft.com/en-us/azure-sphere/install/claim-device