EN
 
English
French
German
Italian
Russian

What if I don't know my expected measurement range?

Lemmie Atom

Posted on 02.10.2019 18:14

Hi,

New-ish user here.

What do you recommend doing if I don't know what my measurement range is expected to be?

For instance, I was taking impact data with accelerometers and "expected" to see up to 5 Gs, so I set the measurement range within that value in the channel sensor settings. During the actual test we got up to 35 G's! I would not have noticed an issue but happened to see the OVL warning in the upper corner of the screen. That's when I went in and selected a higher measurement range.


But had I not noticed I would've clipped my data. What should I do in this case, when I don't know what my expected range will be?


Thanks

DEWESoft Support
Technical support
Posted on 03.10.2019 15:30

Hi,


can I ask what is the range of the accelerometer and which amplifier is used?


If you are using Sirius, you can enable high range and dual core mode.

https://www.youtube.com/watch?time_continue=59&v=mzNyTn3W42s

Lemmy Atom

Posted on 03.10.2019 17:10

@DEWESoft Support

30G accelerometer


The settings below show the measurement range after it had been changed it.

DEWESoft Support
Technical support
Posted on 04.10.2019 11:38

From the accelerometer specification sheet it looks like you reached the accelerometer limit which is 30g. Do you have the option to use different accelerometer with higher range?

Can I ask why are you using the bridge measurement type? From the specification it looks like you should be using a normal voltage measurement type and differential input type.

Lemmy Atom

Posted on 10.10.2019 16:16

@DEWESoft Support

Yes, I understand that I exceeded the range of the accelerometer. Lets say I didn't though, the questions still remains. If I don't know what my measurement range is expected to be what should I set it to? I'm guessing it's okay to set a range one or two stages higher than "expected" due to the dual core feature?


Also, thanks for catching the use of a full bridge input type. That's a habit carried over from our old DAQ's where we treated everything like a full bridge. Do you think it affected the output of the accel? It passed a 2g rollover which is why it didn't raise any red flags for me.

I'll keep it in mind for next time.

Thank you


~EDIT~

I configured my accelerometer to a voltage measurement the way you've shown. I do not have the dual-core check box option.


DEWESoft Support
Technical support
Posted on 25.10.2019 07:38

From the screenshot that you have sent to us it looks like you have Sirius high speed which doesn't have the dual core option.

If you have the option I would suggest using a dual core Sirius which automatically switches between the ranges.

If ithis is not an option, I would suggest using highest range for test and then adjust range if needed.

DEWESoft Support
Technical support
Posted on 25.10.2019 07:38

From the screenshot that you have sent to us it looks like you have Sirius high speed which doesn't have the dual core option.

If you have the option I would suggest using a dual core Sirius which automatically switches between the ranges.

If ithis is not an option, I would suggest using highest range for test and then adjust range if needed.

Login to reply to this topic. If you don't have account yet, you can signup for free account .
This website uses cookies to ensure you get the best experience on our website. Learn more