Hello Ray,

I am using the latest PEMpro v2 build 41.
I'm trying to use the simulator to learn a little more, but it wont work.
According to your help file in Simulator it states it does NOT in any way try to connect to the internet (nor does PEMpro....)
Not correct.
I started simulator in Startup Menu,
started PEMpro, tried to connect to simulator and the following error messages pop up.
PEMpro is trying to access the internet.
PEMpro simulator want to accept connections from the internet.
No response from the simulator. Please start it first from the Startup Menu.

When simulator started first two error messages came up.
Syntax error line 8 in file c:\\ ****.ppc
Syntax error line 9 " " " " .ppc
Both files work in PEMpro.

The help file also states there is a default PPC file included with the installation.
I can't find it.

Any help will be appreciated.
Regards
Vince

The simulator DOES NOT try to connect to the internet. It creates a socket that allows it to talk to PEMPro. The problem with a socket is that a connection _can_ possibly come from the internet, but PEMPro and the simulator only talk to each other on the same PC.

The simulator was used for test/development but it is not really supported any more.

-Ray

Hi Vince,

Attached is the original PEMPro simulator file. It has a ".txt" extension so you will need to rename it to "something.PPC" and then, in the PEMPro simulator, click "File->Load Curve...", navigate to the file and select it.

-Ray

PEMProSimulatorTestCurve.txt (13 Kb, 48 downloads)

Also, if you have created any curves from your own data you will find them in your "Logs and Images" directory. You can load those files into the simulator instead.

-Ray

quote:

Originally posted by Ray Gralak:

The simulator was used for test/development but it is not really supported any more.

-Ray

Are you still entertaining fixing Simulator or looking into such issues? I just tried with V2.5 rev 61 and I cannot get PemPro to connect to the simulator. I get a no reponse from the simulator message even though it is up. I am using Vista 32 if that means anything. Both have been allowed in Firewall tp communicate although I don't think it really matters for the Simulator. If I had to guess some kind of issue with tying sockets to simulator and Pem Pro is the issue.

I just tested the Simulator and PEMPro V2.5 build 62 and they communicate on XP Pro SP3. So somewhere you probably have something blocking or using the UDP ports that PEMPro and the Simulator are trying to use.

-Ray

quote:

Originally posted by Ray Gralak:
I just tested the Simulator and PEMPro V2.5 build 62 and they communicate on XP Pro SP3. So somewhere you probably have something blocking or using the UDP ports that PEMPro and the Simulator are trying to use.

-Ray

I tried it on an older XP machine I have with SP# and your right it works. Any ideaq on how to get Vista make it work. I have turnd off UAC many weeks ago and installed with it off. No erros I could see during installation.

I'm guessing that there is a firewall issue somewhere blocking the packets. Try turning off the firewall temporarily to see if the two apps will communicate. If that is so then you'll need to add a couple rules to the firewall to allow communications. But first, let me know if turning off the firewall works.

-Ray

quote:

Originally posted by Ray Gralak:
I'm guessing that there is a firewall issue somewhere blocking the packets. Try turning off the firewall temporarily to see if the two apps will communicate. If that is so then you'll need to add a couple rules to the firewall to allow communications. But first, let me know if turning off the firewall works.

-Ray

No joy I turned off firewall, looked and saw in any case both were exceptions in amny case. I am qwndoering if it is Windows Defender or some overly strict Socket stuff. Vista Help is pretty worthless. I tyoed in Winsock, Socket and got to the Windows Defender but I cannot see anything there. So firewall is back on. I'll cehck the microsoft site.

quote:

Originally posted by roystarman:

quote:

Originally posted by Ray Gralak:
I'm guessing that there is a firewall issue somewhere blocking the packets. Try turning off the firewall temporarily to see if the two apps will communicate. If that is so then you'll need to add a couple rules to the firewall to allow communications. But first, let me know if turning off the firewall works.

-Ray

No joy I turned off firewall, looked and saw in any case both were exceptions in amny case. I am qwndoering if it is Windows Defender or some overly strict Socket stuff. Vista Help is pretty worthless. I tyoed in Winsock, Socket and got to the Windows Defender but I cannot see anything there. So firewall is back on. I'll cehck the microsoft site.

There appear to be many pags of issues wth Winsock and Vsta. There also appears to be some limit as to how many Winsocks are available. I'm geeting over my head here since I am not a programmer.

You can also check if the programs are bound to the tcp or udp sockets with netstat -abn

C:\>netstat  -abn

Active Connections

  Proto  Local Address          Foreign Address        State           PID

  TCP    127.0.0.1:2556         0.0.0.0:0              LISTENING       3776
  [AstroVidTools.exe]

 
  UDP    0.0.0.0:9126           *:*                                    3776
  [AstroVidTools.exe]

  UDP    0.0.0.0:9124           *:*                                    4248
  [PEMPro-V2.exe]


  UDP    0.0.0.0:9123           *:*                                    4264
  [PemProScopeSim.exe]
  

Also I have had many socket problems because of other applications allocating ports. Since sockets are bound to one app only the other app failes. You might check that as well.

Gerard

If you can find your firewall settings you can just allow UDP on ports 9123-9126, which is what PEMPro, the simulator, and the video app use. You also might want to try running the apps with administrator privileges.

-Ray

quote:

Originally posted by Ray Gralak:
If you can find your firewall settings you can just allow UDP on ports 9123-9126, which is what PEMPro, the simulator, and the video app use. You also might want to try running the apps with administrator privileges.

-Ray

no joy on adding ports 9123 through 9126. my pritout of the command Gerard gave does not look like his. I got no indications of the componets binfding to any socket

quote:

Originally posted by roystarman:

quote:

Originally posted by Ray Gralak:
If you can find your firewall settings you can just allow UDP on ports 9123-9126, which is what PEMPro, the simulator, and the video app use. You also might want to try running the apps with administrator privileges.

-Ray

no joy on adding ports 9123 through 9126. my pritout of the command Gerard gave does not look like his. I got no indications of the componets binfding to any socket

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\roy>netstat -abn

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:13 0.0.0.0:0 LISTENING
[D4.exe]
TCP 0.0.0.0:37 0.0.0.0:0 LISTENING
[D4.exe]
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
RpcSs
[svchost.exe]
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING

Can not obtain ownership information

x: Windows Sockets initialization failed: 5
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING

Can not obtain ownership information

x: Windows Sockets initialization failed: 5
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
[wininit.exe]
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
Eventlog
[svchost.exe]
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
Schedule
[svchost.exe]
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING
[lsass.exe]
TCP 0.0.0.0:49157 0.0.0.0:0 LISTENING
[services.exe]
TCP 127.0.0.1:4664 0.0.0.0:0 LISTENING
[GoogleDesktop.exe]
TCP 127.0.0.1:10110 0.0.0.0:0 LISTENING
[avgemc.exe]
TCP 192.168.1.101:139 0.0.0.0:0 LISTENING

Can not obtain ownership information

x: Windows Sockets initialization failed: 5
TCP 192.168.1.101:49467 63.251.8.249:80 TIME_WAIT
TCP 192.168.1.101:49490 63.251.8.249:80 ESTABLISHED
[iexplore.exe]
TCP [::]:135 [::]:0 LISTENING
RpcSs
[svchost.exe]
TCP [::]:445 [::]:0 LISTENING

Can not obtain ownership information

x: Windows Sockets initialization failed: 5
TCP [::]:5357 [::]:0 LISTENING

Can not obtain ownership information

x: Windows Sockets initialization failed: 5
TCP [::]:49152 [::]:0 LISTENING
[wininit.exe]
TCP [::]:49153 [::]:0 LISTENING
Eventlog
[svchost.exe]
TCP [::]:49154 [::]:0 LISTENING
Schedule
[svchost.exe]
TCP [::]:49155 [::]:0 LISTENING
[lsass.exe]
TCP [::]:49157 [::]:0 LISTENING
[services.exe]
UDP 0.0.0.0:13 *:*
[D4.exe]
UDP 0.0.0.0:37 *:*
[D4.exe]
UDP 0.0.0.0:123 *:*
[D4.exe]
UDP 0.0.0.0:500 *:*
IKEEXT
[svchost.exe]
UDP 0.0.0.0:3702 *:*
FDResPub
[svchost.exe]
UDP 0.0.0.0:3702 *:*
FDResPub
[svchost.exe]
UDP 0.0.0.0:4500 *:*
IKEEXT
[svchost.exe]
UDP 0.0.0.0:5355 *:*
Dnscache
[svchost.exe]
UDP 0.0.0.0:49152 *:*
FDResPub
[svchost.exe]
UDP 0.0.0.0:58371 *:*
Dnscache
[svchost.exe]
UDP 127.0.0.1:1900 *:*
SSDPSRV
[svchost.exe]
UDP 127.0.0.1:49414 *:*
ProfSvc
[svchost.exe]
UDP 127.0.0.1:49728 *:*
[iexplore.exe]
UDP 127.0.0.1:60685 *:*
SSDPSRV
[svchost.exe]
UDP 127.0.0.1:61104 *:*
BITS
[svchost.exe]
UDP 192.168.1.101:137 *:*

Can not obtain ownership information

x: Windows Sockets initialization failed: 5
UDP 192.168.1.101:138 *:*

Can not obtain ownership information

x: Windows Sockets initialization failed: 5
UDP 192.168.1.101:1900 *:*
SSDPSRV
[svchost.exe]
UDP 192.168.1.101:60684 *:*
SSDPSRV
[svchost.exe]
UDP [::]:500 *:*
IKEEXT
[svchost.exe]
UDP [::]:3702 *:*
FDResPub
[svchost.exe]
UDP [::]:3702 *:*
FDResPub
[svchost.exe]
UDP [::]:5355 *:*
Dnscache
[svchost.exe]
UDP [::]:49153 *:*
FDResPub
[svchost.exe]
UDP [::1]:1900 *:*
SSDPSRV
[svchost.exe]
UDP [::1]:60682 *:*
SSDPSRV
[svchost.exe]
UDP [fe80::205d:2821:3f57:fe9a%10]:1900 *:*
SSDPSRV
[svchost.exe]
UDP [fe80::205d:2821:3f57:fe9a%10]:60683 *:*
SSDPSRV
[svchost.exe]
UDP [fe80::2c76:a13b:4eb9:db6f%11]:1900 *:*
SSDPSRV
[svchost.exe]
UDP [fe80::2c76:a13b:4eb9:db6f%11]:60681 *:*
SSDPSRV
[svchost.exe]
UDP [fe80::4980:f12c:761c:a262%12]:1900 *:*
SSDPSRV
[svchost.exe]
UDP [fe80::4980:f12c:761c:a262%12]:60680 *:*
SSDPSRV
[svchost.exe]

C:\Users\roy>^A

quote:

no joy on adding ports 9123 through 9126. my pritout of the command Gerard gave does not look like his. I got no indications of the componets binfding to any socket

Well, since the app works ok in XP and I'm using the .Net platform this is probably a permissions problem on your PC. So outside of turning off UAC and reinstalling PEMPro and running both apps with administrator privileges there there is nothing I can think to try.

-Ray