There is an issue with the new version of the Aquisition Server. With the version 1.3.0 there were no major issues to connect Micromed with OpenVibe. However, since new version, there is a strange error (maybe just in a visualisation).
Namely, the new version of Aquisition Servers shows drift of 800-2000ms
Whereas the on the same PC, the version 1.3.0 shows drift of -5 to + 5ms, which is tolerable for my applications.
Did you change anything regarding the delay visualisation or similar to cause such behaviour?
------------------------------------
2nd: I would like also to suggest some changes too. The architecture of Micromed is a little bit strange and non-intuitive, meaning that the OpenVibe Acquisition Server starts an additional server that listens on the specified port (3000 or 5000), and System Evolution (Micromed Aquisition sw) connects to that server (we would expect the opposite).
The problem is that the time-out on OpenVibe Aquisition Server is hardcoded and set to only 5seconds. This means that it gives you just 5 seconds to start System Evolution and click "Record Button". I don't see a reason why not putting longer time-out? Even a couple of minutes and present a message in console or window to start recording in SystemEvolution?
Code: Select all
,m_ui32TimeOutMilliseconds(5000)
Code: Select all
if(m_pConnectionServer->isReadyToReceive(m_ui32TimeOutMilliseconds))
{
// Accept new client
m_pConnection=m_pConnectionServer->accept();
}
else
{
m_rDriverContext.getLogManager() << LogLevel_Error << "> Time out after " << m_ui32TimeOutMilliseconds << " milliseconds\n";
// Cleans up server connection
m_pConnectionServer->close();
m_pConnectionServer->release();
m_pConnectionServer=NULL;
return false;
}