The "floating-toc" macro is not in the list of registered macros. Verify the spelling or contact your administrator.

FAQ about general jBEAM usage

At this section we want to answer some of the mostly asked questions about general jBEAM usage.

What are the jBEAM system requirements?

Please look here

Where do I find a complete overview about the start parameters of jBEAM?

If you wish to get a complete and up-to-date overview about all possible start parameters of jBEAM including some explanation simple start jBEAM using the ”-help” parameter like:

This will print all available parameters to the console including some advice on how to use them.

-> Complete overview about all possible start parameters of jBEAM

How to integrate external libraries into jBEAM start?

Please look here.

jBEAM licensemanager generates an empty "license.request" file on MS Windows

If the "license.request" file is empty, please install the Microsoft Visual C++ Redistributable Package for your OS.

Which types of files can be imported into jBEAM?

At the moment, the following  file importers are available:

FAQ about data acquisition with jBEAM

Which types of devices are supported by jBEAM?

At the moment, the following  measurement modules are available:

• Advantech-ADAM-Moduls
• Beckhoff-SPS (TwinCat)
• Datalogger (ASCII)
• Digitek DT-4000ZC
• Gantner eBloxx/eGate
• GOM (SCPI-Server)
• HBM QuantumX
• HBM MGCplus-Monitor
• Hygrobarograph (W&T)
• HygrologNT (Rotronik)
• Kratzer PAtools
• Mahr Indicator
• Matsushita PLC
• Modbus Systems
• Newport MicroServer
• NI-DAQ
• OPC-DA-Server
• PSI 9116 Preasure scanner
• Schott-Handylab
• Smart Systems MCM
• Vector CAN-Modul

Is it possible to increase the filename with every period during measurement with QuantumX?

Yes, please use for filenames of value files the embedded formula: @PropValue(CurrComponent,"PeriodIndex") + 1@

FAQ about calculations

The result of max(abs(A)) in formula editor for numeric object (line by line)is max (A), not considering the negative part

The formula editor (line by line) calculates the complete formula line by line. There are no intermediate channels available but only individual values for each line. Therefore a max() operation can be done only with a direct input channel as argument (max(A)). Then it takes for each line the maximum of the input channel A. Also it does only know the last used input channel was A but not, that another operation was done in between (as max(abs(A))). Therefore any statistical function (max(), min(), …) is only allowed with an input channel as direct argument. In the past we had no statistical functions in this formula editor. But customers wanted formulas as "A - min(A)“ which works as long as these statistical values have only a direct input channel as argument.

The object formula editor works completely different. Each operation is done completely for the whole input object (channel, matrix, single value) and gets the appropriate resulting object. In your sample with A as a channel the intermediate result of abs(A) is a channel and the following max(abs(A)) is the maximum of the intermediate channel, which is a single value. 

Meanwhile we can say the object formula editor is the favorite one. It is faster has more functions and works better due to its object approach. The formula editor (line by line) should be used only in special circumstances, e.g. with an input channel of a measurement component where the measurement value come into jBEAM value by value, which is line by line.