Home > FAQ


1. FAQ of Device


Q1: How to change IP address of device?


Step1: make sure PC can ping the device successfully.




The default IP address of device is: 192.168.0.XX, that is IP segment 0

The address of device and PC shall be set and kept at the identical IP segment. For example, if the device IP is, while the IP of PC is, you should set the IP of PC as example), make the PC and device IP in the same IP segment, thus the TCP/IP communication can be set up, and then change the IP of device and IP of PC as you expected.


The default IP address of RF900 is:

The default IP of RF960-4/8/16/32 is start from, and so on, for example, IP address of zone 1-2 is, IP of zone 3-4 is, IP of zone 5-6 is…..


Step 2: Make sure you know the current IP of device.

If you had modified the IP of device but forgot it, please reset the device to the default IP.

The reset method is : press the black reset button on the mainboard for about 5 seconds, as figure 1 shows:



Figure 1 Reset button


Step 3:

Log in the device by telnet in PC, type "Telnet the IP of device is, enter, as the following figures shows:



Type user name and password:



→Execute the command:

-> setip  x.x.x.x  enter----【Note】x.x.x.x  indicates the IP address.


Step 4: reset the device is OK.


Q2. If Ping test between PC and device failed, what is the likely reason?


1. the device is power off

2. The address of device and PC are not at the identical IP segment(refer to Q1 for more)

3. The problem in the network cable

4. The problem in the switch


Q3. How to update the program of device?


1. Interface used for down load: The Ethernet interface of RF900

2. File name to be downloaded:  RC2910SW-RF900_Vxxxxx.bin

3. Double check the file name and the version with the Manufacture Order!

If anything is uncertain, inquiry your manager.

4. Method: Around 10 sec after power up, under DOS promote, type in command:

tftp – i PUT  RC2910SW-RF900_Vxxxxx.bin

The time used for transmission will be displayed on the screen if command executed successfully.


2. FAQ of RFHelper


Q4. RFHelper installation failed

Answer: Make sure that all the firewall and anti-virus software are closed before the installation


Q5. What are the operating system requirements


WinXP, Win7 Ultimate,Win8 Enterprise or Win 10 Enterprise are OK,pay attention that the simplified version (such as Home version)of the operating system can not be used for Win 7,Win8 or Win 10 except Win XP.

After installation, you need to change the compatibility in Win7, Win8, or Win10 system except Windows Xp

Right-click the RFHelper software icon, choose "property", click "compatibility", as the following figure shows:



Notice: the screen resolution should be 1280*768 and its above.


Q6. Why RFHelper can not link the device?


1. Ping test between PC and device failed (refer to Q2 for more)

2. Ping test between PC and device is successful, but IP address of device error (refer to Q7 for more)

3. Firewall is not closed

4. software compatibility is not set yet(refer to Q5 for more)


Q7. How to connect RFHelper successfully?


step 1 : Make sure Ping test between PC and device is successful(refer to Q1 for more)



After configuring IP of PC, you should configure IP of device, as the following descriptions:

Open RFHelper software, click "Communication" ---" Target device IP", type the device IP address, when the software is first use, it is, otherwise, it is the last used IP.





Note: The IP of PC cannot be configured to be automatically acquired.


3. FAQ of RFview


Q8. RFView installation failed


1. If you have previously installed the software and uninstalled it, you should delete the RFView folder under the installation directory, otherwise, the next installation of RFView may be unsuccessfull, or the RFView can not work normally.

2. Make sure that all the firewall and anti-virus software are closed before the installation

3. During the installation, the flowing box will pop up, please wait it to be closed automatically, do not close manually.


4. please confirm the operation system, WinXP, Win7 Ultimate, Win8 Ultimate or Win 10 Ultimate are OK, pay attention that it must be Ultimate for Win7,Win8 or Win 10 except Win XP.


Q9. Why RFView can not link the device?


1. Firewall is not closed

2. Not to do "add device" operation in RFView software

3. WIFI are not closed in PC

4. The problem in the network cable

5. The problem in the switch

6. the device is power off

7. Ping test between PC and device failed (refer to Q2 for more)

8. Ping test between PC and device is successful, but you type wrong IP address of device in the RFView software


Q10. How to connect RFView successfully?


step 1 : Make sure Ping test between PC and device is successful(refer to Q1 for more)



After configuring IP of PC, you should open RFView software and configure IP of device ,


Q11. Why alarm is not reported on RFView software?

Answer: you need to set the monitor roots on RFView software, type the IP address of PC which you want to report, and change it to enable.




4. Other question


Q12. What kind of Optical fiber cable?

Answer: General Single mode fiber (GYXTW cable) is OK


Q13. What is the selection requirement of ODF?

Answer: Select the ODF with appropriate number of interfaces according to the number of defense zones. It should support SC and FC,includes flange with tail fiber


Q14. How to achieve camera joint-action?


Type 1:

Connects RF900/RF960-x main device to NVR/DVR via contact closure, as shown in Figure 3-1 below:

Note: There are various types of NVR/DVR, please refer to the datasheet of the corresponding NVR/DVR. For the usage of contact closure, please refer to section 4.4 in "OPTICAL FIBER FENCE USER MANUAL".


Figure 14-1 Connects RF900 with NVR/DVR via contact closure


Type 2:

It should be taken into account how to integrate RF900/960-x into other perimeter defense systems and realize a coordinated play, when the project contains many zones, or if there are existing video cameras and DVR/NVR.

In this case, making use of LAN, connects RF900/960-x to PC station where RFView is installed. All of the alarm events from zcones will be collected by RFView, and through RS232/RS485, sent to the external converter that converts RS232/RS485 to contact closures, and then connects the DVR/NVR for video joint-action.

The video joint-action here, means to switch the concerned video to an obvious position on the screen, or drive the PTZ camera to focus on the spot where the intrusion event happened. 



Figure 14-2 RFView in the medium-scale project


Note: in this case, you need to set Relay linkage by RFView software, refer to "Relay linkage" in "RFView User Guide" for more.


Type 3:

For some large-scale perimeter fence project, it may contain many fence technologies, such as infrad, video cameras, microwave, and entrance control, and so on. Fiber optical fence is just one of them. For this application, an integrated management software platform usually exists, and the management for RF900/RF960-X must be integrated into that platform.

Refer to Q17 for more.



Figure 14-3 RFView in the large-scale project


Q15. How to do to support message sending and receiving? 


Plug SMS module that we recommended into the PC where the RFView is installed via RS232 port, set SMS function by RFView software. Refer to "SMS linkage" in "RFView User Guide" for more.


How to select and buy SMS module?

Answer: please purchase USR-GPRS-73 module.


Q17. How to integrate into the 3rd party?


Method 1: Through Modbus protocol

Modbus protocol is a standard master/slave protocol. There is only one Master node. other nodes are slave nodes, and each slave device has a unique address.

Our RF900 and RF960-X devices have already realized the Slave function of Modbus inside. The 3rd-party platform is required to realize the Master function of Modbus, so that the third party platform is the Master node, while RF900 and RF960-X devices are all the Slave nodes, as shown in Figure 17-1.

After the 3rd-party makes its own software interface according to the requirements, it can access and configure our equipment through the standard Modbus protocol, such as deploying/disarming the zone, querying the mode of zone, querying the alarm and alarm output time, etc.



Figure 17-1

Note: Modbus is a master/slave protocol. When there is an intrusion alarm in a zone, the slave node cannot report it actively. The master node had to poll from each node. Thus, the platform might not get the alarm in real time.


Method 2: Through the private protocol of RFView

This way will adopt the server of RFView software directly (including SMS linkage, relay linkage and other functions developed by Raycom). As Figure 17-2 shows

First install the server of RFView on the 3rd party platform, then the 3rd party will do its own UI according to the private protocol of RFview. The management for RF900/RF960-x can be achieved by accessing the server of RFView.



Figure 17-2

  • wechat

    Vivian: VivianMa2000