Printer FriendlyEmail Article Link

Positioning Application: PosApp reports BSD Socket messages "Debug: Could not connect UDP socket" / "Debug: Could not connect to server" / "Warning: Client error"

Environment/Versions
  • PosApp (SimGEN)
  • GSS8000
Answer

NOTES:

  1. Before following this article it is recommended that GSS8000 users first follow the checks outlined in article SOL10836.

  2. The following symptoms may also be accompanied by intermittent power-up issues - see article FAQ11980.

 

  • The following messages are likely to be seen in the message log window / message log file during the scenario arming phase
  • They may lead to the scenario not entering the running phase:-
    • Debug : BSD Socket - Could not connect UDP Socket (A socket operation was attempted to an unreachable host.). Please check network cable and settings.
    • Debug: BSD socket - Could not connect to server: connect() timed out. Please ensure server address <192.168.5.101> is correct.
    • Warning: Could not connect to the instrument at IP address: 192.168.5.101
    • Error: Can't read response to *IDN? message from Signal Generator
    • Error: GSS8000 #8502 is not on the IEEE/IP bus
  • These types of messages can be ignored if working in "No hardware" mode
     
  • The following messages are likely to be seen in the message log window / message log file during a scenario run
  • They may ultimately lead to the scenario aborting:-
    • Info: Timeout in low rate wait, > 1100
    • Warning: BSD socket - Client error <An existing connection was forcibly closed by the remote host.>
    • Warning: SimGEN update task completed 16504 ms late
    • Fatal: High rate task over-run -- could not update hardware on time

  • If you notice that the loss of connection with the simulator coincides with the unit having shutdown.
    • This may be due to overheating - see article KNI10908
    • This may be due to power issues - see article KNI10910
       
  • If these sequences of messages are persistent then it highlights a potential fault with the CPU card, which will need to be replaced.
    • Contact Spirent Global Services using the "Submit a Service Request" link on the right hand side of the Knowledge Base page
    • Confirm your simulator model and serial number
    • Confirm the version of PosApp being used (go to menu [Help-->About])
    • Send a copy of the PosApp_message_log.txt file, after seeing the errors (ensure all message types are enabled in menu [Options-->Message Reporting])

Product : GSS8000