Who's Online
Recent Topics/Posts
|
Pages: « 1 2 3 4 5 6 7 8 9 10 »
41
« Last post by henkie on April 17, 2024, 08:38:49 AM »
In the new release of BMS, that roller switch is supported. It indicates that the canopy is closed. The switch you mention is not used in BMS. However, you can use it as the roller switch  If you have the roller switch and use it as the "canopy closed" signal, you could use the other switch for actually open/close a canopy if you have a canopy installed on your pit. In that case, the switch actuates the motor to open/close the canopy (frame).
42
« Last post by Tulkas on April 17, 2024, 05:42:33 AM »
The "roller switch" is atually used in BMS. It is the detection that the canopy is closed.
The other switch that you can manually toggle, and is pushed back when the spider is "closed" is only needed if you want to implement a "real" moving canopy 
That that you said really confused me. I'm still running my cockpit with BMS 4.34 and I use the "other switch that you can manually toggle". Is momentary down, so if you release the canopy stops and doesn't keep on closing, as safety measure, and locks in the up (opening canopy) position. It works as such in BMS, I don't understand what you said about " is only needed if you want to implement a "real" moving canopy"
43
« Last post by henkie on April 17, 2024, 04:52:52 AM »
Of course, if some functionality can be realized by just some hardware, the Arduino + software would be "overkill". It is good to think things through and keep it as simple as possible. But take your example: (interior) LIGHTING. When you read the F-16 documentation, you see that even this panel "hides" some functionality which cannot be simply done in hardware. I designed a hardware "controller" for the LIGHTING panel (years ago), and even though it included some of the described functionality, it did not include everything ... It is also a matter of how far you want to go with the 100% correct simulation 
44
« Last post by Red Dog on April 17, 2024, 03:38:37 AM »
Well, do remember one thing, if your lights work with BMS without DCSbios, then these lights should work on their own with DCStoF4 without DCSbios with DCS
The same was true for my simshaker issue:
- Simshaker has 2 versions depending if you use DCS or BMS
I was using the DCS version that required a declaration in the DCS scrip file which as I said above, does not work
But basically, The simshaker BMS version works with DCS as well through DCStoF4 and that one does not required the script.
So you basically can avoid the declaration in the script file and have the simshaker work through BMS shared mem, like the rest of things
The trick is to have as few as possible declarations in that scrip file of BMS to avoid potential conflicts, pass everything through BMS sharedmem with DCStoF4 and it works much better.
45
« Last post by questerymj on April 17, 2024, 02:45:41 AM »
I don't know about DCSBios, but I run Helios and DCStoF4 with no problem as long as DCStoF4 is above the helios declaration
I do also use simshaker, but that one is not working when DCStoF4 is declared above it. And if I declare simshaker first, then DCStoF4 doesn't work anymore
For now, my pit has no Simshaker anymore... choices and pitbuilding compromises unfortunately
Thank you Reddog! I guess Helios need to be last too. I ever successful get DCStoF4 and Helios run together. but I need either F4TS or DCSbios to run the lamps too. It's pain in ass to endless test how to get all runs well you know...XD
46
« Last post by Rufus on April 16, 2024, 08:10:18 PM »
You'd think that...but I've been doing software testing for aircraft avionics and systems for 35 some years now and watching the screw-ups due to over-reach almost daily. Which usually begin with - "it's just software". Best approach is to select the best approach for the tasking.
I totally agree with doing a lighting controller/box because that's what they do on a real jet...but it's a chunk of hardware and on software is involved. At least for Interior Lighting.
But my thoughts for my pit have more to do with functions or operational procedure not included in BMS base software that can be easily incorporated with wiring. Some of my thoughts on lighting and power management fall into that category.
47
« Last post by henkie on April 16, 2024, 04:10:16 PM »
Also don't forget that there are quite a few things you can hard-wire your pit to do to emulate the RL jet that BMS doesn't think about, or implement correctly. I'm already thinking about such with regard to my lighting power management...just plain bypass BMS and hard-wire.
In my solution (WAT - Wireless Arduino Transceiver) I have both implemented. Try to avoid "hard-wiring", make it a bit more "intelligent". For example lighting. Instead of connecting switches and pots directly to lamps and solenoids or dimmers, connect them to inputs of an Arduino (Nano for example). The software can do the "clever" things (correct F-16 operation). The Arduino drives the hardware (lamps, solenoids etc.) You can do anything in the software
48
« Last post by henkie on April 16, 2024, 04:04:48 PM »
Don`t make just what your sim does, make all that is available, no matter if actual used or not
+1  (that is, make it "future-proof")
49
« Last post by henkie on April 16, 2024, 04:04:11 PM »
The "roller switch" is atually used in BMS. It is the detection that the canopy is closed. The other switch that you can manually toggle, and is pushed back when the spider is "closed" is only needed if you want to implement a "real" moving canopy
50
« Last post by Atlas on April 16, 2024, 11:36:57 AM »
Are there any plans or measurements for the bits where the switches are mounted? Would be nice if I can 3D print these and get them working. I believe I already have a copy of the spider switch and the hinge assembly to connect it to the cockpit, but that's it.
Pages: « 1 2 3 4 5 6 7 8 9 10 »
|
Guests: 10
Hidden: 0
Users: 0
Recent Posts