Compositor SoftwareCompositor Software

Tag : translation

By ruslany

NPO Compositor adapted NRTOS 9.0.2

NPO Compositor adapted NRTOS 9.0.2

It took more than two years to adapt the Compositor 9 software from Compositor Software into Russian language. NPO Compositor has done a great job of introducing new functions and protocols into Compositor 9. The interface and documentation has been translated into Russian language and consists of chapters on IP switching and routing (2700 pages in total). It allows classifying this software as network real-time operating system (NRTOS). Compositor NRTOS 9.0.2 package consists of the real-time operating system itself with a graphical user interface executed on MaxMSP, Niagara software modem, which is a sample of a real-time moment (into which this sample was recorded) made with MaxMSP also, and an Android application RAD96, which inherited its name from the Compositor 9.0.1 main module (in 9.0.2 a22 assembly an extended version of this code is called VSF – virtual switching framework). All three versions have the same documentation as they access the same functionality. The difference is that RAD96 is an autonomous system and contains many more extensions that have not yet been issued. Compositor NRTOS 9.0.2 comes with 9134 extensions of management information bases, which were issued from the autonomous system RAD96 during the production of documentation. Niagara 32 software modem also contains a dump of this database (9134 routing tables). We also succeeded in classifying such an interface: by the type of execution, it can be considered a switching router, in contrast to the Compositor 7, which is considered a switch.

You can see the Russian language interface of Compositor 9.0.2 build a22 below:

Compositor NRTOS 9.0.2
Compositor NRTOS 9.0.2 channel matrix

The command language in documentation can be used within amateur radio terminal software such as TrueTTY on Windows and DroidRTTY on Android. This means that you cannot program the NRTOS directly (only via MaxMSP graphic user interface) but you can issue this commands through a teletype operator working in your autonomous system. Such an operator usually is a part of telegraph services still acting to the present moment. It is the only possible way to reprogram an autonomous system.

Seven protocols, implemented by NPO Compositor for version 9.0.2, enable communication in the Ethernet network. At the testing stage Compositor 9.0.1 was used mainly for packet protocols of amateur radio, but now in version 9.0.2 communication is carried out in the Ethernet network using the protocols used for switching and routing in this network. NRTOS includes 6 interior gateway protocols such as RIPv1, RIPv2, OSPF, OSPFv3, RIPng, EIGRP and one exterior gateway protocol for communication between autonomous systems (BGP – uses IPv4 version of the protocol). In addition, external communication is possible through 6-to-4 GRE tunneling.

Compositor 9.0.2 implements stateful and stateless NAT64, it can be used to create L2VPN and L3VPN services by exporting firmware in WAV and AIFF formats. Conversion from IPv4 to IPv6 is done on the fly in the NRTOS and makes it possible to map a single IPv4 address to multiple IPv6 destinations. As you can see from the Compositor 9.0.2 interface, it is a BSR router and is responsible for loading the system. Such a system consists of extensions that allow the server to participate in various workgroups. Compositor 9.0.2 is the installation program for the CP-6137-960FX server, to which this site is dedicated. This server is the only machine capable of generating emissions from the autonomous system RAD96 and this is its main value.

By ruslany

Compositor v3 in the Radio Session

Here is a demo of Compositor v3 Long Endurance System in a session with professional VLF systems. THIS IS A REAL WORLD EXAMPLE! Ton of technics used to suspend Compositor translation in full-duplex two-way radio system.


First, I thought they are joking; to fight Compositor is a tough task. It almost impossible to shut down due to RTC8k radioprotection features. However, the Compositor v3 regeneration suffered from unauthorized dimmers on that channel. In a translation, you can hear how SASER produces a long-query translation to this sources and how they respond with Morse on that channel.

Second, two feeders were used on an auxiliary channel of SASER. Auxiliary channel available only in Compositor v3 Hypervisor Radio Shack and not in standalone or Max for Live version of SASER. In the recording, you can hear how AI-RT1024 and TC25 generators feed the regenerator to receive long and pure ether from different sources. Up to three sources on the same channel communicates to each other with different LFO and Morse signal translators. The central place belongs to the SASER, which can produce a diversity of patterns.

TC25 is a huge phase rotator, which can potentially brake the incoming signal regenerators. AI-RT1024 from the other side can initiate stable translation in SLF band. Channel protection mechanisms were used in a LINK session. It is hard to predict the chain of feeder tunings, because main tuning comes from RTC8k holographic radar. It rotates the tunings of the feeders in according to the threat source, searching for a better trajectory of signal translation.

By ruslany

Closed loop vs. Infinite loop

Here I would start a series of discussions on a topic of radio translation technics and their impact on the radio-electronic security. First, I would stress out the importance of the subject of comparing two modern technics to initiate radio communications, which are closed loop and infinite loop strategies.

Closed loop and infinite loop both have recreation in Compositor Software instruments such as MDL12 for infinite loop structure and RTC4k, RTC8k and RT-z8 for closed loop structure. The infinite loop stays for an infinite time translation and, as a Fourier series, implements the continuous time interval for non-harmonic analysis. Closed loop from the other hand may be a short type of translation like one bar Morse code message. Closed loop much more secure in its implementation. Infinite loop can be easily broken with radio-electronic security instruments. For example, one flyby of AVACS, navigating through the geographic parallel may completely shut down infinite loop radio translations on a territory of the whole country. The infinite loop can be broken partly or at whole, when both positive and negative frequencies does not work, and the only band, which remains in this situation, is a closed loop structure.

Using Compositor Pro v2 one can edit and reinstantiate the Ether on VLF band. First, you can apply Compositor Pro v2 to negative frequencies and then apply it to positive frequencies. Infinite loop communications are not secure and full-duplex modems must have a resynthesis module as Compositor Software instruments has. Not only resynthesis must happen to instantiate closed loop also the transport technics such as output channel detectors must be used. Both Compositor Pro v1 and v2 has closed loop structure on a C language level. This in fact gives much more stable results compared to later machines implemented on GenExpr C++ code. However proper implementation (such as RTC4k, RTC8k and RT-z8) of higher-level machines can be as stable as Pro versions. The most significant difference is that GenExpr machines are fully real-time compared to Pro versions, which have one bar bufferization.