When it comes to volume, frequency of the beeps and time in between beeps I think the video clip shows how I would like it, just like the clip.

So YOU should take the time to figure out the information needed from the clip. What is the spectral content of the beeps (they are probably not a single pure tone), how long is each one of them, what is the time from the start of the first to the start of the second? There's also the issue of how loud you want it to be.

These are basic specifications detailing what you want, not how to implement it. If you expect others to figure them out, then you can expect to pay those others engineering consulting rates to do so.

 

So YOU should take the time to figure out the information needed from the clip. What is the spectral content of the beeps (they are probably not a single pure tone), how long is each one of them, what is the time from the start of the first to the start of the second? There's also the issue of how loud you want it to be.

These are basic specifications detailing what you want, not how to implement it. If you expect others to figure them out, then you can expect to pay those others engineering consulting rates to do so.

The clip is just to show how I would like to have it and I think the clip shows it well. I appreciate all the effort from all although I do not expect or demand it. I am just a guy trying to figure out how to get a circuit like this for a hobby project and after seeing that movie I thought it sounded great with those two beeps, however my electronic skills are below the level for building this and learning all would take some time although I am moving forward.

 

The clip is just to show how I would like to have it and I think the clip shows it well. I appreciate all the effort from all although I do not expect or demand it. I am just a guy trying to figure out how to get a circuit like this for a hobby project and after seeing that movie I thought it sounded great with those two beeps, however my electronic skills are below the level for building this and learning all would take some time although I am moving forward.

And would like to add that my reply was just to show what I am striving towards and I hope all got a cool video clip, when Yeager is trying to restart the engine, electronic guys usually like a cockpit with beeps, gauges, switches etc

 

I think that what people here are trying to say, is that this is a technical site about electronics. Members here come to share their ideas, knowledge, and experiences, both as hobbyists and professionals alike.

There are many cool things happening in the world and people say, "Gee, that is so cool, I want something like that!"
Hence, if you want it, you either go out and buy it, or you take some of your own time and effort to figure out how to make it yourself.

It is the latter option which this site promotes. We are here to help you learn the steps to DIY that cool gadget if that is the path you wish to take.

 

I think that what people here are trying to say, is that this is a technical site about electronics. Members here come to share their ideas, knowledge, and experiences, both as hobbyists and professionals alike.

There are many cool things happening in the world and people say, "Gee, that is so cool, I want something like that!"
Hence, if you want it, you either go out and buy it, or you take some of your own time and effort to figure out how to make it yourself.

It is the latter option which this site promotes. We are here to help you learn the steps to DIY that cool gadget if that is the path you wish to take.

Will contemplate if the circuit way is the path to take in this case or if buying an ELK-124 annunciator would work just as well, anyway I have gotten forward in my quest and I thank you all for that.

If the way of the circuit is chosen I will most certainly reappear in the shape of the apprentice.

 

Thanks, any idea who could do schematics from description?

The circuit is not complex.

This post is extremely misleading. I read this to mean you could describe the circuit, i.e. the parts involved and connections between them.

What you revealed later is that you had no concept of a circuit, just a video showing what it ought to do.

What you are asking is not drawing a schematic from a description, it is designing a circuit to replicate the behavior shown in a video. That is a far more involved task.

 

My intention was all along to get a view on how to do this based upon the clip and I also mentioned that I do not have the knowledge how to do this. Noone need to answer.

 

My intention was all along to get a view on how to do this based upon the clip and I also mentioned that I do not have the knowledge how to do this. Noone need to answer.

I should also mention that this topic started in another thread called The right stuff "beep beep" circuit and then someone mentioned the company that makes boards, however then all melted together, best would have been of coarse to have stayed in that first thread for all of this topic and avoid misunderstandings.

 

I should also mention that this topic started in another thread called The right stuff "beep beep" circuit and then someone mentioned the company that makes boards, however then all melted together, best would have been of coarse to have stayed in that first thread for all of this topic and avoid misunderstandings.

Maybe. But you asked a valid, simple question. And the straight answer is, no.

I gave you the detailed answer in post #7.

 

Really, in response to post #29, there are engineering firms that will create a design, and in fact the whole system, in response to a request. BUT THEY ARE NOT AT ALL CLOSE TO INEXPENSIVE!!!
I have worked at companies that designed and built assorted systems based on descriptions and specifications of requirements. Usually a lot more complex than producing a string of beeps, by the way.
But always, "Professional rates Applied."
AND, there was at least one instance in which our response was: "We can build just what you asked for, BUT IT WILL NOT WORK"
Then I provided them with a description of just why it would not work. A few days later we did get a request to quote "a system that would work." I did produce a proposal and we did get a purchase order, and we did deliver a system that worked. And we continued to do business with that client for many years after that order.

 

i don't get it how many people spend their life online either using computer or phone and still don't know how to use it. you have internet at your finger tips, ASK IT...! simply talk to machine (AI server of your choice).

as stated before, solutions CAN be engineered though even then, one would likely opt more flexible system using MCU. and if so, why bother engineering something that will be one of, or small volume? just get ready to use "development board" - simple and off the shelf unit (can be small too), download free Arduino IDE and let AI write you code for it and tell you how to load it into your board? instead of wasting time of 10 engineers, talk to Google - zero hand holding needed and you can pat yourself on the back for accomplishing something in no time and on a shoestring budget.

for example:

or faster delivery










and now, you have something with very low part count, low cost and it can be tweaked in code. moreover, you still have several other pins that can be used for any other things if needed. i suggest get the 4pcs from Amazon due shorter delivery and it will give you some pares in case you blow things up or find more uses for it.

as shown above, this load is low (and very brief) so linear regulator on shown unit is more than enough for this. but when linear regulator gets hot, you can use switching regulator (can be external) as a fix. cheap fix with high output current capabilities are also available as ready to use modules, for example:

 

I should also mention that this topic started in another thread called The right stuff "beep beep" circuit and then someone mentioned the company that makes boards, however then all melted together, best would have been of coarse to have stayed in that first thread for all of this topic and avoid misunderstandings.

Since that thread was started by you and was specifically about doing exactly what you are asking in this thread, it definitely should have stayed in one place. We have a policy aim of one thread per topic and one topic per thread.

If you feel that the original thread had come so confused that a clean start was needed (and I don't thing that was the case here), then you should have provided a link to the other thread and said a sentence or two about what was relevant in that thread and what is the specific focus of the new thread (i.e., why you are splitting off), perhaps quoting the key stuff from a post or two.

In general, think of a thread as it's own universe. What happens in a thread stays in a thread, unless explicitly brought into another thread for context. Even members that are following and interacting in both threads usually won't correlate the two as being about the same thing -- we routinely have parallel threads running, started by the same person, that are about unrelated things. But there are also going to be many members that are completely unaware that this other thread exists. So it's important that each thread be standalone and that any information from another thread that is relevant be brought in via quote or paraphrase, or be linked.

 

Really, in response to post #29, there are engineering firms that will create a design, and in fact the whole system, in response to a request. BUT THEY ARE NOT AT ALL CLOSE TO INEXPENSIVE!!!
I have worked at companies that designed and built assorted systems based on descriptions and specifications of requirements. Usually a lot more complex than producing a string of beeps, by the way.
But always, "Professional rates Applied."
AND, there was at least one instance in which our response was: "We can build just what you asked for, BUT IT WILL NOT WORK"
Then I provided them with a description of just why it would not work. A few days later we did get a request to quote "a system that would work." I did produce a proposal and we did get a purchase order, and we did deliver a system that worked. And we continued to do business with that client for many years after that order.

I also worked for a company that specialized in lunatic fringe projects that often started with vague descriptions of what was needed (or, worse, with customers that "knew" what was needed but were completely off target). They generally knew the underlying concepts of the big picture and novel aspects of what they were doing extremely well, but really had no idea what was needed to get an ASIC that would achieve their goals. A large part of the time on some projects was working with the customer to figure out what was actually needed, which sometimes meant convincing the customer that what they thought the needed was not the case. It was very much an iterative process in which we taught them things about our end and they taught us things about their end. In many ways, this was both the most frustrating and the most exhilarating part of the job.

As you said, professional rates apply, but there is a potential alternative.

As has been noted, this project is conceptually very simple, albeit it very poorly specified. The scope is comparable to an early lab project in an MCU course. So approach the people that teach such a course at a university and propose it as such. Let the engineering students try to design and implement a solution. Perhaps you can even participate as a judge.

You could start out something like this:

I am interested in having a device that, when power is applied, produces two beeps just like those in the attached video clip from the movie "The Right Stuff". Unfortunately, I lack the knowledge and skills to design this. But it seems like a good lab project for an appropriate course in your department.

Here is what I'm thinking: Challenge the students to design a circuit that, when 24 V power is applied to it, emits two beeps as nearly identical to those in the clip as they can achieve (in terms of timing, tone, etc). After the two beeps, the device remains silent until power is removed and reapplied.

To motivate students and also give them a taste of real world engineering, perhaps as part of the project each student (or team) could make a short video showing their solution and demonstrating it. I would then review and judge them based on how well they achieve my objectives. That could be folded into their grade in some manner. In addition, whichever team wins could then build a final device to be sent to me in exchange for a $100 prize (paid by me).

If this is an idea you find worth pursuing, let's talk further.

 

So approach the people that teach such a course at a university and propose it as such. Let the engineering students try to design and implement a solution. Perhaps you can even participate as a judge.

This is pretty trivial for a university lab project.

More like a junior high project. Or even something to ask a local maker group or STEM group/class for help with.

 

This is pretty trivial for a university lab project.

More like a junior high project. Or even something to ask a local maker group or STEM group/class for help with.

I'm not talking about a semester-long project. I'm talking about a one-week lab project near the beginning of an introductory microcontroller course (i.e., not long after the blinking-light hello world project).

 

It makes the most sense for engineering students to learn to use discrete logic, ( AND, OR NOT gates,flip-flops, counter) before introducing those little computer blocks that do not teach much other than programming. Useful controls connect to the real world, and mostly that requires I/O circuits with actual voltages and currents, not zeros and ones. Processor modules are quite handy, but vast over-kill for a lot of simple logic implementation.

 

It makes the most sense for engineering students to learn to use discrete logic, ( AND, OR NOT gates,flip-flops, counter) before introducing those little computer blocks that do not teach much other than programming. Useful controls connect to the real world, and mostly that requires I/O circuits with actual voltages and currents, not zeros and ones. Processor modules are quite handy, but vast over-kill for a lot of simple logic implementation.

Notice that I said an introductory MICROCONTROLLER course. This almost always followed one, or even two, courses in digital logic using non-programmable logic.

Now, a very good exercise -- almost never done -- is to have students in a discrete logic course design and implement a system to meet a set of requirements at the end of a discrete logic circuits course and then use that exact same set of requirements as an early exercise in a programmable logic course. This has a few benefits. First, it let's them do an apples-to-apples (albeit anecdotal) comparison between the effort and ease of both approaches. But, from a pedagogical standpoint, it allows them to focus their attention on the aspects specific to using programmable logic instead of the problem being solve because, for them, it is already a solved problem in most respects. Unfortunately, courses are almost never that well coordinated, so it would have to be done as part of the same course. While not impossible, the first part would take away time available to tackle programmable logic topics, and invariably invite grumblings and complaints from students.

 

Useful controls connect to the real world, and mostly that requires I/O circuits with actual voltages and currents, not zeros and ones. Processor modules are quite handy, but vast over-kill for a lot of simple logic implementation.

???

I have no problem using a $2.00 8pin micro for "Simple Logic " Circuits. Which incidentally include I/O cpability.
They posses a plethora of posibilities and Just because it posseses many features, often not required, is a plus of requiring a low inventory.
Changes or mods tend to be in software rather than changing or adding components on a board.
I tend to see picmicros as a further transition or extension of discrete logic usage.
No different than the transition I made from using individual transistors to IC's when they appeared with all the inherent circuitry built in?

 

My big gripe is about one publication that claims to be for electronic experimenters , but their projects always used arduino modules when a single IC would do the job with no code.
How will anybody learn about circuits function if they never read about circuits or how to use them, or how they work??

I am not trying to start a fight or offend folks.

 

My big gripe is about one publication that claims to be for electronic experimenters , but their projects always used arduino modules when a single IC would do the job with no code.
How will anybody learn about circuits function if they never read about circuits or how to use them, or how they work??

I am not trying to start a fight or offend folks.

I sympathize with and share your frustration, but that doesn't change the fact that times have changed. People start at a higher level of abstraction now than they did forty years ago when I did. In fairness, I started out at a higher level of abstraction than the people even a couple decades before me did. And so on. That's the nature of "progress" and it is not without its downsides.