Keyence IV3 fixed vision sensor
Generated documentation for the Axo_IV3 component.
Most of the initialization variables come from the I/O system. The example below is for demonstration purposes.
[!INCLUDE IntializeAndRun]
View the library source at Axo_IV3.st.
The Axo_IV3 .NET twin exposes a reverse-proxy helper (ConfigureProxy) that
surfaces the device's built-in HTTP live view inside the application's web UI.
Two pragmas on the ST component instance drive the wiring:
| Pragma | Purpose |
|---|---|
{#ix-set:DeviceIpAddress = "..."} |
IP address of the Keyence IV3 device that the server will reach. |
{#ix-set:Proxy = "..."} |
Proxy identifier used to mount the reverse-proxy endpoint (/{Proxy}/iv3-wm-i.html). |
The showcase component declaration illustrates the DeviceIpAddress pragma:
The reverse-proxy middleware must be wired in the Blazor host (Program.cs)
before the Blazor endpoint handling so that image requests are routed through
the server and CORS is not required. IHttpClientFactory must also be
registered.
View the .NET twin source at AXOpen.Components.Keyence.Vision.
Axo_IV3 renders via the generic AxoComponent pattern using
RenderableContentControl — the runtime inspects the component type and
selects the matching rendering based on the Presentation attribute. A
dedicated Axo_IV3View is also available when richer visualization
(including the reverse-proxied live view) is required.
Available Presentation values: Status-Display, Command-Control, Service-Control, Spot, Compact.
View the Blazor package at AXOpen.Components.Keyence.Vision.blazor.
PROFINET hardware template at showcase/app/hwc/library_templates/Keyence_IV3/.