bulentkusva napisał(a)
ower fails, the key position information (on / off) does not read.
"Is true, I add this function in next software"
Did you add this feature?
bulentkusva napisał(a):bulentkusva napisał(a)ower fails, the key position information (on / off) does not read.
"Is true, I add this function in next software"
Did you add this feature?
No, but I add soon (maby 2-3 days)
wilkxt napisał(a):bulentkusva napisał(a):bulentkusva napisał(a)ower fails, the key position information (on / off) does not read.
"Is true, I add this function in next software"
Did you add this feature?
No, but I add soon (maby 2-3 days)
I add this in soft ver 2.37, test and check.
http://tinycontrol.ats.pl/forum/viewtopi...f=2&t=2599
192.168.1.100 remote kontrol ---> enable server
192.168.1.101 remote kontrol ---> enable client --- INP1D ---> OUT0
-----------------
192.168.1.101 = INP1D ----> LOW => 192.168.1.100 OUT0 =ON
192.168.1.101 = INP1D ----> HIGH => 192.168.1.100 OUT0 =OFF
OK NO PROBLEM
-----------------
192.168.1.101 = INP1D ----> LOW => 192.168.1.100 OUT0 =ON
192.168.1.101 INP1D ----> LOW |POWER OFF |
INP1D ----> HIGH ----> |POWER ON | 192.168.1.100 OUT0 =OFF
OK NO PROBLEM
---------------------------
192.168.1.101 = INP1D ----> LOW => 192.168.1.100 OUT0 =ON
192.168.1.100 |POWER OFF |
|POWER ON | 192.168.1.100 OUT0 =OFF (192.168.1.101 => INP1D ----> LOW)
PROBLEM
You're right, I added client-side options.
But it works, so that the server receives UDP packets from the client, and if the server is turned off and back on, it does not know how to set the output until get the package from the client. Server does not know what is the address of the client(because there may be many) and can not send the package to the client.
There are two ways to solve the problem.
1.Easier to implement: Add option, the server will remember the outputs stats before off and after turning on them set. Only that this option has one drawback: as the server is turned off and at that time will change the status of the client INPD it will not be noticed.
2. Difficult to implement: Server will remember client IP(the last client package before off) and when you turn on, serwer sends requesting packet to the client the transfer of the current state of INPD.
The first solution is sufficient or not?
client at regular intervals, send INP status?
or to the server, type the IP address of the client, status query INP be a solution?
bulentkusva napisał(a):client at regular intervals, send INP status?
What time intervals will be OK?
bulentkusva napisał(a):or to the server, type the IP address of the client, status query INP be a solution?
It is OK solution, propably i add this option
What time intervals will be OK?
1-20 sec
Control Panel ---> DIGITAL Inputs State : DIGITAL Inputs : INP1D INP2D INP3D INP4D 4 pcs
Network Configuration ---> Remote Control : INP1D - INP2D 2 pcs
Remote Control 4 pcs Is it possible?
bulentkusva napisał(a):Remote Control 4 pcs Is it possible?
Yes, but in new software. I don't now when new software will be done, maby one two months