...
Invalid configurations include: "https://tps.mycompany.com" , "tps.mycompany.com/servlet", "tps.mycompany.com?redirect=true", or any combination of additional decoration, paths, or arguments to the DNS name.
Once the Custom Endpoints are configured the CWM can now be physically connected to the OKE. If the OKE port and baud rate settings differ from the OKE Simulator used for Custom Endpoint configuration then the TPS server must send a Port command to the CWM after it connects to the TPS server. The Port command must have the correct Port configuration for the OKE to which the CWM is communicating. For example, if the OKE simulator used a USB CDC connection and the OKE uses the RS232 interface at 115200 baud then the following Port command must be sent as _pld to the CWM from the TPS server’s /pullform form:
{"oke":{"port":"232","baud":115200}}
Other valid values for port are "usb", "ttl", and "485".
_cmd must be wr.
_dst must be ["CWMDEVID"], where CWMDEVID is the actual Device ID of the CWM.
If you used the simulator with a USB cable connection to the CWM, it will have saved “usb” as the port setting to the CWM. If you used a custom RS232 cable, it would have saved “232” as the port. A common issue is when the cable used for the simulator doesn’t match the equipment’s cable.