Continuous build 5ad5a9f

[Terracotta-6]

1. Event 3 was incorrectly triggered.
2. Incorrect event 5 annotation location.
   

[Terracotta-6]

23-11-05_0522.alog.txt

[MAKOMO]

Thanks for your report. It seems that quantifiers got confused here, but we would need your settings to be able to duplicate. fully understand and hopefully fix this one. Could you please export your artisan settings via menu Config >> Save Settings into an artisan-settings.aset file and drag-and-drop it here on a text field on GitHub, renamed to artisan-settings.aset.txt? Thanks!

[MAKOMO]

The mapping from the slider positions back to the extra devices 4 (Slider 01) and 5 (Slider 23) works fine here. The quantification of the extra device 1, channel 1 ("Slider 4 OT1蓝") to the event type 4 ("Slider 4") works fine too.

For the quantification of the extra device 1, channel 2 ("Slider 2 OT2红") I see some confusion. The begin and end are mapped to event type 1 ("Slider 1") and the middle is mapped to event type 3 ("Slider 3"). Most likely you have to event quantifiers defined for event type 1 and event type 3 which both are taking as source the extra device 1, channel 2 ("Slider 2 OT2红"). Sometimes the one quantifier wins, sometimes the other. Note that per sample interval randomly only one active quantifier fires its action.

For now I do not see an issue in the Artisan software here, but a confusion in the configuration. Thus sharing your configuration and maybe giving us an idea what you intend to achieve can help us to clarify this one.

[Terracotta-6]

artisan-settings.txt

[Terracotta-6]

Event 3 was incorrectly triggered Occurs only in this version. he previously released test version is normal.

[MAKOMO]

Sorry, I am still struggling to understand this whole thing. What is triggering "Event 3" (an alarm rule, a quantifier or an event playback or anything else) and which event is "Event 3" (the 3rd event in the event table)?

It seems you are replaying events from a background profile here. Could you please also share that background profile?

[MAKOMO]

Can you please provide me with detailed steps from a Factory Reset to duplicate the issue you are talking about? I am struggling.

[Terracotta-6]

Yes, following your advice, nothing has changed.

[Terracotta-6]

profile background.txt

[Terracotta-6]

No alarm triggering events were used.

[MAKOMO]

I still do not understand your issue. However, I reworked some things. Could you please re-test with the current continuous build?

https://github.com/artisan-roaster-scope/artisan/releases/tag/continuous

Thank you!

[Terracotta-6]

[Terracotta-6]

the 3rd event in the event table Event 3 ,Still being triggered incorrectly.

[Terracotta-6]

This version started having problems.

[Terracotta-6]

Correct test version.

[MAKOMO]

I still understand where the problem is and don't understand what your refer to by "the 3rd event in the event table Event 3". I also do not have an TC4 to test.

I load your settings, your background profile and your foreground profile that you attached here above. This looks like this to me:

I see that you do not have any event quantifier defined and all alarms are turned off. However, you have the background event replay by time turned on.

The events to be replayed by the background profiles event table are the followings with the 3rd event marked (is it this one you are talking about!?):

Some additional "untyped" events are marked as "error" or "correct". Those are of course not replayed as they do not have one of the four event types assigned. Not sure what this means.

No looking at the event table of your foreground profile I see all those events from the background exactly replayed (just that at charge 4 additional events are generated to mark the state at CHARGE). What is wrong here?

00:00 Slider 1 => 5
00:00 Slider 2 => 20
00:00 Slider 3 => 44
00:00 Slider 4 => 23
01:15 Slider 2 => 30
01:25 Slider 4 => 47
02:00 Slider 3 => 55
02:15 Slider 1 => 10
...

I cannot see anything wrong with the event replay.

Also your extra devices 4 and 5 recording "Slider 01" and "Slider 23" movement are spot on with the background profiles event and the replay of the foreground events.

What I see is that the second channel of your first extra device channel named "Slider 2 OT2红", recording the "ArduinoTC4" channel 6 is first following the slider 3 signal and after minute 2:00 slider 1. This is easily explained as your slider 3 sends out an "IO3;{}" command which is just a variant of the "DCFAN;{}" command in the TC4 PID firmware, modifying the same TC4 variable (intended to regulate the fan speed).

In your "Correct test version." screen shot those lines are not drawn at all. Why?

So I still don't see what is wrong in the current version and what is different to previous builds.

What event is exactly triggered wrong?

Maybe you can simplify the example and remove things that do not contribute like all those extra device lines?

Sorry, I really would love to fix what ever the issue is here, but as long as I don't understand the issue nor can replicate it, I will not able to do so.

Thanks for your support!

[Terracotta-6]

This beta version is working fine again! Since you don't have the physical hardware Hardware-In-the-Loop, thank you very much for taking your precious time to answer！

[MAKOMO]

Thank you for testing and this confirmation that the current builds are working for you again. We plan to make a new Artisan release by the end of this month thus we want everything to work at least as good as the previous version (hopefully even a bit better ;) after all the many changes we applied.