• State Not Answered
  • Date
    33boardop
  • Date
  • Replies 3 replies
  • Subscribers 186 subscribers
  • Views 3423 views
  • Users 0 members are here

Where is the new multi-console shutdown documentation for version 2 .3.3?

After being forced to upgrade to 2.3.3 from 2.2.1 ,because the designer's X-Keys would not work with the old hot key layout ('M' is now Macro, not Mark), I found that network shutdown did not turn off the main console like it used to.

After reading all the shutdown macro complaints on the forums, and figuring that ETC would alter the basic function of existing code, rather than fix the problem directly, I tried selecting the remote shutdown option in the ECU for the main console and TADA, it works again.  Now, do I have to point out what the problem is here?

So, if you can point me to where in the released pdf files this alteration was documented, I would appreciate is.  I tried to access other 2.3.x release notes but the archive search was not working this weekend.

Parents
  • 0
    Hi 33boardop,

    I apologize for the issue with the archive function not working this weekend. We are aware of the issue and have resolved it.

    As for the issue you are reporting in this thread, are you talking about an issue with a shutdown macro not firing unless the remote shutdown was selected in the ECU or are you saying that a macro to shut down the console would not work unless the remote shutdown was selected in the ECU? Please do "point out what the problem is" so that we can adequately address it for you as there was some work in some of these areas in 2.3.2.
  • 0 in reply to starksk
    We do not have a shutdown macro. It used to be that using network power off would shutdown the invoking console as well as the RPUs and RVIs that were enabled. Now it does not unless the invoking console has accept remote shutdown enabled as well, which makes it (seemingly) vulnerable to unintended shutdowns from remote stations.
  • 0 in reply to 33boardop
    This is was feature change.

    It was a request since we had remote shutdown that it was possible to shut down other devices but not the device that fired the command!

    This is is now possible, I don't have Remote Shut Down enabled on my device, at the end of the day I can shut down everyone else but leave my desk on while I save to USB or douse the rig etc etc.

    You will now need to choose between Enabling remote shutdown on your device and be at risk to being shut down by someone else. Or Network shutdown everyone and then take 5 more seconds at the end of the day to shutdown your device.

    Hope this clears things up?
Reply
  • 0 in reply to 33boardop
    This is was feature change.

    It was a request since we had remote shutdown that it was possible to shut down other devices but not the device that fired the command!

    This is is now possible, I don't have Remote Shut Down enabled on my device, at the end of the day I can shut down everyone else but leave my desk on while I save to USB or douse the rig etc etc.

    You will now need to choose between Enabling remote shutdown on your device and be at risk to being shut down by someone else. Or Network shutdown everyone and then take 5 more seconds at the end of the day to shutdown your device.

    Hope this clears things up?
Children
No Data
Related

www.etcconnect.com