Hi all. I think I see what is going on with the three programs. I have found that you need to remove EPICINFO.DLL from the FS module folder. Now if you run FS-xxx and then start FSCOMM it should see FSUIPC. if your EPIC hardware is running it should see it as well. Now if you open EPICENTER and go to tools and open EPICINFO the whole system will lockup. what I do is "close communication" in FSCOMM then I can edit, reload epic and use epicinfo in epicenter.so what you have is this. epicio.dll in win system folder fsuipc in FSxxx modules folder FSCOMM running on same pc as the epic hardware and in my case the FSxxx software. If FSCOMM is on onther pc then you will need wideserver and wideclient up as well. I also remove the epicinfo.cfg files. Just remember to CLOSE COMMUNICATION in FSCOMM befor you mess with epicenter. Hope this helps. Ron.

Hi Ron!It's the first time since a long time I joined this forum and I can say it's really great if I see all this threads about my software FS-Communicator. It's really a good feeling that there are so much people using this software.I know that that FS-Communicator isn't a software for a short 'install and try'but it seems there are a lot of people reading a manual with some MB's (I can't believe it.....). OK, that was a little 'off topic' , but caused by a lot of simbuilding and programming I lost some experience about handling of formus like this one :-).Your infos are correct. Don't use epicinfo with FS-Communicator at the same time(There is really no need for doing something like this!). For opening epicenter the polling should be switched off. The reason seems to be, that epicinfo.dll have problems with multiple requests at the same time. Maybe it works sometimes with larger polling cycles, but I think there is also no need to poll the epic during working with epicenter. FD-Bus polling must not be switched off during working with epicenter, but I think that was clear anyway.CIAO Robert