grodansparadis / can4vscp-frankfurt-rs232

CAN4VSCP Frankfurt RS-232 module

Åke Hedman, Grodans Paradis AB, Sweden ✨

✨ VSCP project home: https://www.vscp.org

✨ Grodans Paradis AB home: https://www.grodansparadis.com

✨ VSCP project blog: https://www.grodansparadis.com/wordpress

✨ My Swedish blog: https://www.akehedman.se

✨ My "music": Spotify

can4vscp-frankfurt-rs232's Issues

Addera info till github

rreg count?

Does it work?

Add "always open" mode.

Scenario 2

1. The test rig is powered on and the daemon and VSCP Works are started.
   

2. Events (temperature measurements) are received in the VSCP Client window.
   

3. The power from the Frankfurt module is powered off and 2 seconds later on.
   

4. No temperature events are received. // I waited > 10 minutes
   

5. VSCP Works is closed and the Daemon is restarted.
   

6. The Daemon reports a driver failure for the Frankfurt module (see attached pic).
   

7. The Frankfurt module is powered off and the daemon is closed.
   

8. The Frankfurt module is powered on and the daemon is started. The driver is successfully loaded.
   

9. VSCP Works is started and the temperature events are received in the client window.
   

10. The scenario does NOT always happen when I cycle the power on the Frankfurt module.

Find command works after close

Find command works also after close command but not before first open.

rreg/wreg show node id

Show node id for rreg and wreg operatiions.

Hang!?

This happened one time: I tried to enable the DM row with the context menu (a test for the observation above) and I got the update error message. Normally “closing and opening” the Device Configurator fixed the problem. But this time, when I initially tried to update the registers, an error was displayed: Failed to read standard registers of device. When I tried to scan for the devices (through the daemon) no devices where found. But the strange thing is that all events (temperature and buttons) where still received (in the VSCP Sessions window). ???

Attempts to fix this (chronologically:

1. Restarting VSCP Works did not work.
   

2. Restarting the daemon resulted in a “Failed to open driver. Will not use it!” message
   

3. Restarting the daemon resulted in a “Failed to open driver. Will not use it!” message
   

4. Restarting the daemon resulted in a “Failed to open driver. Will not use it!” message
   

5. Stopping daemon and cycling the power of the Frankfurt module and restarting the daemon
   

6. Scan found 2 devices.
   

Info is displayed for invalid node.

Should not display info for invalid nodes.

Major problem where protocol of module sync out

In some situations after a time of use the module appears to go into a state where the driver no longer can talk to it. Inspected binary data of some form is received.

Find command hangs if node is alone

If the node is alone on the bus the find command hangs

Possible false reset (Brown out?)

Some observations regarding the disconnected status when a module is powered off/on.

Layout

A Frankfurt module is connected to my computer (COM2).

The Frankfurt is connected with a CAT5 cable to a Beijing module.

The Beijing module is connected to a Kelvin module with a inter module connector.

All three modules are connected a piece of wood (test rig), so all cables are short.

Scenario 1

1. The test rig is powered on (with a reliable power supply). Daemon and VSCP Works are started.
   

2. The Kelvin module sends some temperature measurements. Those are visible in a VSCP Client window “connected” to the daemon.
   

3. I had some strange behavior from the buttons connected to the Beijing module, but basically those events are received to.
   

4. When I pull the RJ45 connector from the Beijing module this happens:
   

a. Beijing and Kelvin module are powered off.

b. The Frankfurt module stays online.

c. No surprise but: No temperature or button events are received.

1. When I attach the RJ45 connector, the Beijing and Kelvin modules are powered on.
   

2. No events are received any more in the VSCP Client window except some heartbeats (not from the modules) and a SEGCTRL_HEARTBEAT. // I waited > 10 minutes
   

3. If a device scan is performed, no devices are received.
   

4. When the Frankfurt power is cycled, the situation stays the same.
   

5. When I restart the Daemon all messages are received.
   

6. The scenario does NOT always happen when I cycle the power on the Beijing (and Kelvin) module.

Single frame VSCP not implemented