background image

RF400 Loggers Trouble Shooting Guide

 

Issue 1 

 Oct 2019 

 

The Professionals’ Choice

 

 

Comark Instruments  
52 Hurricane Way, Norwich, Norfolk, NR6 6JB, UK 
Tel: +44 207 942 0712 
www.comarkinstruments.com 
 
Comark Instruments 
PO Box 500, Beaverton, OR 97077, USA 
Tel (503) 643 5204  
www.comarkUSA.com 
  

 

Comark RF400 

Comark RF400 Help Guide 

 Troubleshooting 

Forced Connection and Transmission 

It’s possible to get the 

RF400 Logger to reconnect to a network and upload any unsent readings to the Comark 

Cloud. To do this hold down the button on the front of the RF400 Logger and it will beep once. Keep the button 
pressed until the RF400 Logger beeps again then release the button. This will force a connection and transmission. 

Signal Strength 

The RF400 Logger reports its current signal strength to the Comark Cloud 
every time it communicates. It is possible to get real time signal strength 
from the RF400 Logger to aid installation issues. To do this hold down the 
button on the front the RF400 Logger and it will beep once. Keep the button 
pressed until the RF400 Logger beeps two more times, then release the 
button. The RF400 Logger will start beeping in relation to the signal strength. 
Fast beeping is a good signal, slow beeping is a poor signal. In addition, the 
LED on the button will flash green indicating a good signal, orange indicating 
a medium signal and red for a poor signal. Press the button once more to 
end signal test. Signal strength will only work if the RF400 Logger has been 
set up to talk to the Comark Cloud. Signal strength test will automatically 
end after 1 minute. 

LED & Buzzer Patterns During Normal Operation 

 

  

Quick Green LED every 5 seconds 

Normal operation 

 battery power 

  

Solid Green LED 

Normal operation 

 external power 

  

Red LED every 5 seconds 

Alarm Active 

  

Quick Red LED every 5 seconds 

Alarm mute 

  

Quick Orange LED 
(short beep every 30 min) 

Generic Fault e.g. Lost network connection or missing probe 

 battery 

power 

  

Solid Orange LED 
(short beep every 30 min) 

Generic Fault e.g. Lost network connection or missing probe 

 external 

power 

 

 

 

Summary of Contents for COMARK RF400

Page 1: ...es To do this hold down the button on the front the RF400 Logger and it will beep once Keep the button pressed until the RF400 Logger beeps two more times then release the button The RF400 Logger will start beeping in relation to the signal strength Fast beeping is a good signal slow beeping is a poor signal In addition the LED on the button will flash green indicating a good signal orange indicat...

Page 2: ...of the RF400 Logger The App will verify that the RF400 Logger is registered to the Comark Cloud account which the user has signed into before showing any information This is a security feature to prevent anybody with an App reading any RF400 Logger When the RF400 Logger detects the NFC from the device it will beep once If I have a power cut or my WiFi network stops working will I lose any of the d...

Page 3: ... to be allocated an IP Address Normally the DHCP service runs in either your router or on a network server Make sure that the configured DHCP IP address range allows the addition of new devices if not then extend the range 9 If your wireless network uses WPA Enterprise make sure that the correct authentication type is selected from the drop down box Only the types listed are supported 10 If your a...

Page 4: ...green flashing light with no buzzer noise indicates that your RF400 Logger is running on battery power is not in alarm or fault state and connection to the Cloud has been established What does a solid green light mean A solid green light with no buzzer noise indicates that your RF400 Logger is running on external power is not in alarm or fault state and connection to the Cloud has been established...

Reviews: