jfk Posted July 9, 2017 Report Share Posted July 9, 2017 This came up off forum and wanted to share findings. First off to be clear, even with watchmaker version 6 (TCP/IP communication to port 4040) you do not have to authenticate. The version 6 user guide tends to be a bit confusing on the use of authenticate. FYI Enabling TCP/IP control in File - Preferences - Controlis all the authentication watchmaker requires The change is the result from sending watchmaker the command authenticate 1 version 6.1.6 responds to this unneeded command like a ping authenticate 1Ready "6.1.6" "WATCHMAKER" "Windows" false version 5.5.2 (and earlier) responds with an error pingReady "5.5.2" "WATCHMAKER" "Windows" trueauthenticate 1Error 7 0 "Unrecognized command: authenticate" Sending or never sending authenticate command to watchmaker v6.x makes no differenceto the way the rest of the watchmaker IP control works. This kind of minutiae does not seem to make it in to release notes . Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.