Closed datid closed 8 years ago
Moving Init Power
to the front of the line. Power should come on first anyway, not sure why I put it as almost last.... Probably just the order I worked on things in. Let's check this again.
OK...two solutions or both:
Pre Launch Init
to start of Actor Core
Power Actor
.I have done the first and I have started the second. Need to test the Actor Core
....
Moved main config to Actor Core
and made the config reentrant. Getting bad behavior now so will need to investigate this further...
Sooooo...latest fix broke the Pre Launch Init
for all devices. For whatever reason, the session references are getting dropped. Have looked at the configuration in the Actor Core
and there is no initial error propagating to stop the references from being no good. Other actors are writing to the log and configuring properly. Hmmmmm....
Almost there...data is not coming now but configuration is good.
So, set a couple of the VIs to reentrant (in the Device
actor) and now all seems to be working. This needs testing, but all of the device stuff is up now and everything is coming up much faster.
Think this is now sorted. Remaining issues with water chiller seems to be associated with the html commands not coming out of the UI correctly. Will raise these as separate issue and thus closing this one.
The TEC (meerstetter) power supply comes on after device configuration so config always fails.
There is a fix in Meerstetter_test branch. Is it the best way to do it - and is it the correct point in the sequence ? (Controller/Actor Core and Init Power affected)