Professional Documents
Culture Documents
5. Further information
6. Warnings on TXBT
______________________________________________________________________________
1. General problems encountered when using the software
1.1 Management of the "page to process" in the dialogue table
From version XBTL1000 V3.4 , the word "page to process" in the dialogue
table must be written once only so as the terminal changes page.
Otherwise, the terminal will continuously change to the page already
displayed (flashing)
1.2 Switching from protocol UNITELWAY1 to UNITELWAY
When switching from protocol Unitelway1 to Unitelway and vice versa,
the addresses of variables are lost.
1.3 Import/Export text via a worksheet
When exporting/importing texts via Excel, if you replace a message by a
longer one, the new message will be shortened to the size of the first
message. When a text is between quotation marks, Excel doubles these
quotation marks. At the time of the importation of these texts,
XBT-L1000 does not recognize them.
1.4 XBTN/XBTH/XBTP/XBTE application name
These characters are not authorized:
(&),(+),( ),(=),([),(]),(^).
1.5 XBTN page tree
The page tree of an application XBTN presents an
different aspect according to the creation links order.
1.6 Entry of command links
XBT-L1000 allows the configuration of more than two links in the same
application page for a command terminal XBTN*(1).
These links cannot be activable with the terminal.
1.7 Protocol Sysmacway
The communication in Sysmacway between Magelis and the PLC variable with
an adress > at 9999 doesn't run. Use only the PLC variable with
an adress <= at 9999
1.8 Floating variable with PLC bounds
When you define the PLC bounds (Maximun and Minimun), you must write an
Integer and not an floating otherwise you will see Maximun= 2147483647
and Minimun= -2147483648.
1.9 Incompatibility of XBTL1000 with some software (example: software VEGA)
When you have installed XBTL1000 with a sofware whose the version of his
file GRID32.OCX is higher than the XBTL1000's file GRID32.OCX, you could
have some problemes with the XBTL1000 running.
Example:
When you have installed XBTL1000 and VEGA software on the same PC, the
alphanumeric terminals alarm pages cannot be displayed.
1.10 Image of system keys
In thedialog table, %MWn+1: Image of system keys doesn't work for a
touchscreen terminal. Only the bit 15 is operational.
Troubleshooting issues
4.1 Management of the "page to process" in the dialogue table (see 1.1)
Write only once the word "page to process" in the dialogue table.
4.2 Import/Export text via a worksheet (see 1.3)
Add spaces in the texts when writing in first language and anticipate
maximum length for messages in the other languages.
Avoid texts between quotation marks.
4.3 Simulations launching (see 2.1.1, 2.2.1, 3.1.2, and 3.2.2)
Just stop the simulation and restart it again.
4.4 Colours in the menus (see 3.1.1 and 3.2.1)
Colours modification is visible only when using some desktop
configuration Windows (Ex. Windows XP desktop configuration).
Colours turn to normal when user changes desktop configuration and uses
Windows classic configuration for instance.
4.5 Buttons of the system menu (see 3.2.3)
The problem is solved by surfing on the menu.
4.6 Transfer to a terminal (see 3.2.4)
Once the XBT software and communication drivers are installed, just
restart your PC. Windows will detect a new equipment: 'UNTLW WDM Device'.
Just launch the automatic installation so as to make the transfer to
the terminals run.
4.7 Display of J and T characters for TXT2 and CYR2 fonts (see 2.2.2)
Do not display text in bold fonts nor increase the font size
4.8 XBTR/XBTN/XBTH/XBTP/XBTE application name (see 1.4)
Do not use characters not recognized by XBT-L1000 and a name longer
than 8 characters for XBTH/XBTP/XBTE
Do not use characters not recognized by XBT-L1000 and a name longer
than 16 characters for XBTR/XBTN
4.9 XBTN page tree (see 1.5)
The different aspect of the page tree does not affect of anything
its validity.
4.10 Entry of command links (see 1.6)
Modify the terminal type to choose an entry model XBTN*(2) for more
than two links in the same page.
4.11 Update of system pages
When opening an application who requires to update system pages, while
an other application is maximized in XBT-L1000, an error can occur. In
order to fix it, do not maximize windows inside XBT-L1000 while opening
an other application.
4.12 Update of the Bios
If the message "Error access to temporary import folder" appears while
updating the terminal Bios, follow this procedure to bypass the problem :
a) Close the current XBT-N application.
b) Create a dummy XBT-N application, of the type of the terminal
currently connected
c) Save this dummy application, and close it.
d) Re-open the application you wanted to download before the
problem appeared
e) Download it. That's it.
4.13 Link with Unity Studio Manager
It is impossible to use the XBTL1000 link integrated in Unity Studio
Manager if XBTL1000 is running. To use Unity XBTL1000 integrated link,
close XBTL1000 first.
4.14 Dialoging with Quantum Unity PLCs
When the terminal is using the protocol "Modbus without Unity support"
on a Quantum Unity PLC (case of XBT HPE/HM/PM/N/R and also XBT-F if the
option "Unity Quantum Support" has not been selected), the mapping between
the memory adresses configured in XBT-L1000 and the memory adresses really
accessed in the PLC is the following one :
-----------------------------------!
XBT
<--> QUANTUM UNITY !
-----------------------------------! 40001+0 or %MW0 <-->
%MW1
!
! 40001+1 or %MW1 <-->
%MW2
!
!
...
<-->
...
!
! 40001+i or %MWi <--> %MW(i+1)
!
-----------------------------------Example : If in XBT-L1000 a field has been configured to monitor the adress
40001+15 (or %MW15 in IEC61131 syntax) the value displayed by
the field will be the value stored at the adress %MW16 of the
Unity Quantum PLC.
4.15 Communication between a PLC SLC05/03 or SLC05/04 and a terminal XBTN/XBTR
The communication doesn't work between SLC05/03 or SLC05/04 and a XBTN/XBT
R
on DH485 protocol. Please use Micrologix 1000 or Micrologix 1200 or SLC500
instead.
_______________________________________________________________________________
5. Further information
This CD ROM contains the Unitelway new drivers :
UNITELWAY V7.8 for Win 95, V1.9 for WinNT, V1.9 for Win98-Win2000-WinXP
NB: For further information on troubleshooting issues, please see the user
guides related to alphanumeric and graphic terminals.
_______________________________________________________________________________
6. Warnings on TXBT
6.1 To reach distant Inputs/Outputs on FIPIO from TXBT, it is required to
have a V3.4 processor version or higher.
6.2 To use the protocol TCP/IP(XWAY) or perform MODBUS+ distant transfer,
it is required to have a V2.2 version or higher installed on TXBT.
*******************************************************************************
_________________________________FRANCAIS______________________________________
_______________________________________________________________________________
TABLE DES MATIERES DU FICHIER LISEZMOI
A. Informations d'installation
1. Anomalies gnrales rencontres avec le logiciel
1.1 Gestion de la "page traiter" dans la table de dialogue
1.2 Passage du protocole UNITELWAY1 UNITELWAY
1.3 Import/Export de texte via un tableur
1.4 Nom d'une application XBTN/XBTH/XBTP/XBTE
1.5 Arboresence des pages d'une application XBTN
1.6 Saisie de liens de commande
1.7 Protocole Sysmacway
1.8 Variable flottante avec limites API
1.9 Incompatibilit d'XBTL1000 avec certain Logiciel (Exemple: logiciel VEGA)
1.10 Image des touches systmes
1.11 Interfaage avec les automates Quantum Unity
1.12 XBT-F/T-XBT-F : Compatibilit entre Carte ModBus Plus MBP100 et Proworx32
1.13 Problme de simulation XBTF lors de l'activation de l'option "Support Unity
Premium"
ou "Support Unity Quantum"
2. Anomalies rencontres sous Windows 2000
2.1 Terminaux alphanumriques
2.1.1 Lancement de la simulation
2.2 Terminaux graphiques
2.2.1 Lancement de la simulation
2.2.2 Affichage des caractres J et T pour polices TXT2 et CYR2
3. Anomalies rencontres sous Windows XP
3.1 Terminaux alphanumriques
Dpannage
6.1 Pour accder aux Entres/Sorties distantes sur FIPIO depuis TXBT, il est
ncessaire d'utiliser une version du processeur suprieure ou
gale V3.4.
6.2 Pour utiliser le protocole TCP/IP (XWAY) ou faire du transfert distant
MODBUS+, il est ncessaire d'avoir une version de l'ACCUEIL installe sur
le TXBT suprieure ou gale V2.2.