Home › Forums › Mooshimeter Support › slow to change channel mapping
- This topic has 0 replies, 1 voice, and was last updated 6 years, 6 months ago by
Anonymous.
Viewing 0 reply threads
- AuthorPosts
Anonymous
InactiveHi,
I’m writing a node.js application to create a UI to my mooshimeter. It’s going well so far — I’m able to talk to the device and get the config tree and do the basic interaction with the device.
One thing I’ve noticed is that it seems to take a long time for channel mappings to take effect, sometime many seconds. Is this likely something that I’m doing wrong, or is it just how the meter operates?
Here is a log of several consecutive runs of a test:
123456789101112131415161718192021222324252627282930313233-------------------------------- TEST1489426327.387 set CH1:MAPPING 11489426329.770 got CH1:MAPPING 1 --elapsed 2.383s1489426329.772 set CH1:RANGE_I 01489426330.764 got CH1:RANGE_I 0 --elapsed 0.992s1489426330.765 set CH1:MAPPING 21489426340.702 got CH1:MAPPING 2 --elapsed 9.937s1489426340.702 set SHARED 01489426350.639 got SHARED 0 --elapsed 9.937s1489426350.640 set CH1:RANGE_I 21489426360.378 got CH1:RANGE_I 2 --elapsed 9.738s-------------------------------- TEST1489426365.390 set CH1:MAPPING 11489426380.451 got CH1:MAPPING 1 --elapsed 15.061s1489426380.451 set CH1:RANGE_I 01489426400.329 got CH1:RANGE_I 0 --elapsed 19.878s1489426400.329 set CH1:MAPPING 21489426430.338 got CH1:MAPPING 2 --elapsed 30.009s1489426430.338 set SHARED 01489426460.746 got SHARED 0 --elapsed 30.408s1489426460.746 set CH1:RANGE_I 21489426490.756 got CH1:RANGE_I 2 --elapsed 30.01s-------------------------------- TEST1489426495.762 set CH1:MAPPING 11489426530.506 got CH1:MAPPING 1 --elapsed 34.744s1489426530.506 set CH1:RANGE_I 01489426570.453 got CH1:RANGE_I 0 --elapsed 39.947s1489426570.453 set CH1:MAPPING 21489426621.090 got CH1:MAPPING 2 --elapsed 50.637s1489426621.090 set SHARED 01489426671.176 got SHARED 0 --elapsed 50.086s1489426671.176 set CH1:RANGE_I 21489426721.062 got CH1:RANGE_I 2 --elapsed 49.886sI noticed in the python example code that it’s requesting PCB_VERSION periodically in order to keep the connection to the device alive. I’m requesting BAT_V, might that be the issue?
- AuthorPosts
Viewing 0 reply threads