Clarification of connecting an Extra Device as an external program while
using ModBus for ET/BT is below, and an update to the 0.9.9 branch from
Marko fixes a bug preventing the execution of the specified external
On 04/19/2016 01:08 PM, Marko Luther wrote:
On 19.04.2016, at 21:25, Dennison Williams
On 04/19/2016 12:02 PM, Marko Luther wrote:
The program name is specified at the bottom of
the ET/BT tab under "External Program". The Help button opens a dialog with some
text that explains how such a program should look like
Hope this helps,
This is helpful. The software is helpful as well. Thank you.
When using the most recent release 0.9.9 I have Modbus specified as the
meter, and my external program specified in the bottom of the ET/BT tab,
but the Program radio button is not checked. In the Extra Devices tab I
have program specified.
That would be the correct configuration.
I have tried to make the output of the program
only one number as well as ",,<number>" in case this use case expects
the number to be the 3rd CSV. But I still do not get the external
program data input displayed in the Roaster Scope window. The mutually
exclusive radio options on the ET/BT tab make me think that only one
sensor of a specific type can be configured from that tab. Any more
insight to resolving this issue would be helpful.
Those radio buttons are mutually exclusive as only one of those options can make it to
the main device returning ET/BT.
Still, the program path for the extra "program" is taken from the (not
selected) external program section. I should have written "should be taken" as I
just discovered, a typo in that code, which prevents to take the program path from that
variable and instead just uses the default "test.py".
I'll fix that and send you a build for testing. Which platform are you on? Windows or
Id attach screenshots, but I am not sure if that is appropriate for this
Artisan-User mailing list