I didn’t even notice Version 14.00 come and now it’s gone already! Garmin released Version 14.10 of its Edge 1000 bike computer software on June 15, 2017, with just one fix when using Singapore maps. Garmin has been whole version number jumping recently, apparently due to the big changes that include Connect IQ and bike light handling capabilities.

Changes made from version 14.00 to 14.10:

Fixed an issue causing the device to freeze when using Singapore maps

Changes made from version 13.00 to 14.00:

Added support for Connect IQ 2.3.1, which includes support for background apps, app trials, and data field trials

In the configuration phase of a SAS Enterprise Business Intelligence (EBI) Platform deployment, the Deployment Wizard prompts the installer for the host name of the Environment Manager Server. This value is used by the Environment Manager Agent as the recipient of all of the data that it collects. The Environment Manager Server resides on the middle (web) tier of a SAS deployment. In multi-tier environments, the metadata, compute, and web tiers all have Environment Manager Agents deployed to them.

It is possible to provide an incorrect host name to the Deployment Wizard, and if that happens, you will quickly notice that no resources are available in the Environment Manager. In this case, the Environment Manager Agent configuration needs to be updated to reflect the correct location of the Environment Manager Server. The configuration file that specifies this information is located at

in a SAS 9.4M4 UNIX deployment. In the agent.properties file there is a property called agent.setup.camIP that is used to define the SAS Environment Manager Server to the agent. The agent.setup.camIP should equal the middle tier’s hostname and can be changed manually. After the agent.setup.camIP value is updated with the correct host name, save the edits and restart the agent and resources should begin appearing in the Environment Manager in five minutes or so. This technique would also be used if the host name of the middle tier is changed.

A developer came to me wondering what was changed on our SAS Enterprise Business Intelligence Server platform because reports he created in Web ReportStudio 4.4 were no longer displaying tool tips when he hovered over data points in graphs. I hadn’t made any changes to the environment, so I opened Microsoft Internet Explorer 11 and verified that tool tips were were not displaying onmouseover. After a quick Google search, I ran across SAS Usage Note 58613, which stated: “In SAS Web Report Studio, graphs might not display tooltips, or they might display tooltips for some segments but not others. This problem can occur if your browser zoom level is not exactly 100%.” I went back to Internet Explorer, clicked the View Menu, and chose Zoom. I noticed that my zoom level was 95%, so I adjusted it back to 100%. My graphs magically displayed tool tips again!

Current Garmin fitness mass storage products like the Edge, Forerunner, and vivoactive series, store your activities in the accessible file structure of the device. This provides a better user experience when using the device with a computer. There may be instances in which additional space is needed on the device. For example, the device memory may fill to the point a software update cannot be sent to during sync interactions with Connect Mobile, Garmin Express, or WiFi. In these circumstances, it becomes necessary to make additional space on the device.

If attempting to permanently delete activities from the device, you may need to delete the associated FIT file. Before deleting from the device, verify all activities have successfully uploaded to Garmin Connect.

Garmin released Version 13.00 of its Edge 1000 bike computer software on May 3, 2017. Seven fixes or improvements were included in the upgrade. For me, the Bluetooth fix and improved grade responsiveness and accuracy are particularly welcome updates.

Changes made from version 12.20 to 13.00:

Added support for Varia UT lights, including a new light control page

Indoor cycling Activity Profiles now turn bike lights off by default

Improved the heading data field to show cardinal directions instead of degrees when paired to Varia Vision

Fixed an issue that could cause Bluetooth disconnects

Made improvements to Grade responsiveness and accuracy

Fixed an issue with routing that was incorrectly preventing some roads from being routed on and changed default avoidance of Major Highways to Off

We had a new project which required the manual configuration of the SAS middle tier to utilize TLS (Transport Layer Security , a successor protocol to SSL). These environments were SAS Enterprise Business Intelligence Server 9.4M4 deployments. With each new maintenance release, SAS has simplified the automatic and manual configuration of encryption services. SAS Documentation suggests using the Deployment Wizard to automatically configure HTTPS and TLS during the configuration phase of a new deployment or upgrade. Unfortunately we already had fully-deployed 9.4M4 environments, so we had to do the configuration manually. This reconfiguration isn’t a complex process, but there are many configuration files to edit and a lot of clicks in SAS Management Console to achieve the desired result. After learning some shortcuts performing the change in our development environment, I was able to reconfigure the production environment in about an hour. SAS has documented this process in the SAS Intelligence Platform: Middle-Tier Administration Guide.

One other step was required for us after the HTTPS reconfiguration was complete. Our reporting environment was accessed using a link on the company intranet. We worked with the webmaster to update the URL and port in the intranet page, but we still had thousands of end users who had the old URL saved as a favorite in Internet Explorer. Instead of asking users to update their favorites, we chose to automatically redirect redirect web traffic from HTTP to HTTPS .

The solution couldn’t have been easier to implement. All we had to do was edit the SAS Web Server httpd.conf configuration file. My deployment is on AIX, so the file was located on the middle tier server atSAS-configuration-directory/Lev1/Web/WebServer/conf/httpd.conf. I added to following lines to the file:

Garmin released Version 12.00 of its Edge 1000 bike computer software on March 20, 2017. The release included a few fixes and a number of new features.

Changes made from version 11.20 to 12.00:

New Feature! Added support for Shimano Di2 Synchronized Shift. Graphical Gear data fields will now blink, an alert tone will be played, and a message banner will be displayed to indicate a chain ring shift is upcoming. Synchronized Shift mode can be changed and the alert tones can be disabled through the Shimano Di2 sensor settings

Added improvements for ANT+ bike lights. Added new Light Beam Activated and network Light Mode settings to ANT+ Bike Lights sensor settings. You can now configure your lights to turn On with a Timer Start by using the new Light Beam Activated setting and there is also a new Trail Light Mode