![]() (While we provide application assistance, it is up to the customer to determine the suitability of the product in their application. Intermapper is a registered trademark of HelpSystems, LLC. For more flexibility, feel free to build your own kit by selecting the individual sensors below. For absolute convenience and no guess work, you'll find a list of sensor kits below which work with InterMapper right out of the box. Installing the custom probe is as simple as copying it into the 'InterMapper Settings:Probes' folder and then telling InterMapper to reload probes. Our Getting Started with OW-SERVER & MeshNet systems in Intermapper article takes you through the initial configuration procedures. For each type of device it monitors, InterMapper requires a probe file which instructs it on how to interact with the device. This probe allows you to view the status of many maps from a top level master map. The other basic probe is the Map Status probe. If Intermapper doesnt receive an SNMP response, the probe is automatically set to ping Echo. Configurable options include IP address, DHCP, LED/Relay behavior, and more. This probe and all SNMP probes cause Intermappers marching ants to show in the map. Begin by providing the network connection to the base unit. The installation of each location consists of one base unit (OW-SERVER or MeshNet Controller) and one or more compatible sensors (up to 7* per base unit). Sensors are available for monitoring:Īll communications with our hardware occur using SNMP enabling you to simultaneously monitor multiple dispersed locations using your existing LANs, WANS, and/or VPNs. The output of the EVAL conditions must be a string, since my format was too big (more than 255 char), it. I want to combine them into a single probe file. The OW-SERVER Intermapper probes support wiring up to 7 1-Wire sensors per server. for now I have two separate probe files for both the devices since both follows different format in Intermapper status window. ![]()
0 Comments
Leave a Reply. |