Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't reset (or send NULL) to an analog_value #36

Open
beodoble opened this issue Feb 21, 2024 · 0 comments
Open

Can't reset (or send NULL) to an analog_value #36

beodoble opened this issue Feb 21, 2024 · 0 comments
Assignees
Labels

Comments

@beodoble
Copy link

Which node-red-contrib-bacnet version are you using?

0.2.7 running in Raspberry pi 2

What happened?

Frankly speaking I'm not sure if this is a bug or not. I want to reset (write NULL) in analog_value property (85: present_value) in priority 8 (manual operation). When sending a blank instead of any value for APP_TAG 4 (REAL) I would expect to remove the value in the priority array, but instead appears 0.

How can this be reproduced?

I successfully read and write properties to different analog_values in my bacnet device (PLC). I always modify property 85 (present value) with priority 8 (manual operation). The issue comes when I want to "reset" this value and remove the value in that position of the priority array. From the bacnet documentation, I understand I have to send NULL to that paticular property and priority, which is indeed what I successfully do with YABE (Yet Another Bacnet Explorer); I simply select property 85 and priority 8 and leave the value to write in blank. When I replicate that in nodered the value written is 0, not null or void, which is not equivalent. I have tried sending directly APP-TAG NULL but I receive this error: "Error: getEnumName() can only be passed an integer value, was given "NaN"". I also tried to send literally NULL as value for REAL type but I receive a timeout error. Is this a bug or am I not understading how to use the write function?

Many thanks for the work done!

What did you expect to happen?

No response

Other Information

No response

@beodoble beodoble added the bug label Feb 21, 2024
@biancode biancode self-assigned this Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants