> For the complete documentation index, see [llms.txt](https://developer.magtek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.magtek.com/sdks-and-tools/universal-sdk-documentation/ios/connectioninfo.md). # ConnectionInfo Create an instance of the ConnectionInfo, then use the function calls described in this chapter. ### getAddress This function returns the address of the device. {% code overflow="wrap" %} ``` (NSString*) getAddress; ``` {% endcode %} Return Value: Returns the address of the device. ### getConnectionType This function returns the type of connection Interface for the device. {% code overflow="wrap" %} ``` (MTU_ConnectionType) getConnectionType; ``` {% endcode %} Return Value: Returns the MTU\_ConnectionType ### getDeviceType This function returns the type for the device. {% code overflow="wrap" %} ``` (MTU_DeviceType) getDeviceType; ``` {% endcode %} Return Value: Returns the MTU\_DeviceType. ### getCertificateInfo This function returns the type for the device. {% code overflow="wrap" %} ``` (CertificateInfo*) getCertificateInfo; ``` {% endcode %} Return Value: Returns the CertificateInfo\*. CertificateInfo: ### initWithDeviceType This function initializes an instance of ConnectionInfo. {% code overflow="wrap" %} ``` (ConnectionInfo*) initWithDeviceType:( MTU_DeviceType) deviceType connectionType: (MTU_ConnectionType) connectionType address: (NSString*) address; (ConnectionInfo*) initWithDeviceType: (MTU_DeviceType) deviceType connectionType: (MTU_ConnectionType) connectionType address: (NSString*) address certificate: ( CertificateInfo*) certInfo; ``` {% endcode %}
ParameterDescription
deviceTypeEnumerated device type.
connectionTypeEnumerated connection type.
address

Address for the device.

For Ethernet devices, address should be in the form:

IP://IP-Address:PORT

for example, IP://10.57.10.180:26

For Wireless devices, address should be in the form: TLS12://TLSDEVICESERIALNUMBER TLS12TRUST://TLSDEVICESERIALNUMBER

for example, TLS12://TLS99261829170E0810 TLS12TRUST://TLS99261829170E0810

For Bluetooth LE devices, address should be in the form:

BLEEMV://DEVICENAME

for example, BLEEMV://DynaPro Go-EB66

For WebSocket or Secure WebSocket devices, address should be in the form:

ws://IP-Address or Hostname wss://IP-Address or Hostname for example, ws://192.168.1.150 wss://b512345.magtek.com

The client private key certificate (e.g. filename client.p12) must be accessible to the custom software that makes a secure WebSocket (wss://) connection to the DynaFlex II PED.

For Serial devices, address should be in the form:

PORT=[PORT],

BAUDRATE=[BAUDRATE],

DATABITS=[DATABITS],

PARITY=[PARITY],

STOPBITS=[STOPBITS],

HANDSHAKE=[HANDSHAKE],

STARTINGBYTE=[STARTINGBYTE],

ENDINGBYTE=[ENDINGBYTE],

CRCMODE=[CRCMODE]

certInfo

Certificate information for TLS Trust and WebSocket WSS connection. Optional. See the following for details on installing a certificate chain: DYNAFLEX TLS CERTIFICATE INSTALLATION MANUAL

The client private key certificate (e.g. filename client.p12) must be accessible to the custom software that makes a secure WebSocket (wss://) connection to the DynaFlex II PED.

The client.p12 certificate is not needed if the connection type is not secure WebSocket (ws://)

Return Value: Returns an IDevice\*. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://developer.magtek.com/sdks-and-tools/universal-sdk-documentation/ios/connectioninfo.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.