cancel
Showing results for 
Search instead for 
Did you mean: 

Connect ctrlX Nexo tightening to ctrlX core

Connect ctrlX Nexo tightening to ctrlX core

TN_X
Long-established Member

Hi All,

Im testing connection of Nexo to ctrlX core as the concept using http protocol below.

TN_X_0-1686282302216.png

In the Nexo tightening web.

I activated http protocol.

TN_X_1-1686282503477.png

At my PC (installed Node-red for testing only) using http in & http response to get the feedback.

first thing I just create a http server in node-red to listen data package from Nexo. But it didnt work, have you ever tried this connection before and could share it with me?

Thank you.

4 REPLIES 4

Sgilk
Contributor

Hello,

I developed the Node-RED code used in the referenced concept. I am requesting the Nexo tool settings from the person who implemented this on the tools.

Here is a generic version of the flow which accepts HTTP post requests at /node-red/tightening. I am using a custom version of Node-RED which includes some additional packages, so all of the functionality won't work in the flow. You should be able to use this as an example of how to establish an input connection though. You can try first to make the connection using Postman or similar tool.

Using the Node-RED app from ctrlX Store, I can post to the http in node at the following route (http://192.168.1.100/node-red/tightening). If you can make the connection with Postman, I'd try removing the port from the "Page" setting on the Nexo tool. I will post the verified settings when I hear back from my colleague.

Save the attached file as .json and you should be able to upload directly into Node-RED. Otherwise, copy and paste the content.

TN_X
Long-established Member

Basically I can create a server in ctrlX core now and can post from Posman or YARC. Its all ok. But when I plug Nexo into ctrlX core then I can not get any feedback data even Nexo shown connected.

Unfortunately, I don't have access to a Nexo tool, so maybe someone else can jump in here. I was informed that the connection tests were actually performed on a System350, not a Nexo. My suggestion would be to remove the http://ip_address:port from your page setting and only list the endpoint (/node-red/tightening in my example) and attempt to connect again.

CodeShepherd
Community Moderator
Community Moderator

Are there any news? Is this still a topic? Or can this topic be closed?

Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist