Hi,
This post will explain how to migrate your existing dEX program written with the flash player version of dEX to dEX 2.0.
If the program (written in the old dEX) already in the logger, dEX 2.0 can convert it straight away if there is no manual channels (i.e.: MODBUS channels) and/ or alarms declaration.
However if you have manual channels and/ or alarm declaration, you will find "dxc compilation error" when attempting the conversion.
This post will also address to users who have dEX file in their computer and currently want to use it.
The first step would be extraction of your old program.
While the old dEX uses XML format to populate the interface, dEX 2.0 uses DXC format which is similar to text program.
Please note:
- The old dEX although it uses XML format there is DXC format saved in the logger.
- dEX 2.0 uses a full syntax rather than the short one which we normally use (people who familiar with text program will understand this).
There are 3 methods to extract the text program:
If the old program already in the logger, you can try to use DeTransfer and send SHOWPROG to get the program. Copy and paste it to a notepad and give any name with DXC extension.
The same situation as before, but different solution. You can also try to access dataTaker FTP server, go to USER folder and extract config.dxc file.
If dex file is stored in your PC and you want to use it on dEX 2.0 then you have to extract it into text version. Unfortunately the only solution would be dEX 1.0 (or commonly known as dEX for desktop). I do not recommend using dEX 1.0 for prolong time other than extracting text version of the program due to change of ownership from Adobe to Harman..
The third option requires installation of Adobe Air (I put 2 version since I am not sure which one will work, try with version 25 first) and dEX for desktop application.
You can use any Adobe Air version and the dEX 1.0 from this link:
https://datatakerforum.com/Documents/Applications/dex_416_code1_desktop.air
The second step would be modification of your dxc program if you have manual channels or alarm channels.
This is one example of text program extracted from the old dEX:
BEGIN"config"
' Generated by dEX Configuration Builder Version 1.85.002 (Firmware Version 9.22.9125)
' Target device: DT85M3-4
password=""
RS1S
RA"Schedule_1"("b:",ALARMS:OV:100KB:W60,DATA:OV:1MB)5M
LOGONA
ALARM1(1V("Voltage_1~mV",=1001CV,LM,NA)<5)"Event triggered on Logger ! at @ on #, ?N value is ?V ?U."{}
' User defined
1MODBUS(AD1,R4:1001,MBF);
END
Alarm section
In dEX 2.0, alarm is no longer part of a channel but it is now a separate channel therefore it is possible for you to have multiple condition at once. This is a complete opposite with the previous dEX.
ALARM1(1V("Voltage_1~mV",=1001CV,LM,NA)<5)"Event triggered on Logger ! at @ on #, ?N value is ?V ?U."{}
In the old dEX, as you can see in the above example channel was becoming channel option for alarm. Alarm was taking the main role.
You can modify the above alarm by splitting channel and alarm, grab the entire channel 1V("Voltage_1~mV",=1001CV,LM,NA) and put it as a new line above the alarm channel, then in the original location replace the channel with CV which is 1001CV.
1V("Voltage_1~mV",=1001CV,LM,NA)
ALARM1(1001CV<5)"Event triggered on Logger ! at @ on #, ?N value is ?V ?U."{}
Manual channel section
You can modify the manual channel as follows, make sure there is no space before 'Manual declaration enclosing the content.
Original syntax:
' User defined
1MODBUS(AD1,R4:1001,MBF);
Modified syntax:
'Manual "Manual"{
1MODBUS(AD1,R4:1001,MBF)
'Manual}
After addressing those two components save the dxc file and you can upload it into dEX 2.0.
Troubleshooting
If you have any issue, you can enable dEX 2.0 diagnostic. Go to Development - Development Tools then click on Console. Try to send the program again and record the diagnostic content to a notepad before sending it to datataker.support@thermofisher.com.
Thank you.
Best regards,
Rudy Gunawan
Hi,
This post will explain how to migrate your existing dEX program written with the flash player version of dEX to dEX 2.0.
If the program (written in the old dEX) already in the logger, dEX 2.0 can convert it straight away if there is no manual channels (i.e.: MODBUS channels) and/ or alarms declaration.
However if you have manual channels and/ or alarm declaration, you will find "dxc compilation error" when attempting the conversion.
This post will also address to users who have dEX file in their computer and currently want to use it.
**The first step would be extraction of your old program.**
While the old dEX uses XML format to populate the interface, dEX 2.0 uses DXC format which is similar to text program.
Please note:
- The old dEX although it uses XML format there is DXC format saved in the logger.
- dEX 2.0 uses a full syntax rather than the short one which we normally use (people who familiar with text program will understand this).
There are 3 methods to extract the text program:
- If the old program already in the logger, you can try to use DeTransfer and send SHOWPROG to get the program. Copy and paste it to a notepad and give any name with DXC extension.

- The same situation as before, but different solution. You can also try to access dataTaker FTP server, go to USER folder and extract config.dxc file.

- If dex file is stored in your PC and you want to use it on dEX 2.0 then you have to extract it into text version. Unfortunately the only solution would be dEX 1.0 (or commonly known as dEX for desktop). I do not recommend using dEX 1.0 for prolong time other than extracting text version of the program due to change of ownership from Adobe to Harman..
The third option requires installation of Adobe Air (I put 2 version since I am not sure which one will work, try with version 25 first) and dEX for desktop application.
You can use any Adobe Air version and the dEX 1.0 from this link:
https://datatakerforum.com/Documents/Applications/dex_416_code1_desktop.air
**The second step would be modification of your dxc program if you have manual channels or alarm channels.**
This is one example of text program extracted from the old dEX:
````
BEGIN"config"
' Generated by dEX Configuration Builder Version 1.85.002 (Firmware Version 9.22.9125)
' Target device: DT85M3-4
password=""
RS1S
RA"Schedule_1"("b:",ALARMS:OV:100KB:W60,DATA:OV:1MB)5M
LOGONA
ALARM1(1V("Voltage_1~mV",=1001CV,LM,NA)<5)"Event triggered on Logger ! at @ on #, ?N value is ?V ?U."{}
' User defined
1MODBUS(AD1,R4:1001,MBF);
END
````
Alarm section
In dEX 2.0, alarm is no longer part of a channel but it is now a separate channel therefore it is possible for you to have multiple condition at once. This is a complete opposite with the previous dEX.
````
ALARM1(1V("Voltage_1~mV",=1001CV,LM,NA)<5)"Event triggered on Logger ! at @ on #, ?N value is ?V ?U."{}
````
In the old dEX, as you can see in the above example channel was becoming channel option for alarm. Alarm was taking the main role.
You can modify the above alarm by splitting channel and alarm, grab the entire channel 1V("Voltage_1~mV",=1001CV,LM,NA) and put it as a new line above the alarm channel, then in the original location replace the channel with CV which is 1001CV.
````
1V("Voltage_1~mV",=1001CV,LM,NA)
ALARM1(1001CV<5)"Event triggered on Logger ! at @ on #, ?N value is ?V ?U."{}
````
Manual channel section
You can modify the manual channel as follows, make sure there is no space before 'Manual declaration enclosing the content.
Original syntax:
````
' User defined
1MODBUS(AD1,R4:1001,MBF);
````
Modified syntax:
````
'Manual "Manual"{
1MODBUS(AD1,R4:1001,MBF)
'Manual}
````
After addressing those two components save the dxc file and you can upload it into dEX 2.0.
**Troubleshooting**
If you have any issue, you can enable dEX 2.0 diagnostic. Go to _Development_ - _Development Tools_ then click on Console. Try to send the program again and record the diagnostic content to a notepad before sending it to datataker.support@thermofisher.com.
Thank you.
Best regards,
Rudy Gunawan