Carlos Ríos
Carlos Ríos
I will take a look into getInputRange(). About the bit resolution, I'm looking a way to get the range resolution in bits, so I can get the actual offset-scale value....
Yeah I know that I can check the datasheet to get the product resolution, just I thought it could be a great idea to get it from something like wirelessNode().getBitResolution(),...
@rwslord is there anyway to transform the `getInputRange()` result into hardware Gain? For example from 2.5mV that I get as InputRange from NodeCommander (I get 2mV as InputRange in MSCL)...
So there is no way to set or get the hardware gain?
Well, I don't know how to look it then. Now I tried to autobalance a SG-Link node, but `node.getInputRange()` returns "Invalid Input Range". From NodeCommander I see the following difference:...
@rwslord, I've compared the input range options that SensorConnect gives me with a SG-Link node, which are: `14mV, 10mV, 7mV, 4mV, 2mV, 1.5mV, 1mV, 812uV` I have autobalanced the the...
@rwslord and what about write directly into the EEPROM using the equation from above? Thanks.
@rwslord In that case, what refers to `Bit value` in the equation? Best regards
@rwslord Worked perfect with SG-Link!! For V-Link, NodeCommander and SensorConnect, gives the following gain options: `21, 30, 75, 147, 291, 569, 1214, 2222, 3799, 13074`. Reading the Eeprom, those gain...
@rwslord the V-Link model number is: 1000-37416. Best regards.