RMA
Member
I'm struggling a bit trying to get WinCC Flex Runtime on a PC to communicate with the PLC via Ethernet. I think I may have made life unnecessarily complicated by integrating the Flex project in Step7, but that's life, I guess!
Everything looks OK in the Communication area of Flex, the only thing that looks a bit odd is that the expansion slot is listed as being 2 whereas the CP is actually in Slot 4. However, since the connection Partner is listed as being the CPU and the CP is the node, then I guess that's probably OK, in any case, I can't see anywhere in NetPro where I can change the Slot number.
The only other thing that occurs to me is that in the process of swapping the licences back and forward between different PCs the Runtime licence has disappeared, could this be the reason for the Ethernet communication not working?
Communication via MPI is fine, but since the customer has already blown the USB adapter in one PC (5m of USB cable makes a pretty good aerial when it's only 2m away from a cable carrying 40,000 Amp pulses) it's pretty important to get the optically isolated Ethernet connection working.
If anybod'y got any suggestions, I'd be pleased to hear them.
Cheers
Roy
Edit: Just a further snippet of information in case it's of any help, I managed to catch the rapidly disappearing error message with the Print Button and copy it into paint, the error is "General connection error 0x384" (loosely translated from the German).
Everything looks OK in the Communication area of Flex, the only thing that looks a bit odd is that the expansion slot is listed as being 2 whereas the CP is actually in Slot 4. However, since the connection Partner is listed as being the CPU and the CP is the node, then I guess that's probably OK, in any case, I can't see anywhere in NetPro where I can change the Slot number.
The only other thing that occurs to me is that in the process of swapping the licences back and forward between different PCs the Runtime licence has disappeared, could this be the reason for the Ethernet communication not working?
Communication via MPI is fine, but since the customer has already blown the USB adapter in one PC (5m of USB cable makes a pretty good aerial when it's only 2m away from a cable carrying 40,000 Amp pulses) it's pretty important to get the optically isolated Ethernet connection working.
If anybod'y got any suggestions, I'd be pleased to hear them.
Cheers
Roy
Edit: Just a further snippet of information in case it's of any help, I managed to catch the rapidly disappearing error message with the Print Button and copy it into paint, the error is "General connection error 0x384" (loosely translated from the German).
Last edited: