Can i fire Shared Variables' "Bad Status" alarm artificially?

[jlu97005082]

And what shall I do to experience 'Bad Status' alarm. SVE is running on Windows platform PC.

[jlu97005082]

Is it a stupid question? Just tell me YES or NOT!

[RavensFan]

I don't think it's a stupid question.  But you will have to be patient.  I don't think there are very many people who know the answer to that, or would have ever thought they would need to know the answer to that.

How of curiosity, what is your reason that you want to fire this "Bad Status" programmatically?

[jlu97005082]

One shared variable one heat level sensor(DS18B20).
I want use it's "Bad Status Alarm" to alarm person on duty -
the corresponding DS18B20 sensor was failure!

But what shall I do to experience 'Bad Status' alarm first?

Don't know why, don't know the solution. Is that right?

Why there is no example project about "Bad Status Alarm"?

http://forums.ni.com/t5/LabVIEW/what-s-the-meanning-of-bad-status-in-DSC-alarm-config-for-Shared/m-p...

NI call this "answer"?

[jlu97005082]

There is an alternative way:

Use one U32 bitfield shared variable to describe most 32 DS18B20 sensors' status. Delete corresponding shared variable on SVE when DS18B20 was failure,  recreate after deploying a good sensor...

[jlu97005082 · Accepted solution]

The answer is positive. I have found the way by myself. I can alarm them on duty the sensor is failed through firing 'Bad Status Alarm'.

[tommy1983]

How did you do that , I encounter the same question.

[jlu97005082]

Binging with itself at that time. But with recent DSC editions, just binding a bad url.

[tommy1983]

That's a good idea.But I'm using a Modbus I/O Server of the DSC module. Your solution may not suit me.Thanks all the same.

[tommy1983]

My url binded to Modbus i/o server is solid and unchanged .