I'm using D2Box application and I'm facing a strange problem
unable to set the value of state variable.
-
arunmib
- Posts: 5
- Joined: 26 May 2008, 12:52
unable to set the value of state variable.
Hi all,
I'm using D2Box application and I'm facing a strange problem
. My BCI application communicates (UDP socket communication) with another application and updates certain parameters in the BCI system. The BCI receives the data from the other application properly and I've double checked it by writing those data in a file and also by adding a message box. What I mean properly here is they contain the values that are expected. When I update the state variables in the BCI only one variable doesn't gets updated (basically the one that has been changed by the external application) . If I modify other state variables inside BCI based on this modified state variable, those other modified variables gets updated in BCI but the one modified by the external application still doesn't. Any help, information or direction to solve this problem will be much appreciated.
I'm using D2Box application and I'm facing a strange problem
-
gschalk
- Posts: 615
- Joined: 28 Jan 2003, 12:37
State problem ...
Arunmib,
This does sound strange. The only thing I can think of is that the state that is being updated by the external program is being overwritten by some other module that also sets the same state.
A few questions:
1) BCI2000 v2.0 has many advantages over the v1.x code base. I strongly suggest updating.
2) Are you using the AppConnector to read states from the external program?
I would try to
1) rename the state and see if the problem persists
2) set the state, just like any other state, without input from any other external program just in the D2Box task code itself.
Let us know what happened.
Gerv
This does sound strange. The only thing I can think of is that the state that is being updated by the external program is being overwritten by some other module that also sets the same state.
A few questions:
1) BCI2000 v2.0 has many advantages over the v1.x code base. I strongly suggest updating.
2) Are you using the AppConnector to read states from the external program?
I would try to
1) rename the state and see if the problem persists
2) set the state, just like any other state, without input from any other external program just in the D2Box task code itself.
Let us know what happened.
Gerv
-
arunmib
- Posts: 5
- Joined: 26 May 2008, 12:52
thanks for the reply gerv. FYI - I don't use the Appconnector to read states, rather I've written separate communication module more to suit my needs.
I've already tried your suggestions, but didn't help much. Sorry, for not mentioning them in my previous post itself.
Well, I've circumvented the problem by adding a new variable in the class and using that as the control.
Anyways, thanks the reply and suggestion.
I've already tried your suggestions, but didn't help much. Sorry, for not mentioning them in my previous post itself.
Well, I've circumvented the problem by adding a new variable in the class and using that as the control.
Anyways, thanks the reply and suggestion.
Who is online
Users browsing this forum: No registered users and 0 guests
