Booster error

[leonardo2609]

The central Booster does the “Boosterback” and the re-entry burn, however, when it finishes doing the last burn mentioned, the “isCoreBooster” gives an error. And the curious thing about this is that the error only happens in the central booster, in the “Falcon Heavy” the error does not happen with the adjacent boosters. How can this be fixed?

[acr8133]

The central Booster does the “Boosterback” and the re-entry burn, however, when it finishes doing the last burn mentioned, the “isCoreBooster” gives an error. And the curious thing about this is that the error only happens in the central booster, in the “Falcon Heavy” the error does not happen with the adjacent boosters. How can this be fixed?

Can you provide a screenshot of the core's terminal?

[leonardo2609]

O Booster central faz o “Boosterback” e a queima de reentrada, porém, ao terminar de fazer a última queima citada, o “isCoreBooster” dá erro. E o curioso disso é que o erro só acontece no booster central, no “Falcon Heavy” o erro não acontece com os boosters adjacentes. Como isso pode ser consertado?

Você pode fornecer uma captura de tela do terminal do núcleo?

Sure here it is:

Here's closer:

This happens shortly after the reentry burn.

[acr8133]

Are you sure that the tags are correct? I can't seem to find the problem with the code as the list of booster should default to having isCoreBooster, unless it's tagged "2" or "3" in which case it removes it.

[leonardo2609]

I put the tags as is in the "README" file. However, this error only happens with the central booster.

[leonardo2609]

And now after a few flights with the code the error mentioned above stopped happening, now the booster simply stops after performing the re-entry burn. But the curious thing is that the script moves the booster, but does not turn on the engines for landing. And again, this error only happens with the central booster. The “Tundra Heavy” side boosters perfectly complete the itinerary:

• [ ] They carry out the boosterback,
• [ ] carry out the cost phase,
• [ ] the re-entry burn,
• [ ] and finally carry out the landing burn and land at the coordinates defined in the itinerary perfectly.

[leonardo2609]

So I decided to test the code and changed the following code:

local isCoreBooster is 1. // for correct engine selection if (core:tag = "2" or core:tag = "3") { set isCoreBooster to 0. }

for that:

local isCoreBooster is 0. // for correct engine selection if (core:tag = "2" or core:tag = "3") { set isCoreBooster to 0. }

and sometimes he lands.

[leonardo2609]

Still no success with the central booster landing. 😥😥

[acr8133]

Hey mate, can you try reverting the changes you did in the script? Then add a nametag on the interstage "1", the nosecones "2" and "3" (without the quotations).

[leonardo2609]

Hey mate, can you try reverting the changes you did in the script? Then add a nametag on the interstage "1", the nosecones "2" and "3" (without the quotations).

Ok, I'll do it and send you the result here.

[leonardo2609]

I have a doubt. What is the purpose of naming ports “APAS”? I ask this because, when I went to launch and I'm going to look which commitment is in the interstage and it is already "1", however, this happens even when I don't name the port with "APAS".

Regarding the request above, I already did the test without the quotes, however, I had the same error.

[acr8133]

May I know which part is the root part of the rocket?

[leonardo2609]

It's the fairing adapter, the one that separates the load.