Known issues and advisories
December 2019 Version 2.12
New or revised issues and advisories:
- Advisory on SIE data file names. Google Chrome and Mozilla Firefox are currently the recommended browsers for accessing the web interface of the XR system. However, Chrome and Firefox browser updates have removed recognition / support of some special characters in file names, in some cases resulting in faulty SIE downloads or unrecognizable SIE file names. To completely preclude potential problems, it is recommended that both SXR setup names and SIE file names consist of only numbers, letters (upper and lower case), and the ‘_’ character. Of course, users can use special characters if they desire and do not encounter problems. If problems are encountered, the user can rename the SIE files via the user interface and run the download again. Following are some known problems. Using the ‘#’ character will result in problems when using the Download Manager application. Using the ‘(‘ or the ‘)’ character will result in problems using the current version of Firefox. Using the ‘%’ character will result in problems using the current version of Chrome.
- Issue with Garmin GPS modules not proving correct Day, Month, and Year data. Some of the Garmin modules delivered to customers in the past have a firmware version that does not provide the correct date parameters noted above. All other Garmin parameters are provided correctly. The only way to fix this is to update the Garmin firmware. This is a somewhat complicated procedure requiring special Garmin software and cabling. Customers who want their Garmin module(s) updated can contact Somat customer (support@usa.hbm.com) to make the arrangements.
Errata (advisories):
- Legacy eDAQ discovery after firmware update (revised). The legacy eDAQ layers on the eDAQXR system are not always discovered after a firmware update, power cycle or system reboot. Improvements were made in v2.8.0 to vastly reduce the likelihood of this issue occurring. Based on long term power cycle tests on multiple systems, this has been seen considerably less than 1 time in 1000 cycles. If a test is running, the system will reset and the test will be restarted.
- Mode 2 networking limitation that affects SIE data file. The number of channel data samples stored in the SIE file will typically not be the same for all channels with the same sample rate when tests are stopped.
- Limitations on CAN database Vector DBC file export.
- CAN database Mode dependent channels are currently excluded.
- CAN database CCP channels are currently excluded.
- eDAQ EBRG/EHLS digital filter limitations. These eDAQ layers do not support certain digital filter / sample rate settings across all 16 channels of any layer. See the Operational Note EBRG and EHLS digital filter limitations in the Help system for details on this and other relevant information concerning limitations.
- Recommended browsers. The recommended browsers when using the eDAQXR web interface are up to date versions of Chrome and Firefox. The web interface may work on other browsers but may result in degraded or undesirable operation.
- SIE file naming conventions when using FTP upload. Please note that file naming conventions and special character usage can affect whether the FTP server you are uploading to, will accept the file. There are characters that are illegal file name characters in Windows systems, and likewise for Linux systems. Please avoid these illegal characters when considering what operating system your FTP server is running on.
- Use of HTTP and HTTPS protocols and browser add-ons / extensions when connecting to the eDAQXR. When performing a firmware upgrade and using the HTTP protocol, a CTRL+F5 refresh of your browser after the firmware update is required to ensure that new features and GUI elements are available. The same is true of the help system. If the user accesses the help system after a firmware update, a CTRL+F5 is required to ensure new help content is made available as well. The optimal performance when using the eDAQXR is realized using the HTTP protocol, inclusive of typical use, as well as download operations from the eDAQXR. Additionally, it is recommended that any browser add-ons or extensions be disabled when using the eDAQXR as their enablement has been linked to degrading performance of the GUI interface when in use.
- Caution when using Netgear networking interfaces. Certain Netgear switches and routers have been known to not work reliably when connected to the Host port of the eDAQXR. The problem will manifest as the Netgear networking interface showing the eDAQXR is not connected when in fact it is. In certain situations, a power cycle of the Netgear networking interfaces can correct the problem. For these reasons, it is strongly recommended that for any high availability or high assurance test platforms, that Netgear networking interfaces not be used to connect to the eDAQXR Host port.
Errata (known issues):
- Single channel editor locks up very rarely. The single channel editor (SCE) can get into a state where it cannot be closed. This can happen when the SCE automatically starts a Strip chart or other data display when opening the SCE dialog window, and the system cannot provide data for the display for some reason. The user can refresh the browser to close the SCE dialog window. There is also a User preference to not automatically start any display in the SCE dialog window.
- Sporadic eDAQ legacy REZERO_TIMEOUT error. This error is seen very rarely after a system boot from a power cycle or software initiated reset. The system reboots on this error and will automatically restart an SIE test that was running when the initial power cycle or software initiated reset occurred.
- Sporadic NETDEV WATCHDOG time out error. This error is seen very rarely after a system boot from a power cycle or software initiated reset. The system reboots on this error and will automatically restart an SIE test that was running when the initial power cycle or software initiated reset occurred.
- Sporadic eDAQ legacy EBRG layer EXCITATION_5V_OFFSET error. This error is seen very rarely after a system boot from a power cycle or software initiated reset. The system reboots on this error and will automatically restart an SIE test that was running when the initial power cycle or software initiated reset occurred.
- Sporadic MX module HANDLE SUBSCRIBE error. This error is seen rarely after a system boot from a power cycle or software initiated reset. The system reboots on this error and will automatically restart an SIE test that was running when the initial power cycle or software initiated reset occurred.
- Limitation with Mode 2 networking. Channels cannot be shared across the network nodes (i.e., channels defined on any given node cannot be used on another node for DataMode triggering, use in a computed channel, etc.). The user interface does not prohibit this. If the user configures as SXR test in this way, the user interface will attempt to start the test run. However, the system will reset on error.
- Limitations on using MX471 modules. The MX471 can be overloaded and not able to keep up with the processing required if there are too many CAN channels assigned. This is significantly affected by the CAN bus load – specifically the broadcast rate of the CAN messages. For example, the following test scenario will result in an overload. Test using all 4 ports with 128 channels assigned to each port (using 32 CAN messages per port) broadcast at 100 messages per second. In most cases, the XR system will reset on an overload situation, but not always. As such, users are strongly advised to avoid MX471 overload situations – particularly for unattended testing.
- Web browser exceptions. The web browser interface will sometimes lock up or not properly reflect the actual states of the hardware or test. Refreshing the browser will usually correct this.
- Potential loss of data sync issue when using Firewire with MX modules. In certain usage scenarios, MX modules can lose PTP sync when a test run is restarted after a reboot. Connecting an MXB module to any other MXB module using FireWire without both having an Ethernet connection to the data processor can result in acquired data not being synchronized to the data processor on one or more MXB modules.
- EX23-R PTP Synchronization with MX modules using ports 5 and 6. Using a system connected with MX modules connected to ports 5 or 6 on the EX23-R can result in the MX modules losing sync with the eDAQXR/eDAQXR-lite until the EX23-R is reconfigured properly. Reconfiguring these ports is fairly trivial. Please contact HBM Support at support@usa.hbm.com if your test application requires using MX modules on ports 5 and 6.
- Push notifications on iOS devices. There is a known issue with the iOS HBM Push application, where notifications will not be pushed, but instead have to be fetched by closing or reopening the app on your iOS device, or performing a pull down refresh of the notification list.
- Setups utilizing multiple video channels from a multi-channel video encoder is not supported. Although the eDAQXR will allow the user to specify multiple video streams from a multi-channel encoder, using more than one channel from a multi-channel encoder is not supported, and configuring a test with this configuration may in not as-configured results, and is at the user’s own risk. It is recommended the user only use one channel on a multi-channel video encoder.
- Live video displays when using the Axis m7001 video encoder. The Axis m7001 encoder can be used, but there are limitations on video display capabilities with this old and now discontinued Axis product. Video frames will be properly stored in the SIE file; however, viewing of the video frames is supported in the Hardware view only. As such, video frames cannot be displayed when the SIE test is running.