News and Announcements
Migration to dEX 2.0

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.
    6001285f7aa8f

  • 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.
    600127fac3085

  • 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 [email protected]

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 &quot;dxc compilation error&quot; 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. ![6001285f7aa8f](serve/attachment&amp;path=6001285f7aa8f) - 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. ![600127fac3085](serve/attachment&amp;path=600127fac3085) - 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&quot;config&quot; &#039; Generated by dEX Configuration Builder Version 1.85.002 (Firmware Version 9.22.9125) &#039; Target device: DT85M3-4 password=&quot;&quot; RS1S RA&quot;Schedule_1&quot;(&quot;b:&quot;,ALARMS:OV:100KB:W60,DATA:OV:1MB)5M LOGONA ALARM1(1V(&quot;Voltage_1~mV&quot;,=1001CV,LM,NA)&lt;5)&quot;Event triggered on Logger ! at @ on #, ?N value is ?V ?U.&quot;{} &#039; 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(&quot;Voltage_1~mV&quot;,=1001CV,LM,NA)&lt;5)&quot;Event triggered on Logger ! at @ on #, ?N value is ?V ?U.&quot;{} ```` 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(&quot;Voltage_1~mV&quot;,=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(&quot;Voltage_1~mV&quot;,=1001CV,LM,NA) ALARM1(1001CV&lt;5)&quot;Event triggered on Logger ! at @ on #, ?N value is ?V ?U.&quot;{} ```` Manual channel section You can modify the manual channel as follows, make sure there is no space before &#039;Manual declaration enclosing the content. Original syntax: ```` &#039; User defined 1MODBUS(AD1,R4:1001,MBF); ```` Modified syntax: ```` &#039;Manual &quot;Manual&quot;{ 1MODBUS(AD1,R4:1001,MBF) &#039;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 [email protected] Thank you. Best regards, Rudy Gunawan
edited Jun 18 at 1:49 am

Hi,

Further to migration to dEX 2.0, you will need to have firmware version 9.20 as a minimum or 9.22 version. You can follow the instruction in the manual on upgrading the firmware.

Also a few users ask me about the possibility of using dEX 2.0 on series 2 logger. The answer is yes, but not all wiring arrangement will be compatible to series 2. Series 3 and 4 has an expanded wiring arrangement which became the basis of dEX 2.0. That was the reason we did not include series 2 in compatibility list in order not to add confusion to the users.

Best regards,
Rudy Gunawan

Hi, Further to migration to dEX 2.0, you will need to have firmware version 9.20 as a minimum or 9.22 version. You can follow the instruction in the manual on upgrading the firmware. Also a few users ask me about the possibility of using dEX 2.0 on series 2 logger. The answer is yes, but not all wiring arrangement will be compatible to series 2. Series 3 and 4 has an expanded wiring arrangement which became the basis of dEX 2.0. That was the reason we did not include series 2 in compatibility list in order not to add confusion to the users. Best regards, Rudy Gunawan

Hi,

There is also several request on using dEX 2.0 while running text program (not dEX version). Text program in complete version is the core of dEX 2.0.

For example:
Users who has knowledge on text program (power users) will write the program as follows:

BEGIN"TEST"
RA1M LOGONA
1V("Voltage~V")
END

That script is simple and can run as intended, but it is not a complete version. In order to make the text program compatible with dEX 2.0 you need to add more options.

BEGIN"TEST"
  password=""
RS1S
RA"Reading"("b:",ALARMS:OV:100KB:W60,DATA:OV:1MB)1M 
LOGONA
1V("Voltage~V",=1CV,NA,LM)
END

The extra line would be password and schedule S declaration, then extra option for schedule and channel.

Then what about the PROFILE setting, the PROFILE setting has become separate component to the program, at this moment you have to check the modified PROFILE from your program and apply the setting individually to the logger through SETTINGS in dEX 2.0.

There is also another option you can use by defining PROFILE setting in a manual channel, in which that channel must be declared after On Activation line.

Best regards,
Rudy Gunawan

Hi, There is also several request on using dEX 2.0 while running text program (not dEX version). Text program in complete version is the core of dEX 2.0. For example: Users who has knowledge on text program (power users) will write the program as follows: ```` BEGIN&quot;TEST&quot; RA1M LOGONA 1V(&quot;Voltage~V&quot;) END ```` That script is simple and can run as intended, but it is not a complete version. In order to make the text program compatible with dEX 2.0 you need to add more options. ```` BEGIN&quot;TEST&quot; password=&quot;&quot; RS1S RA&quot;Reading&quot;(&quot;b:&quot;,ALARMS:OV:100KB:W60,DATA:OV:1MB)1M LOGONA 1V(&quot;Voltage~V&quot;,=1CV,NA,LM) END ```` The extra line would be password and schedule S declaration, then extra option for schedule and channel. Then what about the PROFILE setting, the PROFILE setting has become separate component to the program, at this moment you have to check the modified PROFILE from your program and apply the setting individually to the logger through **SETTINGS** in dEX 2.0. There is also another option you can use by defining PROFILE setting in a manual channel, in which that channel must be declared after **On Activation** line. Best regards, Rudy Gunawan

Rudy,
Will the new version of Dex be more capable like the version on the logger, will it be able to handle multiple lines of text commands like Detransfer?
Can it connect through wifi?

Rudy, Will the new version of Dex be more capable like the version on the logger, will it be able to handle multiple lines of text commands like Detransfer? Can it connect through wifi?
edited Feb 18 at 7:51 pm

Dear Rudy,
I have to use dEX 1.0 / dEX for Desktop for one project and I followed your instruction:

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 Installation of Adobe Air was no problem (I tried two different versions 25 and 32) but after doubleclicking "dex_416_code1_desktop.air" I got an error from Adobe Air saying "The application could not be installed because the installation file is damaged. Ask the application author for a new installation file".

Please can you help me with that?

Thank you.

Kind regards Matthias

Dear Rudy, I have to use dEX 1.0 / dEX for Desktop for one project and I followed your instruction: &gt; 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 Installation of Adobe Air was no problem (I tried two different versions 25 and 32) but after doubleclicking &quot;dex_416_code1_desktop.air&quot; I got an error from Adobe Air saying &quot;The application could not be installed because the installation file is damaged. Ask the application author for a new installation file&quot;. Please can you help me with that? Thank you. Kind regards Matthias
1.36k
4
4
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft