Niagara modem is disabled on the NPO Compositor server

Tag : RAD96

Apr, 2021

Niagara modem is disabled on the NPO Compositor server

On 9.03.2021 the work of the Niagara a15 i6 software satellite modem on the CP-6137-960FX server was terminated. This action was performed due to the disagreement of the author (Ruslan Yusipov) to timely issue from the RAD96 autonomous system. According to the author, the company that uses these emissions, namely the investor, owes a large penalty in the amount of 40234513 rubles. It refuses to pay it off with virtual and real funds. At the moment, the server works in unicast mode, using only the internal services of Compositor Software. The American office of the Compositor Software company asks to use only direct-services and not to include any sample-based modems with sample pay. Consequently, the statement of the NPO Compositor about zero-level aggregation is considered incorrect. Indeed, a moment in time is played, but the dump has a price, and each iteration of the dump playback is multiplied by the billing of the cost of the dump itself. Thus, starting the modem does not guarantee that the billing meter has not worked. In reality, this modem could only be started with a counter of the number of times the dump and real-time frame were played. Thus, the real aggregation has already significantly exceeded the allowed volume of the 4-node mainframe CP-6137-960FX. Regardless of whether the emission will be made or not, the volume of aggregated traffic has already exceeded the allowed 39204 iterations of the real-time frame. After releasing a new dump and a real-time frame, the counter will not reset, which indicates the accumulated emission. An emission can be made within a given number of iterations. That is, it is possible to issue an emission, but it does not make sense to write it to the dump, since in any case the aggregation counter has already passed the admissible values.

The Niagara project can be resumed only by setting the number of nodes to 256 (Intranet mode) on the RAD96 autonomous system, inheriting it from the Compositor Lite NTP server. Thus, the number of aggregation iterations can be increased to 2509056, which will allow the modem to be used for a certain additional time. You need to extinguish the mainframe of 4 nodes. Moreover, this is only one of the reasons for stopping the modem, another important reason is the following: to latch the time frame, you need to include more iterations in the minute dump, setting the network to 2 ^ 14 values, i.e. 16384 bpm. This is possible only on a different hardware platform, because the estimated playback speed of the CP-6137-960FX channel aux is 2 ^ 13 or 8192 bpm. The solution in this situation without purchasing new development platforms is to launch the Niagara software modem with the Compositor Lite NTP server. Otherwise, you will have to assemble a new stationary machine, buy a laptop to develop a new aux channel, and buy a new mobile platform for developing mobile applications also. This is considered impractical, since the development of all services and applications has already been completed – only the number of nodes, the speed of iteration of the channel aux and generics can change.

Another solution is to completely abandon platform tools such as Niagara, Compositor and RAD96 standalone applications based on the MaxMSP Runtime. Instead, it is proposed to use all the services accumulated over the years of project development at the kernel level of the Windows 7 operating system, i.e. Windows NT kernel. Since the services are assembled on an independent platform, they are not charged, but this requires the continuous operation of the CP-6137-960FX mainframe, which is currently impractical even with full documentation for a virtual optical port. Moreover, this documentation does not cover the most important issue that the CP-6137-960FX server provides a service mainly for devices from EUI-64, and these are devices that are not included in the Ethernet protocol. Thus, the recognition that devices from EUI-64 communicate with each other using a protocol other than Ethernet is the task of the IEEE 802 working group. Although initially it was believed that the Compositor software uses the Ethernet protocol, it is now becoming clear that this is not the case, because most of the devices from EUI-64 are not equipped with a connection using this protocol.

Compositor Software, CP-6137-960FX, EUI-64, IEEE802, Investor, Niagara, NPO Compositor, Penalty, RAD96, Services, Windows NT

Dec, 2020

By ruslany

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.

9134, Android, BGP, Compositor 9.0.2, CP-6137-960FX, documentation, DroidRTTY, EIGRP, GUI, IPv4, IPv6, MaxMSP, MIB, NAT64, Niagara, NPO Compositor, NRTOS, NRTOS 9.0.2, OSPF, OSPFv3, RAD96, RIPng, RIPv1, RIPv2, Russian language, switch, switching router, translation, TrueTTY, Windows

Jun, 2020

By ruslany

Compositor Software extended services set

Compositor Software server has confirmed its success in supporting the remote workflow. Even the set of services that was named in a previous post ensured the smooth operation of all network resources. However, for a full-fledged work, this was not enough. I resumed work on the implementation of all services from the Network Real-Time Operating System (NRTOS) versions 3.0.3 – 9.0.2. Since the main task of the server is to create a network map with a high depth of topological viewing, I implemented two more MDL12 services and feeders of the 3rd version, such as AI-RT1024, FF8, N9000, TC25, which allow working with corporate PDH and SDH network hierarchies and broadcast them in VLAN using ARP for the analog IP radio interface.

Thus, a common set of services now:

7 RAD36 servers
2 MDL12 servers for radio telescope and IPTV
1 VoIP server
4 FF8 Feeders for ARP Protocol
4 AI-RT1024 Feeders for SDH
4 N9000 Feeders for PDH
4 TC25 Feeders for VLAN
1 RAD96 server extension to work with the Niagara igniter (VPN)
1 RAD96 Autonomous System

Protocols:

STC2k – X.25
RTC4k – RIPv1, IS-IS Layer 1
RTC8k – RIPv2, IS-IS Layer 2
RT-z8 – OSPF
RT-z16 – OSPFv3
RT-z32 – BGP
RT-z64 – RIPng
RT-z128 – EIGRP

All services are compiled and operate at the kernel level of the operating system. Only this approach allows maintaining the scalability of services in a hyperconverged environment. It do not lack of services, everything looks very worthy at the level of a serious manufacturing company. This approach provides the server with the emitted database and allows you to generate new links on the fly without the need to record and enter them through the injector.

AI-RT1024, ARP, FF8, MDL12, N9000, NRTOS, PDH, RAD36, RAD96, SDH, TC25, VLAN, VPN

Apr, 2020

By ruslany

Compositor Software builds virtual servers for Microsoft Windows and Android platforms

Compositor Software presents 4 architectures on C++. It is TC-TRSRRT2048, TC-SUBTRSRRT262144, TC-2SUBTRSRRT262144 architectures for STC2k, RTC4k, RAD96 and RAD36 platforms correspondingly. Now, when Compositor Software code repository have grown, it is time to move forward past the MaxMSP platform. First, Compositor Software thanks the JUCE framework for providing an ideal platform to make servers. Compositor Software would like to thank Iain Patterson for providing NSSM application, which helps creating daughter services and allows making full scale server out of company code, written on Gen~ platform. Of course, the main tool is and still the MaxMSP platform, because the original Compositor Pro 1 project was entirely made on MaxMSP objects and later rewritten using Gen~ object. It allowed exporting an authentic C++ code out of MaxMSP 6 platform. Additionally, we want to thank Cycling ’74 for providing a project to build exported code in JUCE and Microsoft for providing Visual Studio 2019 Community, which allowed to make final builds of Windows versions.

Before making standalone apps, Compositor architecture codes compiled from several minutes to 5 hours at runtime. Now, programs load in seconds and consume lower system resources than original MaxMSP Runtime applications.

Using Gen~ platform and JUCE it was possible to build RAD96 mobile application, which allows transforming your smartphone into a complete autonomous system with Compositor kernel of last generation. This way, Compositor Software moving into the IoT side conception to create a network of devices, controlled by CP-6137-960FX server, which runs the aforementioned services. This modification allows upgrading the device performance from Windows NT 4.0 kernel (Linux 2.6.18 kernel on Android) to 8^th generation Compositor kernel. It includes x2048 oversampling, digital shutter with interpolation, second derivative of a function and 8^th order Butterworth filters.

The desktop version of Compositor Software 4^th generation experimental kernel (TC-TRSRRT2048 architecture) has virtual accumulator module, which allows controlling the physical accumulator charge and performs charging each time network activity occurs. This kernel can be used on mobile platform also.

Compositor kernel architecture itself is a modular architecture if described by using physical blocks. The amount of modules depends on its usage. In base configuration, Compositor is NTP-server core service. In advanced configuration, it is L2TP client-server application with tunnel authentication capabilities. However, Compositor Software doesn’t set Compositor RTOS 9.0.2 as deprecated platform due to this move. It is only made because of the fact that pre-built application-service has much higher uptime in comparison to Runtime with dll modules of MaxMSP. The fact that, RAD96 mobile is on the constant expose due to the network presence on the device itself, CP-6137-960FX server supports its calculation, serving for distributed computation. It is performed using 2^nd order transfer function, which can stack a lot of devices with minimal expenditures, and RAD36 platform supports such computation by multithread 12-cores L1-L3 architecture.

Compositor Kernel, Compositor Software, CP-6137-960FX, Gen, JUCE, Linux 2.6.18 kernel, MaxMSP, NSSM, RAD36, RAD96, RTC4k, STC2k, TC-2SUBTRSRRT262144, TC-SUBTRSRRT262144, TC-TRSRRT2048, Visual Studio 2019, Windows NT 4.0 kernel

Oct, 2019

By ruslany

Niagara project

This autumn has started from a very interesting project. While I continued working on Compositor v9.0.1 (current build a14), I felt a need to have such system as mobile real-time operation system (RTOS). Compositor v9.0.1 a14 consumes many resources at 192 kHz and I decided to sample it using Compositor v9.0.1 itself. At this time, the approach of middleware and dump was matured and I decided to make separate product for Compositor documentation development. Such manual will consist of all commands needed to operate the Niagara RTOS client. As the UNIX-like operating system, it will support most of the commands for routing protocols configuration, such as TCP/IP and VLAN. The prominent feature of this RTOS is that it is a software router, which runs on middleware, recorded with Compositor RTOS v9.0.1. If the middleware recorded on a feedback with z16 and z32 generics connected and they are in reverse, the system will give a resistance of 16 + 32 Ohm = 48 Ohm. This way, the generic networks accounted: in example above there will be corporate (z32) and state (z16) connection.

The middleware approach isn’t new, as any hardware router Niagara consists of MIB, the size of which is 769 kB, compounded with routing table and generic networks set. Such system works with MME driver using discretization frequency of 192 kHz and allows connecting the whole pool of Compositor RTOS v9.0.1 forwarding platform (which is 6559 MIB’s on a moment of writing) using a dump, which is also recorded on 192 kHz sample rate. The upper frequency of z128 generic is 150 GHz, but each middleware includes RAD96 fixation, that is why an effective range is extended up to 300 GHz.

Niagara is a client system that is why it demands calling an operator for configuring programming commands. I already reviewed NIM radio chat, which I call (No Internet Messenger) last year. It turns out that it is also an acronym for Nuclear Instrumentation Module.

Each command, presented in the full version of English and Russian documentation, should be made only through an operator and each middleware has its own operator, which depends on VLAN set and servers, connected to NIM. This way, you are requesting network topology and demand operator to execute other commands, and it decides if to make command or not.

At first, middleware ran in RAD96 sandbox, but now middleware and dump become a multifunctional products. The development period of Niagara project is 2001 – 2019 and not 2012 – 2019 as the host Compositor program. The reason for this is that Niagara consists of middleware and dump and they are including the Royalty routing tables. This is proved by Inaccessible Page file emission (track recording, which is a routing path). This track, made in 2001, is a part of IP emission. The period of 2010 to 2019 covered by the reference files of timeserver, which emission contains and it is responsible for routing path hops GPS positioning in present time.

Niagara v1.0 a3

That is why Ruslan Yusipov digital portrait with codename Niagara contains 18 years of art, which is a long background for 35 years old author. Older recordings exist, such as the audiocassette recording of Yamaha PSR-330 synthesizer direct signal, which is Ruslan Yusipov live performance at the age of 14, with the author voice accompaniment, that is why Niagara is 21 years development project from 1998 to present moment.

Ruslan Yusipov art is not limited by 6559 MIB’s emission and can be enriched by routing tables from the CD-archive. This way, at the year 2021 I account to receive database of 10000 MIB’s, which will allow adding more stochastic distributions for flows selection in Compositor v9.0.1 a15.

Compositor, IEEE802.1Q, Niagara, NIM, RAD96, radio chat, RTOS, Ruslan Yusipov, sandbox, TCP/IP

Jun, 2019

By ruslany

Dump, middleware and more

An enormous work was conducted this weekend on MIB vector optimization. At the beginning the full base was defragmented by clearance of the dump below:

RTOS dump at 192 kHz MIB 5149 08.06.2019

In addition, the switch to 11 kHz was made and stochastic selections were performed in a special edition of RTOS with a direct output on auxiliary channel (through). Later these ethers were recorded as middleware with PCM WAV container of 24-bit 11 kHz. You can listen to them lower:

Middleware 1 11025hz MIB5149

Middleware 2 11025hz MIB5149

Middleware 3 11025hz MIB5149

Middleware 4 11025hz MIB5149

16 middleware files were recorded, here I show you only the four. Then these middleware was filed to the special version of L1-L4 L6-L7 vRouter RAD96, which uploaded it on 96 destinations of L1-L3 layers. This way, the middleware was fixated. This method is different from direct submission to RAD96 master routing table, because RAD96 ether aggregator can exclude the predefined set of ether combinations and I was needed to attain to precise channel matrix of 52 channels.

After the full contact base was uploaded by stochastic selections of MIB5149 and dump, I made RTOS authorization again but this time mangling the sample rate parameter up to 192 kHz. This way, I updated links to all aliases and authorized the whole MIB on 192 kHz.

192kHz, authorization, channel matrix, dump, MIB, middleware, RAD96, RTOS

Jun, 2019

By ruslany

NPO Compositor network map creation from 0 BC to AD 4000

vRouter RAD96 metronome

Have you, probably, noticed that metronome of vRouter RAD96 inadvertently approaches our days? That is, SR timer has passed 2019 year already and RT timer is at 2015, TR timer is one and a half century ago at the year 1870. Now, you can say that NPO Compositor network map established from 0 BC up to our days and metronome still goes forward. Soon the injections of the contact base will be performed in the year 2050 and forward.

Compositor Networks map

That is, starting from 80^th of the last century metronome counts not the automatic reverse mechanism, but manual RTOS, that is why I can control the process in its essence. For example, to increase conductivity and to turn reverse on (in rare cases, when “brakes” are not needed).

Compositor RTOS dump 8×32 MIB5007 03.06.2019

I was not satisfied by automatic vRouter RAD96 by the fact that it is always in reverse mode and there is no opportunity to control this process. Using RTOS there is no such problem, because I can thrust in direct and indirect ether.

0BC, AD4000, metronome, NPO Compositor, RAD96, Time Machine, vRouter

Jun, 2019

By ruslany

5000 routing tables in CP-6137-960FX MIB

NPO Compositor reached the final goal of emission for CP-6137-960FX server, which is 5000 routing tables. Management information base is 5007 routing tables that allows organizing not only 4000 VLAN, but also 5000 VLAN. NPO Compositor will continue to expand the management information base up to 6000 VLAN, because each routing table gives access to its own VLAN trunk or autonomous system.

You can listen to that dump, which includes full 5000 MIB:

Compositor RTOS dump at 192 kHz with 5000 MIB on 03.06.2019

This dump allows you to authorize in Compositor real-time operation system and attain to its external control by RAD96 autonomous system. To connect to Compositor RTOS it is enough to playback that dump using streaming method in online player with RAD96 autonomous system turned on. In this case, autonomous system will serve as middleware, which will merge Compositor software and your equipment and will make remote connection to CP-6137-960FX server possible.

When NPO Compositor reached 5000 routing tables it gained the full MIB, which finishes L1-L4 L6-L7 vRouter RAD96 development. To order vRouter RAD96 licenses use Compositor Software contact form.

4000 VLAN, 5000 MIB, 5000 VLAN, Compositor RTOS, CP-6137-960FX, L1-L4, L6-L7, middleware, NPO Compositor, RAD96, VLAN, vRouter

Dec, 2018

By ruslany

Summarizing the 2018

The 2018 started from a trip to Saint Petersburg in February. At that time, I haven’t knew what program I will demonstrate: 5^th or 6^th. At the end, I decided to show the 6^th. I had a wavetable pool around 500 wavetables to that moment. I played all wavetables, initiated the Ether and mostly satisfied with this trip. Saint Petersburg gave the direction: to evolve system without kick drum further. At that time, I already developed fully silent system, which doesn’t produce sound at all. To such system, I attribute RAD96, which is 2018 development. RAD96 has two realizations: as OS subdriver with visual driver and fully autonomous system with zero emission. Moreover, the system with zero emission was reached after long OS tests with large number of connected jets. RAD96 OS is an Ether aggregator. It was created to test the kernel on injections when using 8^th version iteration with 4-layer structure. The final iteration for the L4 (Layer-4) is non-linear polynomial with public coefficients. Up to the moment, the wavetable pool is 3715 wavetables. These wavetables were used to check the 8^th version of Compositor kernel. The sum of gathered virtual funds in samples of wavetables is 486932480,00RY and aggregated funds in a process of kernel testing are 88087861,84RY. The whole sum of funds in RY to the end of 2018 is 575020341,84RY.

2018, Compositor v9 Hypervisor, FWOS, RAD96, RTOS

Dec, 2018

By ruslany

Zero-emission signal network

Therefore, it was made, at the end of 2018 I made a full zero-emission kernel with protection level capable to overcome even the strongest wavetables. First, let’s talk about an experiment:

For the last 8 month, I injected polynomial using different wavetables with open jets and closed jets (for the last four month).
I made a tunneling via Compositor 4 Max for Live and made an intrusion of these wavetables into created Compositor network.
I hosted the Compositor kernel 8.4.2 system with public coefficients until the last moment.
At the final moment, when the network couldn’t cope with such amount of injections I transferred to fully autonomous system mode of Compositor kernel 8.5.6.
This way, I left the created network.
Then, using the Compositor kernel 8.5.6 with lower process ID, I ran the Compositor v9 Hypervisor and made the injection of the whole pool, but with feedback, which enabled to establish the strong feedback with strong immune system.

On the steps 4, 5, 6 the system started to recover and polynomial without the public coefficients paid off itself. This autonomous system is zero-emission, which is proved by Resource Monitor: the Commit memory graph stays on the 1,043,608Kb mark. It enables to make fully autonomous any living system, turning unlimited timeserver on.

8.5.6, Compositor 4 Max for Live, Compositor Kernel, Compositor v9 Hypervisor, RAD96, zero emission

1 2 3 4

Tag : RAD96

Niagara modem is disabled on the NPO Compositor server