{"id":22557,"date":"2025-01-20T01:31:06","date_gmt":"2025-01-20T01:31:06","guid":{"rendered":"https:\/\/www.obd2tool.com\/blog\/?p=22557"},"modified":"2025-01-28T01:36:47","modified_gmt":"2025-01-28T01:36:47","slug":"creating-workspaces-in-dts-monaco","status":"publish","type":"post","link":"https:\/\/www.obd2tool.com\/blog\/creating-workspaces-in-dts-monaco\/","title":{"rendered":"Creating \u201cWorkspaces\u201d in DTS Monaco"},"content":{"rendered":"

Once you have set up a relevant Project, it\u2019s time to create a Workspace so you can start working on your van in DTS Monaco. Remember, Projects are a collection of imported SMR-d files that tells DTS Monaco how to communicate with the various ECUs, whereas Workspaces simply create a set of interfaces that allows you to perform various coding, diagnostic, and engineering tasks on your van.<\/p>\n

Go back to the main page of DTS Monaco and under the \u201cEdit\u201d mode, click the \u201cCreate a new workspace\u201d button. DTS Monaco has several templates already built-in and we\u2019re simply going to use one of those to get set up. Once set up, you can edit various aspects of your Workspace within DTS Monaco itself.<\/p>\n

\"\"<\/p>\n

Select the Project you just created and the relevant template. Press \u201cOK\u201d. The main DTS Monaco<\/a> program will open and as is always the case when you open up the program, it\u2019ll ask you if you want to \u201cPerform an ECU update\u201d. Press \u201cNo\u201d (don\u2019t worry if you accidentally press \u201cYes\u201d – it won\u2019t actually work).<\/p>\n

\"\"<\/p>\n

Welcome to DTS Monaco! Once inside the program, press \u201cSave\u201d and give your Workspace a name:<\/p>\n

\"\"<\/p>\n

You\u2019re now ready to start working on your van. But first, you need to make sure interfaces are connected.<\/p>\n

Checking Interfaces in DTS Monaco<\/strong>
\nTo ensure that DTS Monaco can correctly communicate with your van, you need to make sure that your VCI has been set up correctly. In all likelihood, you don\u2019t need to go through this, but in case you do. From the main screen of DTS Monaco, click the \u201cAdministrate and manage DTS projects\u201d button again. This time, head over to \u201cSystem settings\u201d, where you will see the \u201cInterfaces\u201d. From here, click through to the various modules and make sure your VCI is listed. If you are using the VCX SE, then you need to have the following details, which will likely be similar \/ the same for other VCIs too:<\/p>\n

\"\"<\/p>\n

The \u201ctick\u201d box is the currently active interface that\u2019s being used (\u201cVCI_SMR\u201d in my case). Note, there\u2019s also a \u201cSimulation\u201d module, which will allow you to start up DTS Monaco, play around with things, etc., without the need for an actual VCI to be connected. If you right-click on the left-hand side, you\u2019ll see a menu to update your VCI information, allowing you to see what is currently connected to your computer and what is not. In my case, that would be \u201cVCI_SMR, \u201cVCX\u201d, and \u201cSimulation\u201d. The latter will always be shown as connected, since it doesn\u2019t need actual hardware, and the reason why my computer is showing both VCI_SMR and VCX, despite me only having the VCX SE connected, is because those two have identical information. DTS Monaco can only have one VCI connected at a time, so none of this is a problem – I simply created a duplicate for the purpose of writing this guide.<\/p>\n

In the \u201cInterfaces CBF\u201d tab, also make sure that the \u201ceCOM_CBF\u201d interface has been ticked off:<\/p>\n

\"\"<\/p>\n

Once all of this has been done, you are ready to get coding in DTS Monaco itself. Get excited!<\/p>\n","protected":false},"excerpt":{"rendered":"

Once you have set up a relevant Project, it\u2019s time to create a Workspace so you can start working on<\/p>\n","protected":false},"author":1,"featured_media":22562,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[2038],"tags":[1591],"views":1883,"_links":{"self":[{"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/posts\/22557"}],"collection":[{"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/comments?post=22557"}],"version-history":[{"count":1,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/posts\/22557\/revisions"}],"predecessor-version":[{"id":22563,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/posts\/22557\/revisions\/22563"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/media\/22562"}],"wp:attachment":[{"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/media?parent=22557"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/categories?post=22557"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.obd2tool.com\/blog\/wp-json\/wp\/v2\/tags?post=22557"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}