Troubleshooting Issue: Data Transfer of Spectrums and TWFs from CSI 2130 to MHM 5.41

Question:

Hello everyone, I am currently facing a perplexing issue and urgently seeking a solution. Our organization utilizes separate rbm databases for different regions. However, we are encountering a strange problem with a specific database. When we transfer data from CSI 2130 to Machinery Health Manager, only the overall trend is being transferred, rather than the spectrums and Time wave forms. This is a new issue for us, and despite conducting thorough checks, we have not been able to resolve it. We have confirmed the following: 1. The Route Summary in Route Management indicates that waveform and spectra storage settings are correct. 2. We can view the collected data (Spectrums and TWFs) in CSI 2130. 3. There are no bad data flags on the points in the 2130 device. 4. Data dump settings in Data Transfer are configured to store everything and save bad data. We have also scanned for errors using the database utility program, which returned no issues. Despite attempting data transfer with different collectors, the outcome remains consistent. Given that we do not have support from CSI, our options for assistance are limited. We are currently using MHM version 5.41. Any prompt suggestions on how to address this issue would be greatly valued. Thank you in advance for your input. Warm regards, Bala K

Top Replies

Hello everyone, I am excited to share that the issue has been successfully resolved. The database size had exceeded 2GB, causing it to no longer accept new data. By removing some old data, we were able to resolve the issue and upload all the necessary information. Best regards, Bala K.

Hi Bala, I empathize with the trouble you're facing. Based on your thorough analysis, you've covered most possible solutions to this issue. An aspect you haven't mentioned is the compatibility of the version of your MHM and the data being transferred. This can sometimes be overlooked. If the version is older, there might be challenges in compatibility leading to loss of certain data during the transfer. I suggest verifying if there's a more recent version of MHM that might be more suited to handle your data transfer. If an update is available, test the data transfer with the updated version. Hope this helps and looking forward to hearing about your progress.

Hi Bala, Sounds like you've done quite a thorough check already. My suggestion would be to look at your transfer settings again in Machinery Health Manager. Sometimes when you upgrade or alter the settings, it may affect the data types that get transferred. It's also worth checking to see if the hardware is functioning properly. On a more unlikely note, you may need to investigate if there are any compatibility issues between the version of MHM you're using and CSI 2130. These things can be tricky and often require a bit of detective work. Don't lose hope, you're bound to find the solution! Best of luck!

Hi Bala K, It sounds like you've been diligent with troubleshooting this problem, frustrating though it must be. One possibility might be related to the communication or compatibility between CSI 2130 and MHM version 5.41. If possible, attempt a trial transfer with a different MHM version, if one is accessible, or check for any recent updates or patches for your current version. Also, you may want to check if there are any issues with the file type compatibility. Sometimes, certain file types do not transfer accurately across software platforms. In any case, hang in there and hopefully someone on the forum can offer additional insights.

Hey Bala, It sounds like you've done a comprehensive check already, so this is quite a peculiar issue. Nonetheless, I have a few suggestions that might help. Firstly, if it's not already done, update your MHM to the latest version as sometimes older versions might have compatibility issues that have been resolved in newer ones. Secondly, make sure that all your software protocols are on the same version. It could be an integration discrepancy between your CSI and MHM versions. Lastly, double-check to see if there's any data compression happening during transfer, sometimes crucial information can be 'squeezed out' during this process. Hope you find a resolution soon!

More Replies →

Streamline Your Asset Management
See How Oxmaint Works!!

✅   Work Order Management

✅   Asset Tracking

✅   Preventive Maintenance

✅   Inspection Report

We have received your information. We will share Schedule Demo details on your Mail Id.

To add a comment, please sign in or register if you haven't already..   

Frequently Asked Questions (FAQ)

FAQ: 1. Question: Why is only the overall trend being transferred from CSI 2130 to Machinery Health Manager, instead of the spectrums and Time Waveforms?

Answer: Answer: This issue could be due to various reasons such as incorrect settings, data dump configurations, or potential errors in the data transfer process.

FAQ: 2. Question: What steps have been taken to troubleshoot the issue of missing spectrums and Time Waveforms during data transfer?

Answer: Answer: The user has confirmed correct waveform and spectra storage settings in Route Management, verified the data in CSI 2130, checked for bad data flags, configured data dump settings, and scanned for errors using the database utility program.

FAQ: 3. Question: Are there any known compatibility issues between CSI 2130 and Machinery Health Manager version 5.41?

Answer: Answer: There could be compatibility issues between the devices or software versions, which may require updates or patches to resolve the data transfer problem.

FAQ: 4. Question: What are the available options for resolving the data transfer issue if support from CSI is not accessible?

Answer: Answer: In the absence of CSI support, the user can explore community forums, online resources, or consult with colleagues who may have faced similar challenges to find a resolution to the problem.

Ready to Simplify Maintenance?

Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.

Request Demo  â†’