We have developed a TestStand (4.2) OI including a tracelogger function. Code moduls (dll's coded in C++) used in sequences can send trace messages to the OI using the PostUIMessage function (see following code): try { // Get the thread that is executing from the Sequence Context thread = seqContext->GetThread(); thread->PostUIMessage( static_cast<enum UIMessageCodes>(UIMsg_UserMessageBase+4) ,Level ,_bstr_t(Msg) ,TRUE); } catch( _com_error &com_error ) /* TestStand API only throws this kind of exception */ { ..... } It happens that every 10ms a message is send. In general this works well both when running the sequence in the sequence editor and in our OI. But after a time spawn of about 10 min to a few hours (depends on the frequency of the messages) the PostUIMessage throws a com_error Exception. Remark: The code is declared as critical section to ensure it works in multi threaded environments too. Does someone has an idea what might be the reason for these exceptions and how to avoid them? Thanks in advance Peter

Hi Peter, You wrote that cycle rate is about 10ms. This is fast! Normally i use such rates in worker threads or separate TS threads. If you have such of this in your code module or sequence file. Maybe your variables "seqSontext" or "thread" is not valid. Before calling thread->PostUIMessage check that everything is valid. Hope this helps Juergen

NI TestStand

thread->PostUIMessage throws com_error Exceptions

Solved!

Mr.Doug
It's not showing any error and execution is good, implementation done and my point is to improve the speed.
It having 5 to 10 mm variation in every time.
Need to solve and kindly give some idea.

Thanks for your reply

Message 11 of 11

(689 Views)

NI TestStand

thread->PostUIMessage throws com_error Exceptions

Re: thread->PostUIMessage throws com_error Exceptions