BravoYankee4

Hmm... Viggen + WW2 aircraft = Ring of fire. It all makes sense now :music_whistling:

By the way, must make sure that the people running this simulator is throwing out FSX as soon as possible and replace it with DCS :) Anyway it was a sweet experince flying that simulator :)

Aaaahhh... I wish all of you would have the opportunity to see, hear and feel this beauty IRL. It sure was sweet growing up in Sweden during the 80's situated in the middle of two major airbases and all the road bases just minutes away. Thank you LNS! Now I just have to convince the DCS-BIOS and Hawgtouch people what to prioritize next :pilotfly:

Thanks for this update. I'm fully aware of that the extra time for hobbies can be very limited from time to time. Especially when there is a 2.5 year old smurf in the house and a second on it's way ;) I also agree on that a stable version next year is better than something with bugs this year. Regardless of release date, I do appreciate your work. By the way, is there any way that me (or the community) can help out when it comes to get support for more modules (like the MIG-15)? Vielen dank!

Ian, any progress regarding the RS-485 support in DCS-Bios?

There are plenty of different shields available out there, with different kind of terminals, like this one: http://www.seeedstudio.com/depot/Screw-Shield-p-1238.html Search for "terminal shield" or "screw shield" plus arduino. My plan is to wait for the next version of DCS-BIOS with support for RS-485 before I design an build any interfaces. Then it will be possible to have an Arduino MEGA as master and then a lot of slave interface boards. You can of course have a lot of Arduino boards today working in parallel with one serial connection each, but that isn't very effective.

Well, I wasn't really recommending the wire wrapping alternative, just adding an alternative with a smile. I do second that purchase a soldering iron and learn to use it is a good idea. Eventually you will find a lot of things that can be done once you have got some skills.

Yes, human players controlling SAM's would be a nice touch for this game. If they implement the tactics of Zoltán Dani it would be a real threat for the people in the sky, rendering them not so immortal any more :thumbup:

Or put some nails in a wooden board and do some solderless wire wrapping :music_whistling: * Wire wrapping

I am about to do some PCB's for DCS BIOS and Arduino, but mainly focusing on the output, since I will have normal lightbulbs (not LED) in the indicators (*). Since I am also planning a MIG-21 cockpit (unless there is a Viggen announcement soon) perhaps we can work together with this. I have designed and ordered other boards previously, like the A-10C NMSP panel (see attachment below). By the way, these are for sale if anyone want them (cause I have cancelled my plans for a Warthog cockpit). The Leobodnar boards are great, but not for DCS BIOS. Still I will probably use it anyway, connected and configured as a normal input in parallel with the Arduino boards. * Based on ULN2803 Darlington array circuits and/or 2N7000 N-channel MOSFETS, so I will not exceed the current limits of the Arduino.

Yeah, I have spent some years in FSX with airliners and know exactly what you are talking about :pilotfly:

Isn't this something that is specific for different aircrafts? I.e. that some aircrafts just had an on/off airbrake (like the MIG-15).

For that you would need some kind of macro/script. Search for autohotkey (AHK). Or try out the Vaicom software with the voice attack profiles available. Haven't tried it myself yet, but it seems good.

Ok, no problem. DRAKEN, TUNNAN, LANSEN :music_whistling: Any of them would be like x-mas for me.

Perhaps someone of us Swedes will visit the museum again soon? :) I have some pictures from there, but I really don't think any of them is more detailed than the ones posted here...

Shit... with a HKP9 module I must migrate to being a chopper pilot...=)

No, just some wishful thinking... partly based on some clues that are more or less confirmed.

Well, he asked for more details :) And fun to provide some facts and not just wishful thinking and speculation to this thread for a change :music_whistling: No, some of the details I knew about, but most was just translated from the documents from Brisse.

Yes, it is amazing what they achieved. So having all data sent and presented almost in real time in the aircraft is of course and advantage compared to a system with voice based GCI interceptions. The data message was 103 bits long and was sent at 3000 bits per second – so you could get 29 messages/updates per second to the aircraft indicators. Actually only 68 bits was used for the message, the other bits was for validation and some in reserve. For synchronization every message was initiated by twelve “1” in a row and every tenth bit was always a “0”. There was also some parity bits after every part of information (heading, altitude etc) in order to detect bit errors in the data transmission. The messages started with an address/callsign that was one letter (A-Z) and two digits (0-9). So in theory the system could handle 2600 unique aircrafts (5+4+4=13 bits). Next part of the message was about the current phase, that was either Phase I (homing) or Phase II (target acquiring). When in Phase II the Distance indicator (AVST) changed the resolution. Target altitude was sent in a three digit decimal format, with the resolution of 200 meters (2+4+3= 9 bits). The maximum height data indication (HÖJD) for J35 was 20.000 meters and for JA37 it was 30.000 meters. The following part consisted of some pre-defined text messages to the pilot from the ground crew (5 bits). Examples are “FEL” = error, “HÖJDÄNDRING”= altitude change, “NYTT MÅL”= new target, “BRYT” = break, “LANDA = land (RTB) and so on. Next there was the course for the target and this was sent binary coded. In theory the resolution could be 0,703125 degrees (9 bits). Followed by the bearing to the target with same characteristics as above (9 bits). The distance to the target was also binary (9 bits) with the resolution of 1km in the range 40km to 400km (Phase I). In Phase II mode the distance indicator was showing 100m resolution up to 40km. The altitude angle (up or down) to the target was not implemented from start, but according to the resource it was sent as 6 bits. There was also an altitude difference to the target in meters sent with 6 bits. Finally there was 4 bits in reserve in this protocol. Not sure if they where ever used. There was two pre-defined test messages that could be used to verify the functionality (1: course 179,2 degrees, and 2: course 180 degrees). So when the test button was pressed the course indicator should show that course. Since the JA37 plattform had a more sophisticated computer and had better avionics it was not dependent of getting it’s own position from the ground radar. So the only information needed here was the vectors to the target and then the internal computer calculated with higher accuracy. In the J35 there was a dedicated indicator for distance and altitude. The other indication was presented on the radar scope (similar to ILS indicators). When going from the J35 Draken platform to the JA37 Viggen there was only smaller updates of this system so it was operative for almost 40 years (1960’s to 2000’s). Comment: The export models of the Draken didn't have this functionality. In this video (of a Draken in Finland) you can see there are some indicators missing : [ame] [/ame]

Thanks for the documents Brisse. If we get a Viggen (or the Draken) it would be really nice to have the datalink simulated. It was never proven in an open conflict, but it gave the Swedish air force a huge advantage during the whole cold war period. This system was unique in many ways and was way ahead of other countries. According to some sources the radar vendor (Marconi) at some point said this proposed solution was 10 years ahead of everyone else. It gained a lot of interest from the NATO countries (and unfortunately a lot of details was probably revealed to USSR from some spies also). So in the early 60’ies the Swedish air force had a digital data link to the aircrafts providing automatic data with unique target data for all aircrafts. The ground radar continuously measured the position of both the own and the enemy aircraft and sent new data with a high update frequency. The foundations of this systems was used for almost 40 years. With the JA37 platform it was also possible to have a link from aircraft to aircraft.

Discussion on this topic already started some weeks ago here: http://forums.eagle.ru/showthread.php?t=151852 As you ca see there was comments from LNS to provide some material if needed. Some other reference material as well.

Maybe it is a CA module? :joystick:

Well, I have a three monitor setup (however only 3 1280*1024 monitors) and would have a really hard time going back to a less wide format. Depending on how you set it up there could be a decreased field of view... perhaps not with a UHD/4k monitor if you sit closer to it... Going to a three curved screen setup would really be something awesome though :)

I got you babe... da-da, da-da... [ame] [/ame] Sorry for not adding any value to this thread, but we all passed that point approximately 100 pages ago anyway :music_whistling:

I'm planning a MIG-21 cockpit build, but realize that there are some data I need to export, like the selected RSBN and PRMG channels (since the channel selector is a rotary input I can't build something mechanical to show the selected channel). For this my intention is to have two sets of double 7 segment displays connected via DCS-BIOS. As of my understanding I need to have the channel numbers exported in some way. I have seen many similar things done for the A-10C, so I just assume it would be doable also for the MIG-21. Anyone know the exact variables I need to export, and in what format the data is presented? Do I have to convert it to a numeric value etc?