The calculation task does not work when both inputs change at the same time and the output of such input is used for further calculation, this is because the Calculation function, as explained in the manual, and confirmed by the trace log, runs a calculation immediately when one of the parameters in the polynom changes. 

Effectively, because in practice the two variables of the polynom do not effectively get updated at the same time, there are a few seconds of difference, probably because bOS serialises tasks rather than parallelise them, then this yields to errors. In summary do not use the calculation task is the variables change at the same time because you will get wrong calculation. This is an interesting bug.....

Example, a water line running a main pipe split in two branches, you do not need three water counters, but just two to know the water consumption of the two branches and the total.

Total water counter A

Partial water counter B

Partial water counter C, the result of subtracting A-B

what bOS incorrectly does

KNX water counter A

KNX water counter B

Calculation task C, which is the result of A-B

When water is used in one of the branches, let's say branch B, then two counters get updated, counter A and counter B, because the counter update do not happen at the same time, but serialised as done by bOS then the sequence is as followed

a) Counter A updated

b) Counter C calculated because one of the variables in polynom changes

c) Counter B updated

d) Counter C calculated again because one of the variables in polynom changes

Because C has changed twice, then if you use the ouput of the calculation as input to a CounterLog, then you will get disastrous results in your Counterlog, the counter log will take the incorrect value calculated in step b as an input, hence contaminating the counterlog. 

Because there is no documentation of this, it has taken a significant amount of time to find the root cause that was driving my CounterLog to go nuts, it is just bad this situation happens and it is not documented anywhere. I assume not many integrator are using calculation tasks because to me this is very basic

Hi,

When using a CounterLog tasks, the input value used to populate its values only trigger the function to update the TotalValue() value, he remaining values (e.g. Average, Last 24 hours, Daily) are only updated every hour on or about on the hour.

The above possess a significant bug that needs to be fixed, otherwise those using any of those values updated only on the hour or immediately after receive incorrect calculations. This is because bOS calculates those remaining values after the o'clock, hence allocating such value to the next day hence creating and giving significant incorrect information, if this is not a bug then you should forbid using those values in calculations as the result will always be wrong

bOS version 4.7, the below screenshot shows this perfectly, the three graphs use the same calculation against the value. I thought I was doing somethign incorrect, to the point I had to create specific test cases to find out what the hell was going on, effectively proving somethign is wrong in bOS

Graph1 uses 3 variables (one always 0) in the polynom, using TotalValue(), which is updated on the spot by bOS

Graph2 uses 3 variables (one always 0) in the polynom, using TodayCount(), which is NOT updated on the spot by bOS, but on the hour, after the o'clock

Graph3 uses 2 variables in the polynom, using TotalValue(), using TotalValue(), which is updated on the spot by bOS

The results can be easily seen below, at 20:00 the counter shows the correct usage of 1 L of water between 20:00 and 20:59, two graphs are correct, the third one is wrong because the TodayCount calculation happens after 20:59:59 hence pushing the 1L usage of water to the 21:00 to 21:59 block. weird ehh?  The worst part comes at midnight, because at that point the TodayCount does the best weird calculation, the whole day calculation moves to the next day, hence creating an artificial and incorrect 24 L use on the following day, completely wrong way of calculating the values.  The 24L was the actual waster of water in the previous day, but because the function does the calculation past midnight then we get a terrible wrong result, showing that actually past midnight there had been a waste of 25 L of water.

Hi.

Dear,

I try many times but the 1 byte DPT 20.102 HVAC mode is not imported. 

The datapoint is visible and correctely identified in the first step, but in the final step the DPT not present

In finaly the value is not imported to the bOS.

Good afternoon.

We have two doubts regarding the graphic part of bOS, being:

1. Is there a possibility to change the granularity (spacing - interval) of the X axis [hours]?

2. When we execute the Export of the data inside the Configurator, we have the information: Data | Hour | Value; but when we export to the Client, using the button with the Excel symbol, is the data "strange"?

The problem is with the export to Excel button

Please, can someone help us?

Thanks!

Marco Fernandes

STRUXI

Hey,

Is it possible to remove it? Because some of our building managers dont understand it and im tired of explaining that to them every month. 

As an example: when bOS sends out meter values it adds a decimal point if the value is over 1000. to 1,000. Correct decimal point is actually dot . now they want me to change it so the actual decimal point i (,) and remove the 1000 separator. 

Haven't found a option for this.

Regards

Hey,

I'm trying to make a program that monitors 330+ modbus statuses for alarms. If any of those registers are true it should change the common alarm status. If i add just one register it works well.

But i don't know how to monitor them all with one program, it seems like it works with the last register only if i add them all in.

I also tried to make it just with IF commands and last one was else. But had same problem that it wouldn't recognize the middle statuses. Also tried to make two separate program one that turns the status off and one that turns it on, and i think they cancel themself out. 

So how would you monitor so many registers?

Regards

Hello everyone,

Is it just me, or does inserting objects in scenes can become a nightmare???

When creating a scene on bOS, and inserting objects on the configurator, it gets slower depending on how many objects you insert.

E.g.:

If you create a scene with just a couple of objects that's ok. But if you try to add like 20, 40 objects, the more you insert, the more the software freezes and you need to wait several seconds before adding a new object.

Right now I have a scene with 26 objects. If I add a new one, it lets me choose the object, the software freezes, and it took at least 16s until I was able to click the Add button again...

This happens to me all the time, when creating long scenes. The more objects you insert, the slower in gets.

Heeeeeeeelp! I'm almost cutting my wrists...

Hey,

I had a small problem with modbus connection that seemed to be all fine(Was connected and no errors in debug), but actually it didn't update values, but i had the error handling setting set to hide. 

Now here's my question if it's set to hide and there is some error does it drop the connection? Or will it still reconnect after the error just doesn't log the error?

I was looking at the diagnostics/debug and it didn't show me any timeouts but it looked like it only was asking 1 register for updates. after i disabled it and re-enabled it started to talk to me again(Started to poll/update all the registers). So right now i left the error handling to reconnect.(Only reason i left it in hide mode was so i could test registers that didn't respond for some reason, now i just turned off cyclical read on them) Modbus connection was "offline" for 2 days.

Also it would be awesome if we could disable/enable modbus driver from the visualization too,  I haven't found a way to do it. We can see the status of the driver that's it.

Regards,

Jürgen

Hello, I have all my KNX devices at home connected via BOS to Alexa - about 70 devices. All worked well, until suddenly Alexa stopped responding to all devices. i.e. - When I ask Alexa to 'turn on' a device, it says that the device is not responding - this is the same situation with all my KNX devices. To clarify, BOS works well from the app and also Alexa works well with other devices not connected via BOS. Any idea?