Results 1 to 4 of 4

Thread: Communication Error 16 bit controllers

  1. #1
    Join Date
    Aug 2009
    Location
    ifm Exton, PA
    Posts
    195

    Default Communication Error 16 bit controllers

    To communicate with the ifm controllers follow the following guidlines:

    1) The 'Test Pin' MUST have voltage supplied to it (Pin 24 on 16 bit controllers). This is the pin that puts the controller into a 'program/debug' mode that allows the download tool and CoDeSys to communicate with the controller. This pin may be left high for normal operation as well.

    2) Make sure that you have a ground connected to PIN 5 of your RS232 connection.

    3) The proper firmware must be downloaded to the controller using the ifm DOWNLOAD software before communications can be established with CoDeSys

    4) Default Baudrate for most controlllers is 57600. For the CR2500 it may be 9600.

    5) Parity = NO
    Stop Bits = 1
    Motorola Byte Order = NO
    Flow Control = OFF

    6) In CoDeSys Comminucation Parameters, Set the gateway to 'Local'.
    Last edited by Jeremy Kopicz; 02-17-2010 at 08:35 AM.

  2. #2
    Join Date
    Aug 2009
    Location
    ifm Exton, PA
    Posts
    195

    Default

    Also note that CoDeSys will NOT be able to communicate if the ifm DOWNLOADER is open. You must first close the DOWNLOADER before attempting to go online or download with CoDeSys.

  3. #3
    Join Date
    Mar 2009
    Posts
    45

    Default Other serial communication problems

    Occasionally a problem will occur where an already existing normal connection between CoDeSys and a controller stops working.

    This can sometimes occur if power is interrupted, there is a high level on noise present in the environment, the cable is too long, or a cable becomes disconnected during communication.

    Solution:

    The Gateway driver may have been affected. When this happens, the best solution is to close CoDeSys, right click on the gateway server icon in the lower right hand corner of the Windows screen and left click exit. Power cycle the controller, reopen CoDeSys and try to re-establish communication with the controller.

  4. #4
    Join Date
    Feb 2010
    Posts
    29

    Default

    I've also experienced Comm dropout errors when there is a large CANbus load, or high cycle times in the plc program where the combined load of logging or starting a download can trip the watch dog timer causing a plc reset.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •