|
Re: v1.10.1 Woes [message #1801421 is a reply to message #1801402] |
Fri, 18 January 2019 18:58 |
|
Hi,
thanks for bringing this issues to our attention.
Interestingly in a test today I stumbled across the same error message when testing a CFB. In my case the reason was that my 4diac FORTE did not had all the FBs in the composite. Could this be the case for your 4daic FORTE as well?
Unfortunately we have still an issue in detecting missing FB types for CFBs [1].
We did some changes regarding monitoring in 4diac IDE (i.e., harmonizing deployment and monitoring), but I would't have expected to have such an impact. It would be great if we can narrow this issue down. Therefore I would like to ask a few questions here:
- Can you expand on what you mean with „things sorts of goes blank"?
- Is the issue building up over time or because of the number of watched ports?
- Are you watching on more then one or more devices?
- How many FBs ports are you watching when the issues are starting?
- From your observation do you think its happening on 4diac IDE or 4diac FORTE side?
Especially on FORTE side we have some limitations regarding memory and network that may limit the number of ports that can be watched at the same time.
Cheers,
Alois
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=506434
|
|
|
|
Re: v1.10.1 Woes [message #1801529 is a reply to message #1801495] |
Mon, 21 January 2019 20:09 |
|
Hi Daniel,
great that we could solve your first issue.
The second one is rather strange. I normally do activate watches more then one FB at the same time. The cleared monitoring items has been introduced in 1.10.0 to show that the connection to the device was lost. This can be because of a communication issue or some exception in the monitoring handling code. Do you have some trace outputs in .log file that could help us to narrow it down? Or do you have a recipe that leads always to that behavior allowing us to reproduce it?
Cheers,
Alois
|
|
|
|
Re: v1.10.1 Woes [message #1801554 is a reply to message #1801534] |
Tue, 22 January 2019 13:22 |
|
Hi,
thanks for the videos. I'm currently traveling. I'll try to look as soon as possible on them.
You can find the .log file in the .metadata directory in your workspace.
Cheers,
Alois
|
|
|
Re: v1.10.1 Woes [message #1801581 is a reply to message #1801554] |
Tue, 22 January 2019 21:26 |
|
I found some time today in the train to look on your videos and your code. After the first I thought the cause is that you are monitoring inside of CFBs. But the other videos showed my that this is not the case. I think that it could be a race condition in the device communication code. This would be quite quick to fix. However with my tests I was not able to reproduce it. Therefore getting some outputs from your logs could really help us.
Cheers,
Alois
P.S.: have you seen the news post on the improvements in deployment, i.e., you can now deploy also from the system perspective. I think for your tests this could save you quite some time.
|
|
|
|
|
Re: v1.10.1 Woes [message #1802072 is a reply to message #1802027] |
Thu, 31 January 2019 17:25 |
|
Hi Daniel,
thanks for the log. I think what is shown there could really be the concurrency problem I fixed in Bug 543754 as described in my last message. So if you would like to build 4diac IDE from source you can try the latest version from the 1.10.x commit or wait for the 1.10.2 release.
Alois
|
|
|
Powered by
FUDForum. Page generated in 0.05602 seconds