开云体育

Bret, try to select by ID as I have shown in my previous email. Also on the command line run this wile plugging the USB device in and out to see which ones come and go: watch ls /dev/serial/by-id/

That is the same Cable as I am using, and the latest Flow from Daves Group.io I have several COM ports listed not after playing around with the WN2 Watt Meter and making sure the FTDI driver worked

Ok. I have no serial devices. 73 Dave wo2x Sent from my waxed string and tin cans.

Yes. I have it auto ranging plus ability to select range of bar graph manually. The numeric readout is always auto range. You can also select auto scan, sensor 1 or sensor 2. The button background

I no longer use the serial to TCP converter. If I were I would use the TCP in and out nodes. I am now hard wired from the W2 to the Pi as described above Using Elecraft serial to USB FTDI cable. The

Dave, I use auto range and and sensor scan in my code. That way I don't have to worry about which sensor is active at the time. 73, Andreas, N6NU

My experience is that it is best to specify the serial port by ID This is especially helpful when using more than one serial adapter or multi serial adapter on the same Pi. It will protect your setup

Works for me using serial to USB FTDI cable.

Resending Bret. Use these settings. Instead of the TCP in and TCP out nodes, use the TCP Request Node. It has an input and an output, just substitute for the TCP in and the TCP out. Here is a

Actually I believe he will want to use serial on and out. I do not believe I have seen a serial request node. He is not using a serial to IP adapter. Baud rate should be 9600,8n,1 Dave wo2x Sent from

I’ll be available tomorrow and Alan has added a few tweaks to the W2 flow. Give me a call in the morning. I will be up since two hours ahead of you Once I verify Alan’s changes on Bret’s W2 I

You say the usb cable shows as connected. Good Linux found the USB port. Use the same USB port with the settings I sent you, and use the TCP Request node instead of the two TCP in and TCP out nodes.

Yep tried that I am now testing on the bench using the Windows App and all work A-OK, Just wondering do I have to set the COM port serial number in Linux anywhere? also what baud rate does the W2

Also, if that does not work, do as I did Instead of the TCP in and TCP out nodes, use the TCP Request Node. It has an input and an output, just substitute for the TCP in and the TCP out. Here is a

Bret- Re-boot the Pi, then if nothing, power cycle the W2 (unplug, plug back in). Alan WA9WUD

Hi Dave, Hay got the Elecraft W2 Wattmeter today and got it plugged in with the included USB serial cable BUT I am not getting anything coming out of the W2 to the FLow wonder when you have a minute

Hi Kevin, Check out my flows in the file area on this group’s site. Read the readme which describes additional nodes you need to install and how to do it. Feel free to load up one of my flows to see

I just got Node Red installed on my Raspberry Pi3 now to figure out my first project!!!!! Kevin w4kjp

I posted a rough How To in a previous message on setting up the Pi with Node Red. You can find archieved messages at /g/nodered-hamradio 73 Dave wo2x

Looks like a great group starting up. Now to get my Rpi3 running node-red! Thanks - Gordon N1MGO