The power to the sensorProbe may be lost. Check the red LED. It should be steadily lit.
The device is not hooked up properly with the LAN/network/Patch cable. Check the green LED. It should be steadily lit.
The PC used to configure the sensorProbe is on a different subnet than the device. Note: IPSet.exe will not work across routers. It will work across switches and hubs.
Try to connect a crossover cable from a computer directly to the sensorProbe. This is the recommended method to set up the sensorProbe.
Yes, the following steps will help in setting up the IP address.
Find out the IP address of your network adapter by entering the command "ipconfig" at the command prompt.
Add the IP address of the sensorProbe to the routing table by entering
route add 192.168.0.100 x.x.x.x
where x.x.x.x is the IP address of the network adapter
Add an entry to ARP table by entering
arp -s 192.168.0.100 xx-xx-xx-xx-xx-xx
where xx-xx-xx-xx-xx-xx is the MAC address of your sensorProbe.
Ping 192.168.0.100 with a buffer size of 89 bytes. (Ping -l 89 192.168.0.100). If the unit replies and the ping works, then open up a web browser and navigate to the web interface of the device by typing the IP of the device into the browser.
The proxy settings of the browser may be preventing the access to the device. Please disable the proxy settings to access the web interface.
You have updated the micro code of the firmware, but you have not updated the html code. Html code updates have to be done after a micro code update is done.
For changing the Traps to HP OpenView style, you need to send an SNMP command to the device given below:
snmpset .1.3.6.1.4.1.3854.1.2.2.1.60.0 i X
Where IP is the IP address of the sensorProbe. Community default is "public". and X can take 3 values: 1 (WhatsUP gold style), 2 (HP OpenView Style), 3(both Style). By default, the X value set is 1.
This happens when the device is not able to find the IP entered. When a gateway address is entered, the device searches for that host. If it finds that host, it will accept the IP entered. If that host does not respond, it will revert back to the default IP.
I assume that you are using an opto-isolated type of the dry contacts since there is no need to input voltage to the dry contacts that are configured as non-isolated. The dry contacts are designed to have the current on LED in range of 5 to 27mA with 680ohm resister connected internally. The input voltage is then ranging from 5 to 20Volts. So, the maximum voltage that can be put on the dry contact is 20 Volts. This is true for both sensorProbe8-X20 and X60.
Assume you want to input 48V to the dry contacts whether it is opto-isolated or not, you can connect an external resistor at the input pin of the dry contacts. This external resistor will be serial to the 680ohm internal resistor. Let's allow 10mA current to flow in to the LED of the opto; thus, the external resistor value is (48V/10mA) - 680ohm = 4120ohm. A more common value would be 4.7Kohm.
If 4.7K is used, there exist the current of (48V/5380ohm) = 9mA. The power on the resistor is about (9mA)^2 * 4.7K = 0.38 watts. Thus, the 0.5 watt resistor should be enough.
To conclude, putting the external resistor at the input pin of the dry contacts will help prevent the resistors on the board to burn out even though the circuit is not opto-isolated and some voltage is put on the input of the dry contacts.
You can also use the traps to provide, as something called a system heartbeat. To do this you can configure an unused dry contact input. Place it into an alarm state. Configure traps to be resent every a certain period of time (for example, 10 seconds). This should provide you with the heartbeat that you need.
Please note that traps are not guaranteed to be delivered. So they can be lost in transmission without any error indication. On big network management installations traps and polling are used in combination. Traps are used to provide an immediate notification of a problem and also to reduce network traffic. The traps are then combined with periodic polling of the sensors, but at a less frequent rate in order to reduce network bandwidth utilization.
The Digital Voltmeter and 4-20mA sensors have an input as analog signal which will be converted to digital using an A/D converter. Normally, the A/D converter is calibrated in production process. But, you also can do it by following the steps below.
On the web interface, turn off an Autosense for port#1. To do this,
Go to the Sensor setting on the web interface by clicking on a "Sensor" tab.
On the bottom of the left side menu, click on "Autosense".
Select "Disable" for the port# 1. Then, click "Save".
Connect 1.25VDC to RJ45 port# 1. The 1.25V is the voltage across pin 7 and 8 of the cable plugged into the RJ45 port.
Set a Digital Voltmeter sensor online on this port. We only focus on a Raw Analog, so you do not need to change any settings.
a. Go to the setting page of the DC sensor at port# 1. Select "Online" for Go Online/Offline field. Then, click "Save".
Run snmpset command as
snmpset .1.3.6.1.4.1.3854.1.2.2.1.80.0 i 0
Replace with the IP address of your sensorProbe, and with the administrator password.
The raw analog reading from the web interface should read
500 (+/-5).
Please note that all RJ45 ports use the same A/D converter. Therefore, the calibration on any port will also have an effect for other ports. And, an error for each sensor is different due to components (e.g. resistors, capacitors) on the sensor. So, it is possible that the same input value will not be read the same for different sensors on the same sensorProbe.
In the calibration process, we set the offset of the reference voltage so that the raw analog read 500 when the input to the RJ45 port is 1.25 volts. However, the sensor that you are using may still have error due to some components (e.g. resistors and capacitors). Run snmpset command as:
snmpset .1.3.6.1.4.1.3854.1.2.2.1.96. i
where
<IP> is the IP address of your sensorProbe.
<community> is the administrator password.
<port-1> is the port number where the sensor for which you want to adjust the offset is plugged in.
<offset> is the offset value. It should be in a range from 485 to 515.
You will need an external AC voltage sensor/transducer. Then, you can integrate it with the sensorProbe via a Digital Voltmeter sensor or a 4-20mA voltage sensor. Therefore, please make sure that the AC voltage sensor/transducer have an output as either Digital Voltmeter or 4-20mA.
The output of the AC voltage sensor/transducer should be linearized to work best when integrated with the sensorProbe. There is a custom setting section on the Digital Voltmeter and 4-20mA sensor web interface where the unit of a measured entity (AC voltage in this case) can be customized to any text such as "V(rms)" for measuring the RMS voltage.
Note: some sensor/transducer may need a power supply which you have to provide as well.
You can extend the software set on the sensorProbe8Linux or the cameraProbe8.. Nagios is one of many programs that we port, for instance. We also port RRDTool which is a data logging and graphing tool and integrate it to display a graph for our sensors data. On the Summary page of your device, click on "View Graph" of any sensor; then, you will see RRDTool graph there.
The root file system is read-only; therefore, you will need to copy them to a user partition which is editable.
Create a copy of configuration files for Nagios: The place where you can write (create directories and files) is in "/flash1/user" directory. I would recommend you create a directory for all Nagios configuration files as "/flash1/user/nagios/etc"
#/ mkdir -p /flash1/user/nagios/etc
Then, copy all files from "/usr/nagios/etc" to "/flash1/user/nagios/etc"
#/ cp /usr/nagios/etc/* /flash1/user/nagios/etc/
Edit configuration files: You can now edit the configuration files to the way you would like the Nagios to work. You can use "vi" on the sensorProbe8Linux/cameraProbe8 to edit the files.
You also need to modify the files "nagios.cfg" and "cgi.cfg" since some entries inside these files refer to the path "/usr/nagios/etc" instead of "/flash1/user/nagios/etc".
In "vi", you can use the following command to replace all entries.
:%s;/usr/nagios/etc/;/flash1/user/nagios/etc/;g
Start Nagios: the script that is used to start Nagios is also in read-only partition.
You then need to create a file "/flash1/user/etc/nagios" and add the line "NAGIOS_CFG=/flash1/user/nagios/etc/nagios.cfg" to this file and save it.
Then, on the web interface, check the box in front of Nagios on the "System Setup" page and click "Save".
The Nagios web interface is integrated to the "Application" tab. The username and password are fixed.
The username is "nagiosadmin", and the password is "admin".
There are two modes of data storage/graphing on the sP8L: RRD and JavaScript.
If JavaScript graphing is used, the device has enough memory to save 8,640 data points for each sensor. This corresponds to 90 days at a frequency of 15 minutes, or 6 days at a frequency of 1 minute.
35,040 data points for each sensor can be stored in the RRD Tools database. If data is recorded every 15 minutes, then there will be enough data to display measurements for up to 1 year. Besides the increased data capacity, RRD is a highly versatile memory storage tool.
Graphs can be plotted by the RRD Tool, into the web-based user interface. The individual graph (day, week, month, and year) for each sensor type can be customized, simply by modifying the script template used to generate a particular graph.
On our Linux devices, the flash partition for sensor data / graph storage is 32Mbytes. We cannot change this until we start shipping with larger flash. That will probably happen in a month or so - we are currently in the process of upgrading the CPU / Flash board on the sP8L.
Because each temperature sensor connected to our Linux devices is given its own unique OID (Object Identification) on the network, you can also use a freeware MRTG program to graph the temperatures on a PC or remote website. The MRTG tool will poll the sensors OID's and store the data in a graph. In this way you could expand the memory for data storage indefinitely. We can help you to set up your MRTG tool, and provide simple scripts to help you get started.
Our product has ability to integrate with custom sensors via our Digital Voltmeter sensor or 4-20mA sensor. For integration with custom sensors, the unit text can be customized to whatever you would like; this text is reflected on the summary page of the web interface. All numbers are displayed in decimal format.
On the DC and 4-20mA sensor configuration pages, you can display readings either as absolute values or as a percentage of full scale; you can customize a unit for measured entity. The external sensor used should have an output as a linearized Digital Voltmeter or 4-20mA signal
We suggest you find sensors that will best suit your requirements, and then we will make sure they can integrate with the SP2.
For example we have customers that use our Digital Voltmeter sensor to integrate pressure sensors and water salinity sensors. We even have customers measuring radiation using our sensorProbes. The user can easily input their own labels and output value scales.
If you label the sensor output as MPa, sensor values will appear on the summary page and in emails as MPa. You can configure the scale to be absolute such as 0-100 VAC or a percentage such as 0-100%.
The data stored and graphs plotted on the sensorProbe will also have the correct labels and scaled units.
Note: Emails and SMS will also be displayed in the configured units at the correct scale.
4-20mA signals are very popular in industrial sensors, and are particularly resistant to interference from electromagnetic noise.
Note that some sensors and transducers may require an extra power supply, and in some cases may need other electrical components.
You can adjust the sensitivity of the motion detector using the sensor status filter.
The sensor status filter allows you to enter a time delay that must occur before the sensor changes status - thus filtering out noise in the signal. This avoids unnecessary sending of notifications, as fluctuations can occur during normal working conditions.
To find this, go to the Motion Sensor Settings page of the web interface, and click on the sensor status filters button. Change the "Continuous time (secs) sensor is to report" field to some value other than zero. I suggest 1.
The accuracy of our 4-20mA converters is 2%.
The resolution of our 4-20mA converters is 0.1mA.
You can use these figures in conjunction with your sensor's accuracy to find the overall precision of your readings.
You can also calibrate the 4-20mA converter.
This firmware upgrade is for:
sensorProbe2
sensorProbe2-DC
sensorProbe8
sensorProbe8-X20
sensorProbe8-X60
Instructions:
Download the .zip file and extract its contents to a folder on your computer. The extracted folder should include the following files:
IPSetX.X.X.X.exe - this is the program that will load the firmware onto the sensorProbe
spX_firmware_DD_MONTH_YY.zip - this file contains the firmware files
readme.txt - contains basic instructions
We recommend you connect your computer to you sensorProbe using a crossover cable for the upgrade procedure.
Start the program IPSet
Click the System Upgrade button
Enter the IP address of your sensorProbe
Enter the password for your sensorProbe
Enter the name and location of your firmware file - e.g. c:\akcp\ spX_firmware_DD_MONTH_YY.zip
Click the Update button
For support, please contact techsupport@gridconnect.com
Further questions:
I have downloaded the .zip file. How do I update my firmware?
Unzip the downloaded file to a folder on you computer, and follow the instructions in this file.
After installing the updates, do I need to configure anything?
No. After installing the updates, the device will restart. Historical sensor data will be lost (you can download this data before you begin the upgrade). All configuration settings that you have made (mail settings, sensor descriptions etc) will remain intact.
On our Linux based products, (cP8, sP8L), there is an option to backup all configuration settings to a file - you can access this option from the settings page. This is for your peace of mind in case of a system crash.
You can also backup you configuration files for peace of mind on sP2 and sP8 devices - use our application configure2.x to do this. You can download the application from our website, or send an email to techsupport@gridconnect.com.
Will this update erase my existing settings?
No. Your settings will remain the same.
Can I perform the upgrade over the internet?
We recommend you perform the upgrade by connecting your sensorProbe to your PC using a crossover cable.
However, it is also possible to upgrade the firmware over the internet. It may be slow, and you will need to open up ports on the routers you are using, but it works. There is no special procedure for doing this - simply perform the upgrade in the normal way, using our GUI upgrade tool for the sP2 and sP8, or the upgrade section of the web interface on the Linux based systems.
The firmware upgrade routine checks the integrity of the uploaded code. We have enough memory on the sensorProbes to store the whole upload code before we do the flash upgrade.
So if the connection breaks or the data transfer has errors, the flash upgrade won't be started, and the old code will remain functional.
For the sensorProbe (sP2, sP8), we use TFTP (UDP port 69) for firmware upgrades.
Where can I get more information or help?
Please send an email to techsupport@gridconnect.com. We aim to answer all support emails within a few hours.
This firmware upgrade is for:
CameraProbe8
sensorProbe8Linux
sensorProbe8L-X20
sensorProbe8L-X60
Download the firmware_cp-XXX.zipfile and extract its contents to a folder on your computer. The extracted folder should include the following files:
lnuxIPSetX.X.X.X.exe - this program can be used to load the firmware onto the sensorProbe, if you can't access the web interface
cp-XXXx.bin - this file contains the firmware
We recommend you connect your computer to you sensorProbe using a crossover cable for the upgrade procedure.
Log in to the web interface of your sensorProbe8Linux/
cameraProbe8, as administrator
Select the Setup tab
Click Maintenance in the menu on the left side of the web interface
Click the Upgrade button under System Firmware Upgrade
You will get a warning message about rebooting the device into upgrade mode - click OK to continue
The device will reboot into upgrade mode - this will take about 30 seconds, after which you will be redirected to the upgrade mode page
Follow the on-screen instructions, and when prompted to select the firmware file to upload, click the Browse button and navigate to the directory holding the file "cp-xxx.bin". Select this file to open.
Next, click the "Upgrade" button. The upgrade process will take about 60 minutes.
The upgrade should finish without any error, and you will recieve a message saying "Upgrade Complete". The cameraProbe8/ sensorProbe8Linux will automatically reboot to the normal mode.
Note: You may receive a timeout error message from the web browser while it is reloading a web interface. Just ignore it, and open the web interface by entering the IP address of the cameraProbe8/ sensroProbe8 into the web browser.
The upgrade is now finished. On the web interface, click the "Setup" tab. On the System Description line, it should say version number "CP-MXLVxxx".
Further questions:
I have downloaded the .zip file. How do I update my firmware?
Unzip the downloaded file to a folder on you computer, and follow the instructions in this file.
After installing the updates, do I need to configure anything?
No. After installing the updates, the device will restart. Historical sensor data will be lost (you can download this data before you begin the upgrade). All configuration settings that you have made (mail settings, sensor descriptions etc) will remain intact.
On our Linux based products, (cP8, sP8L), there is an option to backup all configuration settings to a file - you can access this option from the settings page. This is for your peace of mind in case of a system crash.
Will this update erase my existing settings?
No. Your settings will remain the same.
Can I perform the upgrade over the internet?
We recommend you perform the upgrade by connecting your sensorProbe to your PC using a crossover cable.
However, it is also possible to upgrade the firmware over the internet. It may be slow, and you will need to open up ports on the routers you are using, but it works. There is no special procedure for doing this - simply perform the upgrade in the normal way, using our GUI upgrade tool for the sP2 and sP8, or the upgrade section of the web interface on the Linux based systems.
The firmware upgrade routine checks the integrity of the uploaded code. We have enough memory on the sensorProbes to store the whole upload code before we do the flash upgrade.
So if the connection breaks or the data transfer has errors, the flash upgrade won't be started, and the old code will remain functional.
For linux models of the sensorProbe (sP8L, cP8), we use HTTP (TCP port 80) for firmware upgrades.
Where can I get more information or help?
Please send an email to techsupport@gridconnect.com. We aim to answer all support emails within a few hours.
Our sensorProbe8Linux, securityProbe and cameraProbe8 (USB) products support the following WiFi adapters:
PLANET 54Mbps Wireless LAN USB Adapter (model: WL-U356)
X-Micro WLAN 11g 54Mbps USB Adapter (model: XWL-11GUZX)
These WiFi adapters use the ZD1211 chipset, which includes Linux drivers.
Check that the camera is connected, enabled, and all your cameras use the same video format (NTSC or PAL). To do this, go to the settings tab, click Camera Settings, and then click Advanced Camera Settings. On the page that is displayed, first press the Check Video System radio button at the top of the page. This will scan the device for connected cameras, which may take a few seconds. Once the system has found your cameras, check the Enable Camera box for all the cameras you would like to enable. You can click the Preview button to display the camera image temporarily in a pop-up window. If you cameras are not detected, please send an email to techsupport@gridconnect.com. Please note that all the connected cameras should have the same video format (NTSC or PAL), to ensure the images are displayed correctly.
![[Search]](http://site.gridconnect.com/web/gridsb01_t.jpg){kind=small}
