| Property Name
| Property Type
Pages using the property "UX-Cons"
Showing 12 pages using this property.
|MHK ISDB/Instruments/BlueView M900-2250 Dual Frequency 2D Imaging Sonar#UserExperience +||My only complaint is that the stitching between the multiple beams creates lines on the image. A recent upgrade made the lines much less noticeable, but they are still there. They do not obstruct the image, however objects are disfigured as they cross from one beam to another. The most recent instrument upgrade resulted in a few issues with image quality. Hopefully, this will be resolved after we send the instrument back for repair/upgrade.|
|MHK ISDB/Instruments/Chelonia C-POD#UserExperience +||In noisy environments (like the seabed of a high-velocity tidal channel) the data buffer allotted to time windows can become full very quickly, and then the sensor stops recording clicks. There can be a lot of 'missing' data because of this.|
|MHK ISDB/Instruments/Fluke 87V Industrial Multimeter#UserExperience +||Resolution on resistance is quite low – for precise measurements, you're better off with a dedicated RLC meter.|
|MHK ISDB/Instruments/Futek TRS605 Rotary Torque Sensor#UserExperience +||The resolution on the encoder could be better.|
|MHK ISDB/Instruments/Kongsberg M3 Multibeam Echosounder#UserExperience +||I think this is both a strength and a weakness: if you run into bandwidth issues, the M3 automatically slows its ping rate without giving a warning (or at least I haven't found the warning). There also isn't an exposed way to change the ping rate - the instrument automatically operates at the fastest ping rate possible for the selected settings. There is a workaround for this by either limiting the bandwidth or editing the instrument settings.|
|MHK ISDB/Instruments/Loggerhead DSG-ST Ocean Acoustic Datalogger#UserExperience +||Although newer versions are different, older models do not provide a way of ensuring the device is operating once the housing has been closed. In previous models it was not possible to synchronize the clock so timestamps were only good to within a couple of seconds.|
|MHK ISDB/Instruments/Nortek Acoustic Doppler Velocimeter#UserExperience +||Data quality is highly dependent on seed particles. Data must be filtered to eliminate poor quality readings due to phase wrapping and/or acoustic interference. Possible flow interference from the instrument head skews readings at the 'top' of the velocity profile. Very fine bin sizes (1 mm) result in lower quality data. A low signal to noise ratio at measurement points farthest from the transducer head can cause spiky data., There is an issue of slight clock drift with the Vector probe. The instrument must be synchronized with a computer clock before every set of measurements to minimize this issue. It would be nice to be able to interface with the instrument directly through serial coms out of the box without needing to work through Nortek’s software interface.|
|MHK ISDB/Instruments/Nortek Signature#UserExperience +||At the time we used the instrument, the battery estimations were not right. The battery lasted less time than expected, resulting in shorter measurement ensembles (Set up for 3 days of high frequency measurements, but only got 1 day of good ensembles)|
|MHK ISDB/Instruments/microAural#UserExperience +||The device is not designed for long-term deployments. The battery is the limiting factor.|
|MHK ISDB/Sensors/CR4100 Series AC Current Transducer#UserExperience +||The response time of 250 ms is quite slow.|
|MHK ISDB/Sensors/CR4500 Series AC Voltage Transducer#UserExperience +||The response time of 250 ms is quite slow|
|MHK ISDB/Sensors/Futek TFF425 Reaction Torque Sensor#UserExperience +||The aluminum versions are quite sensitive to vibration. These require amplifiers and output conditioning (not a problem, but adds complexity to implementation).|