What are we working on? (Waterfall 🌊 Thread)

Hello and welcome in the eve project. As you may know, we’re trying to build the first Open CH4+LOX Liquid Rocket Engine.

In this thread you will find the most recent updates from the members of the project that are not directly related to a specific activity or work package. It’s a sort of sink for unstructured material, ideas, videos or images of your current work on the project that do not fit more structured places in the Gitlab Issue boards.

For the other resources of the project:

Official Documentation

Gitlab

The project root namespace on Gitlab is here. Within that namespace you will find all the individual projects we are currently working on. In particular you can check the project issues in order to see what are the current opened (and closed, if you’re curious) activities, the deadlines and milestones imposed, and what we’re struggling with. If you find something you’re interested in, don’t feel shy and post whatever comes to your mind.

Telegram Group

Feel free to join our Telegram Group . The group is for informal and friendly chat, not for technical discussion that must be conducted in the appropriate place. Non-members, curious people and supporters are welcome!

Calendar

Welcome and enjoy the trip! :rocket::star2: :space_invader:

2 « J'aime »

A recent video from Skyward Experimental Rocketry testing their hybrid rocket motor:

That would be an awesome result after 1y.

1 « J'aime »

Feed line

We propose you here a draft of the engine feed line.

Notes:

  • The architecture is as simple as possible.
  • One relief valve is placed before entering the injection head:
    • It should be as close as possible to the combustion chamber in order to quickly react to a pressure increase.
    • Being positioned on the feed line and not directly on the combustion chamber is not the best solution but it simplifies the first combustion chamber architecture. It should be moved directly to the injector head if possible.
  • One manual valve is placed on each relevant section of the feed line in order to depressurise the system in case of an electric valve failure.
  • One Check (non return) valve is placed on the feed line in order to avoid the pressure raise toward the tank. It can create a large pressure drop: its impact has to be evaluated.
  • The electric valve is commanded through the Eve Control System, following the programmed test path. It is placed as close as possible to the injector head.
  • The electric emergency valve is commanded by the operator through an independent control system in order to abort the test (Eve Safety Control System). It is placed as far as possible from the combustion chamber in order to reduce the probability of being damaged during an explosion.

Feel free to comment with critics, suggestions or proposing a different solution :slight_smile:

3 « J'aime »
1 « J'aime »

I modified the position of two manual valves to be able to depressurize the system even if all the electric valves are inoperative.
Note: the check valves in the schematic are considered “normally open”.

Feed line

2 « J'aime »

4 « J'aime »

I have some updates on the Documentation System. I started to scratch a bit the structure that I have in mind here: https://code.federation-openspacemakers.com/p/P0078-eve/documentation-system/issues/1

It’s also a chance to show how should we use Gitlab issues for project tracking and management. In particular this is really useful: https://docs.gitlab.com/ee/user/project/issue_board.html

1 « J'aime »

It is interesting! :slight_smile:
If needed, we can:

  • add a “requirements” section in “specification”;
  • add a “test” section before “results”.

We utilise a similar management software at work (Jira).

Ehi @luca.litterio, thanks for the feedback. Can you please provide this feedback directly on the Gitlab issue? Let’s keep this forum thread for informal, unstructured discussion.

1 « J'aime »

Hello everyone!

I just join the association and the EVE projet. My name is Calin, I am an aerospace engineer. I have a background in thermal and fluid simulation. I am eager to learn and work on more concrete projects :slight_smile:

I am still reading all the material available on the forum (quite a lot actually !).

Did you ever plan some meetings in Paris?

1 « J'aime »

Hello and welcome on board Calin. Feel free to explore the little things we just started to develop and fee free to ask any question. :).

@luca.litterio @iervese.francesco @erwan.zamora are the other members of the team. Feel free to contact them too.

PS: I’m in Paris (actually in Palaiseau), so we can actually organize a meeting somewhere near the RER B . Maybe with the others that are around Paris or just the two of us… Let’s see if someone else is available :slight_smile:

We’re going to do a videoconference this Sunday

1 Mar 2020 at 19:00 to 20:00 [lang :us:]

@luca.litterio @luca134 @iervese.francesco @mathis.blt @erwan.zamora @antonio.lamonarca

  • Meeting of new members
  • Recap of the current status
  • Organization of the project
  • Task assignement for new members
  • Preparation of the meeting with the Polytechnique’s Fablab

1 Mar 2020 at 20:00 to 20:45 [lang :fr:]

@mathis.blt @luca.litterio @antonio.lamonarca

  • RĂ©sumĂ© de la visio prĂ©cedente en français
2 « J'aime »

Recap Videoconference

Presents: @luca.litterio @antonio.lamonarca @mathis.blt @luca134

  • We just discussed a bit the general situation of the project, especially to the newcomers. We identified three macro-areas on which we’re working on
Mechanical Design of The Combustion Chamber Software Development of The Control System Development of the documentation system
@iervese.francesco @luca.litterio @tid
@luca134 @antonio.lamonarca
@mathis.blt
  • We decided to choose Sunday evening as the day where we do the videoconferences
  • @luca.litterio and @antonio.lamonarca will coordinate during this week on the control system
  • @luca134 and @iervese.francesco will coordinate during this week on the mechanical design
  • We identified a possible task for @mathis.blt that will be the mechanical design of the injector plate.

2020-03-08T19:00:00Z → 2020-03-08T20:00:00Z we’re going to do the next videocall with the objective of setting up a bunch of todos for the next weeks on the Gitlab Issue Board.

2 « J'aime »

A bit of inspiration:

It talks about programming, but the final closure is really enlightening.

3 « J'aime »

Good morning.
We are writing down the circuit schematic for the control system tests. As an example, we report the schematic for the feed line control system test:

As you can see, the schematic has been quickly drawn utilising powerpoint.
Do you know a software which can help in realising a similar schematic in a « better » way?
Better in terms of:

  • precise connection lines;
  • automatic ranging/organization of connection lines;
  • better labeling of connection lines.

Thank you in advance for any idea!

Is KiCaD too complex?

Also Fritzing looks easier.

2 « J'aime »

+1 for Fritzing! Even the starter in electronics that I am was able to use it intuitively.

1 « J'aime »

First handmade part in Fritzing! :grin:

2 « J'aime »

Even if it is not ‹ open ›, Fusion 360 enables since one year the creation of schematic up to gerber files in order to subcontract pcb. (Fusion 360 absorbs Eagle)

Thanks Antoine! The idea is to stay as Open Source as we can. :slight_smile: