Please read (and re-read) the Trotec Speedy 300 Tool Page before using this manual.
The user manual is here: Trotec Ruby Software User Manual
- Key concepts for lasertechs new to Ruby - high level overview
- Transition to Ruby - organisational, administrative and user issues to be considered
- Installation - once-off installation steps
- Configuration - once-off configuration steps
- Materials database management - cleanup, structure, management
- User administration - adding and managing users (members)
- Proposal: Remote access to the laser PC
- Software updates
- Installing Ruby on your own PC
1. Key concepts for lasertechs new to Ruby
1.1 Documentation and resources
Trotec’s information is still a bit thin, and fragmented.
- Help - main documentation
- FAQ - high level information about the future of Job Control and Ruby
- Roadmap - we can track which features are ready, imminent or a long way off
- Release notes
- Submit an idea to Trotec
1.2 Access and security
- Each user has their own username and password - no-one needs to login as email@example.com
- Remote access allows users to explore the software, and push jobs to the queue.
- They can do this on any web browser on any device that is connected to the same network as the laser PC.
- They don’t see the simultaneous activities of any other users, including someone on the laser PC.
- They can only start jobs from the laser PC, so they still have to be physically present at the laser during operations.
- Unlike the existing JobControl workflow, which involves steps that are taken in multiple pieces of software (e.g. Illustrator, then the prin settings, then JobControl), with Ruby you do everything on several screens within the Ruby interface.
2. Transition to Ruby
2.1 Parallel operation
- Ruby and Job Control can and do co-exist.
- We need to check if there is a sync of the materials database, or just a one-off import. We don’t want material settings changes on one platform to affect the other.
- There is an important process for switching the laser between JobControl and Ruby (see below)
2.2 New inductees
- At some point we can decide to induct new users on Ruby rather than Job Control.
- We can run training courses for existing inductees covering just the new software and workflow to help them migrate from Job Control to Ruby.
- Ruby Remote Access (local network) allows for a new mode of training as users could sit in the clean room and explore the software, rather than having to crowd around the laser PC.
2.3 Existing users
There are some big changes to the workflow for setting up a job file and cutting/engraving.
We could offer a mini-course that covers:
- A brief reminder of the overall workflow (from stepping up to the laser to walking away)
- How to prepare a job file in Adobe Illustrator, Inkscape (if there are differences from JobControl)
- Setting up the job and running it
We will only need to find out the finer details if we need to re-install. Some details are:
- firstname.lastname@example.org received a welcome email with a temporary password.
- @Dermot did a default install, logged into the system with the temporary password and created a new password
- The laser settings were fetched from the laser itself (or possibly from JobControl)
- The current JobControl material database was imported
Once this document is private, add the password here
4.1 Configure password
- @Brendon_Hatcher used the email address and temporary password (provided by Dermot) to login
- @Brendon_Hatcher changed the password to the one shared with the lasertechs
4.2 Enable remote access
@Brendon_Hatcher enabled remote access (which actually means access from other devices on the same local network). This only has to be done once, unless we need to re-install.
- Start / Ruby
- Login to Ruby as an administrator
- Menu button (top left)
- User management
- Download the certificate
- In Windows File Explorer, go to Downloads and double click on the file
- Install certificate
- Local machine
5. Materials database management
- The existing JobControl Material Database was imported during Ruby installation.
- Any cleanup planned for JobControl will (probably) have to be done on Ruby as well.
Brendon proposes the following materials database structure:
- Each material database entry is entered as Materialname - thickness (e.g. Ply - 6mm)
- The first tag entered is the category (e.g. Wood)
- The second tag entered is the effects that the entry has - e.g. Cut, Engrave
- The third tag is the name of the “owner” - e.g. @SLMS or @ Brendon_Hatcher
The tags have the benefit of keeping the names short, and the tags are searchable at the same time as searching for the name.
I have made a default material that does nothing, but prompts users to choose a different material.
There is an import/export process for materials, but I can’t see a way in which this will actually be useful. We can discuss.
Import is an XML or TLM file
Export is a binary file in TLM format (not easily editable)
There are access control levels for the materials database, but they are not granular enough.
- Users with restricted rights can modify material settings for a job, but cannot overwrite the settings or make their own
- Users with “materials” rights have the ability to save modified material settings as new entries, or overwrite the originals. We would have to tell them about the rules for saving and overwriting.
- All members can see and edit each other’s settings unless they have restricted rights.
6. User administration
- It seems like only admin users can add new users (@Brendon_Hatcher can’t see any indication of a bulk import procedure).
- Any user can be given administrator rights (16/12/21 - @Brendon_Hatcher this is untested)
6.2 Privacy issue
Lasertechs will need member’s email addresses in order to set them up as the login credentials are sent to the user’s email address. We will need an appropriate way to obtain, use and dispose of this personal data.
6.3 Create new user
- Login as Director/other administrator
- Menu button (top left)
- User management
- Add user
- Email address (match to SLMS-recorded email address)
- Username (match to SLMS username)
- Quickly copy temporary password (if the new user wants to login immediately, and doesn’t have access to their email account)
- Assign administrator permission - lasertechs and directors???
- Materials - y/n - need to explore this setting
7. Proposal: Remote access to the laser PC
No longer needed since we can install a copy on our own laptops.
- Configure/tidy up Ruby and Job Control
- Add new users (since there is no mass-import function)
- Support users with technical issues (especially during the transition to Ruby)
8. Software updates
- Ruby will prompt you to do software updates (only if you are logged in as superadmin?)
- The release notes are here: https://www.rubyhelp.com/article-categories/release-notes/
9. Installing Ruby on your own PC
You do not need to do this for remote access when you are in the Maker Space (see instructions above).
Installing the software creates a completely separate instance.
It is only useful for learning and testing in a sandbox, safe from any accidental changes to the live system on the Laser PC in the makerspace.
1. Obtain installation file
- Go to https://www.troteclaser.com/en-gb/laser-machines/laser-software
- Press the Download Ruby button
- Run the installer
3. First use
- Run the Ruby app
- Login using email@example.com (password from Brendon until this page is secure)
Note: This is not the same password as on the Laser PC at SLMS.
- Create a new password – this is specific to your PC, and won’t sync or change the laser PC at SLMS
Import the settings file:
Download this file: S3-1139.zip
Go to the Windows Notification tray / Ruby / Import configuration / From file
Import the materials database
For now this is the fairly useless one provided by Trotec (it is missing most of the materials we use).
I’ll update this page with a more useful one as I make it.
Download this file: Speedy300-85W.zip
Open Ruby web interface
Login as director
3-bar button / Materials
3-dot button / Import from file
Create a “normal user” so that you can see Ruby as everyday users would see it
Brendon is still working on the options, and the techs will have to decide what access rights we give.