1 / 47

Class:IVU Advanced Instructor: Jack Floyd Winter 2012

Class:IVU Advanced Instructor: Jack Floyd Winter 2012. Objectives. The purpose of this class How to use the setup featrues of the IVU How to use the software applications associated with the IVU Creating a shadow device in the IVU Custom Equipment and Graphics in the IVU

nelly
Download Presentation

Class:IVU Advanced Instructor: Jack Floyd Winter 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Class:IVU Advanced Instructor: Jack Floyd Winter 2012

  2. Objectives • The purpose of this class • How to use the setup featrues of the IVU • How to use the software applications associated with the IVU • Creating a shadow device in the IVU • Custom Equipment and Graphics in the IVU • IP settings for network connectivity • Provide you with the confidence to approach the IVU and take control of your BAS.

  3. Setting up the ivu

  4. Setting up the IVU • When you first start the IVU it is blank • You will have to create the default admin password! • User: Carrier Password: installer • You have to manually scan the CCN Bus to find all of the equipment that they IVU will be used to control • You need to organize the IVU Tree • Create Areas for more convenient navigation • Create Custom Equipment for proper representation of the buildings equipment layout (if necessary)

  5. Setting up the IVU System Setup

  6. Setting up the IVU SCANNING THE BUS Notice the difference between the blocks used to represent each segment. Always scan your devices prior to building your tree!

  7. What to think about when arranging your IVU Tree? Create Areas that make sense. First Floor Second Floor Manage your sub folders Groups inside of groups are a good way to keep information separated For instance inside of First Floor Area you may have three different Tenant spaces Inside of Tennant space 1 you may have six RTU’s and 10 PIUs that serve that tenant Exhaust fans for the first floor may be on the same controller as the Exhaust fans for the second floor. How do I separate them into their respective areas??? By creating shadow devices. A shadow device is a representation of a specific piece of equipment but without mapping all of the points in a controller. You can have multiple shadow devices attached to one CCN element number, such as a Universal Controller.

  8. Creating Shadow Devices You create shadow devices in the setup screen (same screen where you scan the bus) The menu bar on the right side of your screen has an option to add equipment. Keep in mind that whatever area you have selected is where the equipment will be created. You will need to know what the element number that the device being controlled by to go to the next step.

  9. Creating Shadow Devices Once you click the add equipment tool, you will get a pop up screen as seen here. Notice CCN Device: is highlighted in red. This is the bus and element number of the controller you are attaching the shadow point to. Be sure to change your Display name to the corresponding piece of equipment. i.e. EF-1 You can then load your Equipment and View files. (shown later)

  10. Editing Devices Once you have all of your devices scanned into your tree there are a couple of different options for editing One option is to change the address of the CCN object. Simply click on the change addressing button and you will get the pop up shown here. Enter the Bus and Element number of the device you want to change and enter the new Bus and Element number. Then click change address.

  11. Editing Devices You can also edit a device from the home screen of the IVU. Simply right click the device and choose your selection. Configure – allows you to change equipment and view files System Setup – takes you into system setup Rediscover Tables – scans the device for changes in configuration Reload Control Program – reloads the equipment file associated with this device Copy Properties – copies the properties to other devices with same control program Copy Path – copies the path of the device to be used in building view files

  12. General Tab The General Tab (found by going to System Options and clicking on the General Tab) is used for several different functions in the IVU. General Tab holds the IVU Server and Gateway Element numbers It holds the current time, as well as the option to broadcast time to the bus. It also holds the Management Tool link for configuring the IVU IP information and creating or restoring backups of the IVU Server.

  13. Management Tool

  14. Manual Commands The IVU is a computer, and will respond to manual commands much like a dos prompt in a PC. A list of manual commands can be found in the IVU help menu, which is part of every IVU server. Simply click on the help menu button (?) and the help files will launch in a separate browser window. Manual commands can be used to do functions like reboot the server or modstat (status of the module you currently have highlighted. The Help menu is very extensive and very user friendly. It features a navigation tree, an index, as well as a search function to help you along the way.

  15. Manual Commands Whereami – displays the full path of your current location Whoson – displays a list of all users currently logged in, their IP address, and how long it has been since they were active Rebootserver – restarts the IVU server Commstat – complete set of diagnostic information Logoffuser x – logs off a user without warning, where x is the user name Modstat – displays status of the controler Notify – sends a message to all users currently logged into the system Ping – verify communication between two IP address

  16. ModStat

  17. application Builder Building Equipment Files

  18. Application builder is used to create custom equipment files for universal controllers and comfort controllers • These files are typically attached to shadow devices

  19. Building an Equipment File • Before creating the equipment file, you need to have the following: 1. Name of the device 2. Points List 3. Type of Equipment (CCN only, integration, CCN Link)

  20. Building an Equipment File • This example will be CCN Values only (most common type) • Don’t forget to name your Equipment, this will also be the file Name when created at the end of the process. • Select schedule and Set point type (whether or not control will be given to the user.)

  21. Building an Equipment File • There are several options you can implement in your equipment file. Electric meter, water or gas meter, etc. • These supplement your file with added prebuilt features

  22. Building an Equipment File • There are four types of points you can use to create your file. Each point must be properly mapped to the desired point in the controller. This can be done with the copy and paste function while connected to the IVU • Analog read CCN • Analog write CCN • Binary read CCN • Carrier Text • Each point must be created, mapped, and referenced individually.

  23. Building an Equipment File

  24. Building an Equipment File

  25. Building an Equipment File

  26. Building an Equipment File • Once you have created all your points and successfully mapped them, you can finish (save) your equipment file. • Notice that when you save the file, two files are actually created. The equipment file, and a view file.

  27. View builder

  28. View builder is used to create custom graphics for the IVU

  29. View Builder • The IVU by nature creates automatic graphical representations for all Carrier Canned Controllers. • View Builder allows you to create custom graphics for Programmable controllers. • Floor plans with color bubbles • Custom Air Handlers and Equipment • Exhaust fans • Multiple pieces of equipment that are controlled by the same Programmable controller • Slide bars and set points

  30. Much like Application Builder, you have to map the points that you want to reference in the graphic. • The same copy and paste function applies to graphics as does in Application Builder. • You can map a piece of equipment • A specific point from a controller • Reference the Space Temperature in a graphic from multiple controllers • As well as show the status of a controller on a floor plan

  31. Mapping an equipment path

  32. Mapping a piece of Equipment

  33. Add Control menu • The add control menu allows you to insert specific points for mapping

  34. Formatting devices • Positioning and Drawing tools allow you to bring devices to the front and back of the screen • To draw custom blocks • Align devices horizontally and vertically • As well as adjust the colors and backgrounds

  35. Adding Controls • The add control menu allows for inserting numeric point values • Binary point values • Slide bars • Toggle buttons • Set Point adjustments • Equipment color bubbles

  36. Add Images • Add Image menu allows you to add custom images • Add fans, ductwork, or sensor images for representation • The image library comes standard with the IVU installation software

  37. Add Symbol • Add symbol menu allows access to the image library with a kick! • These images are preconfigured to us command and status points to change the graphical image that is displayed based on the state of the point it is mapped to.

  38. Examples of Symbols • Some examples include • Fan turning or static based on a fan status input • Damper position representation that is proportionate to the actual position of the damper • Valve position representation based on the position of a valve. • Cooling/Heating coil color based on the cooling/heating command

  39. Microblock Properties • The microblock properties are represented in the menu displayed here. • Microblock path is the path of the referenced point • You can adjust configurations such as if the point is editable, max decimal points, and units of measure.

  40. Toggle Button • The Toggle Button is used to display different images based on the status of a binary point • Notice the Images off and Images on field. • You can select custom images to be displayed based on the on or off position of a binary point.

  41. Image List • The Image List control is used to display a graphical representation of an analog point. • You could display 10 different images (one at a time) based off of the current position of an analog point.

  42. Image List • Notice that when the first expression is highlighted, the formula is displayed in the bottom Expression field. • For 0_75 image, the present value must be below 5% in the analog point being referenced.

  43. Image List • Notice that when the last expression is highlighted, the formula is displayed in the bottom Expression field. • For 100_75 image, the present value must be greater than or equal to 100% in the analog point being referenced.

  44. View Builder • Graphics can be as detailed or as simplified as you make them • Any point inside the IVU can be inserted as a graphical representation. • Please keep in mind that just because a graphic depicts an object in the IVU is moving (such as a fan turning) that it is still a graphical representation and could be referencing a commanded state opposed to an actual status of the point being referenced.

  45. Troubleshooting • Graphal Representations are just that, representations. • Human error can be misleading. If a point is mapped incorrectly they can be misleading. • Equipment files can be just as bad, what if you installed a job and new it was correct, but a month after you completed the project, someone else accidentally deleted the equipment file out of a shadow device???

  46. Common Issues • The IVU while being a good product does have its flaws. • Common issues known to date include, hard drive failures, battery life, incorrectly mapped points, and early versions of IVU (4.0) faulty operating systems (Lennox). • While controls and graphical representations can be a great troubleshooting tool, they cannot replace a technician with experience and eyes on troubleshooting.

  47. The End!DDC 101 - 2012

More Related