¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Help with Modified MKCM SPE Amp.json


 

So I've downloaded this node and it displays, but I get an ECONNECREFUSED error on the GetSPEINFO function.? What am I missing in the setup?? The IP address is set to the radio (192.168.1.34:4996).

My Node-red is running on a Pi, and it feels like I need a port setting opened up but I'm pretty sure I don't have firewall installed (yet)

Any ideas?


 

Scott

The IP address that would give the message you show should be the IP address of your raspberry Pi.? If Node-Red and FRstack are on the same Raspberry Pi, use the Loopback IP and port :5025


Screen Shot 2021-01-20 at 8.30.06 AM.png

This sets the communications between FRStack and Node-Red

For the SPE amp connection, you need to configure the COM port in the FRStack configuration file, ?located at "/usr/local/frstack/appsettings.json.

Here is a link to the MKCM instructions.? The configuration file is show about 3/4 ways down:



Here is a screenshot:

Screen Shot 2021-01-20 at 8.33.20 AM.png

E-mail me if you need more help.? We can Team View?or Zoom.

Alan
WA9WUD



On Wed, Jan 20, 2021 at 8:02 AM Scott - W5NJK via <w5njk=[email protected]> wrote:

So I've downloaded this node and it displays, but I get an ECONNECREFUSED error on the GetSPEINFO function.? What am I missing in the setup?? The IP address is set to the radio ().

My Node-red is running on a Pi, and it feels like I need a port setting opened up but I'm pretty sure I don't have firewall installed (yet)

Any ideas?


 

After much machinations, I've got my node up and talking with my 6400 and FRStack, hand have configured the FRStack to the amp's USB serial port. (in my instance I have linked /dev/ttyUSB_AMP to /dev/ttyUSB0).

? ? "SPEComPort": "/dev/ttyUSB_AMP", // this is the Serial device for SPE AMP Control port (Not the CAT port)
? ? "SPETuneStandby": "false", // this will set SPE to STANDBY when TUNE is activated
? ? "SPEModeRestore": "false", // this will return SPE to OPERATE after TUNE complete
? ? "SPEOnAntenna": "0", // 0 or 1 or 2; 0 for both, 1 for ANT1, 2 for ANT2
? ? "SPEUseDTR": "false", // this will set DTR to power up amp
? ? "SPEProtocolV1": "true", // this is set true for SPE V1 amps
? ? "SPEAutoOpen": "false", // this is set true to OPEN SPE after connecting to radio
However, the payload coming out of the GetSPEINFO node is { empty }.? So it kind-of feels like I don't really have a serial connection to the amplifier.? Anyone have suggestions to try?




 

Scott

Three items to check.

- For the SPE amp, use a simple USB cable from the SPE USB connection to the Raspberry Pi.? If you only have one serial connection to the Pi, your port config should be good.? Otherwise, look in the "/dev/serial/" directory?for the name of your com connection

- Make sure the SPE amp firmware is up to date.

- In the FRStack Config file, select the correct protocol:

Screen Shot 2021-01-25 at 9.03.42 AM.png

Alan
WA9WUD

On Mon, Jan 25, 2021 at 8:25 AM Scott - W5NJK via <w5njk=[email protected]> wrote:
After much machinations, I've got my node up and talking with my 6400 and FRStack, hand have configured the FRStack to the amp's USB serial port. (in my instance I have linked /dev/ttyUSB_AMP to /dev/ttyUSB0).

? ? "SPEComPort": "/dev/ttyUSB_AMP", // this is the Serial device for SPE AMP Control port (Not the CAT port)
? ? "SPETuneStandby": "false", // this will set SPE to STANDBY when TUNE is activated
? ? "SPEModeRestore": "false", // this will return SPE to OPERATE after TUNE complete
? ? "SPEOnAntenna": "0", // 0 or 1 or 2; 0 for both, 1 for ANT1, 2 for ANT2
? ? "SPEUseDTR": "false", // this will set DTR to power up amp
? ? "SPEProtocolV1": "true", // this is set true for SPE V1 amps
? ? "SPEAutoOpen": "false", // this is set true to OPEN SPE after connecting to radio
However, the payload coming out of the GetSPEINFO node is { empty }.? So it kind-of feels like I don't really have a serial connection to the amplifier.? Anyone have suggestions to try?




 

Scott

I have found pasting the path to the "by-path" serial link into the COM on the FRStack "appsettings.json" config works well to link to the correct serial cable.



Alan. WA9WUD


 

The amplifier is the only device I have plugged into the Pi, and??I did follow the instructions at the bottom of the wiki for assigning the link to the USB serial port (assigning ttyUSB_AMP by VID, PID, and SN).? I also just tried your method and I'm still getting the empty payload issue. And I'm using the ?built-in USB port (which does enumerate to an FTDI serial port), and not the "Port" connector which has the "remoting USF" serial interface.

This is a version 1 amplifier, but it does have the latest firmware.? I've tried setting the "SPEProtocolV1" to both false and true, though I think true is the correct setting.

Scott


 

¿ªÔÆÌåÓý

Baud rate issue?

73
Dave wo2x

Sent from my waxed string and tin cans.?

On Jan 25, 2021, at 10:06 AM, Scott - W5NJK via groups.io <w5njk@...> wrote:

?The amplifier is the only device I have plugged into the Pi, and??I did follow the instructions at the bottom of the wiki for assigning the link to the USB serial port (assigning ttyUSB_AMP by VID, PID, and SN).? I also just tried your method and I'm still getting the empty payload issue. And I'm using the ?built-in USB port (which does enumerate to an FTDI serial port), and not the "Port" connector which has the "remoting USF" serial interface.

This is a version 1 amplifier, but it does have the latest firmware.? I've tried setting the "SPEProtocolV1" to both false and true, though I think true is the correct setting.

Scott


 

¿ªÔÆÌåÓý

Reboot the amp and the pi.?


On Jan 25, 2021, at 10:06 AM, Scott - W5NJK via groups.io <w5njk@...> wrote:

?The amplifier is the only device I have plugged into the Pi, and??I did follow the instructions at the bottom of the wiki for assigning the link to the USB serial port (assigning ttyUSB_AMP by VID, PID, and SN).? I also just tried your method and I'm still getting the empty payload issue. And I'm using the ?built-in USB port (which does enumerate to an FTDI serial port), and not the "Port" connector which has the "remoting USF" serial interface.

This is a version 1 amplifier, but it does have the latest firmware.? I've tried setting the "SPEProtocolV1" to both false and true, though I think true is the correct setting.

Scott


 

¿ªÔÆÌåÓý

Both rebooted....

far as I can tell there's no config option for the baud rate in FRStack, and the amplifier is supposed to be auto-baud detecting...


On 1/25/2021 9:09 AM, David De Coons wo2x wrote:
Baud rate issue?

73
Dave wo2x

Sent from my waxed string and tin cans.?

On Jan 25, 2021, at 10:06 AM, Scott - W5NJK via groups.io <w5njk@...> wrote:

?The amplifier is the only device I have plugged into the Pi, and??I did follow the instructions at the bottom of the wiki for assigning the link to the USB serial port (assigning ttyUSB_AMP by VID, PID, and SN).? I also just tried your method and I'm still getting the empty payload issue. And I'm using the ?built-in USB port (which does enumerate to an FTDI serial port), and not the "Port" connector which has the "remoting USF" serial interface.

This is a version 1 amplifier, but it does have the latest firmware.? I've tried setting the "SPEProtocolV1" to both false and true, though I think true is the correct setting.

Scott
-- 
--- Sent with ProtonMail Secure Email ---


 

Scott

Since you have only one Com connection to the RPi, you can try to just use the default port path:

/dev/ttyUSB0

Next, Dave, WO2X, said to test the SPE amp USB port by downloading the SPE utility. ?Make sure the SPE amp and the Utility work OI, that way you know your USB connection is good.

And last, another ham on this list had the same equipment and problems you are having, and in the end said he found a later version of firmware, that solved his connection issues.. ? ?I forget who it was, so maybe they will see this and jump in.

Alan


 

Scott - Another thought.

Are you shutting down and restarting?FRStack after each change to the config file?

Shutdown Command. ? ??sudo systemctl stop FRStackWebApi

Start Command. ? ? ??sudo systemctl start FRStackWebApi

And then, make sure FRStack is running:

Status Command. ??systemctl status FRStackWebApi

Screen Shot 2021-01-25 at 12.37.14 PM.png

Word of caution.? FRstack will fail to start if there are any syntax errors in the appsettings.json config file.? Good to check FRStack is running.

Alan?


 

Yes I did do the restarting (even reboot, although I know it's overkill).

I have the spe utility running on my windows machine, I'm not aware on a Linux version.

Ill look again for a firmware update, and may try and see if using the remote serial interface works any different.

Thanks for all your help!


Sent from ProtonMail mobile



-------- Original Message --------
On Jan 25, 2021, 11:46 AM, Alan Blind, WA9WUD < a.alan.blind@...> wrote:

Scott - Another thought.

Are you shutting down and restarting?FRStack after each change to the config file?

Shutdown Command. ? ??sudo systemctl stop FRStackWebApi

Start Command. ? ? ??sudo systemctl start FRStackWebApi

And then, make sure FRStack is running:

Status Command. ??systemctl status FRStackWebApi

Screen Shot 2021-01-25 at 12.37.14 PM.png

Word of caution.? FRstack will fail to start if there are any syntax errors in the appsettings.json config file.? Good to check FRStack is running.

Alan?


 

¿ªÔÆÌåÓý

OK, with USB cable plugged into the PC the Windows version works.

?

Next, to confirm, you did move the USB to the Pi? Did you reboot the Pi after plugging in the USB? Not just restart FRStack. From the terminal prompt

sudo shutdown -fr now

?

73

Dave wo2x

?

?

From: [email protected] <[email protected]> On Behalf Of Scott - W5NJK via groups.io
Sent: Monday, January 25, 2021 1:02 PM
To: [email protected]
Subject: Re: [nodered-hamradio] Help with Modified MKCM SPE Amp.json

?

Yes I did do the restarting (even reboot, although I know it's overkill).

I have the spe utility running on my windows machine, I'm not aware on a Linux version.

Ill look again for a firmware update, and may try and see if using the remote serial interface works any different.

Thanks for all your help!


Sent from ProtonMail mobile



-------- Original Message --------
On Jan 25, 2021, 11:46 AM, Alan Blind, WA9WUD < a.alan.blind@...> wrote:

?

Scott - Another thought.

?

Are you shutting down and restarting?FRStack after each change to the config file?

?

Shutdown Command. ? ??sudo systemctl stop FRStackWebApi

?

Start Command. ? ? ??sudo systemctl start FRStackWebApi

?

And then, make sure FRStack is running:

?

Status Command. ??systemctl status FRStackWebApi

?

?

Word of caution.? FRstack will fail to start if there are any syntax errors in the appsettings.json config file.? Good to check FRStack is running.

?

Alan?


 

¿ªÔÆÌåÓý

yes that's correct.? I did sudo reboot not shutdown (but will have tried that by the time you read this :D )

Scott

On 1/25/2021 12:23 PM, David De Coons wo2x wrote:

OK, with USB cable plugged into the PC the Windows version works.

?

Next, to confirm, you did move the USB to the Pi? Did you reboot the Pi after plugging in the USB? Not just restart FRStack. From the terminal prompt

sudo shutdown -fr now

?

73

Dave wo2x

?

?

From: [email protected] <[email protected]> On Behalf Of Scott - W5NJK via groups.io
Sent: Monday, January 25, 2021 1:02 PM
To: [email protected]
Subject: Re: [nodered-hamradio] Help with Modified MKCM SPE Amp.json

?

Yes I did do the restarting (even reboot, although I know it's overkill).

I have the spe utility running on my windows machine, I'm not aware on a Linux version.

Ill look again for a firmware update, and may try and see if using the remote serial interface works any different.

Thanks for all your help!


Sent from ProtonMail mobile



-------- Original Message --------
On Jan 25, 2021, 11:46 AM, Alan Blind, WA9WUD < a.alan.blind@...> wrote:

?

Scott - Another thought.

?

Are you shutting down and restarting?FRStack after each change to the config file?

?

Shutdown Command. ? ??sudo systemctl stop FRStackWebApi

?

Start Command. ? ? ??sudo systemctl start FRStackWebApi

?

And then, make sure FRStack is running:

?

Status Command. ??systemctl status FRStackWebApi

?

?

Word of caution.? FRstack will fail to start if there are any syntax errors in the appsettings.json config file.? Good to check FRStack is running.

?

Alan?

-- 
--- Sent with ProtonMail Secure Email ---


 

Success!

And success using the USB cable!

The secret sauce was making sure that the "SPEComPort" setting had the complete device path! I don't know why that was so difficult, but thanks for everyone who helped.

Now it's time to see if I can get fancy!

Scott,?W5NJK


 

Scott

I am helping another ham with his SPE amp com port. ?Could you send me the Port config line you ended up with?

Alan


 

Sure thing - I found I had to use the whole port string "/dev/ttyUSB_AMP", where I've aliased /dev/ttyUSB0" to "/dev/ttyUSB_AMP" with the SN of the USB serial adapter.

Hope that helps
Scott


 

Hi i? have been trying to install??FRStack a windows 10 computer . what am i missing ? everything i found is? rasberryPi install .
I have node red running, with my dashboard , i added the??FRStack flow , and? i connect to my serial port SPE amp , i get? crazy error bugs flying all over :)?


 

Nick

Assume you have Node-Red installed on the Windows PC.

On the same PC, install FRStack Windows as a normal download and install.

You can command the Windows FRStack via Node-Red ?commands same as you command FRStack on a Raspberry Pi, with some differences:

Under the "Help" pulldown on FRStack, look for "View REST Help". ?You will see the Windows FRStack REST instructions. ?Of note, is the difference in the URL. ?The Windows port is 13522 vs 5025 for Raspberry Pi. ?Also, there is an extra "/api" following the port number. ?All other aspects of the command structure are the same, Windows vs Raspberry Pi.



So, in the "Set Parameters Here" node, you need to use:

"http://127.0.0.1:13522/api" in place of the raspberry pi?

Also, be sure to change the Web socket port number on the "meters" flow. ?No need to add the "/api for the meters web socket.



Another issue with Windows. ?If you try to access FRStack Windows REST commands outside the Windows firewall, you must make rules for the command to penetrate the firewall. ?There are instructions in the help file for making these changes.

Since you have both FRStack and Node-Red on the same Windows machine, there is no need to penetrate the firewall.....makes life so much easier.

Alan. WA9WUD


 

Also, for Windows Node-Red, if you shutdown the CMD prompt with the Node-Red Console, Node-Red will stop running.? You must restart the CMD prompt and issue the "nodered" command to restart Node-Red.

Dave, WO2X, was working on a way to have Node-Red start in the background.? Maybe?he can help here.

Alan
WA9WUD