Download
Share
Print this page
Carel pCOWeb User Manual
  1. Manuals
  2. Brands
  3. Carel Manuals
  4. Network Card
  5. pCOWeb
  6. User manual

Carel pCOWeb User Manual

Hide thumbs

Advertisement

Quick Links

pCOWeb

User manual

LEGGI E CONSERVA
QUESTE ISTRUZIONI
READ AND SAVE
THESE INSTRUCTIONS
I n t e g r a t e d C o n t r o l S o l u t i o n s & E n e r g y S a v i n g s

Advertisement

loading
Need help?

Need help?

Do you have a question about the pCOWeb and is the answer not in the manual?

Questions and answers

Related Manuals for Carel pCOWeb

Summary of Contents for Carel pCOWeb

  • Page 1: User Manual

    User manual LEGGI E CONSERVA QUESTE ISTRUZIONI READ AND SAVE THESE INSTRUCTIONS I n t e g r a t e d C o n t r o l S o l u t i o n s & E n e r g y S a v i n g s...
  • Page 3 CAREL or its subsidiaries are warned of the possibility of such damage.

  • Page 5: Table Of Contents

    ASSEMBLY ......................................... 9 LABELS SUPPLIED ....................................10 STARTING FOR THE FIRST TIME – ACCESSING pCOWeb FROM A COMPUTER ................11 CONNECTING pCOWeb DIRECTLY TO A PC ............................11 ESTABLISHING A CONNECTION BETWEEN THE PC AND pCOWeb VIA A NETWORK ..............14 FUNCTIONS ......................................
  • Page 6 FileZilla Server: A FREEWARE FTP SERVER ........................66 APPENDIX F iReasoning MIB Browser as a TRAP receiver ........................67 APPENDIX G CAREL TAGS FOR pCOWeb HTML PAGES -THE PW_DEMO.HTML PAGE ............... 68 APPENDIX H Library “pw_ajax.js” and CGI “xml.cgi” ..........................76 APPENDIX I STRUCTURE OF A pCOWeb PLUGIN ............................

  • Page 7: Presentation Of The Product

    Figure 1.a - pCOWeb: example of network connection This manual refers to firmware version A2.0.4 – B2.0.4. To check the version loaded on the pCOWeb, see Section 9.2.2 on page 42. In the example shown in sopra pCOWeb is connected to an internal network. If suitably configured, the personal computers in the internal network can communicate with Figure 1.a...

  • Page 8: User Interface: Button And Leds

    Figure Functions of the button When starting up the pCOWeb, this is used to select, for network communication, whether to use the factory parameters or the user parameters (see 3.1.2 on page 12 for the procedure); In normal operation, reboots pCOWeb without needing to disconnect the power supply (see 9.10.1 on page 53 for the procedure).

  • Page 9: Installation On The Pco Controller

    Equipment required: • a 3 mm flat-head screwdriver; • a map of the installation (only when installing two or more pCOWeb devices); • a pair of scissors. Figure 2.a - pCOWeb and the accessories supplied Figure 2.b - Removing the cover from the pCO controller IMPORTANT: to avoid damage, before inserting pCOWeb, disconnect power to the pCO controller.

  • Page 10: Labels Supplied

    If more than one pCOWeb device is installed, a map of the installation should be created, applying the second label provided in the packaging onto the map for each pCOWeb, corresponding to its physical position; in this way, the network administrator can be provided with precise documents on where the pCOWeb devices and corresponding MAC addresses are located.

  • Page 11: Starting For The First Time - Accessing Pcoweb From A Computer

    CONNECTING pCOWeb DIRECTLY TO A PC This connection is used to access pCOWeb from a computer connected by cable. Normally this type of connection is used to test operation on the bench or to initially configure pCOWeb for an installation that does not use “DHCP” automatic address setting (see 9.4.1 on page 45).Paragraph 3.2 on page 12, on the other hand, describes the network connection procedure.
  • Page 12 7. Close the windows using the OK button. 3.1.2 Connection, starting pCOWeb and activating the default network settings (Button) Connection 1. Connect pCOWeb to the Ethernet connector on the PC using a shielded cable (). Figure 3.e – pCOWeb connection pCOWeb +030220966 – rel. 1.1 – 12.12.2017...
  • Page 13 Starting 2. Switch on the pCO controller. 3. Check that both indicator LEDs on the pCOWeb turn on within a few seconds (Errore. L'origine riferimento non è stata trovata.). If this does not occur, see 0 on page 13. Activating the factory network settings (button) INFORMATION •...

  • Page 14: Establishing A Connection Between The Pc And Pcoweb Via A Network

    Remember that if pCOWeb is now rebooted (for example, switching the pCO controller off and on again) without pressing the button again as described in 3.1.2 on page 12, pCOWeb will use the user-set IP address; if this is different than the factory value, it may be impossible to connect to pCOWeb (this situation is described in paragraph 3.2 on page 14).
  • Page 15 (for example, try using Mozilla Firefox to access other sites with assured accessibility); • check the indicator LEDs on the pCOWeb, with reference to paragraph 0 on page 13 (the role of the PC in this case is performed by the switch or the hub); •...
  • Page 16 C in paragraph 3.1.1 on page 11, however with the variants shown in (example for pCOWeb with IP address 10.0.0.145). Figure 3.l - Disabling the proxy for some IP addresses To ensure compatibility for direct communication, as an alternative to the procedures described above, the PC can be configured so that it responds not only to the IP address already set, but also to a second IP address that is compatible for direct communication with pCOWeb.

  • Page 17: Functions

    Also refer to the documentation available at http://ksa.carel.com. APPENDIX G on page 68 lists the CAREL tags and describes an example of the default demo page resident on the pCOWeb. Other pages are shown in APPENDIX I on page 79 (“Plugins”). To create a simple HTML page, the Notepad application can be used on the PC, typing the following lines and saving the file as “example.html”:...

  • Page 18: Accessing The User Memory Via Ftp Or Scp

    Create a new “Site Manager” and enter the data as shown in Figure 4.c and Figure 4.d. NOTE The IP address should be replaced with the address of the pCOWeb; the default Username and Password are: httpadmin / fhttpadmin; paragraph 9.8.2 on page 50 describes how to change this information, and paragraph 9.8 on page 49 shows how to read the current information.
  • Page 19 Figure 4.h - Using Internet Explorer as the FTP client This solution is not recommended, however, as it is not suitable for copying files from the PC to pCOWeb; in addition, previous versions of Internet Explorer had problems in navigating the memory space outside of the areas used for the HTML pages (configuration files …).

  • Page 20: Event Notification: E-Mail, Ftp Push, Snmp Trap/ Inform

    • To be able to send e-mails, pCOWeb must have access to an SMTP server on the local network or the Internet: pCOWeb sends the e-mail to the server and a PC can then access the server and download the messages that have been sent to it. APPENDIX D on page 63 presents the ArGoSoft Mail Server, a freeware application downloadable from the Internet that, once installed on the PC, can receive e-mails from the pCOWeb and then forward them to an e-mail client, for example Microsoft Outlook.
  • Page 21 Events generated upon variations in the value of a variable pCOWeb can be set to send a notification when the value of a pCO controller variable changes. The types of messages sent can be selected separately for each variable. For the settings see 4.3.3 on page 23 and 4.3.4 on page 25.
  • Page 22 Generation of the XML file When a notification event occurs, pCOWeb can generate an XML file containing information on the pCOWeb and the values of the pCO variables, which can be sent via FTP or as an e-mail attachment. XML (eXtended Markup Language) is a standard file format for conveying information organised in a diagram; it is recognised by many types of software that manage data that is imported from files.
  • Page 23 • The syntax of a file with the .xml extension can be validated, for example, by displaying it in Mozilla Firefox; pCOWeb nonetheless only recognises the syntax shown above. In particular, it does not recognise the standard XML <text /> tag, which in standard XML is equivalent to the pair <text> + <text/>.
  • Page 24 “Ftp Push”: FTP Push Configuration recipients for sending XML files.  Input file name (required): used to choose the XML template resident on pCOWeb that will be used as the basis for generating the XML file sent (see 4.3.2 on page 22); “Choose” opens a list of files with the .xml extension in /usr/local/root/flash/http; if the file name is entered, the path must be specified starting from the root (/).
  • Page 25 IMPORTANT: Some settings described below (“Event Handlers”, “Trap Configuration” and “E-Mail Configuration”) are also used for the scheduled events (see section 4.3.5 on page 28). NOTE: all the following settings are valid from when they are confirmed; the pCOWeb does not need to be rebooted. PROCEDURE...
  • Page 26 Figure 4.u - E-mail configuration for an event the contents of the file, before being added to the body of the message, will be processed by the pCOWeb WEB server (see APPENDIX G a pagina 68); in this way, by creating simple HTML pages, the body of the message can contain the value of some pCO variables read at the moment the message was sent.
  • Page 27 It should be noted that in this case Threshold / Hysteresis can be set as values entered or as integer variables that can be selected. Figure 4.w - Opening the integer variable summary settings pCOWeb +030220966 – rel. 1.1 – 12.12.2017...
  • Page 28 4.3.5 Scheduled events (generated at time intervals) pCOWeb can be set to generate events for sending notification when a set and repeated time interval expires. PROCEDURE Open the Tab for setting the events corresponding to Scheduled events (click “Scheduled” on the Events summary window – Figure 4.x).

  • Page 29: Clock And Logger

    When rebooting, the date / time is reset to: 1970-01-01 00:00. pCOWeb can be configured so that it can set its own clock based on the time set on the pCO controller or on the time obtained from a NTP (Network Time Protocol) server.

  • Page 30: Configuring Clock Via Ntp

    20 variables sampled at regular time intervals to non-volatile memory (“Logger” function). pCOWeb can create also a graph using the vector format SVG and representing in the same graph up to 5 of the logged variables. SVG files can be natively viewed using Firefox, Chrome, Safari and Edge browsers, while instead Internet Explorer 8 needs an external plug-in (e.g.:...
  • Page 31 BMP format (the only available format before 1.4.2); pCOWeb creates a file in .bmp format containing a simple graph of the trend in the values of just one of the logged variable. There is a specific html page to set the type of the graph called “pw_logswitch.html”...
  • Page 32 In the “/usr/local/root/flash/http/log” directory, pCOWeb automatically saves the powerup-log.csv file containing the records, with the date / time of the events: “Start firmware” and “Stop firmware”, respectively “Power-up” and “Power-down”. The latter is only written when the Stop follows a reboot while pressing the physical button or selecting the button on the configuration page;...
  • Page 33 IMPORTANT: Whenever the configuration of the Logger is changed during the day, pCOWeb retains the values saved until that moment but updates the first three lines of the header (see Figure 5.g, left); if the selection of the logged variables is changed and the records saved until that moment need to be retained, proceed as follows: before changing the configuration, save the data to the PC by first selecting Update files to this very moment, then Download all csv and graphs;...

  • Page 34: Snmp

    The simplicity of its messages means that SNMP is becoming increasingly widespread, above all for the control of industrial devices. pCOWeb includes an SNMP v2c Agent, that is, an application that responds to network queries in SNMP protocol version 1 and 2c. The pCOWeb SNMP Agent is developed using the Net-SNMP open source package, version 5.7.3;...

  • Page 35: The Pcoweb Snmp Tree

    As the MIB file contains the physical meaning of each object, it can only be created once the pCO application has been defined. For this reason, upon request CAREL only provides the MIB FILES for the standard CAREL pCO applications, which can however be used to as the basis for creating a MIB file for custom applications;...

  • Page 36: Snmp Configurations For Pcoweb

    OID: 1.3.6.1.2.1.1.2.0 Enterprise OID: enterprises identifier used by the device. The default is 9839, which is the identifier assigned to CAREL; the full list of assigned  identifiers is available on https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers. Users should change the identifier only if they do not want pCOWeb to appear as a CAREL device.

  • Page 37: Bacnet

    BACNET pCOWeb can recognise queries sent by a supervisor that uses the BACnet protocol (Building Automation Control Networks), in the following two versions: BACnet/IP (Addendum A/Annex J) BACnet Ethernet ISO8802-2 over 8802-3 The two standards use the same physical means for carrying the data (Ethernet RJ-45 network) but differ as regards the different ways the data packets are encoded.

  • Page 38: Bacnet/Carel Mapping

    BACnet/Carel Mapping For each pCOWeb that interfaces to a Carel controller using a standard Carel pCO connection there can be a maximum of 670 BACnet objects, which include the Device Object. Of the 670 objects, there are always 16 Notification Class objects, 16 Calendar objects, 16 Schedule objects and there can be up to 207 Analog Values, 207 Analog Values or Multi-state Values and 207 Binary Values.
  • Page 39 List_Of_Object_Property_References property can have from 0 to 64 entries. External objects are not supported. Following a restart, schedules are not executed until the pCOWeb clock has been set using a TimeSynchronization or UTCTimeSynchronization. Schedules are checked approximately every 10 seconds for a minute rollover, so scheduled values may not change until 10 to 15 seconds after the minute turns over.

  • Page 40: Modbus Tcp/Ip

    Map mode: it allows to adopt a different mapping scheme, to allow pCOWeb retrocompatibility with older versions of pCOWeb Further explanations about mapping schemes throughout version are available in APPENDIX J, on page 83. Figure 8.c – Modbus TCP/IP configuration page pCOWeb +030220966 – rel. 1.1 – 12.12.2017...

  • Page 41: Basic Configuration And Auxiliary Functions

    NOTE2: To copy a back up from a pCOWeb to another one is necessary that both pCOWeb have the same firmware version In addition, a function is available that deletes all the changes made by the user (settings or files added) and returns pCOWeb to its default state (see 9.3 on page 44).
  • Page 42 NOTE As already mentioned at the beginning of the manual, the following description refers to the configuration page relating to pCOWeb firmware version A2.0.4 - B2.0.4. To check the pCOWeb firmware version, see paragraph 9.2.2 below.
  • Page 43 E – displays the pCOWeb MAC address (see 2.2 on page 10). • F – displays the pCOWeb date and time at the moment of the last update requested for the page displayed from the PC (for example with F5).

  • Page 44: General Info And Restoring The Default Situation

    • View network configuration: shows a summary of the network settings that pCOWeb is using, divided between ETH0 / ETH0:1 / ETH0:2 / ETH0:3 (these can only be displayed if the corresponding logical interface is being used, see section 9.4) / DNS SERVERS / GATEWAY; especially useful when operating with DHCP: shows the effective information acquired from the server and currently used.

  • Page 45: Setting The Network Communication Parameters

    SETTING THE NETWORK COMMUNICATION PARAMETERS For pCOWeb to communicate with the data network it is installed in, a number of network communication parameters need to be correctly set. The assistance of the network administrator is required to establish if pCOWeb can be connected, and to understand the essential data relating to the installation. To better understand the meaning of the procedure for setting these parameters, see APPENDIX A on page 58 and APPENDIX B on page 59.

  • Page 46: Settings Relating To Pcoweb - Pco Communication

    3) is not supported. This enables pCOWeb to exchange up to 12048 variables (5000 analog, 5000 integer and 2048 digital variables) with the pCO application, which has to be specifically designed to use the new extended range of variables to the monitoring system. To enable the modbus extended protocol pCOWeb has to be told: •...

  • Page 47: Configuring From Pco System Masks

    The following mask will be shown: In a few seconds, if communication between pCOWeb and pCO controller is properly working, the fields will fill up wth current parameters. In case fileds were not filled with current values, it is needed to check Bios firmware version and the protocol on BMS serial.
  • Page 48 [ Conflict ] file already present [ !!! ] file not installed correctly Once having completed the installation, the plugin page will be as shown below: Figure 9.p - Installed Plugins pCOWeb +030220966 – rel. 1.1 – 12.12.2017...

  • Page 49: Protection And Access Control

    The access restrictions to the HTML pages MUST NOT BE CONFUSED WITH THE AUTHORISATION FOR USERS OF THE OPERATING SYSTEM described further on; for example, the password specified to access a page is still valid even pCOWeb is started with the button;...
  • Page 50 Table 9.a - Operating system Usernames and Passwords A modifiable Password is provided as default for each of the four users. The modification does not affect the password that is used to access pCOWeb when started with the button pressed (see 3.1.2 on page 12), which is non-modifiable. The Password can be modified to allow only authorised personnel to access pCOWeb.

  • Page 51: Various Tests: Ping - Pco Variables - Notifications - E-Mail

    “carel” AND “guest” USERNAMES These are used internally to run applications. They have no interest for the user of the pCOWeb, except to change the default Password so as to increase security. IMPORTANT: If the password is forgotten, the only way to access the operating system functions protected by the Username/Password is to start pCOWeb with the factory Passwords pressing the button, as described in 3.1.2 on page 12.
  • Page 52  Operation result legend (Undefined / Ok / Timeout): describes the outcome of the last read or write operation: Ok: after a write operation, pCOWeb has received acknowledgement from pCO with the current value of the variable; Timeout: if 10 seconds elapse from the write operation without the pCO sending the acknowledgement message containing the current value of the variable;...

  • Page 53: Restarting Pcoweb

    Disconnect the power supply for a few seconds (the LEDs must go off), then reconnect (if the operation is to be performed after setting the value of a parameter, wait until the setting has been confirmed, to allow time for the confirmation to be sent via the browser to pCOWeb);...

  • Page 54: Firmware Update

    IMPORTANT: If when updating block A the procedure is interrupted due to a power failure, the block A transferred is not valid. Upon next reboot, the normal functions will no longer work, but pCOWeb, due to presence of a valid block B, will continue to operate to allow block A to be loaded again, although with a different procedure (see section 9.11.2 on page 55).
  • Page 55 Figure 9.dd - Flash image upload report – Writing to non-volatile memory At the end of writing, pCOWeb will be rebooted automatically. After around 1 minute, the updated main configuration page can be opened to check that the Figure 9.d firmware version has been changed (see on page 43).

  • Page 56: Pco Application Update

    To update the pCO application, when one of Carel or Modbus protocol is running, the process just needs a zipped file where the needed files are present.

  • Page 57: Technical Specifications

    VERY IMPORTANT It is standard in custom pCO application and in each Carel standard application that, in order to avoid memory mismatching, to re-initialize the unit to the default configuration when the application updates, so that is strongly advised to upload, together with the applications' files, a consistent DEV file for the specific application (i.e.

  • Page 58: Appendix Amac Address - Static Or Automatic Ip Address (Dhcp)

    Each pCOWeb has a MAC (Medium Access Control) address that is unique at a worldwide level from all other network devices. In addition, each pCOWeb connected in the data network must be set with a unique IP address. If the network that the pCOWeb is connected to uses the automatic “DHCP” system for assigning the address, a manual setting of the addresses will not be needed.

  • Page 59: Appendix Bip Addresses, Proxy Server, Subnet Mask, Dns, Gateway

    If pCOWeb is installed in a network with a proxy server, the browser on the PCs in the network are normally already set to send their HTML page requests to the proxy. In this case, if the network server has not yet been set to locate the pCOWeb in the network, a personal computer will not be able to access the pCOWeb HTML pages via the proxy.
  • Page 60 Dest IP #3 255. 255. 00001010 00000000 01000000 00000010 ....Dest IP (#8192) 255. 255. 00001010 00000000 01011111 11111111 pCOWeb +030220966 – rel. 1.1 – 12.12.2017...
  • Page 61 IP destination address; once the response is received, this too will be forwarded to the original sender (the personal computer). Overall, then, the gateway allows the personal computer to access all other IP addresses outside of its own subnetwork. Figure B.a - Communication in a network pCOWeb +030220966 – rel. 1.1 – 12.12.2017...

  • Page 62: Appendix Capplication - Pco - Pcoweb Communication

    At the same time, on the pCOWeb the variation sent flag is raised (comm buffer: delta flag “set”); this flag is ONLY used by the HTML pages when reading to establish whether the variations sent by the page with the “Submit” button have been confirmed by the reception of the new values on the pCO: while there are still some variations that have not yet been confirmed by the pCO, pCOWeb does not generate the confirmation html page on the browser;...

  • Page 63: Appendix D Argosoft: A Freeware Mail Server

    The “Listening on port …” messages confirm that: • SMTP Server started: the server that pCOWeb will send the messages to is running. IMPORTANT: if another SMTP manager is already active, port 25 will be busy and the service will not be started. Close the other manager.
  • Page 64 Figure D.c - ArGoSoft Mail Server: creating a MAILBOX IMPORTANT: When, in Figure 4.p on page 24, the properties are set for sending the e-mail notifications from pCOWeb, if ArGoSoft is used, it is mandatory not to specify the login Username / Password (leave the corresponding fields empty).
  • Page 65 7 – Test account settings...: select this button to test the Microsoft Outlook settings: a test message will be sent and then received by the MAILBOX. At this stage, the ArGoSoft server is ready to receive e-mails from pCOWeb and deliver them to Outlook.

  • Page 66: Appendix E Filezilla Server: A Freeware Ftp Server

    Again with reference to Figure E.b sopra (points 4, 5, 6), set the access Password for the “ftpaccount” user created above (for example “password”). With reference to Figure E.c (points 7, 8, 9, 10), set the shared directory for “ftpaccount” that pCOWeb will be able to copy the files into.

  • Page 67: Appendix F Ireasoning Mib Browser As A Trap Receiver

    Figure F.a - Trap Receiver: confirming the start of the service Figure F.b shows the Trap Receiver window highlighting a Trap message that has been received. Figure F.b - Trap Receiver: confirming the start of the service – details of the TRAP messages pCOWeb +030220966 – rel. 1.1 – 12.12.2017...

  • Page 68: Appendix Gcarel Tags For Pcoweb Html Pages -The Pw_Demo.html Page

    CAREL TAGS FOR pCOWeb HTML PAGES -THE PW_DEMO.HTML PAGE Each CAREL tag entered on an html page is used to read or modify the pCO controller data or the pCOWeb settings. This makes the html page dynamic, that is, it contains the values of variables. The tags are managed by an internal program on pCOWeb with tag parser functions, called “pcotagfilt”. In fact, the web server on pCOWeb has been programmed to recognise the following row in an html page (row position is irrelevant): <!--tagparser="/pcotagfilt"-->...
  • Page 69 “var” returns “U” (see above, description of “var” for reading). If waiting for some echo, pCOWeb will return the page to the PC after a Timeout of 10 seconds from the reception of the last echo; the fields relating to the variables for which no echo has been received will contain the values saved prior to the variations being sent.
  • Page 70 Figure G.d - The “setres” TAG: example CAREL TAGS FOR HANDLING THE pCOWeb CONFIGURATION FILES pCOWeb saves the user settings in a number of files (paragraph 9.1 on page 41), in the following format: <parameter>=<value> An example of these files (SNMP TRAP configuration, ‘snmptrap’ file) is as follows:...
  • Page 71 IMPORTANT: the names of the pCOWeb files are case sensitive. The file is searched by default in /usr/local/root/flash/etc/sysconfig/, which contains the pCOWeb configuration files. To use a new file of parameters for new applications, a path other than the default can be specified, always starting from root (“/”); nonetheless, it is recommended to save the files in the default path so as to group all the pCOWeb parameter settings in the same location.
  • Page 72 <h1 style="text-align: center">pCOWeb Demo Page</h1> <br> <form method="POST" action="example.html"> <input type="radio" name="?script:setdb('clockcfg','clock_sync_enabled')" value="0" id='en_clock_a' onclick="Check_EnVar('1')" <%checkdbradio('clockcfg','clock_sync_enabled','0')%>>Disabled <input type="radio" name="?script:setdb('clockcfg','clock_sync_enabled')" value="1" id='en_clock_b' onclick="Check_EnVar('1')"<%checkdbradio('clockcfg','clock_sync_enabled','1')%>>Enabled <input type="submit" value="Submit"> </form> </body> </html> - The “checkdbradio” TAG: example Figure G.h pCOWeb +030220966 – rel. 1.1 – 12.12.2017...
  • Page 73 “ This takes a long time to run; if when running (that is, until the web page is returned) other web pages are requested, pCOWeb will need to be rebooted. To use this, type the following command directly into the address field in the web browser: http://172.16.0.1/config/result.html?%3fscript%3arccmd%28%27do_log%27%29...
  • Page 74 The following rows in standard html language simply represent comments. The last of the three rows is nonetheless essential for the pCOWeb pages and MUST be included in the page (see the start of APPENDIX G on page 68). This tells pCOWeb which translator must be used for the proprietary tags.
  • Page 75 <input style="width: 100px; margin-left: 20px; margin-top: 10px" type="submit" value="Submit"> </form> End of the page <div id="back-bottom"> (C) Copyright 2003-2010 by Carel Industries S.r.l.., Brugine (PD) - Italy. All rights reserved. Contact: <a href="mailto:pcoweb@carel.com">pcoweb@carel.com</a><br> Linux porting and software implemented by DVE Progettazione Elettronica, Varese (Italy). <a href="mailto:info@dveprojects.com">info@dveprojects.com</a><br>...

  • Page 76: Appendix H Library "Pw_Ajax.js" And Cgi "Xml.cgi

    To cope with the increasing requests to integrate pCOWeb in enterprises system, it had became mandatory for the pCOWeb to integrate a standard way of communicate using the HTTP protocol, that is why the pCOWeb now is able to send information using XML over HTTP (which is the standard way to use the XML).
  • Page 77 Starting from Version A142, the “pw_ajax.js” library is using a new function called “parseResults” which is executed as soon as the browser receives the xml from pCOWeb, so that the values shown in the html can be updated without waiting for the next run of the javascript code. Up to version A135 the function...
  • Page 78 Advantages 1. Web pages can reside in a Apache or IIS web server, they will have to connect to the pCOWeb only to download data, which is extremely useful for integration or to overtake the limitations of the embedded web server of the pCOWeb (for example php or asp or .net could be used to generate dynamic web pages) 2.

  • Page 79: Appendix Istructure Of A Pcoweb Plugin

    Figure I.a - Elements making up a Plugin In the following descriptions the examples refer to the NTP Plugin (Network Time Protocol) for the automatic synchronisation of the pCOWeb clock with a time server, using the NTP protocol; the Plugin is available at http://ksa.carel.com.
  • Page 80 IMPORTANT This should not be confused with the pluginname file, located in the Plugin installation directory, which is only used during the installation and uninstallation phase. Syntax telling the pCOWeb to process the page and replace the CAREL tags with the corresponding values; this is required to be able to write and read the configuration files.
  • Page 81 12-17: As for the start section, the stop section is made up of the same parts, and is called when the pCOWeb is shutdown or when accessed by the user. 19-23: Runs the script again, first the stop section and then the start section, used to have the Plugin reread the new configuration files; it cannot be run from the web page but only from a remote console.
  • Page 82 PLUGIN DIRECTORY For a Plugin to be automatically recognised as able to be installed by the pCOWeb, the directory that will be copied via FTP (see 9.7.1 a pagina 47) and that contains all the files and all the directories must be called “Install-plug-xxx”, where xxx is any name used to identify the contents of the Plugin, yet has no special meaning for the pCOWeb.

  • Page 83: Appendix Jmodbus Tcp/Ip Maps

    Modbus TCP/IP service allows to share pCO variables via Modbus TCP/IP protocol. As shown in Section 0, two different maps are available. The first map is kept for compatibility reasons and refers to the oldest firware versions of pCOWeb (up to v.1.4.x). For these versions, the following map holds:...
  • Page 84 It is possible to read digital variables from 1 to 2047 but not variable 2048. In order to read the desired variables the following must be used: 2. LOGICAL ADDRESSING data register 1 (Number of points 3) as in the picture below: pCOWeb +030220966 – rel. 1.1 – 12.12.2017...
  • Page 85 Again you see 1;1;0. For a correct visualization you should use: Data register 2 Number of points 3 (as using Modscan selection): Version 1.5.x, 1.6.x, 2.0.x and newer Again, the first digital is set to 1. pCOWeb +030220966 – rel. 1.1 – 12.12.2017...
  • Page 86 Again, with MODICON COMPATIBLE settings, trying the previous set, Data register 1 Number of points 3, an error is received. If you use the correct index and settings as point 4 you get the correct information: MODICON COMPATIBLE Data Register 2 Number of points 3 pCOWeb +030220966 – rel. 1.1 – 12.12.2017...
  • Page 87 INDEX $BIN_USERS; 101; 102 permission; 61; 64; 101 $CONF_USERS; 99; 102 PICS; 45 Ping; 64; 65 $PATH; 101 $RC_USERS; 102 pluginname; 99; 100; 104 POP3; 80; 81; 82 %bootvalues; 92 %checkdbradio; 91 port; 29 %checkdbsel; 90; 91 power; 8; 9; 11; 14; 15; 35; 38; 68; 79 protection;...
  • Page 90 CAREL Industries S.r.l. Via dell’Industria, 11 - 35020 Brugine - Padova (Italy) Tel. (+39) 049.9716611 Fax (+39) 049.9716600 http://www.carel.com - e-mail: carel@carel.com pCOWeb +030220966 – rel. 1.1 – 12.12.2017...
Save PDF