How can we remove these dips?

[pacificblue03]

Hello All,

Today i switched from a VUE to a PRO 2 and so to a new console, while it was connecting it read nothing for maybe 10 mins, and my chart shows the below.

Am i able to manually remove the anomaly? what file do i need to edit? I tried to edit the dayfile for the current day but the chart still shows it.
This is in the interface website.

Image:

[freddie]

Use the log editors. Found under the interface menu "Data logs". Sounds like you should select the "monthly logs" option. Not much call for manual editing of log files these days.

[HansR]

I don't think you can remove it from the Recent database and that you have to sit out until it disappears. Editing the logfile won't redo the charts.
Setting up spike handling will help in future I guess although I am not sure because this looks like a fall to zero as if the sensor itself got in error.

I am not sure how CMX handles null values but I assume the logfile will contain a null value in case of sensor error. Those errors can be skipped or have a drawn line.

But all depends on the version of CMX - which are you using?

[freddie]

I think if you stop MX and remove the recent db file, it will get recreated on startup.

[HansR]

I think if you stop MX and remove the recent db file, it will get recreated on startup.

true

[pacificblue03]

But all depends on the version of CMX - which are you using?

Hello, i am using
Cumulus MX - Version 4.3.3 | Build - 4070

[pacificblue03]

I think if you stop MX and remove the recent db file, it will get recreated on startup.

true

I do apologize, where is the .db file / what is it called

[HansR]

the file is data/cumulusmx.db

[pacificblue03]

It did not fix, so i just waited a new day.. all good.

[HansR]

It did not fix, so i just waited a new day.. all good.

Ah... when deleting the db you need to edit the error out of the logfile otherwise it picks up the wrong value again.
But anyway if you are happy, we are happy. Some problems solve themselves by waiting