Search Project: *:* -title:discussion

 
1 2 3 .. 94 > >> (Page 1 of 94)

Licensing (WikiPage)
Licensing on CODESYS Forge The Apache License CODESYS Projects Incompatible licenses All Users CODESYS Account User Accounts Following others Developers Project Maintenance Landing Page Source Code Repositories Providing Downloads Ticket Tool Migrating Projects Contribution Licensing Distributing OS software Services CODESYS SVN FAQ Community Developer Community Legal Imprint / Impressum Terms of Service Privacy Policy Licensing on CODESYS Forge All projects published on CODESYS Forge are published under the Apache License. So you can use them freely under the condituons of the Apache Sofrware License. That doesn't mean, that everything published with the project has to be licensed under the Apache License directly. But the licenses have to be compatible with it. For a list of compatible licenses, check out the website of the Apache Software Foundation. The Apache License The Apache License is a license for open source software, published by the Apache Software Foundation. All projects of the Apache Software Foundation are published under this license. But also other software can use the license to protect their rights. The nice thing of the Apache License and the Apache Software Foundation is, that they din't just describe what the license is granting or what it doesn't, but they also guide developers through real world problems, like combining different licenses and avoiding license conflicts. CODESYS Projects When compiling a CODESYS project, you always perform a static link of all code and libraries used in the project. This is important to know, as it means that the rules of linking categorie A software applies to every CODESYS project, published under the Apache License. Incompatible licenses Please refer to the documentation of the Apache Software Foundation to find out which licenses are compatible. For sure incompatible are the popular GPL licenses, as the resulting project can't be licensed under the Apache License anymore. The result needs to be licensed under the GPL.
Last updated: 5 hours ago

(no subject) (Thread)
Last updated: 5 hours ago

IndexMain (WikiPage)
All Users CODESYS Account User Accounts Following others Developers Project Maintenance Landing Page Source Code Repositories Providing Downloads Ticket Tool Migrating Projects Contribution Licensing Distributing OS software Services CODESYS SVN FAQ Community Developer Community Legal Imprint / Impressum Terms of Service Privacy Policy
Last updated: 6 hours ago

Home (WikiPage)
Project Members: aliazzz (admin)codesys.com (admin) [TOC] [[download_button]] I2C NVRAM Driver Library containing device support for RTC chips containing Buffered SRAM like MCP7941x, 64 bytes. The requirement for full functionality is an appropriate memory range on the controller (NVRam, UPS). If there is no suitable memory range, the values of VAR RETAIN or VAR PERSISTENT variables will be lost in the event of a power failure! Variables declared as RETAIN are managed depending on the target system, but typically in their own memory range, which must be secured against power failure. This can be achieved via battery backup, via FRAM or another suitable method. Changelog v0.0.0.1 Under Construction devdescr.xml: vendor id set to 0004, device id set to 0009, see https://forge.codesys.com/drv/io-drivers/database/Home/ for details. <DeviceIdentification> <Type>501</Type> <Id>0004 0009</Id> <Version>0.0.0.1</Version> </DeviceIdentification>
Last updated: 2 days ago

Post by aliazzz on #3 RS485 IoDriver (Post)
assigned_to: aliazzz
Last updated: 2 days ago

Ticket #3: RS485 IoDriver (Ticket)
Revisit RS485 functionality On roadmap but currently not a priority[u'RS485 IoDriver', u'SPI-IoDrvMonarco', 0, u'tickets', 'Ticket', u'tickets', u'RS485 IoDriver', datetime.datetime(2019, 3, 23, 10, 26, 58, 234000), '5b9fdd464ded5100257d31b5', u'open', 'forgetracker/model/ticket/Ticket#5c31c6dd849e73001486ca0f', False, 0, u'aliazzz', u'Ticket #3: RS485 IoDriver', 0, u'1.0', False, u'/drv/spi-monarco/tickets/3/', u'aliazzz', datetime.datetime(2019, 1, 6, 9, 14, 5, 7000), None, 3, '', '', u'spi-monarco', u'Revisit RS485 functionality\r\n\r\nOn roadmap but currently not a priority', False, False, 2]
Last updated: 2 days ago

(no subject) (Thread)
Last updated: 2 days ago

Ticket #2: RTC nvram (Ticket)
It is possible to store some data in the battery-backed RAM of RTC chip on the Monarco HAT (MCP79410, 64 bytes). This is not yet directly supported in Monarco HAT driver. On roadmap, but currently not a priority.[u'RTC nvram', u'SPI-IoDrvMonarco', 0, u'tickets', 'Ticket', u'tickets', u'RTC nvram', datetime.datetime(2019, 3, 23, 10, 26, 19, 363000), '5b9fdd464ded5100257d31b5', u'closed', 'forgetracker/model/ticket/Ticket#5c31c696849e73001486c9df', True, 0, u'aliazzz', u'Ticket #2: RTC nvram', 0, u'1.0', False, u'/drv/spi-monarco/tickets/2/', u'aliazzz', datetime.datetime(2019, 1, 6, 9, 12, 54, 78000), None, 2, '', '', u'spi-monarco', u'It is possible to store some data in the battery-backed RAM of RTC chip on the Monarco HAT (MCP79410, 64 bytes). This is not yet directly supported in Monarco HAT driver. \r\n\r\nOn roadmap, but currently not a priority.', False, False, 2]
Last updated: 2 days ago

Post by aliazzz on #2 RTC nvram (Post)
status: open --> closed assigned_to: aliazzz discussion: enabled --> disabled
Last updated: 2 days ago

(no subject) (Thread)
Last updated: 2 days ago

i2cNVRAM SVN repository (SVN Repository)
Last updated: 2 days ago

(no subject) (Thread)
Last updated: 2 days ago

Home (WikiPage)
Preface Welcome to the CODESYS open source device database. We opened an own Vendor Range for open source drivers, so that everyone is able to develop and publish his drivers. <DeviceIdentification> <Type>...</Type> <Id>0004 ....</Id> <Version>x.x.x.x</Version> </DeviceIdentification> e.g.: <DeviceIdentification> <Type>501</Type> <Id>0004 0004</Id> <Version>1.0.0.0</Version> </DeviceIdentification> All this is allowed as long as your drivers are open source. To make it transparent you have to add a link to every entry in the database. To avoid conflicts, you should add an entry for every device description that you created, and which allocates a Device ID. To add an entry, you can directly edit this page. Just respect the following rules: Keep the list sorted Don't change the entries of others Keep your entry small (a one-liner) e.g.: 0001 | SPI Template | [homepage](/drv/io-drivers) Devices ID Title URL 0001 SPI Template homepage 0002 I²C Template homepage 0003 SPI Temperature homepage 0004 SPI MCP3008 homepage 0005 SPI Monarco.IO HAT homepage 0006 I²C Mega-IO Expansion Card for Raspberry Pi homepage 0007 FB Template homepage 0008 D-Logg from Technische Alternative homepage 0009 I²C universal NVRAM Driver homepage ID Title URL FFF0 Range for testing... ... ... FFFF ... only if you don't publish the driver
Last updated: 2 days ago

Ticket #42: renamig "drivers" to "device drivers" (Ticket)
Hi, Maybe we should consider rfenaming "Drivers" into "Device Drivers"? This because the new name clearly describes what kind of special category of software this is.[u'renamig "drivers" to "device drivers"', u'Home Project for CODESYS Forge', 0, u'support', 'Ticket', u'tickets', u'renamig "drivers" to "device drivers"', datetime.datetime(2019, 3, 23, 9, 52, 51, 142000), '5a4b8efad85a3d0001a9de7b', u'open', 'forgetracker/model/ticket/Ticket#5c9601f3867c04004f6e7ee5', False, 0, u'*anonymous', u'Ticket #42: renamig "drivers" to "device drivers"', 0, u'1.0', False, u'/forge/support/42/', None, datetime.datetime(2019, 3, 23, 9, 52, 51, 51000), None, 42, '', '', u'--init--', u'Hi,\r\n\r\nMaybe we should consider rfenaming "Drivers" into "Device Drivers"? This because the new name clearly describes what kind of special category of software this is.', False, False, 1]
Last updated: 2 days ago

(no subject) (Thread)
Last updated: 2 days ago

Ticket #36: Individualizing the user's "Home" (Ticket)
Hi, A suggestion, at this moment every Home of each individual is static and its contents is dependant on what the admin dictates. Therefore, is it technically possible for the user to individualise his/her Home? [u'Individualizing the user\'s "Home"', u'Home Project for CODESYS Forge', 0, u'support', 'Ticket', u'tickets', u'Individualizing the user\'s "Home"', datetime.datetime(2019, 3, 22, 7, 46, 58, 895000), '5a4b8efad85a3d0001a9de7b', u'open', 'forgetracker/model/ticket/Ticket#5c04130c0e5169002e2f07bc', False, 0, u'aliazzz', u'Ticket #36: Individualizing the user\'s "Home"', 0, u'1.0', False, u'/forge/support/36/', u'admin', datetime.datetime(2018, 12, 2, 17, 14, 52, 289000), None, 36, '', '', u'--init--', u'Hi,\r\n\r\nA suggestion, at this moment every Home of each individual is static and its contents is dependant on what the admin dictates. \r\nTherefore, is it technically possible for the user to individualise his/her Home?\r\n', False, False, 3]
Last updated: 3 days ago

Post by aliazzz on #36 Individualizing the user's "Home" (Post)
Hi, It seems the layout has changed again. I'd love to see the "menu" next to the table instead of obove the table like it is presented to me now; Hope this helps as the former view (next to each other) was more appealing to me.
Last updated: 3 days ago

(no subject) (Thread)
Last updated: 3 days ago

Artifact 5c91a4da05eb28020ffb9898 (Bin)
Last updated: 5 days ago

Artifact 5c91a4da05eb28020ffb9897 (Bin)
Last updated: 5 days ago

Artifact 5c91a4da05eb28020ffb9896 (Bin)
Last updated: 5 days ago

Ticket #41: feedback on the statistics page (Ticket)
Hi Ingo, Is it possible to let the user decide which collumns can be shown or hidden or even dropped? Personally I think it's rather useless to show the upgoing, downgoing or equal trend for statistics like logging in or the ammount of page contibuations. I rather choose the quality of a contribution over the quantity of contibutions. Example: A good contribution to cForge can/should be awarded a star or a thumb up or something similair, while the ammount of contributions made is not relevant. If someone scores many stars, that says something, instead of the ammount of page mutations or so. I hope you understand what I am trying to convey.[u'feedback on the statistics page', u'Home Project for CODESYS Forge', 0, u'support', 'Ticket', u'tickets', u'feedback on the statistics page', datetime.datetime(2019, 3, 19, 21, 43, 48, 976000), '5a4b8efad85a3d0001a9de7b', u'closed', 'forgetracker/model/ticket/Ticket#5c8fd73705eb2800f8fb9861', False, 0, u'aliazzz', u'Ticket #41: feedback on the statistics page', 0, u'1.0', True, u'/forge/support/41/', u'ingo', datetime.datetime(2019, 3, 18, 17, 36, 55, 338000), None, 41, '', '', u'--init--', u"Hi Ingo,\r\n\r\nIs it possible to let the user decide which collumns can be shown or hidden or even dropped? \r\nPersonally I think it's rather useless to show the upgoing, downgoing or equal trend for statistics like logging in or the ammount of page contibuations. I rather choose the quality of a contribution over the quantity of contibutions.\r\n\r\nExample: A good contribution to cForge can/should be awarded a star or a thumb up or something similair, while the ammount of contributions made is not relevant. If someone scores many stars, that says something, instead of the ammount of page mutations or so.\r\n\r\nI hope you understand what I am trying to convey.", False, False, 2]
Last updated: 6 days ago

Post by ingo on #41 feedback on the statistics page (Post)
status: open --> closed
Last updated: 6 days ago

(no subject) (Thread)
Last updated: 6 days ago

Post by aliazzz on #41 feedback on the statistics page (Post)
"The rest is open for decission when the platform becomes really active." => No further remarks, so you can close this ticket at your own discretion.
Last updated: 6 days ago

1 2 3 .. 94 > >> (Page 1 of 94)

Showing results of 2341

Sort by relevance or date