Activity for Ingo

  • Ingo Ingo committed [r79]

    updated app w/ new logo

  • Ingo Ingo modified ticket #80

    Error 500 Forking or Pushing GIT repositories

  • Ingo Ingo posted a comment on a wiki page

    Hi Ian, this is what counts for open source drivers: https://forge.codesys.com/drv/io-drivers/database/ If you use another range, or you don't register your ID, you are not safe against conflicts with deivers from others.

  • Ingo Ingo modified ticket #78

    GiIThub like workflow for PR

  • Ingo Ingo modified ticket #79

    font bug on homepage of forge.codesys.com

  • Ingo Ingo posted a comment on ticket #79

    Thanks Ian! I wonder why we didn't notice it, yet ;)

  • Ingo Ingo posted a comment on ticket #78

    Yes, the error 500 thing is s.th. else. Hard to catch but happens from time to time.

  • Ingo Ingo created ticket #21

    Future of cforge package

  • Ingo Ingo posted a comment on ticket #12

    Haha, it is a flux compensator (back to future). ;) But I think we change this after we get the App Logo from marketing. Then the direction becomes more clear.

  • Ingo Ingo modified a blog post

    User Migration from CODESYS Forum

  • Ingo Ingo modified a wiki page

    Home

  • Ingo Ingo modified ticket #76

    Raspberry PI image usernames and passwords

  • Ingo Ingo posted a comment on ticket #76

    Hi Daniele! It definitely was root:root. But actually your are not allowed to login through ssh as root. It is very common, that this is not allowed on linux. As a workaround, you can login as a user, and use su to gain root access: $> ssh wharfie@192.168.100.100 login as: wharfie password: <-- here you enter the wharfie password $> su - Password: <-- here you enter the root password Here I committed the Wharfile with which the image was built: https://forge.codesys.com/tol/wharfie/code/HEAD/tree/trunk/wharfie/examples/RaspiRT/Wharfile...

  • Ingo Ingo committed [r48]

    Added example config for the Raspberry Pi RT image.

  • Ingo Ingo posted a comment on ticket #77

    Hi Ian, great idea! The only problem I see is the responsibility. And resulting from this security concerns. The reason is, that I expect, that it makes more sense to have a global repository for forge instead of having those for each project. But if we do so, the way to publish libraries and devices needs to be defined, as well as a concept to maintain the publishing rights. As long as this concept is not set, we can't start.

  • Ingo Ingo modified a wiki page

    Markdown Syntax

  • Ingo Ingo modified a wiki page

    Markdown Syntax

  • Ingo Ingo renamed a blog post

    CODESYS Forge Android App (alpha)

  • Ingo Ingo modified ticket #17

    The button status should follow the URL

  • Ingo Ingo modified ticket #18

    Click on notification should lead to the corresponding page

  • Ingo Ingo committed [r78]

    updated cforge package

  • Ingo Ingo modified ticket #19

    Form data is lost in mobile view

  • Ingo Ingo modified ticket #19

    Form data is lost in mobile view

  • Ingo Ingo posted a comment on ticket #19

    fixed it wrote this ... pressed back button ... and clicked on this ticket again ... => Works ;)

  • Ingo Ingo committed [r77]

    updated cforge package

  • Ingo Ingo modified ticket #20

    History is wrong when back button is used

  • Ingo Ingo posted a comment on ticket #76

    No, you're right. It's root:root in the examples ;) https://forge.codesys.com/tol/wharfie/code/HEAD/tree/trunk/wharfie/examples/CODESYS/Wharfile#l16

  • Ingo Ingo created ticket #20

    History is wrong when back button is used

  • Ingo Ingo posted a comment on ticket #76

    Oh I see. The image was built with wharfie. Seems like I didn't commit the Wharfile with which it was created. I will update that soon. For the meantime: I think the password was the default, which I usually use in the wharfie examples. Thats root:wharfie and wharfie:wharfie.

  • Ingo Ingo modified ticket #73

    CfUnit API Reference keeps showing up as 'revised'

  • Ingo Ingo posted a comment on ticket #73

    Sorry for the inconvenience! Finding the root of the problem wasn't easy. Now I marked the page as deleted.

  • Ingo Ingo committed [r2]

    added cfunit test project

  • Ingo Ingo committed [r1]

    Add initial directories

  • Ingo Ingo posted a comment on a wiki page

    Looks good! Which data type is the vqriable LED? You know, that for a boolean channel, just one bit is copied. The line: pParameter^.dwDriverSpecific := ... ... is storing the address of the variable of your driver FB in the structure of the parameter. This address is then used in ReadInputs/WriteOutputs to copy the I/O data quickly there.

  • Ingo Ingo modified ticket #19

    Form data is lost in mobile view

  • Ingo Ingo created ticket #19

    Forn data is lost in mobile view

  • Ingo Ingo created ticket #18

    Click on notification should lead to the corresponding page

  • Ingo Ingo created ticket #17

    The button status should follow the URL

  • Ingo Ingo posted a comment on a wiki page

    The MCP3008 driver is doing it this way. Step 1) Implement the I/O Driver Interface. For this, the driver defines a new FB, implenting this interface: FUNCTION_BLOCK IoDrvMCP3008 EXTENDS IoDrvBase Step 2) Instantiate the driver FB in your devdesc: <RequiredLib libname="Linux SPI MCP3008" vendor="Open Source" version="1.0.0.0" identifier="deviceLib"> <FBInstance basename="$(DeviceName)" fbname="IoDrvMCP3008"> <Initialize methodName="Initialize" /> </FBInstance> </RequiredLib> Step 3) instantiate your...

  • Ingo Ingo posted a comment on a wiki page

    Your code looks good. I expect, that you are missing some init code. Did you already try "strace" on your python script? I would either try strace or a python debugger to get a better understanding of the python code. In CODESYS you can't do much wrong. Except that you might have the wrong device or frequency configured in the SPI master of your project. Especially the frequency can be important, as on some raspbian versions, the highest possible frequency was not limited correctly. Therefore you...

  • Ingo Ingo committed [r76]

    updated app w/ changes to versioning and fix in notification handling

  • Ingo Ingo posted a comment on ticket #16

    Makes fully sense. But all at its time. And all only when it's needed. So I don't think, that there is any use for a side menu with the current feature set. At the monent an info button in the bottom menu, or even built into the menu of the website makes more sense. While side swiping is desirable. But when we do it, the whole handling of histories becomes more complex. Think of, that you swipe accidently to the side. When you swipe back again, you want to be on the same page, scroll position and...

  • Ingo Ingo posted a comment on ticket #16

    Actually I prepared the notifications already. Mainly the compatible handling between Android Oreo and the versions before is a bit tricky and not working, yet. The versioning is not prepared, yet. Looking forward to the ideas of Erich ;)

  • Ingo Ingo committed [r75]

    corrected notification feed urls

  • Ingo Ingo committed [r74]

    added notification mechanism

  • Ingo Ingo posted a comment on a wiki page

    Hi Brian, I think I understand your situation a bit better now. 1) module file I would recommend to stay with one file. Modules are just additional devices, defined in the same device description file. They share virtually every possible tags with the devices, except those, which are identifying the device in the device repository. So, you can define a module parallel to the device in your device description: ... </Device> <Modules> <Module> <ModuleId>1704</ModuleId> <DeviceInfo> <Name name="localStrings:Name1704>Digital...

  • Ingo Ingo posted a comment on ticket #74

    Hi Aliazzz, you analyzed it already. But, yes a differentiated behavior is possible. Depending on the screensize maybe. Lets see...

  • Ingo Ingo committed [r73]

    fixed bug while rotating the device

  • Ingo Ingo created a blog post

    CODESYS Forge Android App (pre-alpha)

  • Ingo Ingo committed [r72]

    first alpha of the android app

  • Ingo Ingo posted a comment on a wiki page

    Did you already check the [SPI] page? Additionally you can find an SPI Template driver in the code repository.

  • Ingo Ingo modified a blog post

    Hash Tags

  • Ingo Ingo renamed a wiki page

    Feed

  • Ingo Ingo modified a wiki page

    Home

  • Ingo Ingo modified a wiki page

    Home

  • Ingo Ingo modified a wiki page

    Home

  • Ingo Ingo modified a wiki page

    Home

<< < 1 .. 7 8 9 >