Getting a beep

[booshky]

I am a novice user here also:
The problem is this, We are using a Signametrics digital multi meter ISA card to take a reading and then save the value into excel. The macro that Wes wrote works except that the BEEP that we need so the tester can tell if he got a valid value is not working exactly right. Can you use a DLL instead of the beep?
We have a DLL for the DMM that takes the reading, is there one we could use to play a wave sound? It has to be 100% reliable.
The beep we are using is the win-2000 default beep thru the on board sound.

[vass0922]

If the DLL is a com object then yes you could call it from a macro. Possibly from an API call but not sure how difficult that is from VBA.

Should PM a mod to close the other thread.

[qball]

The macro that Wes wrote works except that the BEEP that we need so the tester can tell if he got a valid value is not working exactly right. Can you use a DLL instead of the beep?
We have a DLL for the DMM that takes the reading, is there one we could use to play a wave sound? It has to be 100% reliable.
The beep we are using is the win-2000 default beep thru the on board sound.

How are you trying to 'beep' in the macro?

How do you know the macro accepts a value from the DMM, but doesn't beep?

Why does the 'tester' need a beep? Perhaps MsgBox?

Getting an excel macro to 'beep', should be pretty easy.

Some dumb ways:

Call (ExecCmd??) a DOS batch file that beeps.

Call (ExecCmd??) a java program that does this:

//ASCII code for Bell, which will beep thru soundcard
System.out.print("\007");

[booshky]

Qball: Thanks for the reply.
The Macro accepts the value from the DMM and it puts the data into a cell just as we want it to. The Dmm card by it self has no sound features. I can see the new value put into the cell.
The tester needs the beep ( that was my first question too ) because the circuts are such that if you look away from where you are, you get lost. The beep is critical to this process.
Getting an Excell macro to beep was easy on the first machine I set up for them with a PCI DMM. This one is an ISA card that we used before on a 486 like four years ago. The PCI version is $2k so they balked at getting that. Thanks for the help..

[qball]

Getting an Excell macro to beep was easy on the first machine I set up for them with a PCI DMM. This one is an ISA card that we used before on a 486 like four years ago. The PCI version is $2k so they balked at getting that. Thanks for the help..

Maybe I'm wrong, but this seems more of a macro issue than hardware.

As you state the macro puts value in cell, so hw and macro working, thus not ISA/PCI problem (else no value?).

So answer the questions about how the macro beeps, or no help.

The tester needs the beep ( that was my first question too ) because the circuts are such that if you look away from where you are, you get lost. The beep is critical to this process.

Your definition of critical is different than mine.

Tester can be blind, but hears really good? Tell tester, "no lookey away". Better yet. "look at this cell, if it get's value/value change, workey".

What are the DMM specs and how do they compare to the capabilities of ISA and PCI buses?

Tho if macro gets value from ISA/PCI card and can place in cell, what is the next line in the macro after that?

[booshky]

Maybe I'm wrong, but this seems more of a macro issue than hardware.

That is what I was thinking at first, because all the hardware works, sound card, speakers, computer, DMM card. The problem is the BEEP is not RELIABLE for some reason. It works perfect for 20 readings then skips one. Some times when you stop the macro it plays all the BEEPs that it skipped, like it saved them up. Very weird.

As you state the macro puts value in cell, so hw and macro working, thus not ISA/PCI problem (else no value?).

I have come to believe that it is a hardware/software incompatibility.

So answer the questions about how the macro beeps, or no help

The macro beeps because he has a line that reads BEEP. ( Works on the other machine, Wes said he has used BEEP for years )

Your definition of critical is different than mine.

The person running this has 30,000 parts to check and they all have to work. Looking up at the screen between rows is impossible. Thanks for your help
( we ordered the PCI DMM card yesterday so this is it for me )
Booshky

[qball]

The problem is the BEEP is not RELIABLE for some reason. It works perfect for 20 readings then skips one. Some times when you stop the macro it plays all the BEEPs that it skipped, like it saved them up. Very weird.

Which is why it is most likely macro issue, not:

I have come to believe that it is a hardware/software incompatibility.

For the 20 or so readings, YOU are getting value, and beep, then value, NO beep. The point being you are getting value, but not always beep. Thus, hw is functional. The macro code for beep, as you stated, is problem.

Very weird, no. Since stopping macro can restore lost beeps? Ever get a bepp without value?

What you are experiencing is the difference between synchronous and asynchronous events? Seems reading value from card is synchronous and beep asynchronous.

See if PCI card works, or same problem occurs...

[booshky]

See if PCI card works, or same problem occurs...

I will try that as soon as I can.