npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@thehighestbit/node-red-contrib-ipc-cfx

v1.0.5

Published

A node red node for communicating with AMQP brokers using the IPC-CFX protocol. Uses the official .NET SDK.

Downloads

212

Readme

node-red-contrib-ipc-cfx

A Node-RED node for interfacing with the official IPC-CFX .NET SDK.

Installation

First make sure the host system has .NET Core 9.x installed. Then simply install this node

npm install @thehighestbit/node-red-contrib-ipc-cfx

Configuration

Configuration node

First configure the endpoint config node, specifying the desired endpoint handle (eg. someManufacturer.someMachine.someSerial) and broker URI (eg. amqp://guest:guest@localhost).

CFX in

Pick the desired endpoint configuration and then specify the desired queues (eg. myQueue) this node should subscribe to. Please note that there can only be a single CFX in node per endpoint configuration. This is because there can only be a single message listener per endpoint and thus all in nodes produce the same messages regardless of what channels they are subscribed to.

CFX out

Pick the desired endpoint configuration and then specify the desired AMQP target that this node should publish its messages to (eg. /exchange/CFXExchange). There can be as many out nodes per endpoint as you wish, since the SDK supports publishing messages on a per channel basis.

Usage

CFX in

This node simply forwards the received CFX envelope inside of the msg.payload field.

CFX out

The node expects the msg.payload to be a JSON object that can be serialized into a valid IPC-CFX message. Additionally, the $type property must also be included, otherwise the serialization will fail. For example:

    {
        "$type": "CFX.ResourcePerformance.ProcessDataRecorded, CFX",
        "ProcessData": {
            "$type": "CFX.Structures.Cleaning.CleaningManagementData, CFX",
            "Readings": [
            {
                "ReadingType": "TemperatureMin",
                "ReadingValue": 345
            }
            ]
        }
    }

The outer type field ("$type": "CFX.ResourcePerformance.ProcessDataRecorded, CFX" in the above example) must always be present. Additionally, if the contained data is ambiguous (like in the above example), the type for that needs to be included as well.

If the message is not valid CFX, an error will be thrown.