Home (version 7) discussion
SPI-Temperature
home
(Thread)
Home (version 7) discussion
Last updated: 2018-08-31
(no subject)
SPI-Temperature
home
(Thread)
Last updated: 2018-02-21
mcp3008: ./trunk/mcp3008/Devices/MCP3008.devdesc.xml
Bash
bash
(Bash)
<?xml version="1.0" encoding="utf-8"?>
<!--created with CoDeSys 3.0 (http://www.3s-software.com) by DeviceDescriptionBuilder (3S-Smart Software Solutions GmbH)-->
<DeviceDescription xmlns="http://www.3s-software.com/schemas/DeviceDescription-1.0.xsd" xmlns:ts="http://www.3s-software.com/schemas/TargetSettings-0.1.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Types namespace="local">
</Types>
<Strings namespace="local">
<Language lang="en">
</Language>
</Strings>
<Device hideInCatalogue="false">
<DeviceIdentification>
<Type>501</Type>
<Id>0004 0004</Id>
<Version>1.0.0.0</Version>
</DeviceIdentification>
<DeviceInfo>
<Name name="local:ModelName">MCP3008</Name>
<Description name="local:DeviceDescription">Forge I/O driver for the MCP3008</Description>
<Vendor name="local:VendorName">Open Source</Vendor>
<OrderNumber>-</OrderNumber>
</DeviceInfo>
<Connector moduleType="500" interface="Raspberry.SPI" role="child" explicit="false" connectorId="1" hostpath="-1">
<InterfaceName name="local:PCI">SPI devices</InterfaceName>
<Slot count="1" allowEmpty="false">
</Slot>
<DriverInfo needsBusCycle="true">
<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>
</DriverInfo>
<HostParameterSet>
<Parameter ParameterId="1000" type="std:UINT">
<Attributes channel="input" />
<Name name="In0">In0</Name>
</Parameter>
<Parameter ParameterId="1001" type="std:UINT">
<Attributes channel="input" />
<Name name="In1">In1</Name>
</Parameter>
<Parameter ParameterId="1002" type="std:UINT">
<Attributes channel="input" />
<Name name="In2">In2</Name>
</Parameter>
<Parameter ParameterId="1003" type="std:UINT">
<Attributes channel="input" />
<Name name="In3">In3</Name>
</Parameter>
<Parameter ParameterId="1004" type="std:UINT">
<Attributes channel="input" />
<Name name="In4">In4</Name>
</Parameter>
<Parameter ParameterId="1005" type="std:UINT">
<Attributes channel="input" />
<Name name="In5">In5</Name>
</Parameter>
<Parameter ParameterId="1006" type="std:UINT">
<Attributes channel="input" />
<Name name="In6">In6</Name>
</Parameter>
<Parameter ParameterId="1007" type="std:UINT">
<Attributes channel="input" />
<Name name="In7">In7</Name>
</Parameter>
</HostParameterSet>
</Connector>
</Device>
</DeviceDescription>
Last updated: 2018-07-16
mcp3008: ./trunk/mcp3008/package.manifest
Bash
bash
(Bash)
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<Package>
<Strings>
<String Id="GeneralName">
<Neutral>SPI MCP3008</Neutral>
</String>
<String Id="GeneralCopyright">
<Neutral>Copyright (c) 2016-2018 by 3S-Smart Software Solutions GmbH. All rights reserved.</Neutral>
</String>
<String Id="GeneralDescription">
<Neutral>This Package contains the open source driver for the MCP3008.</Neutral>
</String>
<String Id="license">
<Neutral>license.txt</Neutral>
</String>
</Strings>
<General>
<Id>d4cf73eb-ddbf-4a0f-babd-7b30a6606ef5</Id>
<Version>1.0.0.0</Version>
<Name>$GeneralName</Name>
<Vendor>Open Source</Vendor>
<Copyright>$GeneralCopyright</Copyright>
<Description>$GeneralDescription</Description>
<LicenseAgreement>$license</LicenseAgreement>
<RequiredInstallerVersion>3.5.6.0</RequiredInstallerVersion>
</General>
<Components>
<Component>
<General>
<Id>0</Id>
<Name>SPI MPC3008</Name>
<Description>SPI MCP3008</Description>
<Selectable>False</Selectable>
<SelectedByDefault>True</SelectedByDefault>
</General>
<Items>
<DeviceDescription>
<Path>Devices/MCP3008.devdesc.xml</Path>
</DeviceDescription>
<Library>
<Path>Libraries/SPI_MCP3008.library</Path>
</Library>
</Items>
</Component>
</Components>
</Package>
Last updated: 2018-07-16
spi-temperature: Artifact 5f48f85ae0677b001936b26a
SPI-Temperature
tickets
(Bin)
Last updated: 2020-08-28
spi-temperature: Artifact 5f48f85ae0677b001936b26b
SPI-Temperature
tickets
(Bin)
Last updated: 2020-08-28
spi-temperature: Artifact 5f48f85ae0677b001936b26c
SPI-Temperature
tickets
(Bin)
Last updated: 2020-08-28
Post by aliazzz on #14 create Package bug
CODESYS Forge
tickets
(Post)
now testing! please wait The registry patch for \"%V\" seems to work !** Aliazzz
Last updated: 2020-01-18
Post by ingo on #29 CFORGE Tool doesn't work with SP16
CODESYS Forge
tickets
(Post)
status: open --> closed
Last updated: 2020-08-25
Post by i-campbell on #14 create Package bug
CODESYS Forge
tickets
(Post)
@Ingo Please accept the change to the Setup.reg file, which puts quotes around the directory paths of shell commands to solve the problem of directories with spaces. https://forge.codesys.com/tol/cforge/tickets/_discuss/thread/4441ef6b6f/32d9/attachment/I-Campbell.2020.01.18.19.50.Setup.reg please see this positive tester note https://forge.codesys.com/tol/cforge/tickets/14/#32d9/4a66
Last updated: 2020-01-18
Post by aliazzz on #14 create Package bug
CODESYS Forge
tickets
(Post)
Why don't you do the change and test? I haven't got write-access
Last updated: 2020-01-18
Post by codesys-com on #16 Where can I find the version number for Android app?
CODESYS Forge
tickets
(Post)
Merged changes from erichspitzweg. Version number is the build date, and it is shown in the app-info as well as a short message at startup.
Last updated: 2019-12-31
Post by aliazzz on #21 Future of cforge package
CODESYS Forge
tickets
(Post)
a. As a test, I setup a slack for collaboration, but I don't think that is optimal for open source use. Looking at other OSS projects, I see irc (specifically irc.freenode.net) as a common "chat". One of the tools for a forge/prj/, could be adding the CODESYS forge bot to their irc, and thus archiving the chat logs. I think it should be made clear that chat is best for "we need to "sit in the same room and discuss this"" whereas [talk] or [tickets] is best for "Please take time to consider and respond when you have time". There is an interesting discussion on the use of the two tools here. Having tried MS Teams and Slack, I think irc is the least intrusive to people's workflow, as with irc you are free to choose your own client. It also has the best licencing model. In general my mantra is: Keep It Simple Stupid. So, for this moment, a cForge built-in web chat client would be my personal ideal. Let me paint my vision for you; A permanent chat would be accessible only if you are logged into cForge (a chat button next to search). Your cforge username acts as the your personal chat nick automatically. The chat will have some "prefab" channels which you can join; projects, libraries, drivers, chat, * etc. If a user wishes, he/she can open a private channel with one or more others. No need for installed software, plus the log can be saved as a text file if needed... The chat can add an extra dimension in support question handling, if CODESYS is open for this.... Many commercial companies do this type of communication allready.
Last updated: 2020-04-09
Post by ingo on #2 commit: Implement the action 'commit'
CODESYS Forge
tickets
(Post)
status: accepted --> closed assigned_to: erichspitzweg --> Ingo
Last updated: 2018-08-09
Post by i-campbell on #25 Cannot find Product News
CODESYS Forge
tickets
(Post)
Tester Note: Hmm, when I used the link on the news feed ( here ), somehow I still get V20200208 If I go to https://forge.codesys.com/tol/cforge/code/ and click through to the cforge.apk I get an error 500 However when I hit the Download Snapshot button, I get a zip file with the correct cforge.apk in it I think as it will be in beta on Play Store soon, the simple fix for now is to say "download snapshot of the repository and unzip to get the APK" RESULT: OK - I now have product news in the app
Last updated: 2020-02-20
Post by ingo on #12 CODESYS Forge needs an icon
CODESYS Forge
tickets
(Post)
status: open --> closed
Last updated: 2020-01-31
Post by i-campbell on #21 Future of cforge package
CODESYS Forge
tickets
(Post)
Minutes of short meeting: Present: Ingo, i-campbell From the diagram in the above comment we should focus most on the role of the "contributer". And that we should make the start for the potential contributer, who is new to "open source", "version control" and "continous integration", as easy as possible. This indirectly helps the other user types. Make contributing easier cforge tool should provide the "Wizards" for, for example committing your first project. This should build on the "notes" Ian took committing his first project Publicise notes (TODO: TICKET) Installation of cforge should be smoother. (TODO: TICKET) Integrate SVN commands seemlessly into tortoise svn (TODO: TICKET) To assist those new to open source, a more rigid (recommended) workflow should be documented and encouraged. This will read more like a tutorial or how to. The current documentation documents the platform, and was written when the forge was younger. (TODO: TICKET) A Tube-tutor video should be made, of the typical workflow for collaborating on a Forge project. (TODO: TICKET) Get the community more involved in the governance of forge. Solicit ideas and thoughts on the recommended workflow on forge/talk/ (TODO: FORUM POST) As a lower priority (i.e. for the future), document the governance model, ie, how are decisions about the platform made and documented. how are ideas presented, etc. how are individual projects governed. (TODO: BACKLOG TICKET) Consider monthly(?) "Town Hall" meetings. Think up a coller name though, maybe to do with forges. (TODO: TICKET) Make collaboration on projects easier: Investigate integrating a user chat possibility. Eg private chat. Discussions like this one (the meeting, not the ticket). project meetings. Could include chat / screensharing/video/audio. eg. XMPP server or Jitsi server. Ideally uses same login, rather than having to sign up for yet another account somewhere. Ideally open source. Decide on neccessity of chat log archival. (TODO: TICKET)
Last updated: 2020-04-16
Post by ingo on #6 support context menu entry for common use cases in windows explorer
CODESYS Forge
tickets
(Post)
status: open --> closed assigned_to: erichspitzweg --> Ingo
Last updated: 2018-08-09
Post by i-campbell on #15 renaming cforge commands
CODESYS Forge
tickets
(Post)
Edit: commands from original ticket description show up clarified in the latest installer. But other commands need clarifying as per aliazzz's feedback. @aliazzz is it possible to update the main ticket description with the new requirements?
Last updated: 2020-01-18
Post by ingo on #5 Implement checkout
CODESYS Forge
tickets
(Post)
status: open --> closed
Last updated: 2018-05-15
Post by ingo on #5 Implement checkout
CODESYS Forge
tickets
(Post)
Reopen necessary, as I forgot to commit the command script.
Last updated: 2018-05-12
Post by i-campbell on #14 create Package bug
CODESYS Forge
tickets
(Post)
File for testing attached Steps to repeat: 1. Download and install cforge 2. Double click this attached file to install to registry 3. Reboot(?) 4. Checkout random repository using its cforge:// link to "D:\folder with a space\" 5. Right click that folder in explorer and "create package manifest" ==>IS: "can't find D:\folder\liscence.txt" ==>SHOULD: create manifest successfully
Last updated: 2020-01-18
Post by ingo on #22 Upload doesn't work
CODESYS Forge
tickets
(Post)
labels: App --> status: open --> closed
Last updated: 2020-02-08
Post by aliazzz on #21 Future of cforge package
CODESYS Forge
tickets
(Post)
Hi, On point1: Git integration ETA SP16, nice! On point 2: Currently, generating a .pdf output is cumbersome, to say the least, due to frames, latex and python dependencies, etc, etc. This, while generating a .chm file can be generated via a single command. But only if you read the .libdoc documentation carefully, then you can spot that specific command. Maybe documentation has improved over time, I have not checked it since over a year. Anyway, both a themed .chm and a .PDF are high on my bucketlist, but one must start small ;-) On point 3: I mean your first option: just calling any arbitrarily written python script from and run it against the CODESYS IDE through a right mouse click over while selecting it and choose "cforge -> run script" or something similar like this...
Last updated: 2020-02-03
Post by i-campbell on #21 Future of cforge package
CODESYS Forge
tickets
(Post)
Hi Team! So since February, a lot has happened! 1. forum integration. 2. I made my first forge.codesys.com/prj/ 3. I collaborated with aliazzz on my second forge.codesys.com/prj/ 4. lots of people are working from home. 5. SP16 is sooo close! 6. So many more public and private things for everyone. Some points I have come up with: 1. It took me 4 hours to get my first project from "I have a .project" to "I have a /prj/ people can access". I think I missed a few steps, but it is there. I would like to get that down to half an hour for first time forgers, with ten minutes possible for repeat forgers. While I think it is important that our forge works with the existing users tools / workflows, we should have some super simple "UI" which asks the minimal questions for: 1. converting a .project and .library to a forge project (filling in the appropriate descriptions, licences etc., adding a Ticket tool...) 2. Starting work on a change (branch), either as project member or non project member (have to clone into forge/u/). 3. merge request 4. merge. This UI should then be documented in the "minimal steps with minimal choices" section. 2. Collaboration tools are needed. Ideally we would recommend (or host!) a standard communication toolset. a. As a test, I setup a slack for collaboration, but I don't think that is optimal for open source use. Looking at other OSS projects, I see irc (specifically irc.freenode.net) as a common "chat". One of the tools for a forge/prj/, could be adding the CODESYS forge bot to their irc, and thus archiving the chat logs. I think it should be made clear that chat is best for "we need to "sit in the same room and discuss this"" whereas [talk] or [tickets] is best for "Please take time to consider and respond when you have time". There is an interesting discussion on the use of the two tools here. Having tried MS Teams and Slack, I think irc is the least intrusive to people's workflow, as with irc you are free to choose your own client. It also has the best licencing model. b. Additionally, some sort of webinar like software is needed in the toolset. Again, I would prefer an OSS solution, such as the self hosted openmeetings.apache.org. Again, the recordings could be archived with the forge/prj. Projects could book the CODESYS Forge OpenMeetingRoom (or, as the forge expands, MeetingRoom2 ;)), and interested parties could look at the calendar and see "oh, I see the cforge project is having a scrum meeting this weekend, I'll watch along". Obviously, projects are free to pick their own toolsets.
Last updated: 2020-04-09