**Allgemeine Aktionen:**

Unknown macro: floating-toc

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

Please look here

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:

java -jar jBEAM.jar -help

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

Please look here.

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

At the moment, the following file importers are available:

Importer | File Extensions | Filewatcher Support | Channel Mapping Support | Comment |
---|---|---|---|---|

ASAM-MDF | mdf, mf3, mf4, dat | x | x | |

ASCII | txt, asc, csv, ... | x | x | |

ASCII-Matrix | matrix | |||

ATF (ASAM-ODS) | atf, atfx, xml | x | x | |

Basytec | ParadoxJDBC library needed | |||

BEAM | bsn, bsd, bsm, bvm, bxm, bsr, bvr, bxr, bsu | x | x | |

CAN-files | asc, blf, dbc | |||

Dasylab | ddf | |||

dBase v3-v5 | dbf | |||

DCM | dcm | |||

Dewesoft | d7d, d7x, dxd | x | x | |

Diadem | dat, tdm, tdms | x | x | |

EDAS | edt | |||

FAI-IGC | igc | |||

Famos | fam, dat, raw | x | ||

Gantner Universal-Bin-File | dat | x | ||

Garmin | crs, hst, tcx | |||

Gidas | asc, _asc, dat, tb | x | x | |

Google-KML | knl | |||

GPS-Exchange-Format | gpx | |||

HBM Catman | bin | |||

HBM MGCplus-Harddisk-Files | mea | |||

HBM Perception | pnrf | |||

Hioki HiCORDER | mem | |||

iFILE (AVL) | AVL iFile-files | |||

ISO 13499 (MME) | mme | MME<=1.6 | ||

Labview | lvm | |||

LMS | tdf | |||

LS-Dyna | dat | |||

Madymo | frc, lac, lvl, rds, rlg | |||

Matlab | mat | |||

Microsoft Excel | xlx, xlsx, xlsm | x | x | |

NetCDF | cdf, nc, he5, nc2 | x | ||

Nicolet | wft | |||

PAtools | erg, org, atf_fu, mva | x | x | |

Porsche PD5 | x | |||

PTV (Partical Trace Velocity) | ptv | |||

Q-DAS | dfq, dfd | x | ||

Racelogic Vbox | vbo | |||

Somat | sie, sit | |||

RPCIII (MTS) | rpc, drv | |||

Teac GX-1 | hdr | |||

Tecplot | dat, plt | |||

Uniplot | nc2 | |||

Universal FileFormat | uff58, unv | |||

Yokogawa | hdr, wdf | WDF with additional Yokogawa license | ||

Zebris FDM | ||||

Zwick | erg |

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

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

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.