Embedded Files
September 2012
A user configurable dashboard for a simple Human Machine Interface to your Mitsubishi FX Ethernet/Serial or Alpha2 based Home Automation or Commercial Control System.
Note! The original Desktop.DASH is an app with just Mitsubishi FX Ethernet, FX Serial and Alpha2 drivers built-in. Version 2 has new features and with MODBUS Ethernet and MODBUS Serial drivers added to the Mitsubishi drivers. Single one time low cost license after enjoying an extended trial period!
Desktop.Dash - A simple desktop interface to your Mitsubishi PLC
Help Sections
Getting Started (this page)
Windows OS and Mitsubishi Hardware*
Desktop.DASH has been tested to operate on Windows 10 (32 & 64 Bit), 7 and Xp.
The Desktop.DASH drivers communicate via the various Mitsubishi supplied and supported user interfaces only - (Note: None of the XML Control drivers will work with the PLC in-built programming ports!).
For MC Protocol you'll require a FX3U-ENET or ADP-ENET module on your FX Series PLC
For FX Serial Protocol you'll require a RS-232 or RS-485 module on your FX Series PLC
For Alpha2 Protocol you'll require the AL2-CAB-GSM adapter which will only fit into an AL2-14 or AL2-24 device
Version 2 additions...
For MODBUS Ethernet Protocol you'll require a FX3U-ENET**(or-P502) module on your FX Series PLC
For MODBUS Serial Protocol you'll require a RS-232 or RS-485 module on your FX Series PLC
*At the time of initial writing, this app was built around Alpha2 and FX3G hardware. Since then, new hardware such as FX5 and FX3UJ have been introduced, and whilst not tested, such equipment may also work if the protocols, such as MC Protocol and MODBUS, are supported in them.
Update April 2022! FX5U has been tested with MC Protocol over TCP and MODBUS/TCP successfully. (For MC Protocol you'll need to configure a SLMP connection in the FX5U), and here is an example how-to... Blog: FX5U, SLMP & Desktop.Dash
**If using an FX3U-ENET you cannot set Port 502 (the default Modbus Port), though you may set any port above 1024, and DASH will work Ok. If you really need to use Port 502 then you'll need the FX3U-ENET-P502 module.
And finally, all the above interfaces will require some configuration with the relevant Mitsubishi software programming tools before they will work.
Getting Started
Watch a short introductory video... DASH Introduction
Desktop.DASH does require careful setup, so please follow these instructions in the order shown. Double-click DesktopDash.exe or it's short-cut to start the application...
Empty dashboard after first start up; ready for some gadgets
Set A Project Folder Path
From the main menu choose File > Save. Nothing happens? Correct, there is nothing to save! You get to save when you have some work done.
By default Auto-Save is enabled from the Admin menu; so you will be prompted to save to a project folder in due course anyway.
Auto-Save by default
Configure Basic Options
From the Admin menu choose Options...
Options Dialogue System TAB
Firstly, choose a MAC Address from the list. This helps in the validation of the host PC (as used by the Instant Messenger client.)
Choose MAC Address
Next, choose your required Mitsubishi type communication protocol driver and select a Polling interval in Milli-Seconds...
Choose Mitsubishi Protocol Driver
Driver Notes
Each driver has known characteristics and limitations. Whilst Desktop.DASH was specifically developed for Ethernet communications, legacy support is provided for FX and Alpha2 over Serial as well. Though be aware that these serial communications are sluggish.
The Ethernet option is fast and very responsive though; and your preferred route if starting out with a clean sheet control system design. Some points...
Regardless of how you subsequently configure devices on your dashboard - only ONE driver can ever operate
The driver can only talk to ONE PLC device, as configured...
1. MC Protocol talks to a FX Series PLC or via an ENET module. Stores available are: X, Y, M, D, W (D * 32 Bit), F (D * Float 32), R, S, T and C
2. FX / Serial talks to a FX Series PLC via a Serial module. Stores available are only: X, Y, M, D
3. Alpha2 talks to an Alpha2 via the CAB-GSM adapter. Stores available are: AI, DI, XI, EI, SI, DO, XO, EO, SO, CB and CW (Explain this? See Alpha Stores)
For MODBUS we've simply remapped X, Y, D etc to the equivalent Input Registers, Holding Registers, etc...
4. MODBUS/TCP over Ethernet in Master Station Mode. Stores available are: X, M, D, W (D * 32 Bit), F (D * Float 32) only
5. MODBUS Serial over RS-232/485 in Master Station Mode. Stores available are: X, M, D, W (D * 32 Bit), F (D * Float 32) only
The Polling Interval is the time to wait between device reads and writes. It improves value display stability only - use as required
Graphics Display
Next, skip the Data-Logging and I-Messenger TABs and hit the Display TAB. We need to do one thing...
Display TAB
When we start to configure objects on the dashboard, like lamps and buttons, there is a border which we can show or hide, and it's width cannot be readily determined.
For this reason the Graphics Fudge values can be manually adjusted to suit your OS set up, but for now press [Xp] or [Win7] to get starting point best guess values.
Finally, press the [Ok] button on the Options dialogue, and now you will be prompted to choose a folder path.
Note
Projects are saved to a folder, not a file. When you select your required folder it will be populated with all relevant project resources, which will include a config.dash file, which of course is a plain vanilla XML file, and all images, HTML, PDF files that become part of your dashboard solution. A couple of sub folders will be created as required, one for ERROR-LOG files and one for DATA-LOG files.
The dashboard title bar will now display the current project path...
Title Bar Displays Project Path
In the next section we will look at configuring and testing the target PLC connection.
Page updated
Google Sites
Report abuse