Ham Radio Work Bench

Mike-VA3MW

tparish

David Decoons, wo2x

Tom,

Mike and Andreas, N6NU got me hooked on Node Red. I have mine set up for remote control and monitoring of the KPA1500 amp, Yaesu G1000dxa rotor with Idiom Press serial card, Data Loggers Web Switch Pro , and radio info from 6600.

The programming language is not bad and you create flows for each group. It uses blocks for different things you want to do like parse information from a data stream, input button, send commands to the amp or radio, etc.

For anyone interested in the Node Red project i can share my programming to get you started and see how it works, then customize it to your needs. Very cool stuff indeed.

Dave wo2x

This is a screenshot from my iPad.

Alan

Mike-VA3MW

Hi Alan

The developer turn is pretty wide.  What it means is that it is those that want to role your own.  As an example, unless you eat out all the time, you are a developer in your kitchen.  Here is some of the node-red discussion:  https://community.flexradio.com/flexradio/topics/remote-operating-and-node-red.  In fact, I just looked at Dave WO2X's current panel, and I am going to ask him to send me his 'flow' for his Radio Info panel.   You can then take it to the point where the radio knows what your Amp is going (we do that already with the PGXL), but maybe even other vendors.  Or, make up some IFTT rules.

The Flex product line has always been wide open for others to connect and control the radio.  In fact, that is how the iOS and MAC clients were developed.    There are many many products available today that integrate with a Flex Radio.  This is what makes it an amazing platform for not only an appliance style of operation but those that want to take it to the next level--what ever that is.  

Cool, eh? (spoken in my best Canadian)

de va3mw

Alan

Thanks, Mike

I did pick up on your comments about a new Flex API coming out that has allowed you to do more with node-red.  The Flex API is territory I have not ventured into.

For myself, this all sounds very exciting.  For remote control, I am currently using Apple iHome to control a number of relays and have numerous third-party apps in server/client mode as part of my normal "flow", like PST rotor.    I consider myself somewhat able to read the manuals and integrate apps at the user level. For more adance integrations, like maybe node-red, I am hoping others will "kick start" the interfaces, like was recently done with FRStack and the stream device (or is that comparing apples and oranges?). 

I will follow the links in the community message board to see what others have done so far.

Alan

Mike-VA3MW

No new API, just the current ones.    You don't need to use the API's to talk to the radio.  You can talk directly to the radio with a simple TCP connection.  http://wiki.flexradio.com/index.php?title=SmartSDR_TCP/IP_API

I'm not a programmer at all, but I was able to figure it out with some help from those in the Community.  I just had to learn it.  Never stop learning.  It keeps you sharp as we grow older.  Just do it! 

73

W2ECK

Mike-VA3MW

This one?

https://youtu.be/iEctXuWBHME

W2ECK

that's it - thanks
73 Paul

Joe N3HEE

Hi Dave.  I would be interested in seeing your code for some examples.  I am just getting started with Node Red with Flex radio.  Very cool stuff !!  Thanks -Joe N3HEE

Email good on QRZ

David Decoons, wo2x

Hi Joe, saw the email from Mike Walker. Check your inbox in a bit. Dave wo2x

Joe N3HEE

Thanks Dave. 

I have noticed that some messages being sent by my radio over TCP port 4992 never seem to change no matter what the radio is set to.  For example, it always sends a "speed" message of 30 ?  Also always sends a mode message of CW ?  Am I missing something or is there a bug in Flex messaging ? 

David Decoons, wo2x

Look at my FlexRadio flow I just sent. The top line has a TCP in, then trigger block, and then TCP out.

The top trigger block is what sends the commands to the radio. So if you want to customize it to send other commands you can have a button - trigger - TCP out to initiate commands from a button on the Node Red UI.

73
Dave wo2x

Joe N3HEE

I undertand that part and have that working.  What I was talking about is parsing messages sent from the radio to display on Node Red dashboard.  Such as frequency, mode, cw speed, power, etc.  It seems there is a problem in that many of those messages never change.  Such as mode, cw speed, etc.  I've been watching the msg.payload in the debug window.  If I switch the radio from CW to LSB the mode message still says CW ?

David Decoons, wo2x

Not sure, never played with it that much. Last 2 months have been a blur for me.

If you want, send me a flow with what you are attempting to do and I will try to debug it here later or tomorrow.

Dave wo2x

Gene

Dave, can you send me your code also? I installed Node Red but need to get some examples for interfacing to different equipment. Thanks.

k5pa@arrl.net is a good address.

Much thanks, Gene, K5PA

Mike-VA3MW

Can I make a recommendation that we post it in the NodeRed discussion so all those interested can see and learn?  

I will be doing that with mine, once I clean it up.  I will also add it to GIT or the NodeRed flow page.

Mike

Joe N3HEE

Absolutely.  Link please

David Decoons, wo2x

Hi Gene. Sure will. Will not be til this evening though Dave wo2x