LK3.5-NOWY SOFT - KOLEJNE WERSJE

[agrest]

Cześć. Wydaje mi się, że poprawnie wprowadziłem adres, jednak otrzymuję komunikat o błędzie. Szczegóły w załączniku

[wilkxt]

Cześć. Wydaje mi się, że poprawnie wprowadziłem adres, jednak otrzymuję komunikat o błędzie. Szczegóły w załączniku

problemem jest ! przed serwer_sms , czy on ma tam być?

[agrest]

Tak ma być. W przeglądarce działa.

[wilkxt]

Tak ma być. W przeglądarce działa.

Znak ! jest zabroniony w url LK, byc może podmienimy go na inny ale narazie nie mozna go użyć bo jest wykorzystywany do zamiany % na !

[agrest]

Ok - dzięki za info

[radunre]

Hi Tomek,

I have a problem with a LK3.6, FW1.19. The AM2320 is not working all the time.
If it is down, I press "I2C sensor detection", it works for 12-16 hours and goes down.
The problem is that it never re-connect by itself, I always have to press the button.

What can I do in this matter ?

We'll check it

Hi Tomek,
Any updated regarding "I2C sensor detection" ? Firmware 1.21 is doing the same.

Another strange thing I noticed:
- In the Scheduler, if I set Event1 to change on time base, it will not react, even if already within the time frame. It will only change during the next time frame.
Example:
Current time is 10.00 AM
I set Event1 to be "1", starting at 9.00 AM and "0" at 12.00 AM, daily.
It will not be "1" only the next day.

[wilkxt]

About AM2320, we didn't make any change in softv1.21
But, how is the cable length up to am2320?

Another strange thing I noticed:
- In the Scheduler, if I set Event1 to change on time base, it will not react, even if already within the time frame. It will only change during the next time frame.
Example:
Current time is 10.00 AM
I set Event1 to be "1", starting at 9.00 AM and "0" at 12.00 AM, daily.
It will not be "1" only the next day.

Yes, because the scheduler sets events/outs when passing through the set time. If you would set Event1 before 9:00 AM, it would be set to 1 after 9:00 AM

[wilkxt]

About AM2320, we didn't make any change in softv1.21
But, how is the cable length up to am2320?

Another strange thing I noticed:
- In the Scheduler, if I set Event1 to change on time base, it will not react, even if already within the time frame. It will only change during the next time frame.
Example:
Current time is 10.00 AM
I set Event1 to be "1", starting at 9.00 AM and "0" at 12.00 AM, daily.
It will not be "1" only the next day.

Yes, because the scheduler sets events/outs when passing through the set time. If you would set Event1 before 9:00 AM, it would be set to 1 after 9:00 AM

  lk3_7_firmware_1_21b.zip (Rozmiar: 444.45 KB / Pobrań: 255)
Załaczam testowy soft z zmniejszoną prędkościa odczytu I2C dla czujników AM2320, BME280 i SPS30, Prośba o przetestowanie przez tych co mają problemy z tymi czujnikami zwłaszcza przy dłuższych kablach.

[radunre]

The AM2320 cable length is about 5 meters. It should not have a problem.
Thank you for the "beta" firmware, I'll test it next Monday, at the office.

Regarding the events, I think that the scheduler should set the EVENT variable as soon as reaches or already passed the set time. 
It is rather unusual to wait many hours just to check the right function of a scheduled set of events.

Also, thank you for the thermostat idea. It perfectly fits my needs.

Keep up the great work !

Radu

[radunre]

Hi Tomek,

I tried the 1.21b firmware.
The AM2320 is working for a random period of time. Sometimes 2 hours, sometimes 15 minutes.
It does not reconnect automatically.

For connection I'm using a 6 wire shielded alarm cable. Shall I try to connect the shield to ground ? At this moment, there is no shield connection.

Thank you for your support.

Radu