EX protocol data type "4 char String"
- Sepp62
- Offline Autor
- Elite Mitglied
- Beiträge: 294
- Dank erhalten: 154
I am currently implementing a Jeti telemetry sensor for a turbine ECU.
The ECU gives me status messages concerning the turbine Status:
Run
Stop
Start
Cool
Err
etc.
I would like to have data type which enables the sensor to display a short text in the telemetry display.
From the 16 available data types, there are 4 reserved values for 38 bit values (int38_t). A 38 bit value would be sufficient to display 4 characters ( 4 x 8 bit = 32 bits).
I know I can do this with text display (Jeti box) but showing the Jeti Box in the telemetry display is not very convenient.
(I also know, that this is not a "mainstream requirement")
Best regards
Bernd
The ECU gives me status messages concerning the turbine Status:
Run
Stop
Start
Cool
Err
etc.
I would like to have data type which enables the sensor to display a short text in the telemetry display.
From the 16 available data types, there are 4 reserved values for 38 bit values (int38_t). A 38 bit value would be sufficient to display 4 characters ( 4 x 8 bit = 32 bits).
I know I can do this with text display (Jeti box) but showing the Jeti Box in the telemetry display is not very convenient.
(I also know, that this is not a "mainstream requirement")
Best regards
Bernd
Last Edit:22 Nov. 2015 23:40
von Sepp62
Letzte Änderung: 22 Nov. 2015 23:40 von Sepp62.
Bitte Anmelden oder Registrieren um der Konversation beizutreten.
- Henning
- Offline
- Elite Mitglied
- Beiträge: 316
- Dank erhalten: 144
Hello Bernd,
up to now there is no "ASCII" data type in the EX Sensor protocol.
Of course you could misuse the "unit" data field of the sensor channel to display up to 4 chars (DS / DC-16) or 3 chars (JB Profi), but the problem with this workaround is the update frequency of this data type on the Jetibox side... It seems that this data field is only read once when the sensor is recognized ("learned in"), or at least it is updated with a very low frequency. Too bad - unusable for your purpose... Test setup with a sensor / data field named "Turbine: Status" see attached JPG.
I also had the same problem with a KTW controller project (which is a Jeti MUV sensor in parallel), at the end I just used the numeric 6-bit data type to send the KTW status there.
=> Jeti developers:
If you read this, please think about a "dedicated ASCII" Duplex EX data type with at least 8 chars, e.g. formatted like the sensor name / unit field which is already in use. This would make all kinds of status info much easier. Thanks!
up to now there is no "ASCII" data type in the EX Sensor protocol.
Of course you could misuse the "unit" data field of the sensor channel to display up to 4 chars (DS / DC-16) or 3 chars (JB Profi), but the problem with this workaround is the update frequency of this data type on the Jetibox side... It seems that this data field is only read once when the sensor is recognized ("learned in"), or at least it is updated with a very low frequency. Too bad - unusable for your purpose... Test setup with a sensor / data field named "Turbine: Status" see attached JPG.
I also had the same problem with a KTW controller project (which is a Jeti MUV sensor in parallel), at the end I just used the numeric 6-bit data type to send the KTW status there.
=> Jeti developers:
If you read this, please think about a "dedicated ASCII" Duplex EX data type with at least 8 chars, e.g. formatted like the sensor name / unit field which is already in use. This would make all kinds of status info much easier. Thanks!
von Henning
Bitte Anmelden oder Registrieren um der Konversation beizutreten.
- Sepp62
- Offline Autor
- Elite Mitglied
- Beiträge: 294
- Dank erhalten: 154
Hi Henning,
thanks for your detailed answer.
So I have to deal with the clumsy jeti box display.
Best regards
Bernd
thanks for your detailed answer.
So I have to deal with the clumsy jeti box display.
Best regards
Bernd
von Sepp62
Bitte Anmelden oder Registrieren um der Konversation beizutreten.
Ladezeit der Seite: 1.062 Sekunden