Jump to content

Chris Cilino

  • Content Count

  • Joined

  • Last visited

  • Days Won


Chris Cilino last won the day on September 29 2019

Chris Cilino had the most liked content!

Community Reputation


1 Follower

About Chris Cilino

  • Rank

Profile Information

  • Gender
  • Location
    Austin Texas
  • Interests
    Applying art and craftsmanship to software development using LabVIEW.
    Removing barriers to collaboration among LabVIEW community members.
    Building tools to help LabVIEW programmers do their work more efficiently (bit.ly/ChrisCilino_CSuite)

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2017
  • Since

Recent Profile Visitors

1,871 profile views
  1. Hi @gregoryj Sorry for taking forever to respond. I need to adjust my notification settings apparently. I do use the case that comes with Canakit. I'm able to keep the raspberry pi in the case and even put the lid on because of the ribbon that attaches to the breakout board. I got the ribbon and breakout board from Freenova. My full hardware setup is documented in the bitbucket readme at https://bit.ly/ChrisCilino_LabVIEWCommunityAndRP. And yes... it is fun! Enjoy!
  2. @Bryan Which link are you referring to? I just checked all of them and they seem to be working for me.
  3. GCentral is taking a yearly survey to help identify trends so we have data to back decisions. We're asking for 3 minutes of your time to complete the survey at: https://bit.ly/GCentral_Survey_2020-21 At the end of the survey you'll be able to see a summary of the results. In order to help keep the results accurate, you're allowed to take the survey only once, and requires you to sign in to your google account. Thank you for your time and your opinions. GCentral's success is only measured by its usefulness to you. Help make GCentral what you need it to be. See additional information in the GCentral FAQ. And remember: GCentral is opening VIWeek this Sunday at 9 am CTD (https://bit.ly/VIWeek_GCentralPresentation)
  4. Love this idea! So basically an "idea exchange". I have an idea! Does the solution exist already? Is anyone planning to create it? Can I plan it in such a way that other's can implement it? Can I start implementation so that other's can join in? As a community member I would like answers to all of the above quickly. Is that a fair summary @ChrisStrykesAgain?
  5. #VIWeek The first Virtual LabVIEW Event Hosted By the Community. Starting Sunday, May 17th at 9 AM CDT See the full agenda at https://bit.ly/viweek Cilino VIWeek Intro.mp4
  6. LabVIEW Community Edition rocks! In order to help kick off this momentous occasion, I've put together an example alarm clock. It is broken down into 6 lessons (so far) taking you from blinking an led through creating an alarm clock with a state machine. To download or learn about LabVIEW Community Edition check out GCentral.org Check out the alarm clock here! <-(http://bit.ly/ChrisCilino_LabVIEWCommunityAndRP)
  7. Howdy Brian So this is awesome! I know Jeremy presented some stuff just like this in his NIWeeek 2018 presentation (posted on the LV Wiki). Do you know if something like this was ever exported into a package? I'm having a hard time finding it if it exists.... ironically.
  8. There has been a lot of discussion, which is great, but I feel the need to reiterate GCentral's vision and mission. GCentral envisions a LabVIEW community making the best version of itself by improving its capability through collaboration. GCentral is a non profit organization: for programmers who need to find, share or collaborate on G reusable code or software engineering tools. that provides a platform for G code packages and collaboration resources. that is independent and driven by community experts. GCentral's Mission Enable LabVIEW programmers to collaborate by removing barriers to finding / using code designed for reuse (packaged code) removing barriers to contributing code designed for reuse (packaged code) removing barriers to co-developing code using code with confidence GCentral is package technology agnostic / SCC agnostic GCentral does not endorse or encourage the use of one package manager over the other, nor will we. Each community member can package their code according to their preference. GCentral does not endorse or encourage the use of one Source Code Control Provider (local or cloud based) over the other nor will we. Each community member can use the SCC they prefer. GCentral will ease the pain we all feel when attempting to find and use packages by index the currently available public repositories (Tools Network, GPM, JKI Tools, NI Packages) by indexing an new, un-gated, cloud based storage location that can house any package type. by displaying the index results in a web page / APIs, etc (see https://www.gcentral.org/ for the prototpye) GCentral will ease the pain we all feel when attempting to contribute packages by creating new, un-gated, cloud based storage location that can house any package type (not source). MAYBE creating software to transport built packages from build machine to the new cloud storage location GCentral will ease pain we feel when attempting to co-develop code by Creating template projects for each of the major online SCC. (GitHub, etc). Coming pre-configured to build the package type of your choice and upload to the GCentral package server. GCentral will inspire confidence by Making any submitted package always available. Once submitted, a package cannot be deleted apart from a GCentral administrator. As a result, you can depend on a package without fear of it ever missing. Product pages per package designed to educate on the package and author. The above is a summary of the CLA summit presentation I gave (https://sites.google.com/gcentral.org/website/about-gcentral) The advent of the GitHub Package Registry is very interesting. I've reached out to GitHub to provide clarity on how extensible their framework is. At time 29:44 in the presentation Michael linked above the presenter says "We have a great extension framework for adding support for new registries, which will be opening up in the future". That MAY mean we can provide plugins for their registry to recognize NIPKGs, VIPs, GPKGs. And that may completely solve the "find/use" pain point i mention above... so long as the community is ok putting their packages in GitHub AND sacrificing confidence that the package will always be available to use or link against. In conclusion, GCentral's aim is to impose the least amount of infrastructure on a community member while enabling us to find/use, contribute, co-develop packages designed for reuse. GCentral will use already existing technologies to accomplish its goal and create new technologies where needed.
  9. All In case you haven't already, GCentral could really use your help in getting CLA feedback. If you attended the CLA, summit would you mind taking 10 min to fill out the survey . If you didn't get the chance to attend the CLA summit please feel free to watch the presentation. I've included the presentation outline so you can go to the parts of the presentation you find most interesting. Then we would love your feedback via the survey. We're up to 33 respondents and I'm closing the survey end of next week (Nov 1). We really want to make sure we gather feedback from the community so we know we're on the right track. GCentral is for us as a community. Help us make this happen. Thanks.
  10. As a member of the LabVIEW community I would like to have only one profile so I can have a consolidated summary of my activity in the community (number of ni.com posts, number of packages I've created, average rating on the software I release, etc)
  11. Hi Rolf That's good feedback. The current UI \ UX is just a proof of concept. Once we start designing the actual UI \ UX we hope it'll be efficient to use and pleasant to look at. One other note: the indexer is open source. Please feel free to suggest adjustments by joining the dev team on GCentral's git repo. Keep in mind GCentral.org is in its infancy so we're choosing to sacrifice aesthetics for functionality to avoid bikeshedding. Glad to hear you think GCentral is a good initiative and thanks for your thoughts!
  12. As a participant in the G package community I would like a periodic manifest of all new packages so I can stay up to date on what's new. I want to be able to specify how often I get the manifest and the maximum number of packages listed in the manifest.
  13. At the 2019 Americas Certified LabVIEW Architect Summit, GCentral was introduced to the LabVIEW Community. GCentral is a non profit organization (incorporated September 2019) composed of G community leaders creating a platform for programmers to find/use, contribute, and co-develop G code packages and collaboration resources. While GCentral is leading the charge to solve these problems, we will closely align with the community's needs. This forum is designed to connect GCentral's efforts with the community's needs. Some links to be aware of: GCentral.org LabVIEW Wiki Twitter (@GCentralOrg) LinkedIn Instagram (gcentralorg) Facebook Website GitHub Repo
  14. Rather than have a bunch of links floating around, I'm creating this "one stop shop" for my contributions to the LabVIEW community. This is my Cilino Suite aka "C Suite". Presentations My YouTube Channel of Presentations (bit.ly/ChrisCilino_Presentations) including: My LabVIEW Champion Interview NIWeek 2018 Keynote Presentation Soliton Customer Testimonial LabVIEW Architect's Forum Q3 2018 - LabVIEW Auto Documentation Software LabVIEW Architect's Forum Q4 2016 - Automated Build Process 2018 Certified LabVIEW Architect Summit - Everything a Software Engineer Needs to Know That Has Nothing to Do with Software Engineering My First Keynote Presentation at VIP Days in Germany Code - Reuse Libraries Automated Build System - Software Module Builder Summary: A system that turns source into exports. The exports can be of any type. Also determines build order of hierarchical modules, updates dependencies, and allows you to move the exports to the location you need for your end users to find and install the export and its dependencies. Download BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/software-module-builder.git Dependencies LabVIEW Container (see link below) LabVIEW SCC API Summary: An API designed to abstract server based source code control providers. BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/labview-scc-api.git Distributed as a part of the Automated Build system NI Package Manager Build Spec API Summary: An API to programmatically interact with and edit the LabVIEW NI Package Build Specification. BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/ni-package-manager-api.git Distributed as a part of the Automated Build system Custom Install Step Launcher Summary: Enables NI Package Manager to execute VIs as a Post-Install/Post-Install All/Pre-Uninstall action. Download: Distributed as a part of the Automated Build system BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/custom-install-step-launcher.git Software Module Template - NIPKG and VIP Summary: A template LabVIEW Project designed to be built into an NI Package and VI Package by the Software Module Builder (see above). With this template, a user need only put their code in the "source" directory and edit some build specification information and the build process will do the rest. Distributed with the Software Module Builder BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/software-module-template-nipkg-vip.git Watchdog Framework Summary: A software observer of "situations" that can notify when something of "interest" happens. The observer is the "WatchDog", the thing being observed is a "Perpetrator", and the notification is a "bark". Download BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/labview-watchdog-framework.git Sequencer Summary: A simple design pattern that organizes code on a single block diagram without the inappropriate/excessive use of subVIs. Download BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/sequencer-pattern.git Auto Documentation Summary: Think of this as Doxogen for LabVIEW. Given a Project, Lvlib or .class, this software generates report. The report is "printed" to a confluence page. The software is Object Oriented and designed to be extended through inheritance. Download BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/labview-auto-documentation.git Dependencies LabVIEW Atlassian / Confluence / Jira APIs Summary: An API that allows you to control Atlassian assets such as Confluence and JIRA from LabVIEW BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/labview-atlassian-api.git LabVIEW Container Summary: A dynamic data structure that combines the strengths of a cluster and an array. Download BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/labview-container.git History/Credentials/Social Media LabVIEW Champion Page LinkedIn LabVIEW Champion Badge Certified LabVIEW Architect Badge Twitter NI.com Profile
  15. My apologies for not having much info on this page yet. I'm just trying to get the code in a presentable state and then I'll broadcast it's purpose and stuff.... And Cirrus Logic is not affiliated with NI. I'm not sure why my profile reads "NI"... hmmm.... I'll see if i can get that squared away.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.