Closed tukusejssirs closed 1 year ago
Sure, we could make a veneer for this. I think this is where a Lua collector would make sense since it does not require a recompile and the PMC tags are vendor implementation specific. The "report by exception" requirement is also possible, we just have to manage the data differently inside the veneer.
We also need the address type and number for each one of these https://docs.ladder99.com/focas-api/pmc/pmc_rdpmcrng.xml.
I can assume that Y2.2 is second bit of address 2 of type Y, but I do not know what AL.L3 is.
On track for 0.7 using PMC collector.
Next Docker build should happen next week.
@MRIIOT, the generated devices.xml doesn't has the above macro and pmc variables. I am able to see macro and pmc data being fetched in the trace log. Please guide how and where to add macro variables in the generated devices.xml
Related #21, #4
It would be awesome if we would gather the stack lights status (if the colours are on or off).
ATM I am not at the machines (I’ll be next week), but based on the photos I took from the Fanuc screens, the table below contains all the possible numbers of the individual colours from the ladder diagram on the machines I have access to.
If you need the machine vendors/models and/or whatever, just ask for it (I can get the info next week), however note that the numbers are not the same across machine vendors nor accross model series of the same vendor).
Implementation suggestions
fanuc/{machine}/light_indicator
), e.g.:{data: {green: true, yellow: false, red: false}}
.green
turns off andyellow
turns on →{data: {green: false, yellow: true}}
).