<![CDATA[Forum tinycontrol - LanKontroler V4]]>

<![CDATA[Forum tinycontrol - LanKontroler V4]]> https://forum.tinycontrol.pl/ Sun, 14 Jun 2026 10:18:09 +0000 MyBB <![CDATA[The Strange Comfort of Returning to Horror Games That Once Terrified Me]]> https://forum.tinycontrol.pl/showthread.php?tid=3188 Sat, 13 Jun 2026 04:44:21 +0000 Carrero436]]> https://forum.tinycontrol.pl/showthread.php?tid=3188 horror games that used to scare me so badly I could only play it in short sessions.
The first time I played it years ago, I remember sitting with headphones on, constantly pausing whenever something unexpected happened. Every dark corner felt threatening. Every strange sound made me tense up.
This time was different.
I knew where most of the scares were. I remembered the layout of several areas. I even knew which moments had frightened me the most during my first playthrough.
Yet something surprising happened.
I still enjoyed being there.
Not because the game was frightening in the same way, but because horror games often become something entirely different once the fear fades.
Fear Is Only Part of the Experience
When people talk about horror games, the conversation usually revolves around being scared.
That makes sense. Fear is the genre's defining feature.
But after replaying several horror titles over the years, I've realized that fear is often just the doorway into a much richer experience.
The first playthrough is about survival.
The second playthrough is about observation.
Without the constant anxiety of not knowing what's around the next corner, I started noticing details I had completely missed before. Environmental storytelling became more visible. Character motivations made more sense. Small clues hidden throughout levels suddenly stood out.
The game hadn't changed.
My relationship with it had.
And that shift turned something terrifying into something strangely comforting.
Familiar Fear Feels Different
There's a unique feeling that comes from revisiting something that once intimidated you.
It's not limited to horror games.
People revisit difficult books, challenging hikes, old exams, and uncomfortable life experiences for similar reasons. Familiarity transforms the experience.
In horror games, that transformation can be fascinating.
I still felt tension while exploring dark environments, but it was softer. Less overwhelming.
The atmosphere remained effective.
The uncertainty was gone.
Instead of wondering whether danger existed, I knew exactly where it was. That knowledge removed panic while preserving mood.
It's similar to rewatching a horror film you loved years ago. The monster reveal isn't shocking anymore, but you begin appreciating the craftsmanship behind it.
The lighting.
The pacing.
The sound design.
The little details that helped create the fear in the first place.
Horror Worlds Often Feel More Real on a Second Playthrough
One thing I've noticed is that many horror games become more immersive once you're no longer focused entirely on survival.
During an initial playthrough, players often rush.
They're trying to escape.
They're looking for resources.
They're searching for safe locations.
They aren't necessarily paying attention to every detail.
When revisiting the same game, the pace changes.
You start examining notes more carefully.
You notice objects placed in specific rooms.
You recognize connections between areas that previously seemed unrelated.
I recently replayed a horror game where an abandoned apartment complex served as a major location. The first time through, I barely noticed the individual rooms because I was too nervous.
The second time, I found myself imagining the lives of the people who once lived there.
The horror became less about monsters and more about absence.
That feeling stayed with me much longer.
You can see similar ideas explored in discussions about [environmental storytelling in games], where locations communicate emotions without relying heavily on dialogue.
The Psychology of Knowing What's Coming
It's easy to assume that horror disappears once surprises are removed.
In reality, fear often evolves.
When you know a scare is approaching, anticipation replaces uncertainty.
Sometimes that anticipation is just as powerful.
I've had moments where I remembered a specific encounter from years earlier and felt nervous long before reaching it.
The encounter itself wasn't frightening anymore.
The memory of being frightened was.
That's an interesting psychological effect. Horror games can leave emotional fingerprints that remain long after the actual experience.
Certain rooms.
Certain sounds.
Certain pieces of music.
They trigger memories of how we felt during our first encounter.
In a strange way, replaying horror games can become an exercise in revisiting previous versions of ourselves.
Nostalgia and Horror Make an Unexpected Combination
Most people associate nostalgia with comforting experiences.
Childhood cartoons.
Favorite movies.
Old multiplayer games.
Horror seems like an unlikely candidate.
Yet horror-game nostalgia is surprisingly common.
Part of it comes from remembering who we played with. Some games remind us of late-night conversations with friends or weekends spent discovering secrets together.
Part of it comes from remembering how intensely we reacted.
As adults, many of us become harder to scare. Experience changes us. We learn genre conventions. We recognize common tricks.
Revisiting a horror game can remind us of a time when everything felt more unpredictable.
There's something oddly satisfying about remembering that version of yourself.
The version who checked every corner twice.
The version who hesitated before opening every door.
The version who genuinely believed disaster was waiting around every corner.
Some Horror Games Age Better Than Others
Not every horror game benefits from replaying.
Games that rely heavily on jump scares often lose much of their impact once surprises are known.
Atmospheric horror tends to hold up better.
The reason is simple.
Atmosphere doesn't depend entirely on shock.
A well-crafted location remains effective even when players know what's coming.
Strong sound design remains effective.
Interesting storytelling remains effective.
A compelling mystery remains effective.
That's why some horror games continue attracting players years after release. Their appeal extends beyond simple scares.
Fear may bring players in initially.
Atmosphere keeps them coming back.
You can see this principle reflected in many conversations about [why psychological horror remains effective], especially compared to more straightforward scare-focused experiences.
Growing Out of Fear Doesn't Mean Losing Appreciation
One thing I've learned from revisiting horror games is that becoming less scared isn't necessarily a loss.
For a long time, I assumed horror games would lose value once they stopped frightening me.
The opposite happened.
As fear diminished, appreciation increased.
I started noticing design choices that previously went unnoticed.
I appreciated pacing more.
I paid closer attention to environmental details.
I became more interested in how developers manipulated tension and expectation.
The experience matured alongside me.
What began as a simple attempt to feel scared evolved into an appreciation for atmosphere, storytelling, and psychology.
Why I Keep Coming Back
There are countless games I enjoy, but few genres pull me back as consistently as horror.
Not because I expect to feel the same fear I felt years ago.
That version of the experience is impossible to recreate.
What keeps drawing me back is the opportunity to see familiar places through different eyes.
A hallway that once felt terrifying now feels nostalgic.
A monster that once caused panic now feels iconic.
A story that was hidden beneath fear becomes easier to understand.
The scares may fade, but the memories rarely do.
And maybe that's one of the most interesting things about horror games. They aren't just records of frightening moments. They're records of who we were when those moments frightened us.
When was the last time you revisited a horror game that used to scare you—and did it feel smaller than you remembered, or somehow even more meaningful?]]> horror games that used to scare me so badly I could only play it in short sessions.
The first time I played it years ago, I remember sitting with headphones on, constantly pausing whenever something unexpected happened. Every dark corner felt threatening. Every strange sound made me tense up.
This time was different.
I knew where most of the scares were. I remembered the layout of several areas. I even knew which moments had frightened me the most during my first playthrough.
Yet something surprising happened.
I still enjoyed being there.
Not because the game was frightening in the same way, but because horror games often become something entirely different once the fear fades.
Fear Is Only Part of the Experience
When people talk about horror games, the conversation usually revolves around being scared.
That makes sense. Fear is the genre's defining feature.
But after replaying several horror titles over the years, I've realized that fear is often just the doorway into a much richer experience.
The first playthrough is about survival.
The second playthrough is about observation.
Without the constant anxiety of not knowing what's around the next corner, I started noticing details I had completely missed before. Environmental storytelling became more visible. Character motivations made more sense. Small clues hidden throughout levels suddenly stood out.
The game hadn't changed.
My relationship with it had.
And that shift turned something terrifying into something strangely comforting.
Familiar Fear Feels Different
There's a unique feeling that comes from revisiting something that once intimidated you.
It's not limited to horror games.
People revisit difficult books, challenging hikes, old exams, and uncomfortable life experiences for similar reasons. Familiarity transforms the experience.
In horror games, that transformation can be fascinating.
I still felt tension while exploring dark environments, but it was softer. Less overwhelming.
The atmosphere remained effective.
The uncertainty was gone.
Instead of wondering whether danger existed, I knew exactly where it was. That knowledge removed panic while preserving mood.
It's similar to rewatching a horror film you loved years ago. The monster reveal isn't shocking anymore, but you begin appreciating the craftsmanship behind it.
The lighting.
The pacing.
The sound design.
The little details that helped create the fear in the first place.
Horror Worlds Often Feel More Real on a Second Playthrough
One thing I've noticed is that many horror games become more immersive once you're no longer focused entirely on survival.
During an initial playthrough, players often rush.
They're trying to escape.
They're looking for resources.
They're searching for safe locations.
They aren't necessarily paying attention to every detail.
When revisiting the same game, the pace changes.
You start examining notes more carefully.
You notice objects placed in specific rooms.
You recognize connections between areas that previously seemed unrelated.
I recently replayed a horror game where an abandoned apartment complex served as a major location. The first time through, I barely noticed the individual rooms because I was too nervous.
The second time, I found myself imagining the lives of the people who once lived there.
The horror became less about monsters and more about absence.
That feeling stayed with me much longer.
You can see similar ideas explored in discussions about [environmental storytelling in games], where locations communicate emotions without relying heavily on dialogue.
The Psychology of Knowing What's Coming
It's easy to assume that horror disappears once surprises are removed.
In reality, fear often evolves.
When you know a scare is approaching, anticipation replaces uncertainty.
Sometimes that anticipation is just as powerful.
I've had moments where I remembered a specific encounter from years earlier and felt nervous long before reaching it.
The encounter itself wasn't frightening anymore.
The memory of being frightened was.
That's an interesting psychological effect. Horror games can leave emotional fingerprints that remain long after the actual experience.
Certain rooms.
Certain sounds.
Certain pieces of music.
They trigger memories of how we felt during our first encounter.
In a strange way, replaying horror games can become an exercise in revisiting previous versions of ourselves.
Nostalgia and Horror Make an Unexpected Combination
Most people associate nostalgia with comforting experiences.
Childhood cartoons.
Favorite movies.
Old multiplayer games.
Horror seems like an unlikely candidate.
Yet horror-game nostalgia is surprisingly common.
Part of it comes from remembering who we played with. Some games remind us of late-night conversations with friends or weekends spent discovering secrets together.
Part of it comes from remembering how intensely we reacted.
As adults, many of us become harder to scare. Experience changes us. We learn genre conventions. We recognize common tricks.
Revisiting a horror game can remind us of a time when everything felt more unpredictable.
There's something oddly satisfying about remembering that version of yourself.
The version who checked every corner twice.
The version who hesitated before opening every door.
The version who genuinely believed disaster was waiting around every corner.
Some Horror Games Age Better Than Others
Not every horror game benefits from replaying.
Games that rely heavily on jump scares often lose much of their impact once surprises are known.
Atmospheric horror tends to hold up better.
The reason is simple.
Atmosphere doesn't depend entirely on shock.
A well-crafted location remains effective even when players know what's coming.
Strong sound design remains effective.
Interesting storytelling remains effective.
A compelling mystery remains effective.
That's why some horror games continue attracting players years after release. Their appeal extends beyond simple scares.
Fear may bring players in initially.
Atmosphere keeps them coming back.
You can see this principle reflected in many conversations about [why psychological horror remains effective], especially compared to more straightforward scare-focused experiences.
Growing Out of Fear Doesn't Mean Losing Appreciation
One thing I've learned from revisiting horror games is that becoming less scared isn't necessarily a loss.
For a long time, I assumed horror games would lose value once they stopped frightening me.
The opposite happened.
As fear diminished, appreciation increased.
I started noticing design choices that previously went unnoticed.
I appreciated pacing more.
I paid closer attention to environmental details.
I became more interested in how developers manipulated tension and expectation.
The experience matured alongside me.
What began as a simple attempt to feel scared evolved into an appreciation for atmosphere, storytelling, and psychology.
Why I Keep Coming Back
There are countless games I enjoy, but few genres pull me back as consistently as horror.
Not because I expect to feel the same fear I felt years ago.
That version of the experience is impossible to recreate.
What keeps drawing me back is the opportunity to see familiar places through different eyes.
A hallway that once felt terrifying now feels nostalgic.
A monster that once caused panic now feels iconic.
A story that was hidden beneath fear becomes easier to understand.
The scares may fade, but the memories rarely do.
And maybe that's one of the most interesting things about horror games. They aren't just records of frightening moments. They're records of who we were when those moments frightened us.
When was the last time you revisited a horror game that used to scare you—and did it feel smaller than you remembered, or somehow even more meaningful?]]> <![CDATA[Aktualizacja do 1.38]]> https://forum.tinycontrol.pl/showthread.php?tid=3161 Fri, 09 Jan 2026 10:59:39 +0000 maly_tomi]]> https://forum.tinycontrol.pl/showthread.php?tid=3161
Zaktualizowałem swojego LK4 z 1.24 do 1.38 i po aktualizacji zamiast panelu wyświetla się informacja "Failed to read existing file".
Twardy reset urządzenia nic nie daje. Czy spotkał się już ktoś z czymś takim? Da się jeszcze uratować tego LK4?]]>
Zaktualizowałem swojego LK4 z 1.24 do 1.38 i po aktualizacji zamiast panelu wyświetla się informacja "Failed to read existing file".
Twardy reset urządzenia nic nie daje. Czy spotkał się już ktoś z czymś takim? Da się jeszcze uratować tego LK4?]]> <![CDATA[Konwersja Modbus TCP na RTU, izolacja RS485, zakres VCC]]> https://forum.tinycontrol.pl/showthread.php?tid=3150 Sat, 15 Nov 2025 17:01:21 +0000 marekm]]> https://forum.tinycontrol.pl/showthread.php?tid=3150
Przy okazji pytania, czy RS485 jest izolowany i do jakiego max napięcia? Oraz czy 58V to absolute max VCC - bo pasowałoby mi zasilać LK4 i jednocześnie mierzyć napięcie z magazynu energii (16S LFP), 16*3,65 = 58,4V to dopuszczalne maksimum, rzadko kiedy tyle będzie i powyżej 58V nie muszę mieć dokładnego pomiaru ale czy tak powiedzmy do 60V przez ograniczony czas wytrzyma i nie uleci "magiczny dym"? Szeregowo o zasilaniem oczywiście będzie bezpiecznik, czy wskazane byłoby dodać szeregowo diodę Zenera by zgubić kilka V (wtedy przydałoby się móc przesunąć pomiar VCC o tyle samo w górę, by poprawnie liczyć moc i energię)?]]>
Przy okazji pytania, czy RS485 jest izolowany i do jakiego max napięcia? Oraz czy 58V to absolute max VCC - bo pasowałoby mi zasilać LK4 i jednocześnie mierzyć napięcie z magazynu energii (16S LFP), 16*3,65 = 58,4V to dopuszczalne maksimum, rzadko kiedy tyle będzie i powyżej 58V nie muszę mieć dokładnego pomiaru ale czy tak powiedzmy do 60V przez ograniczony czas wytrzyma i nie uleci "magiczny dym"? Szeregowo o zasilaniem oczywiście będzie bezpiecznik, czy wskazane byłoby dodać szeregowo diodę Zenera by zgubić kilka V (wtedy przydałoby się móc przesunąć pomiar VCC o tyle samo w górę, by poprawnie liczyć moc i energię)?]]> <![CDATA[mqtt brak banych po aktualizacji 1.24]]> https://forum.tinycontrol.pl/showthread.php?tid=3113 Wed, 11 Jun 2025 07:30:52 +0000 sl500]]> https://forum.tinycontrol.pl/showthread.php?tid=3113
Wróciłem do wersji 1.18a]]>
Wróciłem do wersji 1.18a]]> <![CDATA[LK4 błędy w pomiarze energii]]> https://forum.tinycontrol.pl/showthread.php?tid=3111 Sun, 01 Jun 2025 19:24:01 +0000 lodomir]]> https://forum.tinycontrol.pl/showthread.php?tid=3111 Błąd polega na tym, że urządzenie zwiększa wskazania liczników nieadekwatnie do przypisanych im wyzwalaczy.

Na przykład jeśli P/E1 jest sterowane przez INPD4 (impulsator gazomierza), P/E5 przez INPD1 a P/E6 przez INPD2, to przy kolejnych impulsach na wejściu INPD1 lub INPD2 zwiększają się adekwatnie wartości P/E5 i P/E6, ale również wartość P/E1. Wygląda na to tak, jakby algorytm mylił wyzwalacze.

.png

PEcfg.png (Rozmiar: 55.3 KB / Pobrań: 0) ]]> Błąd polega na tym, że urządzenie zwiększa wskazania liczników nieadekwatnie do przypisanych im wyzwalaczy.

Na przykład jeśli P/E1 jest sterowane przez INPD4 (impulsator gazomierza), P/E5 przez INPD1 a P/E6 przez INPD2, to przy kolejnych impulsach na wejściu INPD1 lub INPD2 zwiększają się adekwatnie wartości P/E5 i P/E6, ale również wartość P/E1. Wygląda na to tak, jakby algorytm mylił wyzwalacze.

.png

PEcfg.png (Rozmiar: 55.3 KB / Pobrań: 0) ]]> <![CDATA[MODBUS - niepoprawna obsługa]]> https://forum.tinycontrol.pl/showthread.php?tid=3094 Mon, 07 Apr 2025 20:43:38 +0000 xerxes7]]> https://forum.tinycontrol.pl/showthread.php?tid=3094 Sekcje "Custom" w obsłudze MODBUS zawiera bład.
Próbując czytać R4DCB08 znalazłem problem polegający na nieprawidłowym odczycie temperatury z DS18B20.
Konfiguracja:
{"name":"8xDS_0x0C","bitrate":0,"parityBit":0,"stopBit":1,"delayBetweenReads":1,"readings":[{"index":1,"active":true,"name":"DS1","unit":"C","divisor":10,"address":0,"functionCode":3,"variableType":0,"endian":0},{"index":2,"active":true,"name":"DS2","unit":"C","divisor":10,"address":1,"functionCode":3,"variableType":0,"endian":0},{"index":3,"active":true,"name":"DS3","unit":"C","divisor":10,"address":2,"functionCode":3,"variableType":0,"endian":0},{"index":4,"active":true,"name":"DS4","unit":"C","divisor":10,"address":3,"functionCode":3,"variableType":0,"endian":0},{"index":5,"active":true,"name":"DS5","unit":"C","divisor":10,"address":4,"functionCode":3,"variableType":0,"endian":0},{"index":6,"active":true,"name":"DS6","unit":"C","divisor":10,"address":5,"functionCode":3,"variableType":0,"endian":0},{"index":7,"active":true,"name":"DS7","unit":"C","divisor":10,"address":6,"functionCode":3,"variableType":0,"endian":0},{"index":8,"active":true,"name":"DS8","unit":"C","divisor":10,"address":7,"functionCode":3,"variableType":0,"endian":0}]}

Pomimo dzielnika przez 10 LK4 czyta tylko całkowitą część z pomiaru:

.jpg

LK4_temp_modbus_DS.JPG (Rozmiar: 42.5 KB / Pobrań: 4)

Szczęśliwie nie ma już problemów z ujemnymi wartościami, które były problem w LK3.8 i powodem rezygnacji z użytkowania urządzenia.
Dlatego bardzo proszę o poprawę tego błędu albo zaprzestanie mówienia o możliwości konfigurowania "custom modules", bo wygląda to na naciąganie ludzi na wydatki.

Pozdrawiam, licząc na szybką korektę błędu.
J.J.]]> Sekcje "Custom" w obsłudze MODBUS zawiera bład.
Próbując czytać R4DCB08 znalazłem problem polegający na nieprawidłowym odczycie temperatury z DS18B20.
Konfiguracja:
{"name":"8xDS_0x0C","bitrate":0,"parityBit":0,"stopBit":1,"delayBetweenReads":1,"readings":[{"index":1,"active":true,"name":"DS1","unit":"C","divisor":10,"address":0,"functionCode":3,"variableType":0,"endian":0},{"index":2,"active":true,"name":"DS2","unit":"C","divisor":10,"address":1,"functionCode":3,"variableType":0,"endian":0},{"index":3,"active":true,"name":"DS3","unit":"C","divisor":10,"address":2,"functionCode":3,"variableType":0,"endian":0},{"index":4,"active":true,"name":"DS4","unit":"C","divisor":10,"address":3,"functionCode":3,"variableType":0,"endian":0},{"index":5,"active":true,"name":"DS5","unit":"C","divisor":10,"address":4,"functionCode":3,"variableType":0,"endian":0},{"index":6,"active":true,"name":"DS6","unit":"C","divisor":10,"address":5,"functionCode":3,"variableType":0,"endian":0},{"index":7,"active":true,"name":"DS7","unit":"C","divisor":10,"address":6,"functionCode":3,"variableType":0,"endian":0},{"index":8,"active":true,"name":"DS8","unit":"C","divisor":10,"address":7,"functionCode":3,"variableType":0,"endian":0}]}

Pomimo dzielnika przez 10 LK4 czyta tylko całkowitą część z pomiaru:

.jpg

LK4_temp_modbus_DS.JPG (Rozmiar: 42.5 KB / Pobrań: 4)

Szczęśliwie nie ma już problemów z ujemnymi wartościami, które były problem w LK3.8 i powodem rezygnacji z użytkowania urządzenia.
Dlatego bardzo proszę o poprawę tego błędu albo zaprzestanie mówienia o możliwości konfigurowania "custom modules", bo wygląda to na naciąganie ludzi na wydatki.

Pozdrawiam, licząc na szybką korektę błędu.
J.J.]]> <![CDATA[Czujniki wibracji, ciśnienia]]> https://forum.tinycontrol.pl/showthread.php?tid=3076 Sat, 08 Feb 2025 07:16:53 +0000 lukasino]]> https://forum.tinycontrol.pl/showthread.php?tid=3076
Czy do LK4 mogę podłączyć czujnik ciśnienia powietrza?, oleju? oraz czujnik wibracji przykręcony do silnika, aby wyłapać czy nie na bicia.

pozdrawiam]]>
Czy do LK4 mogę podłączyć czujnik ciśnienia powietrza?, oleju? oraz czujnik wibracji przykręcony do silnika, aby wyłapać czy nie na bicia.

pozdrawiam]]> <![CDATA[Boiler controlling via PWM]]> https://forum.tinycontrol.pl/showthread.php?tid=3070 Sat, 25 Jan 2025 15:33:24 +0000 BMA]]> https://forum.tinycontrol.pl/showthread.php?tid=3070 <![CDATA[How to set up INPA1]]> https://forum.tinycontrol.pl/showthread.php?tid=3050 Sat, 21 Dec 2024 16:35:00 +0000 BMA]]> https://forum.tinycontrol.pl/showthread.php?tid=3050 How should I properly set up INPA1 in LK4? Or into which input should I connect the measured voltage?
Thank youi for help]]> How should I properly set up INPA1 in LK4? Or into which input should I connect the measured voltage?
Thank youi for help]]> <![CDATA[I2C sensor problems]]> https://forum.tinycontrol.pl/showthread.php?tid=3017 Thu, 03 Oct 2024 09:40:49 +0000 syky95]]> https://forum.tinycontrol.pl/showthread.php?tid=3017
.png

Snímek obrazovky 2024-10-03 113854.png (Rozmiar: 21.04 KB / Pobrań: 10) ]]>
.png

Snímek obrazovky 2024-10-03 113854.png (Rozmiar: 21.04 KB / Pobrań: 10) ]]> <![CDATA[Problemy z LK4 z LTE]]> https://forum.tinycontrol.pl/showthread.php?tid=3013 Mon, 23 Sep 2024 21:11:48 +0000 pperzyna]]> https://forum.tinycontrol.pl/showthread.php?tid=3013
SW 1.18a | HW 4.0]]>
SW 1.18a | HW 4.0]]> <![CDATA[Czytnik QR]]> https://forum.tinycontrol.pl/showthread.php?tid=3012 Mon, 23 Sep 2024 21:08:54 +0000 pperzyna]]> https://forum.tinycontrol.pl/showthread.php?tid=3012 Jeśli tak to jaki?]]> Jeśli tak to jaki?]]> <![CDATA[Niespodziewane restarty LK4]]> https://forum.tinycontrol.pl/showthread.php?tid=3005 Mon, 09 Sep 2024 16:09:17 +0000 Zito]]> https://forum.tinycontrol.pl/showthread.php?tid=3005
jako zupełnie nowy użytkownik testuję możliwości LK

W nowym LK4 SW 1.18a | HW 4.0 kasowanie użytkownika z listy w zakładce "Dostęp/Access" powoduje 10x restart urządzenia.

Konfiguracja wyczyszczona (zarówno z www jak i przytrzymaniem przycisku reset)
Firmware wgrany parokrotnie przez www.
Jedyną rzeczą jaką robię to dodaję usera i próbuję go skasować. Powoduje to resety LK ale użytkownik pozostaje.

Czy jest to powtarzalne u innych użytkowników czy to problem z moim egzemplarzem?

Pozdrawiam]]>
jako zupełnie nowy użytkownik testuję możliwości LK

W nowym LK4 SW 1.18a | HW 4.0 kasowanie użytkownika z listy w zakładce "Dostęp/Access" powoduje 10x restart urządzenia.

Konfiguracja wyczyszczona (zarówno z www jak i przytrzymaniem przycisku reset)
Firmware wgrany parokrotnie przez www.
Jedyną rzeczą jaką robię to dodaję usera i próbuję go skasować. Powoduje to resety LK ale użytkownik pozostaje.

Czy jest to powtarzalne u innych użytkowników czy to problem z moim egzemplarzem?

Pozdrawiam]]> <![CDATA[Home Assistatn Inpa problems]]> https://forum.tinycontrol.pl/showthread.php?tid=3000 Wed, 21 Aug 2024 12:37:46 +0000 syky95]]> https://forum.tinycontrol.pl/showthread.php?tid=3000
.png

test.png (Rozmiar: 162.53 KB / Pobrań: 9) ]]>
.png

test.png (Rozmiar: 162.53 KB / Pobrań: 9) ]]> <![CDATA[watchdog issues in LK4]]> https://forum.tinycontrol.pl/showthread.php?tid=2983 Mon, 01 Jul 2024 08:39:32 +0000 kkontak]]> https://forum.tinycontrol.pl/showthread.php?tid=2983 we have some problems with the latest batch of LK4 regarding the Watchdog feature.
(we are using various models of LanController, from LK1.2 to LK4 and the watchdog is essential to us.)

A.
Mainly, there is a problem with the Restart Limit.
It should be able to set it to Unlimited Restarts by using zero("0") value in the web page configuration, in conformance with the statement in the API documentation, which I don't know if it works either because we don't use API:
https://docs.tinycontrol.pl/en/lk4/api/c...tabbed_1_1

Cytat:K - number of consecutive restarts before stopping the watchdog function (value 0 means no limit), integer

Right now in FW v1.18a, it is not possible to set "0" value in the web configuration. It says:

Cytat:This field must be "1" or more.

See screenshot below(A).

The exact same issue exists on LK3.8, see my other post for details:
https://forum.tinycontrol.pl/showthread.php?tid=2982

So, is it possible to re-instate the UNLIMITED RESTARTS "0" value for LK4 and LK3.8 too?

B.
Watchdog #6 (wd6) cannot be enabled.
It stays "off" even though it is enabled in the web configuration.
See screenshot below(B).

C.
In "Ping time [ms]" status fields, it says "0" when there is TIME OUT, which is incorrect and confusing. 0ms means that the connection is perfect, but there is no connection on TIME OUT.
See screenshot below( C).
Other Lan Controller models like LK3, LK3.8 etc., they are displaying the message "Time Out" in RED background and that is very nice.

Thanks for your support.

.png

LK4 wd 0 .png (Rozmiar: 177.8 KB / Pobrań: 6) ]]> we have some problems with the latest batch of LK4 regarding the Watchdog feature.
(we are using various models of LanController, from LK1.2 to LK4 and the watchdog is essential to us.)

A.
Mainly, there is a problem with the Restart Limit.
It should be able to set it to Unlimited Restarts by using zero("0") value in the web page configuration, in conformance with the statement in the API documentation, which I don't know if it works either because we don't use API:
https://docs.tinycontrol.pl/en/lk4/api/c...tabbed_1_1

Cytat:K - number of consecutive restarts before stopping the watchdog function (value 0 means no limit), integer

Right now in FW v1.18a, it is not possible to set "0" value in the web configuration. It says:

Cytat:This field must be "1" or more.

LK4 wd 0 .png (Rozmiar: 177.8 KB / Pobrań: 6) ]]>