Back to Aurora Vision Library website

You are here: Start » Function Reference » Hardware Support » Hilscher » Hilscher_Channel_Open_Profinet

Hilscher_Channel_Open_Profinet


Header: ThirdPartySdk.h
Namespace: avl
Module: ThirdParty

Opens a Hilscher device channel connection.

Syntax

void avl::Hilscher_Channel_Open_Profinet
(
	avl::Hilscher_State& ioState,
	const atl::Optional<atl::String>& inBoardName,
	const int inChannelNumber,
	const atl::Optional<atl::File> inConfig,
	const atl::Optional<atl::File> inNwid,
	const atl::Optional<atl::Array<avl::HilscherSignal>>& inInputSignalConfiguration,
	const atl::Optional<atl::Array<avl::HilscherSignal>>& inOutputSignalConfiguration
)

Parameters

Name Type Range Default Description
Input will be modified ioState Hilscher_State& Object used to maintain state of the function.
Input value inBoardName const Optional<String>& NIL
Input value inChannelNumber const int 0 - 10
Input value inConfig const Optional<File> NIL Configuration file generated in SYCON.net (xxx.nxd)
Input value inNwid const Optional<File> NIL Configuration file generated in SYCON.net (xxx_nwid.nxd)
Input value inInputSignalConfiguration const Optional<Array<HilscherSignal>>& NIL
Input value inOutputSignalConfiguration const Optional<Array<HilscherSignal>>& NIL

Remarks

Initial state

Opening an not configured channel sets all output slots to 0, configured channel data is left as it was.

Channel configuration

The channel is only configured with provided configuration files, if it is in a not configured state - no connection between card and master device (for example a PLC). If it is configured, the filter assumes proper operation, and leaves card configuration in existing condition.

Driver

For profinet: Firmware (recommended 3.13 series) https://kb.hilscher.com/display/PNS3V5/Version+History+-+V3.5+to+V3.x

Firmware needs to be uploaded to the card prior to opening any type of channel.
In case of failing to update the firmware, try to restart your computer.

Multithreaded environment

This function is not guaranteed to be thread-safe. When used in multithreaded environment, it has to be manually synchronized.