Chrisszzyy

8 minutes ago, XyFreak said:

No, using Big Reactors or Extreme Reactors doesn't matter. If you use steam for something else this IS gonna be a problem cause the program makes all kinds of assumptions based on how much steam is required by the turbines. It does indeed compensate but that's mostly for error correction not for making up for missing numbers

Ah good. I tried unplugging the other turbine but the RPM still dipped slowly which is weird when the program indicated the reactor was generating 5.3B of steam which is clearly not correct.

I'm a bit confused. Is there a temporary way I can add the steam required for this other turbine somewhere in the reactor code, so it always generates the turbine required steam + the additional steam?

Cheers

2 hours ago, XyFreak said:

@Chrisszzyy sorry for not noticing the part where you statet you already recalibrated. I guess I was too focused at thinking what MIGHT help and not double checking.

I noticed that your output poly has a max of 9453 mB/t while the reactor I built from your image has 6521 mB/t . Also the calculated optimum is set to 0.01 (wrong) while it has a proper value for me.

Is there a server I can reproduce your issues directly on?

I'm a bit at a loss here but I also noticed something else with extreme reactors yesterday:

@ZeroNoRyouki I'll ping you as well since you might want to know what's going on here.

When I first start up my minecraft and load a single player world for the first time, the APIs related to querying the hot fluid state are broken. Both the old and the new ones. The reactor I built from @Chrisszzyys description has a steam tank holding 31400 mB. While this is reported correctly, the current amount of hot fluid is not. The API maxes out at 6250ish mB for that reactor. I'm not 100% sure of whether it just caps out or actually scales but it might do both. The APIs behave normally as soon as I reload the world.

Restarting minecraft causes this issue to appear again. All active reactors are affected. Even newly built ones.

If this also happens on a server then this might already be the issue (since you can't reload the world without restarting the server - in which case the issue comes up again).

The ER version I use is 0.4.5.49 and zerocore 0.1.2.2

 

The issue CAN be confirmed using BRGC as well as it will display the hot fluid tank as not full when it is - in fact - completely full.

 

@Moobien please excuse me if i ask stupid questions or anything. Your reactor looks fine (size wise) so I'm wondering if there might be an issue with fluid transfer. The reactor is definitely hitting a ceiling before it even gets a chance to take its first measurment - it wouldn't error out otherwise.

I've made a bit of progress by removing the reactor entry in the config file and re-calibrating, although the reactor still isn't generating enough steam apparently - Turbine 0b9 spooled up whilst 5e5 and 954 were at optimum RPM but once the stator was enabled on 0b9, the RPM started dropping:

Thinking about my setup; would a small Railcraft Turbine running off the reactor as-well cause any problem like this? As it's not connected up to the computer system, I wouldn't assume that this would cause any problems? It never has done before with the computercraft system, but obviously this program may calculate the reactor output based on the turbine inputs only. I didn't see this as likely, as shown above the reactor is outputting 5.3mB now whereas the turbines only need 4869mB (3 x 1623)  so its clearly compensating already. Just not quite enough apparently.

The server I use isn't open to the public and isn't really set up to, so I can't really open it up im afraid. I am using Big Reactors, but I take it this won't matter?

16 hours ago, XyFreak said:

@Chrisszzyy

Thanks, I just built your reactor in my test world and it worked flawlessy.

Here's what I think happened: You kicked off everything at once, as you should be able to. This caused the turbines to speed up and the reactor to start calibrating at the same time. Then your turbines went overspeed and got shut down, suddenly causing the reactor to overproduce steam causing calibration to terminate. During the last phase something went wrong when calculating the output curve. I can only suggest you rerun the reactor calibration, assuring the turbines won't suddenly fail.

Can you post your br_control.cfg as well? The generated config should look similar to what I here so we can test whether or not my theory is plausible.

        ["d69713ac-bbb2-4ed1-bda5-6e2b11017210"] = {
                    outputOpt = 0.21747975557943,
                  rodLevelMin = 0,
            outputReversePoly = {coefs={0,0.00015333991938894}},
                   outputPoly = {coefs={0,6521.4590172277}},
        }

 

Thanks for spending the time in testing the reactor setup.

I have previously re-run the calibration on just the reactor as I mentioned in the post on Wednesday at 11:07pm, but I don't think I made the fact prominent - Sorry! This didn't resolve the issue and the calibration finished as I'd expect (Tested to the max)

br_control.cfg is below:

        ["fd004851-7cd3-4a5b-941a-92b755887fe6"] = {
                     outputPoly = {coefs={0,9453.6888854358}},
                PWMLevelOffline = 0.8,
                       disabled = false,
              outputReversePoly = {coefs={0,0.00010577881418761}},
                 PWMLevelOnline = 0.15,
                    rodLevelMin = 0,
                      outputOpt = 0.01,
            regulationBehaviour = "grid",
        },

Cheers,

Chris

On 7/4/2018 at 11:21 PM, XyFreak said:

1 -> The reason the program has issues with your turbines is that it assumes that it has exactly the correct amount of blades. The formular is pretty simple: total steam = #blades * 25mb/t. Since Your turbine has 72 blades that results in a total of 1800 mb/t, which is too much for your setup and your turbines will go overspeed.

3 -> 350 should be more than fine... if it was over 700 i knew where the problem is but that... seems odd. Something propably went wrong with the calibration. My guess right now would be that it can't output enough steam and thus the program can't collect enough samples to approximate the reactors behaviour. The red load bar supports that thought.
Can you post a construction plan of the reactor so I can have a look at it myself ( http://br.sidoh.org )?

 

The entire program is supposed to be fully automated without any/a lot additional user interaction. To make this work, a lot of flexibility had to be sacrificed.

 

Regarding the multimonitor issues. The GUI is designed to only run on one monitor, yes. If you have multiple screens / GPUs installed, it'll bind one of the secondary monitors to any of the secondary GPUs and display the program on there, freeing up the main screen. I've never had it complain about a GPU not being present tho o_O.

Running it more than one time is going to give you trouble for sure. I should propably look into preventing it to even try...

 

EDIT:

About the calibration issue - looking at the current output %, your reactor should've been able to output enough steam to your turbines. Can you speed down the turbines and remove the config file, then reboot the computer? That'll redo everything... if it still fails then .. uh... i need to test the reactor in my own world and plot some curves to figure out what's going on.

1 -> I'm aware that my turbines are not optimal but I've put that number of blades on there along with my stator material for cosmetic reasons.

2 -> Reactor layout is attached. It's an extremely old design so please don't laugh! It has been running since April 2015 so is tried and tested, however inefficient it is.

3 -> As I've said previously, I know the reactor design can output enough steam to my turbines - I've been running them on a previous (ComputerCraft) legacy program for over 3 years. If I remove the config file, it'll wipe the forced turbine RPM and steam inputs, and therefore I'll be back to square one, as the mod isn't able to calibrate with the turbine design I have.

With regards to the monitors - I expected that may be the case. I may have to run multiple instances on different systems for each monitor then.

Cheers

On 7/3/2018 at 8:10 PM, XyFreak said:

@Chrisszzyy first of all, thanks for your feedback.

-> 1)

Can you go into detail please?

Each rotor blade in a turbine consumes 25 mB/t per blade that's attached to the rotor. Unless things have changed significantly, anything more than #blades * 25 mB/t is wasted. The controller should NEVER give your turbine more steam than that. This is mentioned in the instructions. And to be honest.... the method of calibrating turbines is REALLY straight forward. I'm guessing #3 actually the root of your troubles. If your turbines CAN go overspeed (aka you have too many blades) then BRGC is going to run into a brick wall but it'll also tell you that this happened (the turbine ERRORs out).

-> 2)

The CLI was something I hacked together to help out in some instances but was never meant to be actually used by the general public. It can help debugging stuff tho, which is the primary goal. It also helped getting BRGC up and running on computercraft without the GUI a WHILE back as an experiment

-> 3)

The reason the program falls short to produce the required amount of steam is propably because of the reactors core temperature (just a guess). The red bar also indicates that the reactor is running hot. I do agree that I should propably remove the temperature limitation.... If you want to test that out: reactor_active.lua around line 68, assign 0 to pTemperatureLimit instead of the formular that's there. I should propably remove that myself - the limit code IS quite old and is known to cause problems with inefficient setups. (It's also ugly and the code around that needs to be cleaned up >_>).

Out of curiosity: How hot is your reactor running?

 

Lastly please allow me to comment on your first sentence.

I've been working on this since BR for 1.7 got released and Improved it ever since. I released it to the general public because a friend of mine used it on his server and ppl really wanted it (by the time the only real alternative was dw20s script iirc and that one sucked... and could only control one turbine/reactor combo so...yeah). I've been improving it ever since. Trust me - if there's a problem I run into, it's gone in a matter of hours. Same if you actually tell me how to reproduce the issue myself.

This also means that I do not understand the unbelievable part and yes I'm a bit butthurt by this. I do sincerely appologize if using my program has cost you a lot of time. That was never my intention - this program is supposed to just run and go. Anything else is not acceptable.

That being said - if it's so unbelievable I would love to hear all about the troubles you had setting everything up. You can PM me anytime or join my discord or teamspeak if you think straight up talking about it would be faster. You don't need to worry about meeting a pissed XyFreak btw - I'm always open and thankful for suggestions. I'm happy to hear you out off-record. If you want voicechat, tell me and I'll pm you the details.

Thank you for your reply; I really appreciate the effort you have gone through to code this and reply to me in details.

Regarding:

1-> Each turbine has 72 blades in total and when calibrating, reaches over 1950RPM before it displays an error, just like you've mentioned. As I previously said, these turbines all sit happily at 1623mB/t (The highest output) with the old program.

2-> I appreciate that lol. I assumed there'd be more options to configure things via the GUI if someone wants to go on a manual approach, so I tried using the CLI.

3-> I've tried implementing that code (Plus re calibrating the reactor) but it doesn't seem to have made a difference. It's currently running at ~228 degrees Celsius whereas they usually run up to ~350 degrees without issue. Picture is attached for the reactor.

Regarding the rest - Most of the problems have stemmed from issues getting the GUI to run on certain monitors - Literally I've had it working on one monitor, unplugged and restarted the server it's all running on (OC Server) and the other screen it complains about a GPU not being present - Very random stuff. This coupled with not being able to run it on more than one screen (which looking at it now looks to be by design) and not being able to set parameters for the turbine.etc on the GUI, soured my initial impression of the program. I apologize for this - I've found it rare in the past to get any kind of useful response from a developer and in this case I've been wrong to assume that.

Thank you for your support!

I've been trying this mod over the past few days and have run into so many problems, it has been unbelievable.

I've managed to get round a few but there are still a few (Critical) problems left.

• What's your issue? (expected vs actual behavior)
  • 1 - Turbine calibration seems to only suit one type of turbine - The most efficient. Anything else and it loses its marbles - Bear in mind this program may be used by players not-yet on the end-game Ludicrite ore or purely have chosen not to go down that route. I've had to manually set the max RPM/steam consumption of the turbines on my install due to the fact the calibration clearly does not work with my setup.
  • 2 - The CLI. There are a few very frustrating, rudimentary mistakes with regards to guiding the configuration via GUI. The "help" command will tell you to put a sequence of arguments in one order but when doing so, it coughs up errors relating to the order of arguments. There's also a general lack of documentation surrounding this method of configuration - The only available resource seems to be the "help" command.
  • 3 - (The biggest) - Despite overcoming the above, the program does not seem to be capable of managing my reactors' steam output vs. turbine requirements. On the trial setup, I have one reactor & three turbines; each of which consume exactly 1623mB/t for an optimum RPM of 1841RPM. For some reason, this program is only enabling the reactor to produce around 3.89 B/t, clearly short of the ~4,869mB/t required. One turbine is sat continuously on "KICKOFF" and the other two are barely at max-RPM. I can get one turbine to max output alone but put another on and it starts buckling. My reactor is definitely capable of it (See bottom).
• What version of OC / ER are you using? (actual mod versions pls)
  • OC: 1.7.2.1166
  • BR: 0.4.3A
• Is your reactor active / passive?
  • Active
• Are there error messages popping up when the GUI is closed / when you run brgcctrl? 
  • Not in relation to the problems above, no
• Is the grid controller enabled?
  • Yes
• Are there external energy components connected? If so which and how many?
  • N/A
• Can you screenshot anything that might be useful? (e.g. actual reactor / turbine GUI)
  • See Attached

Just as a sidenote; I came across this mod to replace the legacy ComputerCraft monitoring system currently in operation across my power station. It has been in continuous use for almost 3 and a half years (24x7) and is fully able to manage the 2 reactors and 6 turbines (2 identical stations on the same site) at maximum capacity, so ultimately I know the setup is capable of operating at the spec mentioned above. I have also specifically chosen to run this turbine setup rather than the most optimum due to a decision I made very early on in the project.

If you have any tips or suggestions, I'd appreciate it.

Thank you for the program thus far; with the functionality out of the question, it looks great!