Keyboard Shortcuts
Likes
Search
Frstack running fine until I enable the SPE part
I have my expert connected to usb port on the Raspberrypi I get this from /dev/serial/by-path...... /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3:1.0-port0 I have entered that to the SPEComPort in appsettings.json and set the SPEProtocolV1 to true as it is an early version of the 1.3K-FA .I get The following warning from the node-red console [http request:GetSPINFO]? JSON parse error, if I disable the spe flow the error disappears. What am I missing?
Everything else in the frstack flow appears to be working as far as flex control meters etc. The expert is working fine via the FTDI serial cable with windows. Thanks in advance for any help. Cheers Paul |
Paul Your path looks good, except paste in the path to the "by-id" link of the FTDI cable. This is what my FTDI cable looks like.? Your FTDI cable number will be different. /dev/serial/by-id/usb-FTDI_UT232R_FT44JLEC-if00-port0 Alan On Tue, Feb 23, 2021 at 1:26 PM Paul Menown <pako20@...> wrote: I have my expert connected to usb port on the Raspberrypi I get this from /dev/serial/by-path...... /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3:1.0-port0 I have entered that to the SPEComPort in appsettings.json and set the SPEProtocolV1 to true as it is an early version of the 1.3K-FA .I get The following warning from the node-red console [http request:GetSPINFO]? JSON parse error, if I disable the spe flow the error disappears. What am I missing? |
Hi Alan,
I have pasted the by-id into the appsettings file it now reads?/dev/serial/by-id/usb-FTDI_USB_Serial_Converter_FTGCBLZT-if00-port0? ?but I am still not getting anything as far as information from the amp. I get the message there are some unused configuration nodes when i deploy when i check for unused nodes it says 2 hidden beside the spe Amp. Do i need to put any info in the SPEINFOUrl ? |
Here is my Appsettings.
?"SvcConfig": {
? ? "AutoConnect": "true",
? ? "initRadioName": null,
? ? "initClientName": null,
? ? "MRUMatchDelta": "0.000999",
? ? "FollowActiveSlice": "true",
? ? "MuteOthersOnSliceActive": "false",
? ? "EnableTxOnSliceActive": "false",
? ? "TempUnitInF": "true",
? ? "PgxlTuneStandby": "true", // this will set AMP to STANDBY when TUNE is activated
? ? "PgxlModeRestore": "true", // this will return AMP to OPERATE after TUNE complete
? ? "PgxlRadioMaxPower": "50", // this is MAX radio power level when AMP is OPERATE
? ? "PgxlRadioStandbyPower": "100", // this is MAX radio power level when AMP is STANDBY
? ? "PGXLOnAntenna": "0", // 0 or 1 or 2; 0 for both, 1 for ANT1, 2 for ANT2
? ? "RCATXACCTuneDisable": "false",
? ? "RCATX1TuneDisable": "false",
? ? "RCATX2TuneDisable": "false",
? ? "RCATX3TuneDisable": "false",
? ? "RadioTuneModeDetect": "true", // this is set true if you want to detect a Radio Tune button push, remember to set TX Delay on radio
? ? "SPEComPort": "/dev/serial/by-id/usb-FTDI_USB_Serial_Converter_FTGCBLZT-if00-port0", // 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
? ? "SteppIRComPort": ",9600,None,One,0,false,true,1,2", // port,baud,parity,stop,FollowAntInt,EnabledBool,SyncManualBool,AntTxInhibitInt,AntType eg. "/dev/ttyUSB0,9600,None,One,0,true,true,1,1"
? ? "FDXProtect": "false,false,false,false,false,false", // enabled,ant1,ant2,rxa,rxb,wide
? ? "UDPSettings": "false,255.255.255.255,12070,false,127.0.0.1,12071,false,127.0.0.1,12072,false,127.0.0.1,12073", // enabled,IPADDR,PORT, enabled,IPADDR,PORT, enabled,IPADDR,PORT, enabled,IPADDR,PORT?
? ? "UDPMeterSettings": "false,255.255.255.255,12270,false", // enabled,IPADDR,PORT,SMeterEnabled
? ? "ModeSetsDax": "0", // 0 - Disable, 1 - turn DAX on when mode is DIGL/H, 2 - turn DAX off if not DIGL/H, 3 - both
? ? "CustomFunctions": "",
? |
Paul Com?looks good. I would next try making "SPEProtocolV1". ? "false" I am not knowledgeable on all aspects of the SPE versions, but I have set up three other hams with SPE1.3K amps and we used "false" in all cases. (for the 1.3K). Last, check that you have the latest firmware for the amp.? It needs to be the latest version. Alan WA9WUD Alna On Tue, Feb 23, 2021 at 4:50 PM Paul Menown <pako20@...> wrote: Here is my Appsettings. |
¿ªÔÆÌåÓýMy amp is also a series 1 but that does not matter as it is a 1.3K so it uses the same protocol for all 1.3, 1.5 and 2.0 models. ? Mark ? From: Paul Menown
Sent: Tuesday, February 23, 2021 4:07 PM To: [email protected] Subject: Re: [nodered-hamradio] Frstack running fine until I enable the SPE part ? Mark, if you check here??? ? |
¿ªÔÆÌåÓýI will be releasing an update to FRStackWebApi shortly for all platforms. This updates the SPE Amp serial port logic to address an issue that showed up when I switched to .NET 5. In the meantime RPi 32bit users can download? ? 73, Mark W3II ? ? From: Alan Blind, WA9WUD
Sent: Tuesday, February 23, 2021 5:22 PM To: [email protected] Group Moderators Subject: Re: [nodered-hamradio] Frstack running fine until I enable the SPE part ? Paul ? Com?looks good. ? I would next try making "SPEProtocolV1". ? "false" ? I am not knowledgeable on all aspects of the SPE versions, but I have set up three other hams with SPE1.3K amps and we used "false" in all cases. (for the 1.3K). ? Last, check that you have the latest firmware for the amp.? It needs to be the latest version. ? Alan WA9WUD ? Alna ? On Tue, Feb 23, 2021 at 4:50 PM Paul Menown <pako20@...> wrote:
? |
Paul Try using the default USB port path.? This will work if you have one USB cable.? Debian will assign USB0 to the first cable and then each additional cable in sequence: /dev/ttyUSB0 Did you verify your SPE1.3 Firmware is up to date? If this does not work, can you send us a screenshot or duplicate of your appsettings.json file? Alan On Wed, Feb 24, 2021 at 6:54 AM Paul Menown <pako20@...> wrote: I updated to FRStackWebApiRPi_3_1_27_56 |
Paul And, just in case you are not doing so, shutdown and restart FRstack?after making config file changes.? Following the restart command, verify FRStack starts up. Shutdown. ? ?sudo systemctl stop FRStackWebApi Restart. ?sudo systemctl start FRStackWebApi Status. ??systemctl status FRStackWebApi Alan On Wed, Feb 24, 2021 at 7:09 AM Alan Blind, WA9WUD via <a.alan.blind=[email protected]> wrote:
|
I Checked the amp firmware, it has the same date but has B_15s at the end rather than C_15s
the page advises only to update if the date is earlier so I am reluctant to update. Not sure if that would have an impact. Also do i need to port forward 5025 to the pi, as It just doesn't seem to be reading the usb0 port at all. Although the usb port is working if i connect via virtualhere server on the pi and run the windows client the usb control panel works perfectly. ?Almost no hair left hihi and xyl complaining about the amount of time I have spent on this.. Also I appreciate all the help from the group, mainly yourself and others. Paul GI4FZD |
Paul You have introduced new variables, which I cannot comment on all. Your question about opening port 5025.? Not sure how that enters into your configuration.? Normally, TCP Port 5025 is used by FRstack.? Do you mean opening up port 5025 on your router?? I cannot think of any reason to do so. How does "Virtual Here" enter into your configuration?? Are the SPE amp and the device running FRStack not connected with a USB cable, or are you using a virtual USB port?? If yes, I cannot help you with that configuration.? Or, perhaps?Virtual Here is causing the USB ports to not work alongside?FRStack using USB ports?? Others can comment on that. ??My responses to you have been based on the SPE amp connected directly to the device running FRStack via USB cable and no other apps using?or configuring the device's USB ports. Alan? On Wed, Feb 24, 2021 at 8:29 AM Paul Menown <pako20@...> wrote: I Checked the amp firmware, it has the same date but has B_15s at the end rather than C_15s |
Paul I cannot help you any further because I lack knowledge of your configuration (virtual here).? Perhaps others can comment. Another approach is to build a separate?Raspberry Pi SD card dedicated only to FRstack and Node-Red.? That is the configuration?that I have had success in configuring the SPE1.3K amp.? We can use that SD card to "eliminate" unknown?variables that other apps you are using may be causing. I am available via ZOOM if you like to help you build a new SD Card.? Since you are in Europe, anytime between 1700 and 2200 GMT is best for both of us. Alan On Wed, Feb 24, 2021 at 9:27 AM Paul Menown <pako20@...> wrote: Virtual here is not running I only used it to check communication with the amp via the pi.. It is not in the equation when running node red or frstack.? |
Thanks Alan for the offer, but i finally got it running.
I didn't realise that you had to hit the open button on the spe dashboard to get it to read the serial port, it is all now working as it should..? Once again I appreciate all the help the protocol is set to false and the com port contains the By-id path. Cheers Paul GI4FZD |
¿ªÔÆÌåÓýHi Paul, ? Thanks for letting us know. I fo have any pointers since it is fresh in your mind please let me know. I can add a SPE section to the WiKis to help the next person. ? 73 Dave wo2x ? ? From: [email protected] <[email protected]> On Behalf Of Paul Menown
Sent: Wednesday, February 24, 2021 12:36 PM To: [email protected] Subject: Re: [nodered-hamradio] Frstack running fine until I enable the SPE part ? Thanks Alan for the offer, but i finally got it running. |