Muse script and Automator differences for read write
Technical Support Guide
Table of Contents
Brand:
- AMX
Models:
- MUSE
Overview:
Depending on the method used to create a program which performs file read/write, the path listed should be altered.
Automator:
If using 'Deploy' mode, the file is created and stored on the PC running Automator.
If using 'Push' mode, the file is created and stored on the Muse controller.
Note:
If using the Muse path "/user/<filename>" in deploy mode, the file will be located within "C:\user\<filename>", and on the Muse controller will be generated in /duet/<filename> (Can be verified with SFTP connection to the /duet folder).
If not using /user/, when in 'Push' mode, the file would not be generated on the Muse controller.Info Callout Body
Scripting:
If handling file read/ writes via scripting, the filepath on the Muse controller is /mojo/program.
If managed without specifying the filepath, the location for the file would be as follows:
/mojo/program/<projectname>/<filename>
If you wish to have the script accessible to multiple projects loaded on the Muse controller, it's possible to specify that the file be located in another directory, for example:
Python code: mySharedFile = open(r"../aFileForEveryone.txt","w")
To manually send/ receive files on the Muse controller which have been set up via scripting, SFTP to /mojo/program/
Table of Contents