2. pCOWeb

3. pCOWeb and pCOnet 2 different add-on cards PCO1000WB0 - ETHERNET :
BACnet Ethernet
BACnet over IP
SNMP v1, v2, v3
HTTP (web server)
FTP, DHCP,...
available
PCO1000BA0 - EIA 485 :
BACnet MS/TP

4. pCO 2 pCO C pCO 1 pCO B pCO XS pCO 3
pCO available
pCO 2
pCO C
pCO 1
pCO B
pCO XS
pCO 3

5. pCOWeb
It allows to access to the variables of the controller (pCOx) through a common Ethernet LAN.
Board features
Power by pCO
ARM7 74MHZ
16MB RAM, 8MB flash
Linux
10Mbit
Protocols
HTTP (web pages 4MB)
SNMP (Simple Network Management Protocol)
BACnet (BACnet over IP and BACnet over Ethernet)
FTP server, FTP client (plug-in optional)
NTP (Network Time Protocol) (plug-in optional)

6. Introduction Serial Port n.1 BIOS: any version is good
pCO WEB act as a local supervisory sistem
SW application:
SERIAL1_PROTOCOL=1 (Carel Local (Slave))
19200 baud (default)
IDENT: not important (1-207, 0 not allow)

7. LEDs and Button
2 LEDs
Left LED : “Status” Communication with controller
Right LED : “Ethernet” Communication with LAN
1 Button
During runtime : Reboot card. Press the button for 5 to 10 sec.
At start-up : copy the factory values from Flash to RAM Press the button. Power-on controller. As soon as the left LED starts blinking (red/off).The pCOWeb will make 3 fast blink = confirm.
IP address=
Subnet mask=
Username=httpadmin, password=fhttpadmin, etc…

8. Installing the board
Upload SW application into the board. Check protocol & baud rate (SERIAL1_PROTOCOL=1, INI_BAUD_SPV=4)
Plug the board into the serial port n.1 (BMS)
Connect pCOWEB to the PC
Test Plan : use cross cable
Switch On the control. Wait till the end of the boot (about 1min) Boot’s end when the left green LED blinks

9. Configuring the PC
Usually the TCP/IP configuration of the PC doesn’t match with the pCOWEB one(DHCP, subnet mask)
Change Network Properties/ Internet protocol (TCP/IP)

10. Configuring Browser (Explorer)
Disable the Proxy server
Run Explorer
Click tools/Internet options
Click Connection tab
Click LAN setting
Unselect Use proxy server…
Check Box

11. Accessing to the main page
Run Explorer (or other browser)
(default address for the new card)

12. Web Administrator
Open the main/index page (complete address:
Click on Web Administrator reserved area link
Login: admin, password: fadmin

13. PcoWeb HTTP

14. PcoWeb HTTP

15. PcoWeb General
Used/Free Flashdisk space

16. PcoWeb General
These setting are used when you press the button at start-up

17. PcoWeb General
Ethernet Configuration (IP,n° RX/TX,...)

18. PcoWeb General
Ethernet Variables

19. PcoWeb General
Adjust HTML pages attributes

20. PcoWeb General

21. Network Configuration
Most Important Parameters
IP address
Netmask
Gateway, DNS: for FTP client (send file to

22. pCO COM Communication Parameters with the controller
You can change only the baud rate

23. pCOWeb Users

24. Users

25. pCOWeb SNMP
SNMP (Simple Network Management Protocol) is a communication protocol designed to manage TCP/IP networks and devices.
Developed by the IETF (Internet Engineering Task Force) and adopted as a TCP/IP-based management standard in 1989.
SNMP is a set of standards for network management including:
a protocol,
a database structure specification,
and a set of data objects.
ARCHITECTURE
The SNMP architecture defines a Client/Server relationship.
The Server (Network Management Station) executes management applications or directives which manage and control network elements.
Clients (Network elements) are devices which have management agents responsible for performing the network management functions requested by the Server.
The database, controlled by the SNMP agent, is referred to as the MIB (Management Information Base) and is a standard set of statistical and control values.

26. pCOWeb SNMP

27. pCOWeb SNMP http://www.simpleweb.org/ietf/mibs/validate/
SNMP v2.c: available
Carel OID:
TRAP
User trap
System TRAP
TRAP editor
FILE MIB: “Describes” the variables/objects (i.e. “Room Temperature”, “High Pressure Alarm circuit 1”,...)
MIB for standard applications: available
MIB for custom applications custom: “easy” to do
MIB validator available on the internet

28. MIB
The list of values that an object supports is often referred to as the SNMP “Management Information Base” (MIB).
“MIB” is simply an abstraction like “Database”
STANDARD MIB
The standard MIB includes various objects to measure and monitor IP activity, TCP activity, UDP activity, IP routes, TCP connections, interfaces, and general system description.
PRIVATE MIB
SNMP has become prominent mainly from its ability to augment the standard set of MIB objects with new values specific for certain applications and devices.
Hence, new functionality can continuously be added to SNMP. This is accomplished through a process usually referred to as “compiling” a new MIB, which allows the user to add new MIB definitions to the system. When a MIB is compiled into an SNMP manager, the manager is made “aware” of new objects that are supported by agents on the network.

29. MIB
The SNMP MIB is arranged in a tree-structured fashion, similar in many ways to a disk directory structure of files.
The top level SNMP branch begins with the ISO “internet” directory, which contains four main branches:….

30. TRAP
SNMP traps are an important part of the SNMP standard, and allow devices to self-report problems.
These traps are typically logged by the network manager, and drive event notifications.
Traps are asynchronous and outside of the control of the network manager

31. PcoWeb BacNet Database
The pCO* communicated variables are mapped to analog_value and binary_value BACnet objects.
A table-based list of BACnet-visible values is maintained by the pCOWeb.
Each interface table value is accessible by BACnet clients as a Present_Value property of a standard object.
The Carel variable for each interface table slot defines the object type implicitly.
Analog variables are mapped to BACnet Analog Value object type with an instance number equal to their variable number, e.g. analog variable 17 would appear to be BACnet Analog Value 17. Because analog variables are implicitly scaled "times 10" their conversion to REAL in BACnet is scaled accordingly. So the value "123" which is taken to mean "12.3" is converted to a floating point "12.3" as the value for the AV object Present_Value property.
Integer variables are mapped to BACnet Analog Value object type with an instance number equal to their variable number plus 1000, e.g. integer variable 17 would appear to be BACnet Analog Value The integer value shall be converted to REAL in BACnet. So the value "123" should be converted to a floating point "123.0" as the value for the AV object Present_Value property.
Digital variables are mapped to BACnet Binary Value object type with an instance number equal to their variable number, e.g. digital variable 17 would appear to be BACnet Binary Value 17.
Carel variables
BACnet variables
Digital variable 1
Binary value instance 1
Digital variable 199
Binary value instance 199
Analog variable 1
Analog value instance 1
Analog variable 127
Analog value instance 127
Integer variable 1
Analog value instance 1001
Integer variable 127
Analog value instance 1127

32. PcoWeb BacNet BACnet Standardized Device Profile (Annex L):
BACnet Application Specific Controller (B-ASC)
List all BACnet Interoperability Building Blocks Supported (Annex K):
DS-RP-B, DS-RPM-B, DS-WP-B, DS-WPM-B i.e. act as a server that can execute Read/Write single or multiple properties
DM-DDB-B, DM-DOB-B i.e. dynamic device and object binding. Support initiating I-Am in response to Who-Is, and at configurable interval (Who-Is only, Who-Is plus startup, Who-Is plus every N minutes). This option is configurable through software.
DM-DCC-B, DM-RD-B i.e. DeviceCommunicationControl and ReinitializeDevice. These features shall support a Reinit Password configurable through software.
AE-N-I-B, AE-ACK-B, AE-INFO-B i.e. generate EventNotifications when programmed alarm conditions occur; accept acknowledgements for those notifications marked as requiring acknowledgement, and support GetEventInformation requests.
Segmentation Capability:
Segmentation not supported

33. PcoWeb BacNet Standard Object Types Supported: Device Object:
No dynamic Creation or Deletion supported
No proprietary object types or properties supported
Device Object:
Optional Properties Supported:
Daylight_Savings_Time
Description
Location
Local_Date
Local_Time
Max_Info_Frames
Max_Master
Profile_Name
UTC_Offset
Standard Properties Used In a Non-standard Way:
Process_Identifier
Recipient

34. PcoWeb BacNet Writable Properties: APDU_Timeout Daylight_Savings_Time
Description
Location
Max_Info_Frames
Max_Master
Number_Of_APDU_Retries
Object_Identifier
Process_Identifier
Recipient
UTC_Offset
Property Range Restrictions:
Description, Location (limited to 64 characters)

35. PcoWeb BacNet Analog Value Objects: Optional Properties Supported:
Acked_Transitions
Deadband
Description
Event_Enable
Event_Time_Stamps
High_Limit
Low_Limit
Notify_Type
Reliability
Time_Delay
Standard Properties Used In a Non-standard Way:
Ack_Required
Issue_Confirmed_Notifications
Priority
Writable Properties:
Limit_Enable
Object_Name
Present_Value
Units
Property Range Restrictions:
Description (limited to 64 characters)
Object_Name (limited to 32 characters)

36. PcoWeb BacNet Binary Value Objects: Optional Properties Supported:
Acked_Transitions
Active_Text
Alarm_Value
Description
Event_Enable
Event_Time_Stamps
Inactive_Text
Notify_Type
Reliability
Time_Delay
Standard Properties Used In a Non-standard Way:
Ack_Required
Issue_Confirmed_Notifications
Priority
Writable Properties:
Object_Name
Present_Value
Property Range Restrictions:
Description (limited to 64 characters)
Object_Name, Active_Text, Inactive_Text (limited to 32 characters)

37. PcoWeb BacNet Object Support of Intrinsic Alarming
In lieu of full support for Notification Class objects, the intrinsic alarming features of AV and BV objects determine the destination for event notifications using added properties in the Device object, and individual AV and BV objects:
The Device object includes these standard properties used in a non-standard manner
Recipient writable, representing the device instance to send event notifications to.
Process_Identifier writable, representing the process identifier of the recipient process in the device to which notifications are sent.
The AV and BV objects include these standard properties used in a non-standard manner
Issue_Confirmed_Notifications writable, whether alarms from this object should be sent as confirmed or unconfirmed.
Ack_Required writable, whether alarms from this object require individual human acknowledgement.
Priority writable, what the alarm priority for this object is in event notifications (note that all transitions use the same priority)
The AV and BV objects include alarm detection and reporting logic to implement high/low limit alarming for AV and Change-Of-State alarming for BV. The detection algorithms behave as described in , and of for standard intrinsic alarming. The resulting event notifications are reported to a single destination specified device configuration. The Description property is used as the alarm message description in event notifications.
Data Link Layer Options:
Ethernet (clause 7), BACnet/IP (Annex J), MS/TP master (Clause 9), baud rate(s): 9600, 19200, 38400
Device Address Binding:
Static device binding is not supported. (No client functionality is included).
Networking Options:
None
Character Sets Supported:
ANSI X3.4

38. PcoWeb BacNet

39. PcoWeb BacNet
BACnet LAN Type: select the protocol to use BACnet/IP or BACnet Ethernet.
BACnetIP UDP: if BACnetIP is used then a UDP port must be assigned, the default port for BACnet is “BAC0” hexadecimal.
pCOWeb Device Instance: This is the device instance of the pCOWeb on the network. It defaults to but can be set from 0 to Every device on the network must have a unique instance number.
Description: A 64 character field that can be used to describe the device.
Location: A 64 character field that can be used to describe the physical location.
APDU Timeout: Indicates the amount of time in milliseconds between retransmission of an APDU requiring acknowledgement for which no acknowledgement has been received. The default setting of this property is 5000milliseconds. This value must be non-zero if the APDU Retries is non-zero. In order to achieve reliable communication, it is recommended that the value of the APDU Timeout be the same in all intercommunicating devices.
APDU Retries: Indicates the maximum number of times that an APDU shall be retransmitted. The default value is 3. If the value of this property is non-zero, then the APDU Timeout field must be non-zero.
Password for Restart: This is the reinitialize password. The default is The value can up to 9 characters long. It is required from the responding BACnet-user prior to executing the ReinitializeDevice service.
Alarm Parameters:
Alarming Enabled: Set to yes to enable the intrinsic alarming features of AV and BV objects.
Alarm Destination Device Inst: Insert the device instance of the destination for the alarms. Allowable range is
Alarm Process Id: Insert the process Id or handle which is meaningfull to the alarm destination device. This handle will be used to identify the process within the destination device that should receive the alarm notification.
Interval to send WhoIs: The pCOWeb will send a WhoIs command to the alarm destination device. WhoIs will continuely be sent at the interval provided until a valid response is received. Setting this value to 0 will disable this command.
Clock Parameters:
Daylight Saving Time: Check yes if it is required to automatically track daylight savings time.
UTC offset: Universal Time Coordinated offset is used to enter an offset in minute resolution. The UTC time zone is GMT (or Zulu time in military terms). For example you would enter -300 to get Eastern Standard Time (EST).
Submit Button:
Pressing the “submit” button will save your changes. Then you must reboot the pCOWeb by pressing the reset button on the card or by resetting power to the pCO* controller.

40. BACset Tool
From the BACset tool you can add descriptions and set point limits for the BACnet side.

41. Compatibility

42. Plugins
Installation
Configuration -> plugins
WITHOUT PLUGINS

43. Plugins Connect via FTP to your pCO Web: login : HTTPADMIN
psw : fhttpadmin
copy the folder “install-plug-xxxx” into “/usr/local/root/flash/http/” directory.

44. Plugins
The web page shows a new link “Install/uninstall plugins” for install the plugin

45. Plugins Installation report Report messagges:
[ ok ] installation correct
[ Yet present ] file is already present
[!!!] installation not correct.

46. Plugins
Uninstall plugins

47. FTP configuration Address of your FTP Server
FTP Server Port (default is 21)
FTP Login ID
FTP Server Password
Path to your FTP directory
The output file name. We suggest using an XML extension, since the file is in XML format
Pause (in seconds) between executions of the FTP push routine
IP Address of your proxy server (if you do not use a proxy server, leave this blank)
Comm port of your proxy server (if you do not use a proxy server, leave this blank)

48. Example .XML <?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2005 rel. 3 U ( by Alessandro Schiavo (Carel S.p.A.) -->
<PCOWEB>
<SYSTEM>
<HOSTNAME>localhost</HOSTNAME>
<DATE> </DATE>
<IP_ADDRESS/>
<MAC_ADDRESS>00:0a:5c:10:00:06</MAC_ADDRESS>
<UPTIME>1d5h54mn</UPTIME>
<SYS_VERSION>B1.1.4be</SYS_VERSION>
<APP_VERSION>A1.2.6be</APP_VERSION>
<SEPARATOR_CHAR>.</SEPARATOR_CHAR>
</SYSTEM>
<PCO>
<PCONAME>Prova PcoWeb</PCONAME>
<PCOID>1</PCOID>
<DIGITAL>
<VARIABLE>
<INDEX>1</INDEX>
<VALUE>0</VALUE>
<PAR_DESCRIPTIONS>
<NAME>Al_hp_1</NAME>
<DESCRIPTION>
<EN>High pressure compressor 1</EN>
<IT>Alta pressione compressore 1</IT>
</DESCRIPTION>
<CODE>
<EN>HP1</EN>
<IT>HP1</IT>
</CODE>
<EXTD_DESCRIPTION>
<EN>High pressure circuit 1, chiller 2</EN>
<IT>Alta pressione circuito 1, chiller 2</IT>
</EXTD_DESCRIPTION>
</PAR_DESCRIPTIONS>
<OPTIONS>
<UNIT>--</UNIT>
<MIN>0</MIN>
<MAX>1</MAX>
<RW>R</RW>
</OPTIONS>
</VARIABLE>

49. NTP
NTP
Network Time Protocol (NTP) is a system for the synchronization of computers clock time through the Internet; developed mainly near the Delaware university in the United States. They have been some defined 3 versions: the 1 in 1988, the 2 in 1989 and the 3 in The running version is 3, compatible with the previous ones. In order to facilitate the use of the NTP on notebook have defined the simplified version NTP (SNTP 1995).
The main characteristics of the NTP are following:
Is completely automatic and maintains the synchronization.
It’s possible to use with all types of computers.
Resistant to the breakdowns.
It diffuses UTC time, therefore is independent from time zone and the daylight time.
The synchronization precision is until 1 millisecond.

50. NTP Configuration

51. PcoWeb Firmware

52. Download Firmware

53. Tests

54. Tests

55. Tests

56. How to download/upload a page
An FTP client is required. (i.e. Explorer, TotalCommander, WS_FTP, SmartFTP, …)
Explorer: open Total Commander:
Login: Username: httpadmin, password: fhttpadmin
Root directory: ftp://
The new board have only 1 file: index.html Originale (R): /usr/local/root/defindex.html User (R/W): /usr/local/root/flash/http/index.html
Copy/Delete/Rename files is like your local disk (Drag&Drop)

57. How to download/upload a page

58. How to download/upload a page

59. How to create a WEB page You must know the HTML language
Pages must include the following lines(within the firsts 10 line) <!—tagparser=“/pcotagfilt”-->
Special tags (most common)
Read variable: <%VAR(0,t,i)%>
Write variable: GET method name=“script:var(0,t,i,min,max)” t=type. 1:digital, 2: analog, 3:integer. i=index 1…199 (Digital), 1…127 (Analogic, Integer). min, max=minimum/maximum value (i.e for analog)

60. Test page Test Page Show temperature, setpoint, cooling
Change Setpoint

61. Remarks
You can customize all pages (index, configuration ,etc) Use the system ones as template
Browser / View HTML command: You don’t see the real source HTML files. Carel tags are replaced with value.
Flash Memory
Reserved Area (about 4MB) Contains operating system and pages configuration. It isn’t possible to damage the content.
User Area (about 4MB) User pages are stored here.
When pCO WEB boots, firmware is copied into RAM, then continue to boot from RAM. System uses conf.params in RAM (important if you press the button)

62. Useful Address Index.html (user) Browser: 172.16.0.1
FTP:/usr/local/root/flash/http/index.html
Web administrator page (original)
Browser: /config/adminpage.html
FTP:/usr/local/root/flash/config/adminpage.html
KSA site
download/support/communication&protocols/pcoweb
INFO

63. pCOWeb vs. WebGate PLUS self-powered Linux embedded
high power and memory (10 times the WebGate)
BACnet gateway
SNMP alarm management (TRAP)
easy to install (DHCP)
4MB vs 500kB for html pages
FTP Push & NTP
MINUS
for pCO* family only (except pCOB*)

64. Contact
Alessandro Schiavo Product Specialist - Communication & Protocols Marketing Dept.
direct (+39)