c45459f

[Terracotta-6]

[MAKOMO]

Is this with the Windows build? Could you try with the next build again?

[Terracotta-6]

Works fine on 6d745f9. thank you ！

[MAKOMO]

Thanks for reporting. We had to downgrade numpy to 2.x again as pyinstaller (Windows/Linux only) seems to bundle 3.x correctly. We will look into this later and update to 3.x once resolved.

[MAKOMO]

Could you please retry the current build under CI construction. I had to downgrade again also the scipy package which depends on numpy. We have to wait for those package upgrades until the issue on the numpy side is resolved which might take awhile. A pity as it works well on macOS and seems to have some performance advantages. Thanks!

[Terracotta-6]

3c4e2e0 Running well, waiting to upload updates to 15203a5

[Terracotta-6]

Just roasted two boilers of coffee with the 15203a5 version and it's running great!

[MAKOMO]

Excellent! Thanks for testing that quickly. Your tests are very valuable!

[Terracotta-6]

[Terracotta-6]

artisan-settings.aset.txt
Kaleido M1-97_24-07-17_2049.alog.txt

[MAKOMO]

What is exactly wrong here? I see that the two air events are replayed correctly, right? I cannot spot more events to be replayed. Looks all correct to me.

[Terracotta-6]

The start time of the three events cannot be started at 00:00, and can only be started after 00:00

[Terracotta-6]

The event playback of the latest version is changed. The event that starts at 00:00 cannot be played. The event must start at 00:01 to trigger the wheel cast. When the new version is used, some events are detected that are not triggered. To trigger events after 00:00, Alarms or other methods are required

[MAKOMO]

Very good catch! The general rule is that events are only replayed after CHARGE is set.

The condition of event replay around 00:00 has been relaxed in the latest build such that events scheduled for 00:00 in the background are replayed even if time is already passed 00:00. However, they might be replayed a little delayed at 00:01 due to switch of the feature just ON on CHARGE. If autoCHARGE is used, the CHARGE event is set in retrospect even a bit later, thus those event might only be replayed if roastime is 00:02 or 00:03, depending on your sampling rate. There is no good way around this, but better to have those events replayed a little delayed than not at all. THANKS FOR REPORTING!

[Terracotta-6]

After clicking CHARGE, it will not be displayed, but after clicking DROP, it will be displayed again. Can it be displayed during baking?This area is the Show/Hide background curve switch.A bright text display shows the background, and a darker text hides the background.

[MAKOMO]

[Terracotta-6]

Thank you for your answer！

[Terracotta-6]

[Terracotta-6]

Strange finding As long as SV is not equal to the number 180, the other values can be set normally.

[roasterdave]

Duplicate of Issue #1631. Your finding is correct.

[Terracotta-6]

It has been fix , thank you!

[Terracotta-6]

[roasterdave]

Thanks for finding and reporting! Fixed in the latest build.

[Terracotta-6]

It has been fix , thank you!

[Terracotta-6]

The command ON modbus cannot transmit commands，The previous version didn't have this phenomenon, and I can't tell what the problem is. OFF The modbus command is normal.

[MAKOMO]

That PID ON command is operational only after ON. Can you verify this?

This was already like this as early as v2.0 of Artisan (haven't checked older versions). I don't see specific reason for this restriction and thus will relax it for v3.

[Terracotta-6]

My use method is wrong, thank you for your advice.