8350200B – Field network communication has not been established.

Modified on Thu, 13 May 2021 at 06:31 PM

**Attention**: Read this resource  material carefully and in its entirety before use, to ensure it is  understood and used properly.  Failure to properly follow the  instructions in the resource materials DPAM provides may result in  damage to your equipment.  As a result, by using the resource materials,  you are assuming the risks associated with modifying your equipment.  DENSO holds no liability, implied or otherwise, for damage, injury or  any legal responsibility incurred, directly or indirectly from the use  of the resource materials, including any loss of data or damage to  property which may occur by your use of the resource materials. The use  of the resource materials are not recommended unless you have technical  knowledge and functional experience with the equipment and related  software. DENSO is unable to provide support, remote or otherwise, for  the information included in the resource material, nor for the ancillary  topics relating to the information included in the resource materials.  Therefore, if you are not fully comfortable with it, we strongly  recommend that you send your unit to one of our Regional Support Centers  for repair.  The information contained in the resource materials are  subject to change at the sole discretion of DPAM. 


If you are getting this error you will first need to check your Wincaps III project settings and determine if you have the correct field bus configuration. You will want to you a freshly uploaded project, so you know you are working the current configuration setup from the controller.

Related Error codes:

Applies to these robot controllers:


Open your project’s folder and double-click on the .WPJ file

Go to Project -> Property -> I/O 

Confirm that your “Device” setting matches your hardware configuration.

For example: If your controller has an Ethernet IP card installed in it then you should have EtherNet I/P Adapter selected as your device. If you are not using an additional field bus to communicate with a control device (PLC) then the device should be set to Mini IO.

Whatever communication method you have selected here is what the control will try and use. If you have a device selected that is different than what you are setting up or does not physically exist in the controller then you will get this error because the controller cannot connect via this device setting.

Each selected device has its own configuration settings that also need to be set correctly. Determine the size of data you want to send back and forth and your communication speed. Some will also require you to set a node address, station # or IP address (note – this is a different address than the LAN port used for communicating via PC on the back of the controller). All of these settings need to be matched with your configuration settings on your PLC. Any changes made will need to be downloaded back into your controller and then reboot the controller.

If you have confirmed all the correct settings match from your PLC side and your robot controller side then check your cables/wiring. If there is an error in the cable connection then you will also receive this error.

Owner's Manual Reference

You can refer to the link below in the manuals for your specific fieldbus configuration settings.

If the error still occurs then you may need to refer to the manuals for setting your desired configuration for the PLC manufacturer that you are using.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article