A B&R FTP client running in ARSim H4.93 returns error 65535 with i_result 9999 while attempting to reach an FTP server at 192.168.0.50. The evidence points to ARSim network-interface binding as the first condition to check: ARSim defaults to the 127.0.0.1 loopback interface, which cannot reach the server address.
Identify the Network-Scope Mismatch
| Item | Observed value | Engineering implication |
|---|---|---|
| Runtime | ARSim H4.93 | Check simulator interface binding before changing FTP logic. |
| Default ARSim interface | 127.0.0.1 |
Loopback traffic remains on the host and cannot reach 192.168.0.50. |
| FTP server | 192.168.0.50 |
ARSim must use an interface with access to that network. |
| Reported diagnostics | Error 65535; i_result 9999 |
Record both values, but the evidence does not define their product-specific meanings. |
Configure ARSim Network Access
Change the ARSim IP configuration from 127.0.0.1 to 0.0.0.0. This allows ARSim to listen on all interfaces of the host PC, including an interface that can reach 192.168.0.50. Treat the broader binding as a security exposure: apply the host firewall and network-access controls appropriate for the machine.
- Stop the running ARSim application.
- Open the ARSim network configuration and set its IP address to
0.0.0.0. - Restart ARSim, execute the existing FTP client call, and monitor the block status and result outputs.
- Confirm that error 65535 and
i_result9999 clear and that the target file operation completes on the FTP server.
Separate FTP Client and Server Settings
The CPU property labeled “FTP Server” concerns hosting an FTP server on the controller runtime. The application shown is acting as an FTP client, so lack of ARSim support for the CPU-side FTP server does not by itself prove that the client is unavailable. Do not use that property as the acceptance test for outbound FTP connectivity.
The supplied client parameters specify /SIP=192.168.0.50, /PROTOCOL=ftp, a user, and a password. Preserve separators between parameter tokens; the displayed text places /PASSWORD immediately after the username value, so verify the actual runtime string before retesting. The evidence does not provide an authoritative parameter grammar, so no corrected delimiter syntax can be asserted here.
Verify the Result on Simulator and Hardware
First verify the interface change in ARSim because it directly addresses the loopback restriction. If the client still fails, capture the exact parameter string and all FTP block outputs, then test the same application on actual B&R hardware. A successful hardware test would isolate the remaining fault to simulator or host-network configuration; failure on both targets would shift attention to the client parameters, credentials, server reachability, or server-side logging.
FAQ
Why can B&R ARSim not reach an FTP server at 192.168.0.50?
ARSim defaults to 127.0.0.1, which is the host loopback interface and cannot access 192.168.0.50. Configure ARSim to use 0.0.0.0, restart it, and repeat the FTP operation.
What do B&R FTP error 65535 and i_result 9999 mean?
The evidence records both values but does not define their exact meanings. In this case, check the ARSim interface binding first and verify whether both values clear after network access is enabled.
Does the B&R CPU FTP Server property enable the FTP client?
No direct dependency is established by the evidence. The CPU property concerns hosting an FTP server, while the shown application initiates an outbound FTP client connection.