11-04-2020, 07:16 AM | #1 |
Lieutenant Colonel
1044
Rep 1,943
Posts |
Which version of Esys is everyone using for coding
I have both 3.27.01 (32 bit) and 3.34.00 (64 bit) installed on my machine. I'm using Esys-X to code and I seem to prefer 3.27.01, but something about not using the latest possible version nags at me. It seems Esys-X plays nicers with 3.27.01 than it does 3.34.00. For example, you can edit the NCD file directly from the coding tab on 3.27.01. On 3.34.00 it gives me an error so I have to go the FDL editor and edit it that way. Not a huge deal, just 2 added clicks that I otherwise don't have to do on 3.27.01. Curious what everyone elses thoughts were on this.
|
11-04-2020, 08:45 AM | #2 |
Lieutenant Colonel
1197
Rep 1,587
Posts |
I use 3.35.3 and previously 3.34.0.
Are you sure you have configured esysx correctly with the 3.34.0 64-bit version? I don't experience an issue editing fdl directly from Coding. |
Appreciate
0
|
11-04-2020, 10:51 AM | #4 | |
Lieutenant Colonel
1197
Rep 1,587
Posts |
Quote:
I have the option, 'Edit NCD', not 'Edit FDL' That's not the normal behaviour of 3.34 with esysx so its something environmental in your setup. |
|
Appreciate
0
|
11-04-2020, 11:09 AM | #5 | |
Lieutenant Colonel
1044
Rep 1,943
Posts |
Quote:
I do have a custom path b/c I have both 3.27.1 installed and 3.34.0 installed. Surely that can't be the issue. |
|
Appreciate
0
|
11-04-2020, 11:15 AM | #6 | |
Lieutenant Colonel
1197
Rep 1,587
Posts |
Quote:
I'd take everything off including launcher pro if you have it, then reinstall esys. Maybe go for 3.35.3 while you are at it. Then install esysx, configure and save the 64bit esys path. See what happens. Only other issues ive had with esys has related to java versions. I don't have any JRE installed. I'm not an expert in getting this stuff working, but I do know yours is broken and don't cal me shirley |
|
Appreciate
0
|
11-04-2020, 01:43 PM | #7 | |
Lieutenant Colonel
1044
Rep 1,943
Posts |
Quote:
|
|
Appreciate
0
|
11-04-2020, 02:21 PM | #8 | ||
Private
35
Rep 51
Posts |
Quote:
I can upload it and share. Please check your Esysx version, support for 3.35 was added on 20/09/2020 update. |
||
Appreciate
1
VTENGR1043.50 |
11-04-2020, 02:23 PM | #9 |
Lieutenant Colonel
1044
Rep 1,943
Posts |
|
Appreciate
0
|
11-04-2020, 03:28 PM | #11 | |
Lieutenant Colonel
1044
Rep 1,943
Posts |
Quote:
|
|
Appreciate
0
|
11-04-2020, 03:38 PM | #12 | |
Lieutenant Colonel
1197
Rep 1,587
Posts |
Quote:
What happens if you just start esys, no esysx? Does Edit NCD still result in a crash or does it open the editor albeit with trimmed codes? Assumption you are using W10 2004 or 20H2 |
|
Appreciate
0
|
11-04-2020, 03:42 PM | #13 | |
Lieutenant Colonel
1044
Rep 1,943
Posts |
Quote:
Windows 10 Pro 2004 Edit - Added error details if that helps anyone. |
|
Appreciate
0
|
11-04-2020, 03:55 PM | #15 |
Lieutenant Colonel
1044
Rep 1,943
Posts |
|
Appreciate
0
|
11-04-2020, 04:02 PM | #16 | |
Lieutenant Colonel
1197
Rep 1,587
Posts |
Quote:
There seems to be quite a few reports of this error with esys versions newer than 3.27.1. No solutions just the workaround to use 3.27 or use fdl editor. What I do know is that a new build of w10 2004 or later with esys 3.34.0/3.35.3 works without issue. Just wonder if there is some issue with legacy software registration such as launcher pro / esysx versions. |
|
Appreciate
0
|
11-04-2020, 04:04 PM | #17 |
Lieutenant Colonel
1044
Rep 1,943
Posts |
Strange - I reached out to Esy-X to see if they could shed some light on it. Maybe I need to go through my registry and remove everything pertaining to esys and esys-X and start from scratch.
|
Appreciate
0
|
11-04-2020, 04:11 PM | #18 |
Lieutenant Colonel
1197
Rep 1,587
Posts |
There's a JRE folder thats installed with esys. Sometimes independant installs of JRE can cause conflicts.
What happens if you start e-sys.bat instead of exe? Sets a few paths inlcuding some java ones. |
Appreciate
0
|
11-04-2020, 04:19 PM | #19 |
Lieutenant Colonel
1044
Rep 1,943
Posts |
|
Appreciate
0
|
11-04-2020, 04:25 PM | #20 |
Lieutenant Colonel
1197
Rep 1,587
Posts |
If you have access to a virtual environment Id install a clean build of W10 and just esys 3.35.3 just for your own sanity. Confirm it works.
If you want to try uninstalling esys, just make sure the folder is completely removed in EC-apps. Also uninstall esysx, Java, and reinstall esys. then just try esys. After that it's going to need a deep-dive with log analysis which is probably not worth it. Almaretto and shawnsheridan don't seem to have identified a solution in the posts Ive seen so might be easier to rebuild, or stick with the constraints. |
Appreciate
0
|
11-04-2020, 04:28 PM | #21 | |
Lieutenant Colonel
1044
Rep 1,943
Posts |
Quote:
|
|
Appreciate
0
|
Post Reply |
Bookmarks |
Thread Tools | Search this Thread |
|
|