I'm afraid I'm not making much progress on the 3S forums. So you lot are going to get pestered now!
I'm using 3S Codesys v2.3
I'm trying to create a boot project and do sourcecode download on my build server and I'd like to avoid having any hardware plugged into it. I'm using the following command line to run Codesys:
Build.bat:
"C:\Program Files\3S Software\CoDeSys V2.3\Codesys.exe" OptimusPlcFirmware.pro /cmd Build.cmd /batch
Build.cmd:
echo on
online sim off
project rebuild
online bootproject
online sim
online login
online sourcecodedownload
online logout
online sim off
When I do this I get the windows "has encountered a problem and needs to close, with accompanying Send Error Report / Don't Send buttons"
The boot project has been created succesfully and the sourcecode all seems correct. Can anyone explain what's happening?
Thanks
Matt
I run Twincat 2.11 here which is based on CoDeSys 2.3 but may be my idea can be useful. You cannot go Online (Login) until target (your local runtime as well) is in Running mode. Probably your local runtime is in Config mode and thus doesn't accept login and program download. Switch it to Running and try to run your script again.
Taras
I've tested with CoDeSys 2.3.9.13 and I have a similar issue. It seems that the problem comes from the online sourcecodedownload command.
I didn't know if it is valid to download the source code in the PLC in simulation mode. It looks strange to me. In any case, even if it's not possible it shouldn't crash.
I hope it helps
Related
I am currently in the process of exploring the possible use of VS Code Server on Sagemaker Studio. Of course, if you sign up through Code Server preview, I was able to set and start it up. However, when I tried to serve it locally, I encountered a blank page after modifying the /default/proxy/XXX part of the url like how we access tensorboard.
Just wondering on whether are there any tinkerers out there that managed to get it working? (and yes, I understand that somebody managed to get it running https://coder.com/docs/code-server/latest/CONTRIBUTING. but wondering whether anybody managed to use the native installation to work properly? Any possible steps that i may be missing?
Check out the blog post here for hosting code-server on SageMaker Studio - https://aws.amazon.com/blogs/machine-learning/host-code-server-on-amazon-sagemaker/
And associated git repo here - https://github.com/aws-samples/amazon-sagemaker-codeserver
I have created a shiny app on my computer that runs with no error. Now, I deployed the same app to the shiny server we have in our organization, and i cannot initiate the app. I receive the following error message:
transpose listening on http://127.0.0.1:43202
Warning: Error in tabPanel: argument "tabName" is missing, with no default
65: tabPanel
Execution halted
here are my questions:
(1) I do use shinydashboard and shinydashboardplus libraries in my app and both are installed on the shiny server as well so this shouldnt be a problem since tabsetPanel and tabPanel are in these libraries, correct?
(2) tabPanel and tabSetPanel do NOT have a tabName argument. so what is this error specially because the app does work on my computer with no issue.
I know probably I need to provide the code but I cannot at the moment unless i significantly take stuff out of it (government property) but I was hoping someone can help considering the fact that it works on my computer but it doesnt when i deploy it.
Just a quick note that the R version installed on my laptop is 3.5.2 but the one on the server is 3.6! can this be an issue?
Thanks!
I think a library bs4Dash was masking tabSetPanel which is quite confusing because i didnt have that problem running the app on my laptop...
So today, whenever I try to sign My Blackberry app using the WebWorks packager, I get this error...
"General failure. Please try again. Server may be unavailable".
My proxy settings have not changed and I have been using the same command line instruction with success before.
I've also checked the status of the Blackberry signing server using the following link...
http://isthesigningserverdown.com/chart/index.php?sigType=RBB or RCR or RRT
And everything appears to be online!
So, where could I be going wrong? Here's the command line instruction I've been using. First, I navigate to my Blackberry build folder and run the following instruction against it...
bbwp appname.zip –g <password> –o z:\projects\appname\signed
It goes through through parsing the various elements. The signing tool pops up and then the error is generated.
So, after a couple of days of banging my head against the wall-the answer finally came to me. I'm on a MAC but am also using a Windows virtual machine for Blackberry developement, which is running on another network altogether and this specific network is using a firewall, which, according to the network administrator, is currently experiencing a severe technical problem.
The way round it was to sign my Blackberry app using configured proxy settings to communicate with the signing server and viola! It worked!
One of my projects requires that a COM server be registered on the build machine. My first (and only) lame attempt was a simple pre-build step, but I assumed that would not work in the cloud, and I was correct. Problem is, I need to use this component, I only have a binary, and I'm a bit stumped as to what to do.
The error message is predictable:
The command "regsvr32 /s "path_to_dll" exited with code 5. Please verify that you have sufficient rights to run this command.
TFS Azure is in preview at the moment, so I'm not sure how many people have experience with it yet. I posted the same question on the official forums and have not yet received a response. Searching did not help either.
Silly me, just need to reference the interop assembly instead of directly referencing the native DLL. Problem solved.
I am trying several examples from the forum, most of the samples are not in my phone but are unable to be installed via the B4ABridge even it says it is connected. How can this be fixed?
this is what it says:
Installing file to device. 0.20
Installing with B4A-Bridge.
Installation will fail if the signing key is different than the previous used key.
In that case you will need to manually uninstall the existing application.
Completed successfully.
regards
First check if other features work. For example, can you see the logs?
Make sure that you allowed installation of non-market applications.