Components

note

This page has been automatically translated and has not been reviewed in detail yet. Therefore, the translation might not be completely accurate.

Components are the atoms of the NeuroomNet system.

NeuroomNet has numerous interfaces. If “something” is connected via one of these interfaces, be it dedicated hardware, software or another endpoint, then we call it a “component”. There is probably no really universal name that summarizes everything, which is why we decided to use the term “component”.

Why is this important or why do I need to know this as a system installer?

Components are the basis of our billing system. If you don't have many components, you only need a few licenses. We offer licenses in packages. Therefore, you don't need to know the exact number of components in advance, but a rough idea will help you decide which package you need. Of course, the packages can be expanded at any time.

Here are some examples to clarify:

A video projector is a component:

Module setup: projector component example

A projector that is connected to the system via a network is a component from the system's perspective.

It doesn’t matter which protocol is used for communication, be it a “universal” protocol like PJLink or a proprietary protocol.

A socket can be a component:

Module setup: component example socket

This depends on whether you want to address this socket separately. If we assume KNX as the interface, then the electrician would also have to have assigned an address for each socket. However, if there is only one KNX address to switch all sockets (of a room, on a floor) together, then all of these sockets are just one component in NeuroomNet.

A PC is a component:

Module Setup: Component Example PC

The NeuroomNet PC client (software tool) is installed on the PC.

From then on, the PC is a component. The system can then turn off the PC, turn it on, reboot or simply detect whether the PC is running. The NeuroomNet PC client is operating system independent and can integrate Windows, Linux and Apple PC systems.

A software on the PC is a component:

Module Setup: Component Example Software

A POI software, a digital signage software or a game is a component. To do this, the software only needs to use the NeuroomNet API. Any third-party software can communicate with NeuroomNet via the API, or NeuroomNet can simply determine that the software is still running.

DMX light can be many components:

Module setup: DMX light component example

DMX 'runs' in NeuroomNet via ArtNet. Here, too, you can in principle create a component for a single DMX channel. However, a moving head spotlight with 8 DMX channels can also be a component if you want to control this spotlight separately. If you want to control a battery, say ten of these spotlights together, you can create a component that includes 80 DMX channels. In the end, several DMX universes can also be combined into one component, for example for a long LED strip.

The smallest unit in NeuroomNet is always a component.

Component providers and component types

The type of component, the provider, is determined by the interface protocol, e.g. KNX, TCP/IP, PJLink, DMX, SNMP etc .

In addition, a component can also have a Component type to better specify the component. Let's take the example from above again, the KNX component. Basically NeuroomNet only knows the protocol (KNX) and the address. Now, as an administrator, I can assign the component type, either the socket in question, or light, or a heating actuator, or, or.

The same applies to most types of components (providers). An SNMP component can be of the type printer, network switch, etc. and a DMX component can be of the type moving head spotlight or fog machine, etc. The component types can be freely defined.

You don't have to assign a component type, but it gives you the option, for example, to switch lights and sockets separately, to filter them better, etc.

Module Setup: Illustration of component providers versus component types

Components have properties:

The properties name and type are common to all of them. The name can be freely assigned and the provider results from the protocol. In the case of the socket, the provider would be e.g. E.g. KNX. A type can optionally be assigned. Components may have additional properties that depend on the component type, e.g. IP address, bit width, etc.

Components have actions:

Depending on the component provider, different actions are available. In the case of the socket, this is usually just switching on and off. In the case of the video projector, these are a few more such as switching on, switching off, shutter-on, shutter-off, input HDMI1 etc.