Frequently Asked Questions

How to operate several Simulyzers parallel in Sensor mode2020-09-28T17:23:19+02:00
Copy to Clipboard
Copy to Clipboard
How to hold several older versions of the Win-GUI app on your PC2020-08-27T11:25:36+02:00

Win-GUI apps of different Simulyzer types may be installed in parallel on your PC.

But you may only have one version of the same type of Win-GUI app as an official installed version on your PC. But before de-installing an older version (in order to install a newer one), you may create a copy of your C:\Program Files (x86)\SesKion GmbH\*Type*-Simulyzer directory and rename it to for example C:\Program Files (x86)\SesKion GmbH\*Type*-Simulyzer_Vx.y . You need Admin rights to do this!

*Type* may be PSI5, SPI, DSI or SENT

After having the copy directory you may de-install the old version and install a newer version.

To use the old version you may create a link on your desktop to C:\Program Files (x86)\SesKion GmbH\*Type*-Simulyzer_Vx.y\*Type*_SimulyzerGUI.exe .

To get rid of such an older version, just delete the C:\Program Files (x86)\SesKion GmbH\*Type*-Simulyzer_Vx.y directory and remove the desktop link.

combining and splitting SesKion license-file features2020-08-24T12:04:19+02:00
Copy to Clipboard

existing license

Copy to Clipboard

and new license

Copy to Clipboard

can be combined into a single file:

Copy to Clipboard

The order of the features is of no relevance.

See also: Where to copy seskionLicense.xml license files on your PC

How to pre-view SesKion Standard Win-GUI app2020-07-28T17:46:48+02:00

Normally the SesKion standard Win-GUI app needs a license to be operaded together with a Simulyzer USB box.

However if the customer does not yet have a Simulyzer USB box, he still may download and install the app and he may have a look-and feel about the GUI app and the API.

Where to copy seskionLicense.xml license files on your PC2020-08-24T11:32:49+02:00

SesKion license files always have a filename of “seskionLicense.xml”. The license file will not be recogized with a different name.

The license file has to be copied to locations on your Windows System-Disks (mostly C:) depending on the type of Simulyzer:

  • PSI5-Simulyzer licenses: copy to C:\ProgramData\SesKion GmbH\PSI5_Simulyzer
  • SPI-Simulyzer licenses: copy to C:\ProgramData\SesKion GmbH\SPI_Simulyzer
  • DSI3-Simulyzer licenses: copy to C:\ProgramData\SesKion GmbH\DSI_Simulyzer
  • SENT-Simulyzer licenses: copy to C:\ProgramData\SesKion GmbH\SENT_Simulyzer
  • Simulyzer-RT licenses: copy to C:\ProgramData\SesKion GmbH\Simulyzer-RT

After starting a licensed application, even with not yet having the license, this app will create the directory location.

If you have a license-file with license “features” for different types of Simulyzers, just copy it to all related deirectory locations. The SesKion app just picks the license “features” out of the license-file and ignores the features belonging to different kind of Simulyzers.

See also: “FAQ How about licensing of Simulyzers”

See also: combining and splitting SesKion license-file features

How to prepare a Break-out ECU2020-07-28T16:42:39+02:00
Signal NamePin Sub-D 25Pin post-connector 26wire in flat-ribbon cable
do not use122323
do not use132525
How large have the file-based ringbuffers to be configured2020-07-17T17:28:47+02:00

To ask a bit more precisely:

How large have the file-based ringbuffers of the PSI5-Simulyzer to be configured to hold the data of a given timespan

1. sensordata

Sensordata contain the acquisition of sent and received PSI5-frames / sync pulses

The formula for calculating the size is:

fileSize = (sizeSyncInfo+sizeRespFrame*numberOfSlots)*numberOfInterfaces*numberOfSynperiodsPerSecond*numberOfSecondsToAcquire;

sizeSyncInfo = 6; // Byte

sizeRespFrame = 12; // Byte

numberOfSlots = 4; // lets asume a worst case of 4 timeslots in P10P-500-4H

numberOfInterfaces= 2; // lets asume a worst case of both interfaces

numberOfSynperiodsPerSecond = 2000; // lets asume a typical case of 500µs Syn-periode

When using the values above, the formula reduces to

fileSize = (6 + 12 * 4) * 2 *2000 * numberOfSecondsToAcquire;

fileSize = 216000 * numberOfSecondsToAcquire;

In this worst case scenario, you need a ringbuffer filesize of 216000 Byte for each second to acquire.

Lets say, you want 10 Minutes to acquire:

fileSize = 216000 * 60 * 10; // gives 129600000 Byte (124 MByte)

The standard WIN-GUI app can handle this and even larger file sizes if

  • The used filesystem supports this file size
  • There is plenty of room on the drive to hold the file
  • The file has to be a local file, not a network file!

2. rawdata

Rawdata contain the acquisition of PSI5 voltage and current curves being sampled with 3MSamples/s. Only one of the two interfaces can be sampled at a given acquisition.

The formula for calculating the size is:

fileSize = 12MB * numberOfSecondsToAcquire;

You need a ringbuffer filesize of 12 MByte for each second to acquire.

Lets say, you want 10 Minutes to acquire:

fileSize = 12MB * 60 * 10; // gives 7200 MByte (7.1 GByte)

The standard WIN-GUI app can handle this and even larger file sizes if

  • The used filesystem supports this file size (NTFS does support even larger files)
  • There is plenty of room on the drive to hold the file
  • The file has to be a local file, not a network file!

3. Conclusion

In the examples above, you would have to set this sizes:

But please consider, despite this storage size will be handled properly, it may not be so easy to find special parts inside this acquisition.

Nor may it be practical to handle a csv export of such large files.

What supply voltages can be used with DIO-1 card2020-07-17T17:31:29+02:00

To be precise: What supply voltages can be used for power supply settings of DIO-1 card

Our first requirement was to be able to generate output voltages on SUPPL_1 .. SUPPL_4 between 1.5V and 5V. This found his way into first version of the technical data-sheet.
But in practice, we found the voltages can be generated with defined accuracy between 0.5V and 6V.
So our automatic test-procedure checks all DIO-1 cards between 0.5V and 6V and would give error if accuracy is out of limits.

You also have to distinguish between

  1. Values that can be reasonable set inside the API (range of DAC): 0V .. 6V
  2. tested and guaranteed voltage range: 0.5V .. 6V
  3. recommended values of SUPPL_4: 0.5V .. 5.5V

The tightened range of SUPPL_4 can be constituted because this SUPPL_4 also serves to supply our 48 DIO Driver chips inside the DIO-1, and these chips are only specified up to 5.5V.
We will correct this in our technical data-sheet.

What physical errors does the PSI5-Simulyzer recognize2020-07-16T14:11:40+02:00
The PSI5-Simulyzer recogizes following errors upon receiving a Manchester Frame:
ErrorError bitMeaning
timeslotError0x01data frame starts before start of timeslot or ends after end of time-slot
startBitError0x02error in requested value ’00b’ of startbits
manchesterError0x04no polarity change in mid of Manchester bit or number of bits different to configured one
parityError0x08error in parity bit or in CRC bits
currentError0x10only detected if ‘CurrentCheckMode’ is enabled; reported if “0”-current is outside 0-upper or 0-lower limit or if “1”-current is outside 1-upper or 1-lower limit
noDataError0x20no data (polarity change) within time-slot
bitTimeError0x40only detected if ‘ExtendedTiming’ is true; the bit-times do not match the default the default tolerance of +5% and -5%
How to configure sensor simulation with PSI5-Simulyzer2020-07-28T17:44:05+02:00
How about licensing of Simulyzer boxes2020-08-24T12:05:13+02:00

All SesKion Simulyzer boxes like

  • PSI5-Simulyzer,
  • DSI3-Simulyzer,
  • SPI-Simulyzer and
  • SENT-Simulyzer
  • PSI5-POD
  • SQUIB-Box
  • Simulyzer-RT

and their software can be licensed in three very different manors.

box stored license-bit

The original kind of licensing (and still the most used one), is by storing license information in the nonvolatile memory of the box. This is normally done in factory at SesKion. It is the case when additional licenses are directly ordered together with the box. Additional licenses can also be ordered later when the box is at customer site. In this case SesKion will send a license key to the customer via e-mail that can easily be programmed to NV memory of the box. This kind of licensing is call “box stored”. If it is a hardware feature, like activation of a second interface, this is the natural kind of licensing. Features, licensed “box stored”, can be used with this box from any PC having installed our WIN-GUI app.

boxSN-bound license-file

If a “boxSN-bound license-file” is used, the license is not in the NV-memory of the box but in a license-file on the PC. The license feature is not bound to this PC but to the SerNo of the box. Features, licensed as “boxSN-bound license-file”, can be used with the box having this SerNo, from any PC having a copy of the license-file.

PC-ID bound license-file

Application as our standard WIN-GUI app can also be licensed “PC-ID bound”. This means, the Simulyzer box does not have the license in its NV memory but the license is in a license-file on the PC. A “PC-ID bound license-file” feature may only be used on this PC The advantage is, it can be usd with any Simulyzer box.

Activation of the license has always to be done by the customer. You have to start one of our WIN apps, no matter if it is still not licensed. Here you have the possibility to send an e-mail to SesKion with your PC’s HostID. Seskion then will create the license, bound to this HostID and send it to the customer where it has to be placed in the file-system of the PC with this HostID.

Overview of licenses:

Feature / Optionavailable as box stored license-bitavailable as boxSN-bound license-fileavailable as PC-ID bound license-fileRemarks
second interface (channel) for Simulyzer boxyesyesyes“PC-ID bound” maybe not very useful
optinal CAN interface (PSI5, SPI)nononohardware option
optinal CAN interface (PSI5-POD)yesyesyes
standard WIN-GUI app (PSI5, DSI3, SPI, SENT, PSI5-POD)yesyesyes
PSI5-Tester appnoyesyes
PSI5 programmernoyesyes
PSI5 EMC-test appnoyesyes
SPI sensor modelnoyesyesbox stored license-bit is planned in future
Simulyzer-RT WIN-GUI app (PSI5)nonoyes
Simulyzer-RT activation of monitor-mode in APInonoyes
Simulyzer-RT endurance appnonoyes
Two approaches to get sensor data inside your app2020-07-16T14:13:57+02:00

This is about getting sensor data while your app is running.
There are two situations when you may want to get the data:

  1. Immediately after starting the data acquisition you want to look at the data while it continuously streams from the box or
  2. after stopping of the data acquisition you may want to look at the data.

In case 1, you have to to hurry to get the data fast enough to keep up with new arriving data. This may be the preferred method if you have a long acquisition time, even with no predefined end.
In case 2, you have all the time you want to get the data. his may be the preferred method if you have a short acquisition time, lets say some seconds. Then you start acquisition, stop it after some seconds and then look at the data.

You will find examples below your installation directory in C:\Program Files (x86)\SesKion GmbH\PSI5-Simulyzer\API\
You also will find a complete Visual-Studio project PSI5-Simulyzer4AnsiC.vcxproj in C:\Program Files (x86)\SesKion GmbH\PSI5-Simulyzer\API\ANSI-C\PSI5_Simulyzer4AnsiC\PSI5_Simulyzer4AnsiC

How to replace a fuse inside Simulyzers2020-07-10T08:48:14+02:00

At this time, this information can be found in a PDF document:

How-to-Replace Fuse

We may also transfer this information directly to this page in the future.

How to permanently store your received sensor data in files2020-07-09T14:34:22+02:00

First of all, the files in the temp-directory are not intended to be processed after terminating the your application. They just are intended as a file-based ring-buffer where received binary data is temporary stored. While you application is still running, there are API calls to get data out of these temporary files (see discussion further down).
If you want your acquired data to be available after terminating the your application, you should call

StoreData(HANDLE hSensor,unsigned char mode,char *rawDataFile, char *sensorDataFile);

if your .ppf project files is named myProject.ppf and is located in /your/Path/to/Config/
you should give following parameters:

StoreData(yourSensorHandle, 3, "/your/Path/to/Config/myProject.rawData", "/your/Path/to/Config/myProject.sensorData");

Of course, you may chose different path, different file-basename and different extension, but doing it this way has the advantage you could use our standard WIN-GUI app to open /your/Path/to/Config/myProject.ppf and the GUI will automatically find and open the myProject.rawData and myProject.sensorData files and also open them for showing them as graphs and tables.

Go to Top