IBHNet:Accessing PLC variables - Revision history

Jonas at 10:45, 9 April 2013

2013-04-09T10:45:17Z

← Older revision		Revision as of 10:45, 9 April 2013
Line 468:		Line 468:

	It is also possible to access the LOGO! RCE versions via RFC1006. In this case the MPI address 128 has to be used in the function Connect(), for Connect_DP() the slot 128 has to be used. MPI address and rack need to be 0. The possible variables are inputs, outputs, flags, the DB1 and the order number.		It is also possible to access the LOGO! RCE versions via RFC1006. In this case the MPI address 128 has to be used in the function Connect(), for Connect_DP() the slot 128 has to be used. MPI address and rack need to be 0. The possible variables are inputs, outputs, flags, the DB1 and the order number.

			Additional security settings are necessary with S7-1500 to permit access from IBHNet. To do so, navigate to the PLC properties 'Protection' section. There the Option: 'Connection mechanisms - Permit Access over PUT/GET communication from remote partner' must be checked.

Joscha at 06:36, 24 September 2012

2012-09-24T06:36:30Z

← Older revision		Revision as of 06:36, 24 September 2012
Line 26:		Line 26:
	\|-		\|-
	\|		\|
	Set up PLC connection<br />'''HRESULT Connect([in, string] BSTR Station,[in] long MPIAdr)'''<br />Station: Station Name<br />MPIAdr: MPI Addrerss<br />Return Value: Successful operation returns S_OK, E_FAIL or the sequence number if failed.<br />The function Connect_DP of the interface IIIBHNet3 should be ~~preferd~~ to set up a connection, because it returns always an exception in programming languages like VisualBasic or C#, if failed.		Set up PLC connection<br />'''HRESULT Connect([in, string] BSTR Station,[in] long MPIAdr)'''<br />Station: Station Name<br />MPIAdr: MPI Addrerss<br />Return Value: Successful operation returns S_OK, E_FAIL or the sequence number if failed.<br />The function Connect_DP of the interface IIIBHNet3 should be preferred to set up a connection, because it returns always an exception in programming languages like VisualBasic or C#, if failed.
	\|align="center"\| X		\|align="center"\| X
	\|align="center"\| X		\|align="center"\| X
Line 377:		Line 377:
	!align="center"\| S7 <br/> 200		!align="center"\| S7 <br/> 200
	\|-		\|-
	\|Set up PLC connection.<br />'''HRESULT Connect_DP(BSTR Station, long DPAdr, long Rack, long Slot)'''<br />Station: Station name<br />DPAdr: MPI<sup>®</sup> or Profibus address<br />Rack: Rack number (normally 0)<br />Slot: Slot number. For MPI normally 0, for Profibus the slot number of the CPU inside the rack.<br />Return Value: Successful operation returns S_OK, E_FAIL if failed.<br /><br />The function Connect_DP of the interface IIIBHNet3 should be ~~preferd~~ to set up a connection, because it returns always an exception in programming languages like VisualBasic or C#, if failed.		\|Set up PLC connection.<br />'''HRESULT Connect_DP(BSTR Station, long DPAdr, long Rack, long Slot)'''<br />Station: Station name<br />DPAdr: MPI<sup>®</sup> or Profibus address<br />Rack: Rack number (normally 0)<br />Slot: Slot number. For MPI normally 0, for Profibus the slot number of the CPU inside the rack.<br />Return Value: Successful operation returns S_OK, E_FAIL if failed.<br /><br />The function Connect_DP of the interface IIIBHNet3 should be preferred to set up a connection, because it returns always an exception in programming languages like VisualBasic or C#, if failed.<br />If the protocol RFC1006 is chosen in the IBHNet station, the parameter DPAdr is irrelevant. For connections to a Siemens CP, only the parameters Rack and Slot are regarded. With an IBH Link S7++, the MPI/Profibusaddress is a combination from the lower 5 Bit of the parameter Slot and the lower 3 Bit of the parameter Rack.
	\|align="center"\| -		\|align="center"\| -
	\|align="center"\| X		\|align="center"\| X
Line 383:		Line 383:
	\|align="center"\| -		\|align="center"\| -
	\|-		\|-
	\|Set up a routed PLC connection to a PLC in a MPI/Profibus subnet, if the CPU supports it.<br />'''HRESULT Subnet_Connect_DP(BSTR Station, long MPIStart, long MPIZiel, long RackZiel, long SlotZiel, long Subnet_HH, long Subnet_LL)'''<br />Station: Station name<br />MPIStart: MPI<sup>®</sup> or Profibus address, the IBH Link is connected to.<br />MPIZiel: Destination MPI<sup>®</sup> or Profibus address inside the subnet.<br />RackZiel: Destination rack number in the subnet (normally 0).<br />SlotZiel: Destination slot number in the subnet (normally 2).<br />Subnet_HH: Subnet ID HighWord, from Project.<br />Subnet_LL: Subnet ID LowWord, from Project.<br />Return Value: Successful operation returns S_OK, E_FAIL if failed.<br /><br />The function Connect_DP of the interface IIIBHNet3 should be ~~preferd~~ to set up a connection, because it returns always an exception in programming languages like VisualBasic or C#, if failed.		\|Set up a routed PLC connection to a PLC in a MPI/Profibus subnet, if the CPU supports it.<br />'''HRESULT Subnet_Connect_DP(BSTR Station, long MPIStart, long MPIZiel, long RackZiel, long SlotZiel, long Subnet_HH, long Subnet_LL)'''<br />Station: Station name<br />MPIStart: MPI<sup>®</sup> or Profibus address, the IBH Link is connected to.<br />MPIZiel: Destination MPI<sup>®</sup> or Profibus address inside the subnet.<br />RackZiel: Destination rack number in the subnet (normally 0).<br />SlotZiel: Destination slot number in the subnet (normally 2).<br />Subnet_HH: Subnet ID HighWord, from Project.<br />Subnet_LL: Subnet ID LowWord, from Project.<br />Return Value: Successful operation returns S_OK, E_FAIL if failed.<br /><br />The function Connect_DP of the interface IIIBHNet3 should be preferred to set up a connection, because it returns always an exception in programming languages like VisualBasic or C#, if failed.
	\|align="center"\| -		\|align="center"\| -
	\|align="center"\| X		\|align="center"\| X
Line 389:		Line 389:
	\|align="center"\| -		\|align="center"\| -
	\|-		\|-
	\|Set up a routed PLC connection to a PLC in a TCP/IP subnet, if the CPU supports it.<br />'''HRESULT Subnet_Connect_IP(BSTR Station, long MPIStart, BSTR IPZiel, long RackZiel, long SlotZiel, long Subnet_HH, long Subnet_LL)'''<br />Station: Station name<br />MPIStart: MPI<sup>®</sup> or Profibus address, the IBH Link is connected to.<br />IPZiel: Destination TCP/IP address inside the subnet.<br />RackZiel: Destination rack number in the subnet (normally 0).<br />SlotZiel: Destination slot number in the subnet (normally 2).<br />Subnet_HH: Subnet ID HighWord, from Project.<br />Subnet_LL: Subnet ID LowWord, from Project.<br />Return Value: Successful operation returns S_OK, E_FAIL if failed.<br /><br />The function Connect_DP of the interface IIIBHNet3 should be ~~preferd~~ to set up a connection, because it returns always an exception in programming languages like VisualBasic or C#, if failed.		\|Set up a routed PLC connection to a PLC in a TCP/IP subnet, if the CPU supports it.<br />'''HRESULT Subnet_Connect_IP(BSTR Station, long MPIStart, BSTR IPZiel, long RackZiel, long SlotZiel, long Subnet_HH, long Subnet_LL)'''<br />Station: Station name<br />MPIStart: MPI<sup>®</sup> or Profibus address, the IBH Link is connected to.<br />IPZiel: Destination TCP/IP address inside the subnet.<br />RackZiel: Destination rack number in the subnet (normally 0).<br />SlotZiel: Destination slot number in the subnet (normally 2).<br />Subnet_HH: Subnet ID HighWord, from Project.<br />Subnet_LL: Subnet ID LowWord, from Project.<br />Return Value: Successful operation returns S_OK, E_FAIL if failed.<br /><br />The function Connect_DP of the interface IIIBHNet3 should be preferred to set up a connection, because it returns always an exception in programming languages like VisualBasic or C#, if failed.
	\|align="center"\| -		\|align="center"\| -
	\|align="center"\| X		\|align="center"\| X
Line 395:		Line 395:
	\|align="center"\| -		\|align="center"\| -
	\|-		\|-
	\|Set up a routed PLC connection to a PLC in a H1 subnet, if the CPU supports it.<br />'''HRESULT SubnetConnectH1(BSTR Station, long MPIStart, BSTR H1Ziel, long RackZiel, long SlotZiel, long Subnet_HH, long Subnet_LL)'''<br />Station: Station name<br />MPIStart: MPI<sup>®</sup> or Profibus address, the IBH Link is connected to.<br />H1Ziel: Destination H1 address inside the subnet.<br />RackZiel: Destination rack number in the subnet (normally 0).<br />SlotZiel: Destination slot number in the subnet (normally 2).<br />Subnet_HH: Subnet ID HighWord, from Project.<br />Subnet_LL: Subnet ID LowWord, from Project.<br />Return Value: Successful operation returns S_OK, E_FAIL if failed.<br /><br />The function Connect_DP of the interface IIIBHNet3 should be ~~preferd~~ to set up a connection, because it returns always an exception in programming languages like VisualBasic or C#, if failed.		\|Set up a routed PLC connection to a PLC in a H1 subnet, if the CPU supports it.<br />'''HRESULT SubnetConnectH1(BSTR Station, long MPIStart, BSTR H1Ziel, long RackZiel, long SlotZiel, long Subnet_HH, long Subnet_LL)'''<br />Station: Station name<br />MPIStart: MPI<sup>®</sup> or Profibus address, the IBH Link is connected to.<br />H1Ziel: Destination H1 address inside the subnet.<br />RackZiel: Destination rack number in the subnet (normally 0).<br />SlotZiel: Destination slot number in the subnet (normally 2).<br />Subnet_HH: Subnet ID HighWord, from Project.<br />Subnet_LL: Subnet ID LowWord, from Project.<br />Return Value: Successful operation returns S_OK, E_FAIL if failed.<br /><br />The function Connect_DP of the interface IIIBHNet3 should be preferred to set up a connection, because it returns always an exception in programming languages like VisualBasic or C#, if failed.
	\|align="center"\| -		\|align="center"\| -
	\|align="center"\| X		\|align="center"\| X

Jonas at 11:49, 25 June 2012

2012-06-25T11:49:26Z

← Older revision		Revision as of 11:49, 25 June 2012
Line 90:		Line 90:
	\|align="center"\| X		\|align="center"\| X
	\|align="center"\| X		\|align="center"\| X
	\|align="center"\| X		\|align="center"\| -
	\|-		\|-
	\|Reads the revision of the SoftPLC.<br />'''HRESULT PLC_Version([out, retval] long *pVal)'''<br />pVal: reports the revision.<br />Return Value: Successful operation returns S_OK, E_FAIL on Errors. E_NOTIMPL will be returned, if the connected PLC does not support the function.		\|Reads the revision of the SoftPLC.<br />'''HRESULT PLC_Version([out, retval] long *pVal)'''<br />pVal: reports the revision.<br />Return Value: Successful operation returns S_OK, E_FAIL on Errors. E_NOTIMPL will be returned, if the connected PLC does not support the function.

Jonas at 11:42, 25 June 2012

2012-06-25T11:42:54Z

← Older revision		Revision as of 11:42, 25 June 2012
Line 428:		Line 428:



			In the installation folder of the '''''IBHNet''''' driver, samples for Visual Basic 6 can be found. The samples are commented. Samples for other programming languages will follow. Contact our product support to ask for more samples.





			{\|class="wikitable"
			\|class="hintergrundfarbe5"\|'''Attention: If multiple threads need to access the same IBHNet object, the access functions to the IBHNet object need to be locked from each other. Suitable mechanisms are for instance Critical Sections, Semaphores or Mutexes. A simple locking with variables is not suitable to securely avoid race conditions.'''
			\|-
			\|}


	~~In the installation folder of the '''''IBHNet''''' driver, samples for Visual Basic 6 can~~ be ~~found. The samples are commented. Samples for other programming languages will follow. Contact our product support to ask for more samples.~~		Following error codes will be returned:

	~~<table>~~		{\| class="wikitable"
	~~<tbody>~~		\|-
	~~<tr~~ class="~~odd~~">		!Errorcode
	~~<td align="left"> </td>~~		!Description
	~~</tr>~~		\|-
	~~<tr class="even">~~		\|1
	~~<td align="left">'''Attention: If multiple threads need to access the same IBHNet object, the access functions to the IBHNet object need to be locked from each other~~. ~~Suitable mechanisms are for instance Critical Sections, Semaphores or Mutexes~~. ~~A simple locking with variables is not suitable to securely avoid race conditions~~.~~'''</td>~~		\|netpcomv.CreateInstance failed
	~~</tr>~~		\|-
	~~<tr class="odd">~~		\|2
	~~<td align="left"> </td>~~		\|netpcomv.MPI_open failed
	~~</tr>~~		\|-
	~~</tbody>~~		\|3
	~~</table>~~		\|netpcomv.MPI_ConnRequest failed
			\|-
			\|4
			\|connection request to SoftPlc failed
			\|-
			\|5
			\|netpcomv.MPI_close failed
			\|-
			\|}

	~~Following error codes will be returned:~~

	~~<table>~~
	~~<tbody>~~
	~~<tr class="odd">~~
	~~<td align="left">'''Errorcode'''</td>~~
	~~<td align="left">'''Description'''</td>~~
	~~</tr>~~
	~~<tr class="even">~~
	~~<td align="left">1</td>~~
	~~<td align="left">netpcomv.CreateInstance failed</td>~~
	~~</tr>~~
	~~<tr class="odd">~~
	~~<td align="left">2</td>~~
	~~<td align="left">netpcomv.MPI_open failed</td>~~
	~~</tr>~~
	~~<tr class="even">~~
	~~<td align="left">3</td>~~
	~~<td align="left">netpcomv.MPI_ConnRequest failed</td>~~
	~~</tr>~~
	~~<tr class="odd">~~
	~~<td align="left">4</td>~~
	~~<td align="left">connection request to SoftPlc failed</td>~~
	~~</tr>~~
	~~<tr class="even">~~
	~~<td align="left">5</td>~~
	~~<td align="left">netpcomv.MPI_close failed</td>~~
	~~</tr>~~
	~~</tbody>~~
	~~</table>~~

	If accessing a variable fails, still an exception will be raised.		If accessing a variable fails, still an exception will be raised.

	It is also possible to access the LOGO! RCE versions via RFC1006. In this case the MPI address 128 has to be used in the function Connect(), for Connect_DP() the slot 128 has to be used. MPI address and rack need to be 0. The possible variables are inputs, outputs, flags, the DB1 and the order number.		It is also possible to access the LOGO! RCE versions via RFC1006. In this case the MPI address 128 has to be used in the function Connect(), for Connect_DP() the slot 128 has to be used. MPI address and rack need to be 0. The possible variables are inputs, outputs, flags, the DB1 and the order number.

	~~<br />~~

Jonas at 11:39, 25 June 2012

2012-06-25T11:39:01Z

Show changes

Jonas at 11:30, 25 June 2012

2012-06-25T11:30:20Z

← Older revision		Revision as of 11:30, 25 June 2012
Line 329:		Line 329:
	\|		\|
	\|-		\|-
	!~~'''Systemfunktionen der Schnittstelle~~ IIIBHnet2		!System Functions of the Interface IIIBHnet2
	!align="center"\| S5		!align="center"\| S5
	!align="center"\| S7 <br/> 300/400		!align="center"\| S7 <br/> 300/400

Jonas at 11:29, 25 June 2012

2012-06-25T11:29:36Z

Show changes

Jonas at 11:18, 25 June 2012

2012-06-25T11:18:40Z

← Older revision		Revision as of 11:18, 25 June 2012
Line 19:		Line 19:
	\|align="center"\| X		\|align="center"\| X
	\|-		\|-
	\|Search further configured stations<br />'''HRESULT NextStation(BSTR* pVal)'''<br />pVal: Station name<br />Return Value: Successful operation returns S_OK~~<br />~~<br />If no further station exists, S_FALSE is returned.		\|Search further configured stations<br />'''HRESULT NextStation(BSTR* pVal)'''<br />pVal: Station name<br />Return Value: Successful operation returns S_OK<br />If no further station exists, S_FALSE is returned.
	\|align="center"\| X		\|align="center"\| X
	\|align="center"\| X		\|align="center"\| X
Line 26:		Line 26:
	\|-		\|-
	\|		\|
	Set up PLC connection<br />'''HRESULT Connect([in, string] BSTR Station,[in] long MPIAdr)'''<br />Station: Station Name<br />MPIAdr: MPI Addrerss<br />Return Value: Successful operation returns S_OK, E_FAIL or the sequence number if failed.~~<br />~~<br />The function Connect_DP of the interface IIIBHNet3 should be preferd to set up a connection, because it returns always an exception in programming languages like VisualBasic or C#, if failed.		Set up PLC connection<br />'''HRESULT Connect([in, string] BSTR Station,[in] long MPIAdr)'''<br />Station: Station Name<br />MPIAdr: MPI Addrerss<br />Return Value: Successful operation returns S_OK, E_FAIL or the sequence number if failed.<br />The function Connect_DP of the interface IIIBHNet3 should be preferd to set up a connection, because it returns always an exception in programming languages like VisualBasic or C#, if failed.
	\|align="center"\| X		\|align="center"\| X
	\|align="center"\| X		\|align="center"\| X

Jonas: Created page with "== Accessing PLC variables == The '''''IBHNet''''' network driver ships with an object, which allows access to variables of the PLC. This COM-Server can be used in any progra..."

2012-06-25T11:17:11Z

Created page with "== Accessing PLC variables == The '''''IBHNet''''' network driver ships with an object, which allows access to variables of the PLC. This COM-Server can be used in any progra..."

Show changes