1

New Fields for Sensors / Parentheses and Decimal Places

(edited by Fernando Brochetto 30/10/2019 16:14:23)

Topic: New Fields for Sensors / Parentheses and Decimal Places

Hello,
I would like to suggest to include these two new fields inside the sensors because the clients are always asking me the purpose/meaning of the numbers/content inside the parentheses in the values of the sensors, but this is some technical details that they doesn't need to know most of times.

1) Adding the possibility of remove decimal places or select how much you need;
2) Enable/disable the information of which is appearing inside the parentheses in the value of the sensor.

Thank you!

Fernando Brochetto
Technical Support, Rastreasul

fernando@rastreasul.com.br
2

New Fields for Sensors / Parentheses and Decimal Places

Re: New Fields for Sensors / Parentheses and Decimal Places

Hello Fernando,
I want to notice, that all suggested settings concern unit, so this setting will do the same for all users: your clients, technical specialists and top user. So, if you hide smth then no one will see it.

1) Adding the possibility of remove decimal places or select how much you need;

Do you have any case from practice when such a setting is required? Or this is just for clients' comfort as this is a common view for them?

2) Enable/disable the information of which is appearing inside the parentheses in the value of the sensor.

Did you use option "Visible" in the sensor table? I think that this option would be a proper solution to the situation you describe.

Tatsiana Kots
Ex-Business Analyst, Gurtam
3

New Fields for Sensors / Parentheses and Decimal Places

Re: New Fields for Sensors / Parentheses and Decimal Places

Hello tata,
1) Both suggestions I've sent are more for the design of the platform for the client. Unitl now two decimal places has always been enough, however sometimes it kind of disturbed like the sensor of oil pressure (kPa), for example.

2) In some cases I'm using, but for example the sensor of the mixer:
It's a sensor composed by two inputs (1 - 2) and the client need to constantly monitor, but it is always appearing the values 0, 1000 or 2000 in the parentheses that he is not going to use.

Fernando Brochetto
Technical Support, Rastreasul

fernando@rastreasul.com.br
4

New Fields for Sensors / Parentheses and Decimal Places

Re: New Fields for Sensors / Parentheses and Decimal Places

1. I'll note it. As this is "a cosmetic feature," then we won't plan it in the nearest future.
2. Do you mean that your clients do not want to see raw sensor value but converted into the text values only? Is it a bulk request from your clients, or just a couple of them don't want to see full sensor values?

Tatsiana Kots
Ex-Business Analyst, Gurtam
5

New Fields for Sensors / Parentheses and Decimal Places

Re: New Fields for Sensors / Parentheses and Decimal Places

Hello tata,
Yes, these requests aren't anything with some high priority.
2) We'll start instaling some equipments into a fleet with mixers and this client asked me if this was possible.
I had another one in other case too, that is using the outputs of the equipments to block/unblock the vehicles and a buzzer too.
So for now it's just a couple.

Thank you!

Fernando Brochetto
Technical Support, Rastreasul

fernando@rastreasul.com.br
6

New Fields for Sensors / Parentheses and Decimal Places

Re: New Fields for Sensors / Parentheses and Decimal Places

Thank you for the explanations! I've noted both proposals. They may be developed together with some other UX improvement for sensors.

Tatsiana Kots
Ex-Business Analyst, Gurtam
7

New Fields for Sensors / Parentheses and Decimal Places

Re: New Fields for Sensors / Parentheses and Decimal Places

Thank you tata! smile

Fernando Brochetto
Technical Support, Rastreasul

fernando@rastreasul.com.br