grodansparadis
commented
4 years ago Hi sorry to here that you have trouble with it. I have several running with that setup here so it should work AFAIK.
if you can telnet into the remote daemon from the node-red machine and see the events when you issue "rcvloop" then something is definitly strange in the vscp-tcp-in. The only thing I can think of that could do this is the "filter" setting. If no filter is defined you should get everything. Is it setup like this
or do you have a filter defined?
/Ake
On 2020-08-24 07:15, JohanBraeken wrote:
I have a VSCP daemon (v14.0.4, latest release) connected to a CAN bus. The CAN bus is fully functional and VSCPworks displays all events on the CAN interface correctly.
I'm trying to get all VSCP events from this CAN bus into Node-RED through the "vscp tcp in" node. (v1.2.1, on Node-RED 7.1.0) However, it seems I only get events originating from the VSCP demon itself. (Heartbeat, Node_heartbeat, and SEGCTRL_hearbeat.)
As described on https://grodansparadis.com/wordpress/?p=4517 I assume I should be able to see the VSCP events from the CAN bus.
Node-RED and the VSCP daemon are not on the same machine, however the connection seems OK. Investigating the traffic between both systems reveals all events from the CAN bus are effectively forwarded from the VSCP daemon to the Node-RED system after the "rcvloop"-command is issued, so it looks like these messages are filtered on the Node-RED side.
Playing with the interface setting on the node configuration doesn't seem to make any difference. Specifically setting the interface to the CAN interface of the VSCP daemon, still gets me the VSCP events from the daemon itself, and not the events on that interface. Even when setting the interface to one where there shouldn't be any traffic, I continue to get the events from the daemon itself. So I suspect something is not working correctly.
How can I troubleshoot this further?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/grodansparadis/node-red-contrib-vscp-tcp/issues/3, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKLYI7K4M5FEOQD3QMVCTTSCHZOBANCNFSM4QJDBRCQ.
-- Be Hungry - Stay Foolish! Åke Hedman, Grodans Paradis AB / Paradise of the Frog Brattbergavägen 17, 82050 LOS, SWEDEN, +46 8 40011835 http://www.grodansparadis.com http://www.vscp.org http://www.akehedman.se
JohanBraeken
I have a VSCP daemon (v14.0.4, latest release) connected to a CAN bus. The CAN bus is fully functional and VSCPworks displays all events on the CAN interface correctly.
I'm trying to get all VSCP events from this CAN bus into Node-RED through the "vscp tcp in" node. (v1.2.1, on Node-RED 7.1.0) However, it seems I only get events originating from the VSCP demon itself. (Heartbeat, Node_heartbeat, and SEGCTRL_hearbeat.)
As described on https://grodansparadis.com/wordpress/?p=4517 I assume I should be able to see the VSCP events from the CAN bus.
Node-RED and the VSCP daemon are not on the same machine, however the connection seems OK. Investigating the traffic between both systems reveals all events from the CAN bus are effectively forwarded from the VSCP daemon to the Node-RED system after the "rcvloop"-command is issued, so it looks like these messages are filtered on the Node-RED side.
Playing with the interface setting on the node configuration doesn't seem to make any difference. Specifically setting the interface to the CAN interface of the VSCP daemon, still gets me the VSCP events from the daemon itself, and not the events on that interface. Even when setting the interface to one where there shouldn't be any traffic, I continue to get the events from the daemon itself. So I suspect something is not working correctly.
How can I troubleshoot this further?