JCI VMA-1620 - I'm not able to write setpoints to it.

[CtrlPuffer]

I am trying to integrate a number or these VAVs under a new Jace, they are currently on a Metasys system which is going away.
There are AHUs and VAVs. I can write to all setpoints on the AHUs, but on the VAVs I get faults when I try to write to setpoints like:
- Occ Cool Stpt
- Occ Heat Stpt
- Min Occ Cool CFM
- Max Occ Cool CFM

I only found one setpoint I could write to, something like ZoneSP. (but not Occ Cool Stpt, etc)

I have tried writing at different priorities, no luck.

Any ideas of what's going on here?
Thanks!

[Cagey57]

Try changing the "Present Value" field to "3113" and see if that works.

[CtrlPuffer]

hi KG,
Unfortunately, I'm no longer at the site but will make another visit before too long.
From the jace I've been trying to write a new value at various priorities with no luck.
Are you thinking the point may not have a pri array, and therefore those writes may not work?

I'm not sure how to write to the present value without a priority. Can you do that from workbench?

And while we're at it, is their significance to 3113?

thanks a lot!

[orion242]

I'm not sure how to write to the present value without a priority. Can you do that from workbench?

Ever use the fallback slot on a writable point? That's exactly what tridium does with BACnet.

And while we're at it, is their significance to 3113?

Its a little game JCI plays to waste your time. You need to change the property your working with to 3113 from present value and forget about priorities as they have nothing to do with your problem.

Try changing the "Present Value" field to "3113" and see if that works.

[CtrlPuffer]

ah ha. Glad I asked again as I didn't get it the first time.
Thank you both. So JCI invented property 3113 and uses it instead of the BACnet present value (I believe property 85)
I will certainly try that!

[CtrlPuffer]

The other impediment to moving the devices to the jace is that about 10 of the devices have device instance = 1.
Do you think the utility in workbench for changing device number will work on the JCI devices? Somehow I doubt it will, and I'm afraid to try it while the system is still operating under the old system. I'm pretty sure I could not set device instance back to device 1 with 9 other devices at that same instance number.

[orion242]

JCI's signature game....make all the instance's the same number.

Device instance is not writable, so you cannot just change in Tridium that I'm aware of. Could be another hidden property for this but I assume you will need PCT/CCT.

[CtrlPuffer]

they are good... I was thinking the instances probably could not be changed from "the outside."
I will see if we have those tools on the workstation. If not we may have to trash those devices, unfortunately.
Appreciate the good advice!

[bolt950rider]

Try changing the "Present Value" field to "3113" and see if that works.

What’s different about 3113?

If the point is an activity input or output the only way I’ve m known to change them was to change them to write on the relinquish default property instead of present value. Downside is overrides and then going back to auto does not put the values back.


Sent from my iPhone using Tapatalk

[CtrlPuffer]

thanks bolt, I'll test just using the relinquish default (fallback) of the actual point property 3113, and have a psuedopoint exposed to the user which can be locked etc. The psuedopoint will write to the actual point.

[legionrider]

Just to clarify, you need to change the point's proxy ext Property Id from the default of "Present Value" to "3113"

[bolt950rider]

Just to clarify, you need to change the point's proxy ext Property Id from the default of "Present Value" to "3113"

What’s 3113?
I’ve tried typing it in and got faults. However if i select relinquish default, that works.

Anyways I just make network inputs instead as they take overrides better.


Sent from my iPhone using Tapatalk