Sign up Calendar Latest Topics Donate
 
 
 


 
Poll Results
 
 Data collection time is
 A 0.01 - 0.05 secs 0 0%
 B 0.1 - 5 secs 6 85%
 C. 10 - 50 secs 1 14%
 D 1 - 5 mins 0 0%
Total votes: 7   Please or sign up to vote.


Reply
  Author   Comment   Page 3 of 3      Prev   1   2   3
RustyCas

Avatar / Picture

Admin
Registered:
Posts: 1,689
Reply with quote  #31 
I am a bit puzzled by the 1000 Hz Fmax I’m seeing in some comments. For the most common speeds of 1500 and 1800 rpm that’s only 40 and 33 orders, respectively. That seems low. Are you *not* wanting to see rotor bar pass? I’ll have to confirm, but I’m thinking that most “bad bearings” I see have a ‘mound’ of energy at around 1400 Hz.
__________________
"The trend is your friend"
RustyCas

Avatar / Picture

Admin
Registered:
Posts: 1,689
Reply with quote  #32 
Vibe, is it possible that “awful” unit you mentioned that wrote to the HDD also allowed you to “stream” data to that HDD, which you could then post process to your hearts content? That unit today would have an SDD which would be almost as fast as the 2140, and still have the “data recorder” feature which the 2140 will likely never have. Just sayin’...
__________________
"The trend is your friend"
fburgos

Sr. Member
Registered:
Posts: 540
Reply with quote  #33 
Quote:
Originally Posted by RustyCas
I am a bit puzzled by the 1000 Hz Fmax I’m seeing in some comments. For the most common speeds of 1500 and 1800 rpm that’s only 40 and 33 orders, respectively. That seems low. Are you *not* wanting to see rotor bar pass? I’ll have to confirm, but I’m thinking that most “bad bearings” I see have a ‘mound’ of energy at around 1400 Hz.


I do as follows,

velocity 90x and 6400 lines
peakvue 1000 hz and 6400 lines
special wave 15 revs or less,  220x-3200 if its a gearbox I do 440x and 6400 lines.

but im thinking in removing the special wave and adding an acceleration point.... database redo i know its a pain and waste 2 years data
MarkL

Avatar / Picture

Sr. Member
Registered:
Posts: 989
Reply with quote  #34 
I Normally spot that Mound in acceleration more so than Velocity Rusty,
If I spot something 'Icky' or 'interesting' I take some additional off-route data which I can manually set up any parameters fmax lines etc and save and dump to file and add to the route after. For monthly routine stuff, the setup I'm using works fine.
RustyCas

Avatar / Picture

Admin
Registered:
Posts: 1,689
Reply with quote  #35 

Ferdy, when I started lubricating motors, I added one point per bearing that is 10 kHz with an acceleration spectrum and it’s been a great help. Adds practically nothing to collection time when part of a “group.”  But I only had about 30 machines to modify, so maybe 45 points. Adding supplemental points is not easy given the 3-character point name that MHM restricts us to. Perhaps this restriction will be removed eventually. I’m just not sure I’ll be able to afford it ($$).

I‘ve always used the special TWF to catch bearing noise, and the velocity spectrum for better resolution of actual defects. The big disadvantage is the spectrum is *not* produced by the waveform pictured on your screen - they don’t “match”. Not a perfect system.


__________________
"The trend is your friend"
fburgos

Sr. Member
Registered:
Posts: 540
Reply with quote  #36 
Do you measure 10khz acceleration on all 3 directions of each bearing?

First I though this special waveform is great, I can have a high resolution spectrum and high resolution waveform at same time, but it takes it after the peakvue is finish then the speed benefit is none.

3 character point name is not a big restriction for me, my system is number the bearings from 01 in the driver outboard/free side and grows to the driven machine in this order according to the number of shafts all odds numbers are in the "back" of the machine and even numbers are in the "front", for example.

-01-Motor-02- /coupling/--03--*gear1*--04--
                                    05--*gear2*--06--/coupling/--07--fan-08-

the last character is reserved for a letter.

for example on bearing 01

01X displacement probe X
01Y displacement probe Y
01V absolute vibration vertical
01H absolute vibration vertical
01A absolute vibration vertical
01P peakvue
Shurafa2

Sr. Member
Registered:
Posts: 109
Reply with quote  #37 
This is a summary of the newly added configurations:

Noknroll
VEL & PKV both @ 80X (2000Hz)/3200 L + 10,000Hz/6400L acceleration.
All grouped takes < 5 sec.


Rusty

1600 lines/2000 Hz with 3 averages and 50% overlap ~ 1.6 sec
3200 lines /3000 Hz with 3 averages and 50% overlap ~ 2.2 sec
“special” 3000 or 4000 Hz acceleration TWF for most REBs. Speeds above 3600 rpm. I cannot calculate the time.


Mark

Velocity and envelope/gE3 at 3200 lines/1000hz with 3 averages (no overlap) ~ 9.6 sec
Acc 6400lines /5000hz (no averaging) ~ 1.28 sec


Regards- Ali M. Al-Shurafa
MarkL

Avatar / Picture

Sr. Member
Registered:
Posts: 989
Reply with quote  #38 
Just to Clarify there is only one average taken with gE3 same as with peakvue.
Also the Microlog multiplexes so whilst the readings are taken with one button push per point they are taken  sequentially unlike the CSI 2140 which takes it all in one go( I think?)
That said I am really getting into the weeds now.

Sinski

Avatar / Picture

Sr. Member
Registered:
Posts: 370
Reply with quote  #39 
Quote:
Originally Posted by RustyCas
Vibe, is it possible that “awful” unit you mentioned that wrote to the HDD also allowed you to “stream” data to that HDD, which you could then post process to your hearts content? That unit today would have an SDD which would be almost as fast as the 2140, and still have the “data recorder” feature which the 2140 will likely never have. Just sayin’...

Rusty. It was awful and no it was not a SSD. It would take ages for it to write the data to the HDD and you had to wait for that to happen to collect the next point. Thats if the operating system had not crashed in the meantime. Was totally not suited for paper machines. Cannot remember if it could "steam" data though.
RustyCas

Avatar / Picture

Admin
Registered:
Posts: 1,689
Reply with quote  #40 
Sinsk, I was saying that the modern version of that unit would use a SDD. I can’t imagine why it took so long for the data to be written to disk. How long ago was that? When ai say “stream” data, I mean record. I’m working with an Adash unit, and you can record as much data as you’d like, and then post process it any way you’d like, over and over again. I can’t really say how well it works yet - haven’t gotten that far yet.
__________________
"The trend is your friend"
MarkL

Avatar / Picture

Sr. Member
Registered:
Posts: 989
Reply with quote  #41 
Did you purchase or demoing Rusty? What model do you have?
Sinski

Avatar / Picture

Sr. Member
Registered:
Posts: 370
Reply with quote  #42 
Quote:
Originally Posted by RustyCas
Sinsk, I was saying that the modern version of that unit would use a SDD. I can’t imagine why it took so long for the data to be written to disk. How long ago was that? When ai say “stream” data, I mean record. I’m working with an Adash unit, and you can record as much data as you’d like, and then post process it any way you’d like, over and over again. I can’t really say how well it works yet - haven’t gotten that far yet.

I cannot really remember the times but that was a long time ago. From memory it would take one guy a few weeks to get around to collecting a whole paper machine, pulp mill, boiler and woodyard. When we had a chance we took 2 2120s to site and knocked it all over easily within 2 days. It was back in the early 2000s so quite some time ago. They might be using SSD now but you would not be buying a unit back then hoping a tech upgrade would speed it up to be close to what was already available elsewhere.
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.