Knowledge Base / Protocols


Search KB


Browse Categories

Why do some of the settings for my DFNT solution show different values in the Diagnostic Menus than the values I downloaded in my DFNT.CFG file?

If you see different values displayed in the Diagnostic menus than what are in your DFNT.CFG file in the [DF1 Pass-Through Port] or [DF1 Pass-Through Server Port 1] sections, it could be due to the Pass-Through Server or Pass-Through Port being disabled. This is caused by a quirk...

Lire la suite

How many client and server connections are available on the ProLinx DFNT products and what service port do they use?

Each ProLinx DFNT module will support at least one client connection, and as many as 5 simultaneous server connections.With one client connection, the module will open a socket to a server (slave) device and will obtain data from it based on the configuration done in the ProLinx ...

Lire la suite

What service port number is used on my DFNT module?

When the module is configured as an EtherNet/IP server, service port 44818 (0XAF12) is used to access the module. All EtherNet/IP server devices use this service port number. When the module is configured as a client, it will use a service port number greater than 1024 to identif...

Lire la suite

Can the ProSoft/ProLinx Ethernet I/P products (DFNT driver, exp MVI46-DFNT, 5201-DFNT-MCM, PTQ-DFNT, etc…) communicate with any EtherNet I/P device?

The implementation of the DFNT product line can talk to many EtherNet I/P devices, but by no means all of them. The module when used as a Client (master) can only issue PCCC commands to the Server (slave) device. A PCCC message always uses a file address like N10:0, F15:2, etc Th...

Lire la suite

As a Ethernet/IP server, how does the internal memory of my DFNT module relate to the Ethernet/IP client command reference?

When a Ethernet/IP Client is reading or writing to a DFNT (server) Database Address, the addressing is listed as below:v:* {behavior:url(#default#VML);}o:* {behavior:url(#default#VML);}w:* {behavior:url(#default#VML);}.shape {behavior:url(#default#VML);} Normal 0 false false fals...

Lire la suite