Terminal remembers Sensor's Data Count as per ID?
- dl7uae
-
Autor
- Visitor
-
- Dank erhalten: 0
Terminal remembers Sensor's Data Count as per ID? wurde erstellt von dl7uae
Posted 13 März 2013 14:19 #1
Hi JETI!
Still no response from you on my Expander issue..
Another oddness:
It seems that a terminal (Profibox, transmitter) remembers the number of data items a sensor (ID) transmits. Independant of a "profile" which can be deleted! In it's EEPROM? (Even full poweroff (switch) or an update (procedure) does not help.)
So my problem is as follows:
Users of my sensor (JLog2) can configure which data items in which compilation they want to have. Three of the possible four configs send 15 items, the 4th only 9. The 4th ("config 3") compiles all 9 items into only two EX messages. This is to overcome the "Expander problem" in co-existence with other sensors as described in my other post here.
Now.., my device definitely does not send EX text messages 10..15 (display name) as well as not the corresponding binary messages 10..15 in "config 3".
Only.., the terminal, Profibox and the DC-16 as well, shows up with 15 items although only 9 in the downstream. If you select one of the 10..15 then no data appears behind them of course.
These "zombie displays" 10..15 definitely come from the last config which sent in fact 15 items. Depending on which compilation (config) was in use before the 9-item config 3, the naming of those zombies appears in the terminal.
I had that problem from the beginning on, at time I started to implement the EX extension. The only thing that helped was to change my sensor ID. Now no chance to do this because the user configures the number of items. I only could use a 2nd different sensor ID in case config 3 is selected.
So, what's going on, why/where remembers the terminal the relation sensor ID / item count?
Thanks in advance, Tom
Still no response from you on my Expander issue..
Another oddness:
It seems that a terminal (Profibox, transmitter) remembers the number of data items a sensor (ID) transmits. Independant of a "profile" which can be deleted! In it's EEPROM? (Even full poweroff (switch) or an update (procedure) does not help.)
So my problem is as follows:
Users of my sensor (JLog2) can configure which data items in which compilation they want to have. Three of the possible four configs send 15 items, the 4th only 9. The 4th ("config 3") compiles all 9 items into only two EX messages. This is to overcome the "Expander problem" in co-existence with other sensors as described in my other post here.
Now.., my device definitely does not send EX text messages 10..15 (display name) as well as not the corresponding binary messages 10..15 in "config 3".
Only.., the terminal, Profibox and the DC-16 as well, shows up with 15 items although only 9 in the downstream. If you select one of the 10..15 then no data appears behind them of course.
These "zombie displays" 10..15 definitely come from the last config which sent in fact 15 items. Depending on which compilation (config) was in use before the 9-item config 3, the naming of those zombies appears in the terminal.
I had that problem from the beginning on, at time I started to implement the EX extension. The only thing that helped was to change my sensor ID. Now no chance to do this because the user configures the number of items. I only could use a 2nd different sensor ID in case config 3 is selected.
So, what's going on, why/where remembers the terminal the relation sensor ID / item count?
Thanks in advance, Tom
Last Edit:13 März 2013 14:24
von dl7uae
Letzte Änderung: 13 März 2013 14:24 von dl7uae.
Bitte Anmelden oder Registrieren um der Konversation beizutreten.
- PW
-
Offline
- Moderator
-
- Beiträge: 9742
- Dank erhalten: 3832
Hallo Tom,
is I know you are the man responsible person for programming the SM (Stefan Merz) products
; this is a private forum and this forum is not responsible for answers from Jeti for your company problem !
I suggest:
SM (Stefan Merz) or you as programmer for SM should go in direct mail contakt to Jeti/Cz to solve your SM (Jlog) problems.
Please be so kind

Regards
PW
is I know you are the man responsible person for programming the SM (Stefan Merz) products


I suggest:
SM (Stefan Merz) or you as programmer for SM should go in direct mail contakt to Jeti/Cz to solve your SM (Jlog) problems.
Please be so kind


Regards
PW
Rechtsbeistand u.a. bei "Modellflugproblemen"etc. : Rechtsanwälte Wessels & Partner, Tel.: 02362/27065
PW Modellbautechnik ( Jeti Kombiangebote, Beratung/Einstellservice etc.)
PW Modellbautechnik ( Jeti Kombiangebote, Beratung/Einstellservice etc.)
von PW
Bitte Anmelden oder Registrieren um der Konversation beizutreten.
Ladezeit der Seite: 0.986 Sekunden