Download all fails after assigning terminal to temperature input

[MatthewBurkhart]

When I create an analog input (Temperature Input) and do a download all, download is successful.

When I configure the engineering units and sensor type and do a download all, download is successful.

When I assign the terminal to UB1 on a MP-C-24A and do a download all, download fails.  

If I take the point out of service and download all, download is successful.

If I place the point back into service and download all, download fails.  

The error looks to be write access denied:

INFO [19:30:54 23-Sep-20 EDT][schneiderMPX] Download All -- > Started.
INFO [19:30:54 23-Sep-20 EDT][schneiderMPX] Deleting the object(s) from MPX Controller[MP-C-24A].
INFO [19:30:54 23-Sep-20 EDT][schneiderMPX] Creating the object(s) into MPX Controller[MP-C-24A].
INFO [19:30:54 23-Sep-20 EDT][schneiderMPX] Object [Temperature Input] creation status [Already present on controller].
INFO [19:30:54 23-Sep-20 EDT][schneiderMPX] Downloading the object(s) into MPX Controller[MP-C-24A].
SEVERE [19:30:54 23-Sep-20 EDT][schneiderMPX] Error while downloading object[Temperature Input][10-MPX-TemperatureInput].
Cannot write property [presentValue] in [Temperature Input]:
Property:Write Access Denied
at com.tridium.bacnet.stack.transport.BBacnetTransportLayer.sendConfirmedRequest(BBacnetTransportLayer.java:483)
at com.tridium.bacnet.stack.transport.BBacnetTransportLayer.sendConfirmedRequestSimple(BBacnetTransportLayer.java:339)
at com.tridium.bacnet.stack.client.BBacnetClientLayer.writeProperty(BBacnetClientLayer.java:1163)
at javax.baja.bacnet.BBacnetObject.writeProperty(BBacnetObject.java:985)
at com.tridiumx.ps.schneider.config.util.Helper.lambda$downloadObject$2(Helper.java:407)
at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
at java.util.stream.ReferencePipeline$Head.forEachOrdered(ReferencePipeline.java:590)
at com.tridiumx.ps.schneider.config.util.Helper.downloadObject(Helper.java:349)
at com.tridiumx.ps.schneider.device.BDownloadAllObjectsJob.lambda$run$4(BDownloadAllObjectsJob.java:210)
at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
at java.util.stream.SortedOps$SizedRefSortingSink.end(SortedOps.java:352)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.forEachOrdered(ReferencePipeline.java:423)
at com.tridiumx.ps.schneider.device.BDownloadAllObjectsJob.run(BDownloadAllObjectsJob.java:204)
at javax.baja.job.BSimpleJob$JobThread.run(BSimpleJob.java:85)

INFO [19:30:54 23-Sep-20 EDT][schneiderMPX] Downloaded object[Temperature Input] in controller[MP-C-24A].
INFO [19:30:54 23-Sep-20 EDT][schneiderMPX] Downloaded object[deviceObject] in controller[MP-C-24A].
INFO [19:30:54 23-Sep-20 EDT][schneiderMPX] Downloading the object's bindings(s) into MPX Controller[MP-C-24A].
INFO [19:30:54 23-Sep-20 EDT][schneiderMPX] Bindings are downloaded for [Temperature Input] in controller[MP-C-24A].
INFO [19:30:54 23-Sep-20 EDT][schneiderMPX] Download All -> Completed.

[Jim_Okapal]

Matt,

I tended to get this error on the binary values when i've corrupted the object setup in some way.

What i had to do was go to the Config Folder Manager, discover the point, make sure it's

grayed out at the top display and solid at the bottom display, highlight the bottom object,

delete the point using the button at the bottom of the page. 

If the object was not grayed out at the top, then bring it into the bottom half of the section.

Then highlight the new object and delete along with anything else that aren't the standard

objects.

Perform a download all for only the basic controller with no new objects to make sure the

application manager is giving you good information. If this still fails, make sure to repair

host by right clicking on the device and choosing it.  Also ping it.  Make sure the properties

page says it's online.  I've even seen it say online and fail, but a ping has tended to get

the ball rolling.  

I've noticed that the first object i create in a brand new initialized controller has the hardest

time getting going.  If i repair host and ping, download all and just make sure the core objects

are reading good, then it's been smooth sailing to create your first Input/Output

[MatthewBurkhart]

Thanks for your input.  I did as you said and deleted the point as described.  I pinged and repaired hosting.  I then tried to repeat the procedure I used before: downloading after each step.  Download All failed when I assigned UI1 to the point.  Once there I cannot download all anymore, even if I delete the termination.  Thanks, Matt

[Jim_Okapal]

As a curiosity, which firmware version is in the MPC-24 at?

As an experiment last week, there was an MPC-24 that l

tried from factory firmware and it was acting pretty badly for

point additions. After that, i upgraded to the 3.2 version of 

firmware and it cleared up.  The bad news is that i had to

get EBO 3.2 all loaded up, and then got the MPC firmware

upgraded by those means.  I was getting access errors as

well from the old firmware.

Are you hosting from the N4 Supervisor or the Jace8000?

The Jace8000 definitely won't work at the current time.

[MatthewBurkhart]

The firmware is at 3.2.  I've been factory resetting the MP-C-24A via Ecostruxure to clear out the database.  I am using the Vykon Version of Niagara 4.8 if that makes a difference. 

[Jim_Okapal]

From my understanding, the Vykon is basically the same Jace as

the Schneider version...so that part should be ok.

When I did the factory clear, I had hit the reset button for about 25 seconds.

Anything over 20 seconds does the full clear-out.   Does your MPC-24 have

the display on it?   I used it on mine to make sure I was doing a full reset

based on what it was showing me.  

Not positive if the EcoStruxure reset vs the Reset button has a difference

or not, but I know this is for sure one difference I can note.

[Jim_Okapal]

Matt, 

I'm typing a 2nd post to the one above in case you saw It before I can edit it.

For the Ecostruxure side, do you have it disconnected from the same network

that everything else is on or cleared out the original hosting from that workstation

listing?   I'd be curious that if the ecostruxure side is totally removed from the network,

if it clears up.  Maybe old hosting information in the EBO side station is hanging up 

the Niagara side.

If both the Workstation and N4 Supervisor are on the same computer, I had shut down

the EBO station and made sure its service had stopped before enabling the Niagara

service in the Windows control panel.

You also mentioned about choosing "UI1" in a later post.   I kind of glossed over that, but

are you sure there still aren't choices for Ub inputs and Uc inputs?   UI1 is more related

to the Vav controller profile.  

[MatthewBurkhart]

I am using an AS-P to reset the MPX.  I have removed it from the network after the reset.  I did mean Ub1 - sorry.  I think the error has something to do with writing the present value.  I get write access denied.  

[RandyDavis]

When you add the input to the wiresheet it is set out of service.  Selecting a terminal reference and saving will set the Out of Service to false and now you cant write to the object.  If you set the object back Out of Service and do the download all, it will work.

[ChrisHoward · Accepted solution]

I think we may be able to resolve this issue by asking Tridium to exclude Present_Value for input objects during the download operation.  Understanding 'input' object types are intended to provide values from equipment and are only writable when out-of-service is TRUE, I can't see a use-case that would require the need to write Present_Value for an input object during a download operation.  Of course, the user could still write Present_Value to the controller through the property sheet (assuming out-of-service is TRUE, of course).