Q1a-2015 CIT Release

Welcome to Tehama CIT software version

After receiving a report or two of DCAPs failing the update we removed the feature until we could investigate.  We feel the issue is now resolved so you will once again be prompted to update DCAPs when you visit sites.  This is the only change from released two weeks ago.

We do appreciate your ideas on how to improve the CIT software so please keep your comments coming, especially on the new Network View screen.

Enhancements and the bug fixes are detailed below.  But first, it is VERY important for you to update your DCAPs with the new firmware that is included with this version of the CIT software.   We strongly encourage everyone to update DCAPs as you encounter them.   Details can be found below in the DCAP section.  If you do not update you may lose the ability to access the DCAP remotely at some point in the future.

1. CIT Changes:

  • Graphical presentation of the network is shown in the Monitor Data tab, Network View (Beta) sub-tab. 

This allows you to visually see the RF path to the DCAP for a device (including the number of repeater hops) and quickly identify the weak repeater links.  Mouse over any node to highlight the path back to the DCAP.  Green links have good Link Quality, Blue are OK, Red are weak.  Click on a node and get the details about the device.  Right click on a node to get a context menu of options.  Hold down the Alt key and drag a window around an area to zoom into that window.

As the tab name suggests, this is a beta feature for now so please keep that in mind.  Any and all feedback about the current implementation or features you might like to see are certainly welcome (send to support at tehamawireless.com).


You might not see the Network Tree View in the left after leaving this new graphing screen.  Using the icon buttons added in the prior CIT release, click the View/Hide Network Tree button to get it back.

  • Event messages can be downloaded from a DCAP, events such as Repeater Power Loss or MDT Low Battery Alarm.  Access it from the Reports -> Alerts History menu.  Use this when preparing to visit a site to see what maintenance issues you may face.

With this feature it is highly recommend you enable the MDT_Battery alert from the QuickSet button in the Alert Email area.  Otherwise the DCAP won't record these particular events.

  • MDTs added are now automatically enabled in the Daily Report.  However it is still recommended to always check the QuickSet button.


2. CIT Fixes:

  • Better sorting on columns with time data (Last Log Reading, etc.)
  • For Dual Pulse MDT units, a 2nd Pulse input is assumed for the imported Meter Configuration Data.
  • Improved support for very large properties using Gateways and a Cloud Server.
  • Support the late model Laptops with high resolution screens.


3. DCAP Changes:

  • Support for a new QuickTest feature on new MDTs and Diversity Repeaters.  This is part of a new mobile web application we will release shortly allowing easy field access to DCAP data.  Look for an email announcement in your inbox soon!
  • Shadow Backups of the configuration data are saved on the DCAP.  Call Tehama if you need to restore a site from this backup should you not be able to find a local CIT backup.  A future CIT version may allow you to do the restore yourself.
  • Lowered the timeout to drop a broken connection to the DCAP, which often occurs when using a cellular hot-spot for Internet to your laptop.  You would see this as a "Too Many Connections" error in the CIT.
  • Support for updated Access Code infrastructure. This is the reason you should update all your DCAPs.  We are beefing up and securing the remote access links as we move to this new infrastructure.  All this will be transparent to you the user; however it will take two updates to fully implement. This first update will set the groundwork and a future release will complete the update.

Reminder:  Firmware updates to a DCAP can be done after you are finished working on a site, rather than having to do the update immediately when connect to a DCAP.  Also, more than one instance of the CIT software can be running on your PC in case you need to look at multiple sites at once.

 4.  DCAP Fixes:

  • Historical Reporting is now reliable.  It previously would work the first time but may not after that.  Also, only one report can be done at once, so the CIT now checks for this and won't allow you to run a second report.  If you need many reports, use the date range feature to run multiple days or even multiple months.  Note that each day’s report can take a few minutes to generate so be patient for them to arrive.
  • More reliable Status LED.  It will stay red if the firewall is blocking remote access to the DCAP even if other features are working (email & FTP).  Tip: If ever you have a connectivity issue, disconnect the Ethernet cable for a few seconds then reconnect to reset the remote access function.

Q3-2014 CIT Release

Welcome to Tehama CIT software version  There is only one change in this release.  A change we made based on customer feedback in the last release created confusion for other customers regarding the dates displayed when pulling historic reads. 


In the previous version (, when pulling monitor data (reads) for a date range in the past, the log msg time stamp column was displaying the last time a log msg was received (which is almost always the current date).  Thus the CIT reports are not displaying the last time a log msg was received in the specified time period downloaded, but rather it was displaying the most current log msg time.  The reads received and displayed were correct for the date range downloaded. 

 With this latest version of the CIT, the column “Last Contact Time Stamp” now displays the last time a log message was received in the specified time period downloaded.  Hovering your mouse over the column headers will cause pop up text to appear to remind you of what is data is in each column. 

Last time.png

Q3-2014 CIT Release

Welcome to Tehama CIT software version  We appreciate your ideas on how to better the CIT software, so keep your comments coming!  Enhancements and a few bug fixes in this release include

1. User Interface (UI) Enhancements: 

  •  In the network tree display area, the number of MDTs currently using a repeater has been added to each repeater shown in the parentheses next to each repeater.
  • A new menu item is added, CIT-> Site List-> Use Current and ->Use Backup.  This allows the user to select and use their current site list or to select a historical site list. 
  • The IMR and Count Factor are now available column choices in the Monitor Data views.
  • Fractional values, 1 decimal place, for the Initial Meter Read value are now allowed.
  • To see how long an MDT or Repeater unit has not been reporting to the DCAP, the Last Contact time is now included for units that have not reported within the time period the user downloaded using the CIT.

2.  DCAP Communication Enhancements:

  • When connecting to a DCAP, if the Site name is different from the Site List name, then the user is notified and prompted for action. 
  • To bypass the automatic downloading of the last 12 hours of sensor monitor data when connecting to a DCAP, press the CTRL key while clicking on the Connect button (CTRL-Connect button).


  • The CIT now checks for any needed update to the DCAP’s firmware when either disconnecting from a site or exiting from a site.


  • The DCAP can act as a Central Server as long as the total capacity remains under 1000 units.  For example, two neighboring small sites could use one DCAP acting as the primary database, and the second DCAP being a Gateway.  Both DCAPs would need Ethernet access. 


  • The *.out file report generators have been updated so multiple daily historical reports can be generated in one step.  Note: Using the most recent ReportGenMod#.zip.aes script is required and may require reinstalling the script in the DCAP. 

3. Various Bug Fixes and Minor Improvements

  •  Selecting the Hawaii Time zone is now fully supported in the DCAP.


  • The CIT no longer hangs when showing the DCAP firmware update progress and the CIT is exited.


  • The DCAP’s Current Script now shows "Unknown…" when connecting to a DCAP. Previously it was showing the last DCAP setting.


  • Fixed Last Contact time to update when the user does the command to Get Latest Monitor Data.


  • Units are not displayed in the Monitor View grids if the Last Contact is not inside time window of the downloaded Monitor Data, and the unit is not commissioned.


  • Expand/Collapse options have been added to the Network Tree when you right-click on the Network Tree. 
  • Various fixes done to better support the import the CSV files.


  • For CIT error handling, unhandled exception data is copied to the Windows clipboard if an email is not being sent and more diagnostic info is logged. 


Q2-2014 CIT Release

Welcome to Tehama CIT software version  Again, many of the enhancement ideas came from your great feedback, so keep your comments coming!  The enhancements and a few bug fixes in this release include:

1. Various UI Improvements:

  • Add Collapse/Expand buttons in the Icon bar to hide the Network Topology and Activity/Filtering area.  Provides maximum screen area for the primary data grid views:
  • Initial timescale for graphs follow the time period downloaded, so relative data timestamps between different nodes is more apparent.
  • When connecting, if the Site List name is the default site list name (i.e. "A Site Name") then the CIT will automatically change it to the site name that is in the DCAP.
  • Firmware updates to a DCAP can be done once you are finished working on a site, rather than having to do the update immediately when connect to a DCAP (or skipping the update and then forgetting to update altogether):
  • Add back the much requested "Add This Uncommissioned Device" to the Network Topology right click options:
  • Add indication symbol that a unit has been powered down ( red circle with horizontal line):
  • Speed up the time to save Configuration data to the DCAP.

2. Easier Network Tree filtering

  • Add tabs in the Network topology area and add Tree Filtering options:
  • Add "Show Network Topology" checkbox  to Network Tree:

3. Improved the “Find” functions

  • Text searches using the Find search box are no longer case sensitive.
  • In the Site List, Tree View tab and when using the Site Search String box, the search is no longer case sensitive and searches will search all the columns in the Data Grid View.

4. Improved support for Daily Report

  • On the DCAP Configuration tab, the name of the ReportGen script and version (for version 116 and above) is displayed so the use can see what report script is loaded on the DCAP:

5. Various Bug Fixes

  • Loading SQLite data was causing duplicate developmental data when saving to the DCAP.
  • When CIT DisConnects this was not immediately being reflected in the Title bar, etc.
  • When connecting to ES sites and the radio ID display was set to decimal, the CIT no longer crashes.
  • When entering Initial meter read value, the Initial meter time is now updated with the current time.
  • When connecting to certain sites containing an excessive amount of RF Network statistics data, the CIT no longer hangs.


CIT Update Q1-2014

We've found a few issues to fix since the big update a few weeks ago, and we added a few new features along the way.  Here is the list for this update.  The release notes are below.

  • The prior update for the DCAP could cause your custom daily report to be replaced with a default version.  That has been fixed, however we recommend you re-upload your custom report after performing a DCAP update.
  • A carriage return will once again select the next cell in the Node View
  • Non-communicating units are now displayed in the Monitor View tab.  No longer do you need to go to the Node View tab to see non-comms, while you then look at the Monitor View to see the weakly communicating units.
  • We added a few more scroll bars in windows when the CIT is run on laptops with smaller screens.
  • You can now start multiple instances of the CIT, allowing you to view different sites at the same time.
  • The Hawaii time zone has been added
  • An audit trail history of configuration updates by user name and date is available in the upper right area of the Site Configuration tab.
  • A number of subtle bugs in the new Filtering function have been fixed. 


Initial Release notes for

January 28, 2014

Welcome to the new Tehama CIT software version  Many of the enhancement ideas came from your great feedback, so keep your comments coming!  The enhancements in this release include:

  •  Colors have been added to the various tabs to help you navigate.
Color Tabs.png

  • Search boxes to quickly find various data have been added.  In the Site List, you can search on DCAP name, Property ID, Access Code, or IP address.  In the grid views, you can search on any field such as Apartment Number or DeviceID.

Whenever a grid is displayed in the main Panel, a Find Box will appear at the top right corner of the main panel. This feature allows you to quickly highlight the cells containing a specific string in any of the grid fields.

Steps to using Search:

Enter the desired string in the Find box, hit Enter.

The cells containing the string will be highlighted:

CIT Find.png

Use the Find Next button to scroll through each highlighted cell.

Note that for each cell the corresponding graph (when existing) will automatically open and the corresponding MDT will be highlighted in the tree view.

There is also a Find box in the Site List tab, allowing you to easily find a site by Access Code, Site Name, etc.

  • A Filtering feature has been added so you can restrict the displayed data in the main grid to specific devices.  For example you can choose to see only uncommissioned MDTs, only Inovonics® PMTs, or only missing units.  You can even filter on values, such as MDTs below a specified battery voltage.
CIT Filtering.png

You can either choose from several preset filters (Simple filters) or you can easily define your own (Custom filters.  The filter is defined in the Filter settings tab below the main grid.

Simple filters:

By selecting the Simple Mode radio button, you get access to several useful filters.

CIT Filtering2.png

You can choose to display only:

  • Commissioned, Uncommissioned or both device
  • A specific type of device: MDTs, PMTs, Repeaters or RPMT
  • Devices with a Battery voltage below 2.2 V or/and a link quality below 40
  • Specific Status icon
  • Or any combination of those criteria.

After selecting the desired combination of criteria, click on Turn ON Filtering to enable the filtering of the data in the main Grid.

Custom filters:

By selecting the Custom Mode radio button, you can define your own set of criteria.

To edit each criterion, click on the first line and select the parameter to filter on in the dropdown list:

CIT custom filtering1.png

Click then on the second line and select the operator in the dropdown list:

CIT custom filtering2.png

And finally enter the constant in the 3rd cell– in our example we are defining a filter criteria to display only the devices whose Radio ID contains 81.  You can add up to 10 criteria to your filter.

CIT custom filtering3.png

To disable an existing criterion, return its first line value to “unused”.  Once your set is defined, click on Turn ON Filtering to filter data in the Main grid.

You can also save your filter setting in a CSV file by clicking on Save Filter Setting, which will allow you to reuse the filter at a later time by clicking on Get Filter Setting and choosing your file.

When using a filter, the Tab names will be in between stars to remind you that you are viewing data in a filtered mode. To turn off the filtering, simply click on the filter settings tab and Turn OFF Filtering.

CIT custom filtering4.png

  • RF information of RSSI and Link Quality values can be displayed as the average (like before) or just the most recent value.  By clicking on the Options menu you can select which value is displayed:
  • Uncommissioned PMTs can be filtered out in situations where there are neighboring property units showing up.
CIT remove uncomm.png

It is recommended to remove the uncommissioned Inovonics® devices from the CIT by checking the check box above the Network Tree – it will keep potential neighboring properties devices and their data from cluttering your network.  Checking this box will remove the Monitor Data for UnCommissioned PMT and RPMTs in the CIT.

 This can be useful when you are in an environment where there are "Neighboring" properties with sensor networks that include PMTs and RPMTs. These "Neighbor" PMT and RPMT nodes can be picked up via the Receiver attached to your DCAP. The DCAP has no real way of knowing that these PMT/RPMTs are from a "Neighbor" network. So it saves this data as it would for any Monitor Data received from a PMT/RPMT. The result is, you can get a lot of "Neighbor" nodes cluttering up the network tree and the Data Grid Views. Checking this box will remove this "extraneous" Monitor Data.

UnChecking this box will allow you to view Monitor Data for UnCommissioned PMT and RPMTs in the CIT.


  • Building and Apt information is displayed on all graphs.
CIT graph.png


  • A Daily Report file can now be created from the Monitor Data Views in the CIT.

By right clicking on the grid information displayed in the Monitor Data tab, a popup menu appears and one of the options is Generate Report.  Upon selecting this menu option, a *.csv file can be created with the data from the grid.  Note that which data is displayed in the grid is configurable using the other menu choices.

CIT gen report.png


  • The Sensus protocol has been added to the monitoring of our Encoder MDT product.
  • Inovonics FA and ES Repeater status is now available in the daily report file.
  • An FAQ link has been added under the Help menu.

Note: As part of the prior release, the CIT automatically checks for updates every time you launch the CIT.  Therefore, the next time you launch the CIT, you will be notified that the new version is ready and you will be prompted to restart the CIT for the update to take effect.  The update also includes a firmware update for the DCAP, and you will be notified when to update DCAPs as you connect to them

Q3-13 Bug Fix Update

OK, we were not perfect.  You found a few bugs and let us know (thank you!), and we found a few ourselves.  This minor update to covers these issues:

  • A problem updating Configuration Data has been fixed, especially related to enabling commissioned units into the daily report.
  • Change the behavior of the disconnect button (left most icon in Icon bar).  When green, indicates you are connected to a DCAP; when orange, indicates you are not connected.  Clicking the icon will take you to the Site List where you can Connect/Disconnect using the large button.
  • When importing configuration data, the CIT now auto-detects whether you are importing Hex or Decimal RadioIDs.
  • References to Unknown_Sensor_Type have been hidden  
  • A Carriage Return in the Node View table will again move the input area to the next cell down.
  • Decimal vs Hexadecimal viewing mode wasn't consistent.  Now the CIT will always use the setting from the Options menu.  This option is sticky, meaning it will use the setting whenever you launch the CIT.
  • Daily Reports and Alerts related to the Battery Voltage can now be set with the Quick-Set buttons
  • Importing CSV files with Dual Input MDTs is now handled correctly
  • A bug preventing access to some DCAP-TFA sites has been fixed
  • A bug that corrupted the Site list during a DCAP firmware update has been fixed

We have also added a new FAQ section (Frequently Asked Questions) here on our web site.  This can be accessed anytime from the FAQ line of the Help Menu, or by clicking the FAQ link you see right now to the left. Check back here if you have specific questions; we'll be updating this as new questions arise from our user base.  


Finding non-reporting Devices

A quick way to find which devices (MDTs and Repeaters) are not reporting in is to go to the Configuration Data -> Node View tab, then sort on the Icon column (the first column).  This will sort the list by connection status.  A binocular icon identifies a non-reporting unit.  You may need to sort twice to bring the binocular icons to the top of the sorted list (each click will change the sort order between Ascending or Descending order).   Note that a unit is considered non-reporting if no Reads data was seen in the data that was downloaded from the DCAP.  The default download period is the last 12 hours. So if you instead download 48 hours of data for example, some units that previously were missing could appear now as OK as there was some data from that unit within the 48 hour period.  

Here is the meaning of each Icon: 


How do I save a daily ReportGen script?

Tehama distributes the ReporGen scripts as an encrypted zip file that you upload to your DCAPs using the CIT software. We offer both our standard ReportGen (pre-installed on DCAPs or available here), or provide you with a custom script by email.  Refer to App Note AN-104 for more information about our customization options.

To load a script to the DCAP:

1: In the Configuration -> DCAP View -> Site Configuration tab, right click in the white area of the Daily Report Email Configuration area to see a context menu as shown here:


2: Select the Save Scripts to DCAP option. This will open a Script File viewer window as shown:


3: Click on the Select File button to open a file browser window. Select the ReportGen script you want to load, and click the Open button (or double click on the file). The full path to the file will be shown.

4: Click the Save to DCAP button. This will cause the CIT to send the file to the DCAP and install it. You will see some activity in the bottom area of the CIT.  Note that the new script will overwrite any previously loaded script.

5: Once the file has been uploaded to the DCAP, you can verify the report is working by selecting the “Send a Report” now option. This will instruct the DCAP to run the report and send the CSV file to the expected location. Make sure you have an email address entered in the Daily Report Email Configuration space if you expect the report to be sent by email.

How do I delete unwanted or extra devices?


Go to the Configuration Data -> Node View Tab, where all commissioned devices are listed. There are two ways to remove a commissioned device from the list.  The first way is to highlight the row in the Node View by clicking on the Icon (green checkmark or binocular icon) and hit the delete key.  The second method is to right click anywhere in the row and select the "Delete Node Configuration Data from CIT" .

If on the other hand you are seeing extra units in the Monitor Data tabs, and these extra devices have a yellow triangle symbol in the left column, then these units are not commissioned, and cannot be included in the daily report.  If these yellow triangle units are turned off, they will eventually fall off the list once their last received data point is older than the amount of data you download from the DCAP.

Why have MDTs or Repeater “Disappeared”?

First look at the Configuration Data tab -> Node View, then sort on the first column usually filled with the green check circle. This will sort the list based on the icon, and any Commissioned units not reporting in will be shown with the binocular icon. You should click twice if you want the missing units at the top of your list.  The number of binocular icons will match the count next to the binocular icon in the Site Health section above the Network Tree pane.

A unit is considered missing if there has been no communication from the device over the period of time specified when you downloaded data.  If you only just connected to the DCAP, then only 12 hours of data was downloaded.  If you manually download only three hours of data to the CIT for example, a unit is considered missing if, for example, that unit was on the edge of its range and succeeds only to get a few messages a day through, or if a Repeater was recently unplugged in the area of the unit. If you download 24 hours of data, often you will find these units are not missing, but just come in less often than once an hour.

In the Monitor Data tabs, if you enable the Last Contact column, you can sort on that column to see how recently a unit has reported in.  The time is relevant from the time of the last download that you made.

Q3-13 CIT Release

Released September, 2013

The new CIT brings a number of updated features. Most prominent is the method used to install the CIT on your computer. The new method does not require admin rights, however you will now have two CIT installs on you computer. We recommend you manually uninstall your prior CIT using the instructions provided upon launch of the new CIT. The other key new feature is that the CIT will now automatically update if we publish a new release. A check is made for updates every time you launch the CIT and you will be notified by a pop-up window if one is found. You need to close down and restart the CIT for updates to take affect. As always, new CIT releases might contain an update for your DCAPs, and you are notified upon connecting to a site when this is needed. With every new CIT update you will be presented with this web page to describe the new features. You can also access this page at any time from the help menu.

Other CIT Features or Enhancements

  • When first connecting to a DCAP, 12 hours of monitor data are now automatically downloaded along with the configuration data. No need to connect, then download monitor data. This feature can be disabled from the Options menu. 
  • Neptune ProRead encoded output meters are now supported. 
  • The CIT now performs checking on data importing, catching non-conforming RadioIDs due to simple typos or Excel's incorrect interpretation of certain RadioIDs as numbers. 
  • The RSSI value displayed now ranges from 0 to 100 (max), matching the range of Link Quality. Now if either Link Quality or RSSI are below 25, the MDT should be considered out of range.
  • The Site List layout has been improved for ease of use, and the connection button enlarged. 
  • The Site List Tree View implements folder structures for grouping of properties by region or management company. You can drag and drop entries to organize the list as you like. 
  • The Site List file can be exported and imported now. If your company has a master Site List, you can distribute it to all your technicians. 
  • While updating the firmware on a DCAP, you are no longer locked out from using the CIT to access other sites. You can even update multiple sites at the same time.
  • The sub-tabs in the Monitor Data viewing window are now all completely customizable. Any tab can be set to display any of the Configuration or Monitor data parameters such as Building, Apt, Reads, Units, RF network data, etc.) and the associated site configuration data (Apt. #, notes, etc.).
  • The CIT now fully supports properties over 1000 meter points in size, using our Gateway DCAP and Central Server products. 
  • You can now set the Time Zone for the data you download or view, set to either your local time or to the DCAP's configured Time Zone.
  • Most all progress bar updates have been moved to a dedicated bottom bar. 
  • The USB Configuration window to eliminate confusion between the two separate tasks displayed

Bug fixes

  • CSV data exports now add "=" in front of the RadioID field so Excel will correctly import the column as Text. 
  • Fixed bug related to Received RadioID when using the Decimal display 
  • Improve the Apt column sorting so it sorts as numbers and not as text 

DCAP Updates

  • The DCAP Remote Access mechanism is more robust, especially for property sites with often changing IP addresses. The connection is now checked every hour, compared to every 24 hours in the prior version. 
  • A new standard ReportGen script is available here. This new version adds a feature whereby historical reports are stored on the DCAP for up to 90 days. For now, you will need to contact Tehama to access the historical reports. A future release of the CIT will allow the user to access these reports. If you have a custom ReportGen script, contact Tehama to receive an update to version 115.