Activity for Ingo

  • Ingo Ingo committed [r2] on Code

    test

  • Ingo Ingo committed [r1] on Code

    test

  • Ingo Ingo modified a wiki page

    IndexMain

  • Ingo Ingo modified a blog post

    Add own log messages

  • Ingo Ingo modified a blog post

    Add own log messages

  • Ingo Ingo posted a comment on a wiki page

    Hi Alimans, thanks for the feedback! 1) To debug, you can easily set the compiler define "IoConfigLateInit". That will instruct our device object to execute the Init code of your driver in the first Task-Cycle. This way, you can easily set a breakpoint in your library and debug it. 2) Which pages to you mean in detail? Most of them are just coming from specific configurator plugins. So when you see the configuration pages in EtherCAT or Profinet or s.th., those are developed specifically for this...

  • Ingo Ingo modified a wiki page

    Startpage

  • Ingo Ingo modified a wiki page

    Home

  • Ingo Ingo modified ticket #21

    update project information

  • Ingo Ingo posted a comment on discussion Runtime πŸ‡¬πŸ‡§

    Hi all! Let's give you a bit more background why this issue is hanging around for so long. First, lets try to devide and conquer. Actually we are talking about two issues: 64Bit kernel, which comes with an update automatically 64Bit user land, which you get, when you choose "Raspberry Pi OS (64-bit)" 64Bit kernel 64Bit linux kernels are AFAIK always compatible with 32Bit. So you are able to mix you user land with 64Bit and 32Bit programs. The only thing you usually need, are all libraries, which...

  • Ingo Ingo modified ticket #16

    codesys ide docker image

  • Ingo Ingo posted a comment on ticket #16

    Hi Orby, sadly that's not easily possible. You are only allowed to build such an image, when you own a windows license. These are the license terms of DotNet. Cheers, Ingo

  • Ingo Ingo posted a comment on discussion Runtime πŸ‡¬πŸ‡§

    That's right. Investigations on the licensing concept are ongoing. So other options (at least network licenses) will be possible soon. simonbysmal no-reply@codesys.com schrieb am Mo., 27. MΓ€rz 2023, 09:52: Solved (ish) The documentation does not mention that this is not possible. At least as of now, licensing the runtime is only possible using a codesys dongle when the runtime is running in docker! Soft Container missing? ARM 64 SL (Docker) https://forge.codesys.com/forge/talk/Runtime/thread/698b118dfe/?limit=25#9096...

  • Ingo Ingo posted a comment on discussion Runtime πŸ‡¬πŸ‡§

    Hi Ketchup ;) Technically, you are creating a library, which is loaded by Linux. So there is technically no such limitation. But practically you have to have a deep understanding of C and C++ to master the binding between them. The starting point is: Create one object, which implements the C interface, that is used by CODESYS. Then you create an interface header, which contains C interfaces, sourounded by eytern "C" statements. This interface can then be used, and called from the C wrapper, and builds...

  • Ingo Ingo posted a comment on discussion Runtime πŸ‡¬πŸ‡§

    I don't know your driver. But the GPIO open error sounds suspicious. Otherwise I can say, that there is no real difference between a BBB and another runtime. When you registered your driver handle (IBase) in UpdateConfiguration correctly, and you used the channels in your project (check device->Task Deployment to be sure), your ReadInput/WriteOutput functions should be called.

  • Ingo Ingo posted a comment on ticket #8

    Hi Paula! That should be as easy, as changing the URL in install2.sh. The variable is called CDS_LINK, and it contains the SP16 version number. I didn't test it with SP11, but guess it should simply work...

  • Ingo Ingo modified a blog post

    Searching Forge

  • Ingo Ingo created a blog post

    Searching Forge

  • Ingo Ingo posted a comment on discussion Runtime πŸ‡¬πŸ‡§

    Hi @mondinmr, thanks again for this nice summary about realtime optimizations! And also thanks for the outlook regarding the Rasperry Pi 4. Looking forward to hear from that. Hint: If you post the Raspberry Pi results in CODESYS Talk, maybe use a different topic for RPI. Then it will be easier found. Don't know if you found this already, but from CODESYS there is an FAQ, giving some optimization hints: https://faq.codesys.com/pages/viewpage.action?pageId=122748972 And soon, there will be a new chapter...

  • Ingo Ingo posted a comment on discussion Forge πŸ‡¬πŸ‡§

    The only problem is the new installer. I didn't find a stable way, yet to install it. When installed, everything runs fine. But you might have noticed, the automation of the setup of wine and CODESYS in Docker is quite tricky. πŸ˜‰

  • Ingo Ingo modified ticket #6

    Error while building project

  • Ingo Ingo posted a comment on ticket #6

    Thanks for diving into the rabbit whole. πŸ˜‰ I now improved the error reporting and stability of build-bootapp. Hint: You can call it like this, from the folder of your *.project file... docker run -v $(pwd):$(pwd) -w $(pwd) codesys-ide codesys build-bootapp

  • Ingo Ingo modified ticket #161

    Dimension numeric keypad font

  • Ingo Ingo posted a comment on ticket #161

    Sorry, but you may ask this question in CODESYS Talk

  • Ingo Ingo modified ticket #170

    CoDesys not opening

  • Ingo Ingo posted a comment on ticket #170

    Sorry, but seems like you reached the wrong place. You might find an answer on CODESYS Talk.

  • Ingo Ingo modified ticket #169

    Installing Problem

  • Ingo Ingo posted a comment on ticket #169

    Hi @nezirsss, Unfortunately you reached the wrong spot. This is the support page for the CODESYS Forge platform, not the CODESYS product itself. You may ask your question to the community on CODESYS Talk, or you use the "My Question" form on CODESYS Store to reach our support.

  • Ingo Ingo modified ticket #168

    NBS Library to eth1

  • Ingo Ingo posted a comment on ticket #168

    Hallo Florian, das war leider nicht genau der richtige Ort. Dies ist der Support Bereich für CODESYS Forge, die Open Source Community von CODESYS. Du kannst deine Frage gerne an die Community in CODESYS Talk richten, oder dich alternativ über Meine Frage im Store, an unseren Support wenden. Grüße, Ingo

  • Ingo Ingo modified ticket #165

    Gateway wont start. Win10 Pro xc152

  • Ingo Ingo posted a comment on ticket #165

    Sorry for the late answer @josephm. But I expect you wanted to ask this question in CODESYS Talk

  • Ingo Ingo modified ticket #166

    https://help.codesys.com/ VS https://helpme-codesys.com/

  • Ingo Ingo posted a comment on ticket #166

    Thanks for the pointer! Actually I updated it to the new one. The other thing might be more confusing.

  • Ingo Ingo modified ticket #167

    Network Variables communication protocol is needed

  • Ingo Ingo posted a comment on ticket #167

    Hi @allprimo, and welcome. Unfortunately you hit the wrong place. You may ask this question in CODESYS Talk

  • Ingo Ingo posted a comment on discussion Forge πŸ‡¬πŸ‡§

    Hi @mondinmr , you got me curious. I'm wondering: How did you install SP18? Did you manage it with the installer, or did you use the install2.sh script, or ... ? Cheers, Ingo

  • Ingo Ingo posted a comment on discussion Forge πŸ‡¬πŸ‡§

    Hi! I already encountered the same issue in a different context. The problem occurs also when you try to run the simulation, or connect to a PLC with encrypted communication. I assume it is a bigger task, but I believe the clean solution is to implement ncrypt in wine. Googling for it, turned out, that there was a fix in this region recently: https://www.winehq.org/announce/7.3 The microsoft installer was the driving force for that. Maybe you want to try this new wine version? I am already very curious,...

  • Ingo Ingo modified ticket #160

    Login via Browser SAML error message !

  • Ingo Ingo posted a comment on ticket #160

    This was a temporary issue, and should be solved

  • Ingo Ingo modified ticket #163

    SAML Error on LogOn, no actions possile

  • Ingo Ingo modified ticket #156

    SAML error

  • Ingo Ingo modified ticket #157

    LOG IN -> SAML Authorization failed

  • Ingo Ingo modified ticket #159

    login -> Authorization failed

  • Ingo Ingo posted a comment on ticket #159

    This was a temporary issue, and should be solved now

  • Ingo Ingo modified ticket #162

    Can't log into Forge SAML Error

  • Ingo Ingo posted a comment on ticket #162

    This was a temporary issue, and should be solved.

  • Ingo Ingo modified ticket #164

    EtherCAT eeprom imaging with ESI (.xml) file using codesys

  • Ingo Ingo posted a comment on ticket #164

    Sorry, seems like you reached the wrong place. You may want to ask this question in CODESYS Talk

  • Ingo Ingo posted a comment on ticket #154

    What do you think about this project? https://github.com/dom111/webdav-js You can try it as a bookmarklet. And it looks great to me. Thus it doesn't support a file editor. But it enables you to easily upload / download stuff. My question is: What is more important? Editing files via a native HTML editor, or upload / download. You can try it out easily with the provided "bookmarklet", and visiting your webdav URL. e.g.: https://forge.codesys.com/svn/lib,counit,code/trunk/

  • Ingo Ingo modified ticket #151

    Git staging not working as expected

  • Ingo Ingo modified ticket #153

    Socket remains active on Raspbian OS after stopping / starting the controller

  • Ingo Ingo modified ticket #153

    Socket remains active on Raspbian OS after stopping / starting the controller

  • Ingo Ingo posted a comment on ticket #153

    Hi! Unfortunately you asked this question in the wrong place. This is the support ticket system for the CODEYS Forge web page. You may want to ask this question in CODESYS Talk

  • Ingo Ingo modified ticket #155

    Where are my artefacts after a succesful build?

  • Ingo Ingo posted a comment on ticket #155

    Hi Aliazzz, there was a permission problem, which prevented the artifacts to be written to the correct place, when there was already a folder in that place. This bug should be fixed. And now, the artifacts, will be available under /download/<repo-name>/...</repo-name> For example: https://forge.codesys.com/download/drv,d-logg,code/trunk/d-logg.package This is the artifact, which was written to ".drone-artifacts/trunk/d-logg.package" in the repo "drv,d-logg,code".

  • Ingo Ingo posted a comment on discussion Runtime πŸ‡¬πŸ‡§

    Maybe I can explain the mysterium about the scheduler interval: It is an interval, in which the scheduler checks all IEC task watchdogs, as well as the processorload watchdog. The IEC task watchdog is what you define in the taskconfiguration in CODESYS. And when you increase this value in the. config file, your system will react later on a watchdog event. The interval of the processoload watchdog can't be lower than the scheduler interval (at least it would not make much sense), because it is the...

  • Ingo Ingo modified ticket #21

    update project information

  • Ingo Ingo posted a comment on ticket #21

    Hi Aliazzz, thanks a lot! I did myself not know how to customize the project information. But what was the future import good for? it doesn't seem to be used anywhere.

  • Ingo Ingo posted a comment on discussion Runtime πŸ‡¬πŸ‡§

    Merry christmas! The screenshot says, that everything is OK, and that the runtime was started. Sounds good to me πŸ˜‰

  • Ingo Ingo posted a comment on discussion Runtime πŸ‡¬πŸ‡§

    Hehe, sounds great! One of the "tricks" in our setup is currently, that we use "isolcpus", and start the runtime without multicore support, bound to one of the isolated cores. So this core is free of any interrupts. Only some rare kernel locks are producing some slight jitter.

  • Ingo Ingo modified a blog post

    Licenses of projects

  • Ingo Ingo posted a review comment

    Test

  • Ingo Ingo posted a comment on discussion Runtime πŸ‡¬πŸ‡§

    Thanks a lot for your feedback. I will forward it to the team. An additional information: We are working on a students project to analyze the realtime performance on Kubernetes. On the testsystem, we got a maximal Jitter below 10us. This is achieved with several tweaks of the system, and by making heavy use of multicore. Its very impressive what's possible with a current realtime kernel!

  • Ingo Ingo committed [0620e3]

    Added workaround to use a central license server.

  • Ingo Ingo committed [r27]

    avoid download, when packages are already there

  • Ingo Ingo posted a comment on discussion Runtime πŸ‡¬πŸ‡§

    It depends a bit of the card that is used. Currently you can configure the runtime to use a fix memory mapped NVRAM, when the memory is mapped to a fix address, and behaves similar to a normal RAM. check this post: https://forge.codesys.com/forge/talk/Runtime/thread/170a3edf96/#519d

1 >