After a very enjoyable 2 hours with the youtube guide I started to think about what I wanted to do with my dashboard. I have very few accessories, no rotator, no amp.Just a IC7300 and a cloud based logging system called Cloudlog. this gives me an to connect to my log. Should be simple, right?

Well I've tied myself in knots. I tried to connect using the KD4Z flow after adjusting the command sent to receive the frequency (If I send FEFE94E003FD I should get a response like FEFEE0940300000007). I'll need a corresponding command for mode and maybe a few other odds and sods like power and stuff like that from the meters but for now just Frequency.

I get an error with a permission denied initially but a unplug and plug seems to help that. Actual error is:

"[serialconfig:919d09e7886da906] serial port /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_IC-7300_03007370-if00-port0 error: Error: Error: Permission denied, cannot open /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_IC-7300_03007370-if00-port0"

I notice that the serial out is doing what it should but it is reporting 'not connected' on the serial in. I could do with a bit of help please.

Machine is Ubuntu with node red all happily running as a snap. I'll transfer it all to a RPi at some point, but for now some basics first. I've attached the flow as it currently stands

73

g7kse

ok, got the serial error sorted. Something to do with permissions in snaps on Ubuntu. Easiest thing was to use a spare RPi and set that up (I was going to do that at some point anyway). Connection made but errors crop up with function nodes now.

This is happening on a couple of nodes now so there must be some kind of issue that needs resolved there too.

Alex

开云体育

I don’t have Icom but guessing.?

Alex,

Can you post a screen shot of the Debug outputs showing the msg.payload going into and out of the Function node throwing the errors, and what is actually in that Function node?? You attached my sample with only one Function node.? If that is the function that is throwing errors, I would think it is due to the payload length is different than what my sample code was written for. (IC-706 / IC-725)?

Warren, KD4Z?

Evening Gents,

The IC7300 has a whole host of rig settings that work in one scenario and not in another. The setup for N1MM isn't happy with the Fldigi one for example. I'm not entirely convinced the rig setup is not 99% of the issue here. I wasn't getting any output on the serial in node until I changed something on the rig. Also when I changed the parse C-IV node RADIO_ADDR to 0x94to match the 94h in the 7300 it gives an error. Oddly enough I have a similar error on another unrelated flow.More investigation required there I think.

Anyway. Here's a couple of screen shots. First is the debug from CI-V Get Freq, Second shows the whole flow and output from Serial In. There is no output from the final debug which leads me to think that the outgoing serial message is ok but Icom magic is killing something

So a little more progress, only not using this flow

I wanted to make sure that there wasn't something missing with the rig so using rigctld I can set a session up on the RPi and can connect to it using a TCP node and can get the data I'm after from the rig. Perhaps this is the right way to go (Hamlib rather than direct connection). Not managed to find the time to 'set' the rig to do something using a button on the dashboard. I'll have to figure that out as I'll want several settings to be changed with one button. A bit like a macro I suppose.

As a none programmer I'm getting the hang of this, although some of the html / css & javascript is a bit tough going for now. Hopefully I'll get there, mainly doing it by trial and error and by hacking around with other people's flows

Alex,

I loaded in your flow, changed the CI-V address to match my IC-7610 and ran it. I don't know why you are getting permission denied errors. That often implies that another program is attempting to access the serial port or has control of the serial port already. However, your Serial Node is not configured properly. It should look like the attached screenshot. You can ignore the Serial Port and Settings sections, those will be different than yours. What is important is the Input section. That should match what I have. Once I made that change, your flow started working for me.

I am using an FTDI USB to CI-V serial cable rather than the built-in Silicon Labs interface. That interface connects to my logging program directly. However, the Silabs interface will work the same once you fix the Input section.

73,
Scott
AK5SD

Thanks Scott,

I'm 99% sure the permission thing is a Ubuntu snap 'feature' if I get the strength I'll see what I can do to fix it. Interestingly I didn't have the 0xFE and 0xFD in the boxes I'll give that a try when I'm back home. I'm sure it was close to working but not quite there.

Alex