Plugin organization - device w/ 2 interfaces

[timbutler-um]

I have a device with 2 serial interfaces that I am controlling with a COSMOS5 plugin. I was looking for some advice on how to organize my plugin.

My take is that each serial interface would be represented by a separate TARGET, with a corresponding INTERFACE defining its specific serial connection details. Following the example of the demo plugin, I would define 2 TARGET folders under the top level targets/ folder. Command and telemetry packets, which are specific to each serial connection, would be defined therein.

However, I had to write a Protocol module to handle some specific details of my serial interface, which is exactly the same for both target connections. Instead of duplicating this module to the lib/ directory of each target, is there some way to share it across targets?

Thanks,
Tim Butler

[ghost]

Hi Tim,

You should be able to place the Protocol in a top level "lib" folder in the plugin and have it work. Try that and let us know how it goes.

[timbutler-um]

Hi Ryan,

Thanks for the suggestion. Unfortunately, it didn't seem to work. Just to make sure I tried this correctly, here's the pertinent content of the plugin directory. Both the DIAG and IDSC targets attempt to use the protocol under the top-level lib/ directory.

plugin.txt
lib/
  checksum_protocol.rb
targets/
  DIAG/
  IDSC/

The plugin load fails, with these ERROR messages in the log:

DEFAULT__INTERFACE__IDSC_INT	Unable to require checksum_protocol.rb due to cannot load such file -- checksum_protocol.rb. Ensure checksum_protocol.rb is in the COSMOS lib directory.
DEFAULT__INTERFACE__DIAG_INT	Unable to require checksum_protocol.rb due to cannot load such file -- checksum_protocol.rb. Ensure checksum_protocol.rb is in the COSMOS lib directory.

Short of any other suggestions, I'll just duplicate the Protocol into each target's lib/ directory.

Thanks again,
Tim

[finchlt]

I'm having a similar issue with a custom protocol. Tried this as well with no luck.

[ryanmelt]

This should work with the latest 5.0.5 release. Are you guys on that?