Very hard to implement a long process dll or applicatio​n in TestStand such as firmware download task.

Question

Hi All
In my daily projects there are many firmware download tasks on mass production for kinds of products sucha s phone, mp3, game box and so on. The common download is performed via USB or serial port.
Firmware download is often a long process what will take up to hundreds of seconds. The download application or dll is often provided by customer or the chipset supplier, I have ever call a download dll in TestStand, the only way is to run the dll in another threading and at the UI threading I monitor the dll's log file for status, it looks a very stupid way to do, things oftn lose control.
This time I have to automatically download firmwares to a mp3(Sigmatel chipset), Sigmatel provided an application for parallel downloading what is very unstable, the application often hangs or crash, I tried to update the application source code but Sigmatel says they will not support if I change something.
If someone use the application, he needs to press the START button, if fail, press the STOP firstly, if crash..... everything lose control. In my opinion, even if I change the application to a dll, there are still long processes, I must let TestStand wait there for the log file information? I do not think that is a good idea.
My thought is this is a usual task in manufacturing, could someone please advice me how do you handle this kind of testing in your test station? How to run a long process task in TestStand and communicatio with it and keep everything in control.
Thanks.
帖子被paulbin在04-06-2008 07:49 PM时编辑过了
*The best Chinese farmer*

Answer 1

Hi,
I have used a VC++ dll
Here are some snipptes
void CProcessLoaderApp:ostMessageToProcess(LPPROCESS_INFORMATION lpProcessInformation,UINT Msg, WPARAM wParam, LPARAM lParam)
 FINDWINDOWHANDLESTRUCT fwhs;
 fwhs.ProcessInfo = lpProcessInformation;
 fwhs.hWndFound  = NULL;
EnumWindows ( EnumWindowCallBack, (LPARAM)&fwhs ) ;
 PostMessage ( fwhs.hWndFound, Msg, wParam, lParam );
BOOL CALLBACK CProcessLoaderApp::EnumWindowRcs5SystemTestCallBac​k(HWND hwnd, LPARAM lParam)
 FINDWINDOWHANDLESTRUCT * pfwhs = (FINDWINDOWHANDLESTRUCT * )lParam;
 DWORD ProcessId;
 CString Title;
 GetWindowThreadProcessId ( hwnd, &ProcessId );
 // note: In order to make sure we have the MainFrame, verify that the title
 // has Zero-Length. Under Windows 98, sometimes the Client Window ( which doesn't
 // have a title ) is enumerated before the MainFrame
 CWnd::FromHandle( hwnd )->GetWindowText(Title);
 if ( ProcessId  == pfwhs->ProcessInfo->dwProcessId && Title.Compare("MyApplicationName_ReplaceThatStuff"​) == 0)
  pfwhs->hWndFound = hwnd;
  return false;
 else
  // Keep enumerating
  return true;
 MainStuff:
SetCursorPos(10,23);
 m_App.PostMessageToProcess(&g_pi,WM_LBUTTONDOWN,0​x01,0x000A0017);
  WaitForSingleObject(Event,200);
 m_App.PostMessageToProcess(&g_pi,WM_LBUTTONUP,0x0​0,0x000A0017);
  WaitForSingleObject(Event,200);
Greetings
juergen
=s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=