Look, guys, I really like the board but your support seems do not know the matter... Really frustrating experience!
I am exchanging emails back and forth with someone from support (do not know if it is one person or not).
I explained exactly what is the problem many times. But they found something in the code they think is wrong and keep telling me that this is the reason.
It looks like they do not understand a simple code of 3 lines!
Moreover- even if the support were correct- it will not cause the phenomenon I am experiencing! I asked to explain why it would cause sending from EM3 instead from EM1- did not get answer.
So, out of no choice I put here this code of 3 lines (which is actually nothing to do with the real problem!):
TSTEQ VAR6[43200000] 0 VAR1
GOTO VACANT
GOTO MOVEMENT
They claim that every time VAR6 flips 1-0-1-0-1, it will also go to flipping Vacant-Movement-Vacant.
This claim is actually contradict with both PLC command explanations in the manual and actual, real work of the board!
They still keep telling the same...
Here is my explanation (and it actually works this way in reality!!!):
The first line (TSTEQ) will get true if VAR6 will be zero within 43200 seconds or more.
In case of TRUE, it will go to VACANT; otherwise it will go to MOVEMENT.
Therefore, the line TSTEQ VAR6[43200000] 0 VAR1 means that it will go to Vacant ONLY if 43200 seconds passed without VAR6=1.
No matter how many flips 1-0-1-0 VAR6 does- it will go to Movement all the time because the condition of 43200 seconds did not meet!
It will go to Vacant only after last VAR6=1 was 43200 (12 hours) seconds ago (if VAR6 was 0 within last 43200 seconds)!
If after 12hours VAR6 gets 1, it will go to Movement again and will stay there until last time VAR6=1 was 12 hours ago.
Every pulse of 1 of VAR6 will reset counter of 43200 seconds to zero but it stays on Movement.
Again, even if their claim were correct (flip vacant-movement), I would get constant emails from Vacant-Movement respectively. This does not happen, of course.
My problem is that when 2 events that happen at the same time trigger their respective email notifications (from different EMs), instead of receiving 2 emails from 2 EMs, I get 2 emails from the same EM- with the same subject in the email, but I/O data inside the each email correspond to each event. There is something that cause these 2 emails jammed, mixed up when they should be sending at almost the same time.
In no way the code shown above (whether it is correct or not-does not matter) would cause such a phenomenon.
I am exchanging emails back and forth with someone from support (do not know if it is one person or not).
I explained exactly what is the problem many times. But they found something in the code they think is wrong and keep telling me that this is the reason.
It looks like they do not understand a simple code of 3 lines!
Moreover- even if the support were correct- it will not cause the phenomenon I am experiencing! I asked to explain why it would cause sending from EM3 instead from EM1- did not get answer.
So, out of no choice I put here this code of 3 lines (which is actually nothing to do with the real problem!):
TSTEQ VAR6[43200000] 0 VAR1
GOTO VACANT
GOTO MOVEMENT
They claim that every time VAR6 flips 1-0-1-0-1, it will also go to flipping Vacant-Movement-Vacant.
This claim is actually contradict with both PLC command explanations in the manual and actual, real work of the board!
They still keep telling the same...
Here is my explanation (and it actually works this way in reality!!!):
The first line (TSTEQ) will get true if VAR6 will be zero within 43200 seconds or more.
In case of TRUE, it will go to VACANT; otherwise it will go to MOVEMENT.
Therefore, the line TSTEQ VAR6[43200000] 0 VAR1 means that it will go to Vacant ONLY if 43200 seconds passed without VAR6=1.
No matter how many flips 1-0-1-0 VAR6 does- it will go to Movement all the time because the condition of 43200 seconds did not meet!
It will go to Vacant only after last VAR6=1 was 43200 (12 hours) seconds ago (if VAR6 was 0 within last 43200 seconds)!
If after 12hours VAR6 gets 1, it will go to Movement again and will stay there until last time VAR6=1 was 12 hours ago.
Every pulse of 1 of VAR6 will reset counter of 43200 seconds to zero but it stays on Movement.
Again, even if their claim were correct (flip vacant-movement), I would get constant emails from Vacant-Movement respectively. This does not happen, of course.
My problem is that when 2 events that happen at the same time trigger their respective email notifications (from different EMs), instead of receiving 2 emails from 2 EMs, I get 2 emails from the same EM- with the same subject in the email, but I/O data inside the each email correspond to each event. There is something that cause these 2 emails jammed, mixed up when they should be sending at almost the same time.
In no way the code shown above (whether it is correct or not-does not matter) would cause such a phenomenon.