14.01.2015 Views

Gemini GV6K and Gemini GT6K Programmer's Guide

Gemini GV6K and Gemini GT6K Programmer's Guide

Gemini GV6K and Gemini GT6K Programmer's Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Error Response<br />

SEE NTIO<br />

INVALID SERVER TYPE<br />

NETWORK INPUTS AND OUTPUTS CANNOT<br />

BE ASSIGNED TO A VARSHO<br />

NETWORK IP ADDRESS CANNOT BE<br />

CHANGED WHILE CONNECTION IS<br />

OPEN, SEE NTCONN<br />

NO NETWORK IP ADDRESS SPECIFIED<br />

FOR CONNECTION, SEE NTIP<br />

NTFEN MUST BE 1 TO USE THIS<br />

COMMAND<br />

NTRATE MUST BE 0 TO CHANGE NTFEN<br />

NTSELP ALREADY ENABLED ON THIS<br />

TASK<br />

OPTION CARD CAN NOT BE USED WITH<br />

ETHERNET - SEE NTFEN<br />

VARB USED BY OPTION CARD<br />

VARIABLE MAPPING CONFLICT, SEE<br />

NTMPRB, NTMPRI, NTMPWI, NTMPWB<br />

MAPPINGS<br />

Possible Cause<br />

\ANO, \TANI, \TANO, \TIN, or \TOUT comm<strong>and</strong>), but that<br />

I/O point was configured with the NTIO comm<strong>and</strong> to be<br />

different I/O type.<br />

Tried an OPTO22-related comm<strong>and</strong> (\TANI, \TANO, \TIN,<br />

\TOUT, \TIO, \IN, \OUT, \ANI, \ANO, etc.) for a non-<br />

OPTO22 connection.<br />

Tried to assign the status of OPTO22 I/O to a VARSHO<br />

variable.<br />

Tried to execute an NTIP comm<strong>and</strong> while the connection is<br />

open.<br />

Tried to connect (nNTCONN1) to a server # that has not yet<br />

been established with the NTIP comm<strong>and</strong>, or tried to<br />

connect to a server in an incompatible subnet.<br />

(Peer-to-peer connection only) Tried to execute an NTRATE<br />

comm<strong>and</strong> while NTFEN is set to a value other than NTFEN1.<br />

(Peer-to-peer connection only) Tried to execute an NTFEN<br />

comm<strong>and</strong> while NTRATE is set to a non-zero value.<br />

NTSELP, which enables program selection via OPTO22<br />

inputs, has already been enabled (if multitasking, it has<br />

been enabled for this specific Task).<br />

Tried to enable the internal Fieldbus Option card for<br />

PROFIBUS or DeviceNet communication (6Kn-PB <strong>and</strong> 6Kn-<br />

DN products only) with the OPTEN1 comm<strong>and</strong>. You must<br />

disable Ethernet communications with the NTFENØ<br />

comm<strong>and</strong> before enabling the Option card. The 6K cannot<br />

communicate over a Fieldbus connection <strong>and</strong> Ethernet<br />

connection simultaneously.<br />

Tried to map a binary variable to read from or write to an<br />

Allen-Bradley data file, but the variable is already used for<br />

Fieldbus (PROFIBUS or DeviceNet) data transfer functions.<br />

Tried to map the same 6K VARB or VARI variables for read<br />

<strong>and</strong> write functions. Or tried to map the same 6K VARB or<br />

VARI variables to another PLC.<br />

Error H<strong>and</strong>ling<br />

The 6K has a Error Status register for logging certain error conditions. If you enable checking<br />

for an error condition (see ERROR comm<strong>and</strong>), the 6K will branch to the designated error<br />

program (see ERRORP comm<strong>and</strong>) when it detects the error condition. The Ethernet networking<br />

related Error Status register bits are noted below.<br />

ERROR<br />

Bit #<br />

Cause of the Error<br />

23 Ethernet Client<br />

Connection Error.<br />

(Can’t connect.)<br />

Gosub<br />

24 Ethernet Client Polling Gosub<br />

Error. (After connect <strong>and</strong><br />

polling device for data,<br />

polling timeout occurred.<br />

Cause could be<br />

disconnect, client lost<br />

power, etc.)<br />

Branch Type How to Remedy the Error<br />

to ERRORP<br />

Clear the error bit (ERROR.23-0), reestablish<br />

the Ethernet connection<br />

(nNTCONN1), <strong>and</strong> then issue ERROR.23-1.<br />

Clear the error bit (ERROR.24-0), reestablish<br />

the Ethernet connection<br />

(nNTCONN1), <strong>and</strong> then issue ERROR.24-1.<br />

Chapter 2. Communication 55

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!