Hi,
We have loggernet 4.3.
We can compile crbasic programs without any problem.
When we update it to 4.4 it stops compiling and it writes only "Could not Compile program" without any words.
I tried on some other PC's some of them works but some of them not.
I tried uninstall all and install again nothing changed.
When Uninstall Loggernet and install 4.3 again it is working.
I have two identical Notebook and one of them is working well but the others not.
PC has win10.
Could anyone have this problem ?
And how can I solve this problem?
regards
This is caused by the CRBasic pre-compiler crashing on a portion of CRBasic code in your program. The CRBasic pre-compiler is shipped with LoggerNet but is a seperate product that is built from the datalogger operating system code. New versions of the compiler are shipped with new operating systems. When you download a new operating system from Campbell Scientific's website, the executable not only contains a new operating system for your datalogger, but a new CRBasic pre-compiler as well.
To solve this issue, download the latest operating system from the downloads page for your datalogger. After running the executable, retry compiling your program. If it still fails, please send me a copy of your CRBasic code at gtroberts -at- campbellsci.com
We have seen two different issues in the most recent LoggerNet release related to using the precompilers.
The first is that a virus checker (in particular, F Secure) was affecting the file being able to run. There have been reports that this can be fixed by uninstalling LoggerNet, disabling the virus scanner, re-installing LoggerNet from your original disk and the 4.4 patch if needed, and then re-enabling the virus checker. I was told that you can also mark the Campbellsci directories as "safe" so that they are not checked by the virus scanner. My assumption is that you can also mark the CRBasic exe files as safe, too (though I don't use F secure).
The other instance of a problem was with non-ASCII characters in the path where the CRBasic files were stored. For instance, directory names that contained Chinese characters would cause a crash. This has been fixed in the precompilers, and the fix will be contained in the next release (when we release a new OS for the dataloggers, we also release new precompilers). The interim solution is to set up directory names that contain only ASCII characters.
Best,
Dana
Hi,
Thank you for answers.
I tried all of above but couldn't make the CRBASIC to work.
Also Reinstall the windows but nothing changed.
Then I noticed that user name includes a Turkish character. I reinstall the windows again and give a user name only includes standard English characters and it will work.
But I have another Variable changed also , I use to load loggernet 4.3 and than install 4.4 patch. But this time I install Loggernet 4.0 and then install 4.4 patch.
Now CRBASIC working well.
Regards
I Have the same problem today.... the solution:
The folder were i have the programa have a tilt in the name......... "Medición" over the o
"D:Programas/Medición"
I delete that tilt in the folder name and everithing works well again:
"D:Programas/Medicion"
Hope that help, work for me
Regards
In Spanish many words have a tilt over some letters............. probably will be good to add the tilt feature in CRBasic.......... Some times when i write explanations in the main code cant write well in spanish and cant use some leters like the " ñ " or put tilts over some words....... is not a big problem but always is good to respect the spelling in the texts and explanations
Thanks
You can add the character you are looking for by using the Tools -> Insert Symbol from the menu. Just place the curser where you want the new character to be, then enter Unicode code point 00F1 (zero, zero, F, one) into the Enter Unicode code point (xxx): field, the press the Insert at Cursor character. You can also add it to the list so you don't have to enter the code every time.
I believe the original problem of the compiler not handling non-ASCII characters in a directory path has been fixed in LoggerNet 4.4.1.
Dana W.