|
|
Post by raderik on Dec 15, 2018 17:30:43 GMT
Hello, First I apologize for my poor English but maybe you will understand me.
I noticed a serious problem with battery life in the DC-10-30CF panel during the APU and GPU operation(APU Generator are connect). After turning on the APU or GPU, I always prepare maps and calibrate the INS system etc, it takes about 10-15 minutes. After this time it is impossible to turn on the engines and landing, navigation and beacon lights because the battery is dead. Even when the APU/GPU is working properly, the energy is lost until the battery is fully empty. But the panel indicates that everything is fine!
I used the Doug Dawson dsd_battery_charger tool for testing. And actually , the energy from the battery is drain despite the operation of APU or GPU.
Could any of the developers check this problem?
I’m Using FSX-SE version, maybe this is a problem?
Thanks for the help.
|
|
|
|
Post by aerofoto - HJG Admin on Dec 15, 2018 18:43:46 GMT
Have you changed any of the the panel configuration or imported any other additional utilities into the panel your using ? Otherwise .... there must be a simple step you are overlooking in regard to either engaging the battery switch (it should be "ON" be default but can also be disengaged in order to aid a full cold & dark panel connfigiguration/reconfiguration and engine start if desired) .... or the 3 Battery Bus switches .... all of which are located within the Electrical section which forms to top left quarant of the F/E sub panel. Are you (correctly) running the APU "prior to" engaging the Electrical Bus switches ? Or alternatively .... Have you (correctly) simulated connecting to a GPU/external poer supply if not using the APU ? .... "both" scenarios are available in these simulations (but only one of which can be used at any time) and each worlks fine .... "so far as I'm aware", Using either scenario "correctly" results in what I can only describe (from experience) as being "a very stable source of power supply" for all panel instrumentation and prior to engine startu" .... and which I can leave "ON" for very long periods without ever risking or even observing any power supply failures. For starters .... I suggest you review the following sectionss of our online/forum based manual for the DC-10's .... DC-10 MANUALtonymadgehjg.proboards.com/thread/9147/dc10-panel-installation-handling-notesI recommend you refer to each of the following sections of the manual .... 2A.00 and 2B.00 FLIGHT ENGINEERS PANEL/s .... the Electrical system for each DC-10 F/E panel is identical but other features differ in accordance with aircraft type version. 3.00: DC-10 ELECTRICAL SYSTEM .... general information. 4.00 APU & GPU ASSISTED POWER SUPPLY OPTIONS .... tutorials and videos. 5.00: PANEL CONFIGURATION/FLIGHT PREPARATION CHECKLISTS .... checklists. Be advised that further updated/improved versions of our DC-10 aircraft base packs, panels .... and their supporting guages/core files also, are soon to be released (not available yet) .... though none of the edits/improvement featured within these new files implicates the Electrical system/s simply because no need for any changes has ever been demonstrated .... to date. Mark C BOG/CO |
|
|
|
Post by George Carty - HJG on Dec 15, 2018 20:54:51 GMT
I designed the panel to work in both FS9 and FSX, and since the former doesn't have native APU or GPU support, I decided to force the FS internal electricity to always be on (using electric_always_available=1 in the aircraft.cfg file) and do all the electrical power simulation within my own panel code.
Does this help?
George
|
|
|
|
Post by aerofoto - HJG Admin on Dec 15, 2018 22:39:05 GMT
What George (and I) are both saying (trying to) here is .... These DC-10 simulations each load into FS with a default "ready to go"/engines running scenario .... MEANING  .... all essential systems are "ON" by default .... i.e. Battery Switch "ON", APU and its associated Electrical Bus switches "OFF", Engine Generator switches and associated AC and DC Tie switches "ON" .... and all other essential systems are "ON" and/or otherwise correctly pre-configured "by default". Using this default scenario all one needs to do is .... adjust fuel loading (best done during the actual aircraft selection process), set radio frequencies and both navigation and flight instruments, set interior/panel and external lighting "ON", and finally set both flaps and elevator trim .... "prior to" departure. To try'n reclarify some of this .... 1. The Battery Switch is always "ON" (by default) .... all essential panel systems are also "ON" (by default) .... so .... there's no way any power supply failure can occur during this scenario .... unless part of the electrical system is manually disengaged in error. 2. If the engines are shutdown when then these simulations are first loaded into FS .... then this action "will" (intentionally) result in a total power failure .... with all instruments/systems flagged or otherwise inoperative .... unless the APU has first been started and its Electrical Bus correctly engaged .... OR .... unless External Power Supply (the alternative GPU scenario) has been engaged (instead of of using the APU system) .... both "prior to" engine shutdown. 3. Following engine shutdown .... and so long as the APU has been started and its Electrical Bus correctly configured .... OR .... so long as the GPU and its External Power Supply system is correctly configured .... there's no way any power failure can occur and nor will these panels/simulations suffer any power failure either following engine shutdown .... even if left to sit for a considerably long periods of time. To reconfirm that all is functioning properly I have, during the past hour, conducted tests .... using the APU scenario and with all engines shutdown. I then left the simulation running in this state for over 30 minutes (APU only running) .... and "all is functioning correctly". No interrupted power supply or failures were experienced occurred at all. I can only "suggest" you must be misunderstanding and/or possibly mis-configuring either the APU or GPU power supply scenarios .... and which could then result in failed or interrupted power supply along with an associated loss of all instrumentation too. Again .... please refer to the manual extracts (tutorials and checklists) which I've provided for you above. These are our proven/recommended/prescribed procedures for each of these DC-10 panels .... and they "do" each work faultlessly .... "if employed correctly" to start with . Mark C BOG/CO |
|
|
|
Post by raderik on Dec 16, 2018 9:54:33 GMT
Thanks for the quick answers. Of course, before I started using the DC-10 panel. I read the instructions, 'Panel Installation & Handling Notes' aerofoto which version of flight simulator you used for testing FS 2004 or FSX? I did the same as in this movie from Benoit Plamondon www.youtube.com/watch?v=oKsRksZ_Y_MIt is strange that the panel indicates that everything is powered correctly.I installed the dsd_battery_charger tool by Doug Dawson(Of course, I tested the panel first without any modifications!) to run the test. It allows you to check the battery voltage. After switching on the APU and system power supply. The dsd_battery_charge utility indicates the battery voltage drop(But the panel shows that everything is fine with power). When the voltage drops to 17 volts it is not possible to start the lights and engines.It looks as if the panel was based on the default FSX power supply. What's strange, the electric always available = 1 entry should protect against energy loss. Amazingly, the panel seems to work correctly, but, as I repeat, I can not start the engines, and the navigation lights and position lights stop working. Panel lights work correctly, but the dome light has disappeared. The only solution to my problem is installing dsd_battery_charger which prevents the battery from losing energy. Or just quickly switching on one engine and turning on the generator ENG I have tested many airplanes like the TU-154B2 from project tupolev. Also HJG DASSAULT MERCURE 100 and I've never had problems with electric power. |
|
|
|
Post by aerofoto - HJG Admin on Dec 16, 2018 13:05:03 GMT
This entire DC-10 project took some 3 years to develop. As it was developed it was tested in both FS2004 and FSX .... the entire project is both FS2004 and FSX compatible. The manual is based on FS2004 primarily .... but .... the recommended procedures are precisely the same for both FS2004 and FSX .... there are no differences. Benoit's tutorial videos were made in FSX only. There must be a step in the procedures which you're either misunderstanding and/or possibly not implementing correctly .... because the recommended procedures are well tested and proven to work fine in both FS versions. I can't understand why you should need to do that at all .... and we can't comment in regard to any item/utility that we don't provide as part of our simulations or that we're othyerwise not familiar with. No other modules are required for these DC-10 simulations .... with the exception of either a "free" or "fully licensed" version of FSUIPC .... only if one wishes for the WX radar, fuel transfer system, and fuel dumping systems to function. Even if the electrical system is correctly configured .... the engine will not start if the pneumatics system is not correctly configured .... you need to check this .... maybe. I regret to say .... I cannot replicate the issue, you say, you are experiencing  As a courtesy to its author/designer .... please remember (everyome) the DASSAULT MERCURE "is not" an HJG production .... we can't take credit for something that's not ours. HJG "did" provide some minor developmental assistance .... BUT .... this particular project is the exclusive property of Mario NORIEGA and must be publicly acknowledged as such. HJG simply host the MERCURE by kind consent  Mark C BOG/CO |
|
|
|
Post by George Carty - HJG on Dec 16, 2018 14:19:00 GMT
Panel lights work correctly, but the dome light has disappeared. This implies that the native FS electrical power (which powers the dome light) has failed while the electrical power simulated within my own panel code (which power the remaining lights) is still working. I've tried leaving the panel running in FSX (DVD version with the Acceleration expansion) for 30 minutes with either APU and GPU power running (and both with and without FSUIPC installed) but with all engines shut down, and I saw no draining of the battery. Perhaps it's an issue specific to FSX Steam Edition? George |
|
|
|
Post by raderik on Dec 16, 2018 14:55:12 GMT
Panel lights work correctly, but the dome light has disappeared. This implies that the native FS electrical power (which powers the dome light) has failed while the electrical power simulated within my own panel code (which power the remaining lights) is still working. I've tried leaving the panel running in FSX (DVD version with the Acceleration expansion) for 30 minutes with either APU and GPU power running but with all engines shut down, and I saw no draining of the battery. Perhaps it's an issue specific to FSX Steam Edition? George I suppose that problems can be caused by the FSX STEAM edition. Unfortunately, I do not have another version of the Simulator except FSX SE. I will continue to play, but I think I will have to look for a solution on my own. Thank you again and I am sorry that I took you so much precious time.
I also wanted to congratulate the whole team on this amazing panel P.S And I am asking for forgiveness I know MARIO NORIEGA created this wonderful plane which is DASSAULT MERCURE |
|
|
|
Post by aerofoto - HJG Admin on Dec 16, 2018 18:00:42 GMT
No problem .... since that's what we "TRY" to do here for everyone's benefit ANYWAY .... George's test results seems to concur with my own .... as described above. After replying last night (and thinking more) I was going to "suggest" the very same possibility too .... since experience has taught us that different things can be experienced using different FSX versions, but, with no one particular experience being unanimous/common.to either or a specific FSX version ... .and that's where things tend to get really difficult. Not saying this is the foundation on this issue, but, if not caused by a simple panel misconfiguration then it could (possibly) have some bearing on "RADERIK's" experience. Mark C BOG/CO |
|
|
|
Post by George Carty - HJG on Dec 16, 2018 18:14:19 GMT
I've PM'd Mario to have a look at this, as he spotted and fixed an FSX Steam specific issue with his own Dassault Mercure project: maybe he can try reproducing the bug as I haven't been able to...
George
|
|
.... all essential systems are "ON" by default .... i.e. Battery Switch "ON", APU and its associated Electrical Bus switches "OFF", Engine Generator switches and associated AC and DC Tie switches "ON" .... and all other essential systems are "ON" and/or otherwise correctly pre-configured "by default".
