You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Zranger2 driver is declaring the same log variable as zranger1 which results in zranger2 variable being the only one readable from the ground. This can be tested by trying to log range.zrange when a zranger or flow deck V1 is installed and then doing so again with removing zranger2.o from the makefile: if zranger2.o is compiled range.zrange always returns 0, if zranger2.o is not part of the build the log variable returns the range correctly.
One possible fix would be to centralize all range in an API file: this way there is a single point to get ranges to different direction independently of the mean this range has been acquired and we have a single point to declare log variables.
The text was updated successfully, but these errors were encountered:
The Zranger2 driver is declaring the same log variable as zranger1 which results in zranger2 variable being the only one readable from the ground. This can be tested by trying to log range.zrange when a zranger or flow deck V1 is installed and then doing so again with removing zranger2.o from the makefile: if zranger2.o is compiled range.zrange always returns 0, if zranger2.o is not part of the build the log variable returns the range correctly.
One possible fix would be to centralize all range in an API file: this way there is a single point to get ranges to different direction independently of the mean this range has been acquired and we have a single point to declare log variables.
The text was updated successfully, but these errors were encountered: