-
Notifications
You must be signed in to change notification settings - Fork 16
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
ParameterType is 'NULL' #18
Comments
Hi @uwsrf, The type in the encoder is taken from the node that you pass as the first argument to the If the ember decoder returns a Parameter with type Null that means either the parameter was unreadable for some reason or the provider you are connecting to does not implement the specification properly. As far as I can tell from the specification our implementation is currently correct. If you have an example BER buffer that we could debug this against I'd be happy to help you figure out which one it is but without more information there is little I can do. |
Hi @baltedewit, |
From the BER buffers it was clear that some devices do not send a parameter type at all. And it turns out that when the ParameterType is empty there are other rules that hint the type of the parameter, the ember+ spec says the following: To determine the effective type of a parameter, follow this rule: This piece of documentation for some reason never made it out of the ASN notation changelog, which is not a place one would typically look when implementing from scratch. oh well... I will try to add this logic to the library soon. |
setValue()
doesn't work for me. While debugging I found out, that the parameterType in my request was alwaysNULL
. Setting the parameterType explicitely in \Ember\Client\index.js on line 180 toqualifiedParam.contents.parameterType = 'REAL'
fixed the problem.I always get the type "NULL" on
getElementsByPath()
.The problem seems to be, that in BER-Decoder the parameterType is not set correctly. Since I have no idea of BER, I couldn't investigate further...
The text was updated successfully, but these errors were encountered: