If you're interested, I hoped that the 150A current sensor has a "hidden" capacity counter built in. Analyzed the output. Nope. There is only the current coming out. I still wonder why they did not put a capacity counter in (this takes maybe an hour addidional programming)....

Of course you are right. No one said it can't be done. Just that is is nowhere near as simple as some believe it to be. For example, due to the polling rate, the calculation can't really be performed in the transmitter with any accuracy. That means additional hardware in the sensor, perhaps a microprocessor to track it all and package it up to send to the transmitter. I reality, it's isn't that big of a deal. However it does make the sensor more expensive and is far from a simple software upgrade to the transmitter only. At some time, if they perceive there is a market for such a sensor, I'm sure they'll produce one. However, a handful of people on a forum complaining about the lack of such a device doesn't prove a significant demand for such a product.

Of course you are right. No one said it can't be done. Just that is is nowhere near as simple as some believe it to be. For example, due to the polling rate, the calculation can't really be performed in the transmitter with any accuracy. That means additional hardware in the sensor, perhaps a microprocessor to track it all and package it up to send to the transmitter. I reality, it's isn't that big of a deal. However it does make the sensor more expensive and is far from a simple software upgrade to the transmitter only. At some time, if they perceive there is a market for such a sensor, I'm sure they'll produce one. However, a handful of people on a forum complaining about the lack of such a device doesn't prove a significant demand for such a product.

How would it be such a big hardware addition? The current sensor is there and there has to be a clock pulse somewhere in the telemetry module already. Current vs time= accumulated mah. I am really missing something here??? Shouldn't make the sensor any more expensive.

Based on a few people in a forum who actually say something about it would lead me to believe there are a lot of people who want it but just are not on the forums.

I wouldn't hold my breath waiting for them to come out with such a sensor. Andy responded to many ideas/requests for additional features in the DX18 that they were in the database for consideration and six months in now and their have been few additions that I can see.

New Features & Improvements
• Enabled telemetry sensor for GPS, JetCat, and High Current (Amps).
• Enabled up to 32-pole motors for the Brushless RPM sensor.
• Enabled access to more switches as telemetry log starters.
• Enabled French and Italian languages. Note that these are two separate
downloads (English/German/French or English/Italian).
• Improved interchange with DX10t-created SPM files.

Some may argue some of those should have been there in the first place.

If you're interested, I hoped that the 150A current sensor has a "hidden" capacity counter built in. Analyzed the output. Nope. There is only the current coming out. I still wonder why they did not put a capacity counter in (this takes maybe an hour addidional programming)....

Really?? Omg how disappointing... Is this a production version? Will this ever happen in the near future?

I've been waiting for this to come out for one year, since it was shown at Nuremberg this time last year..(I actually asked about it 2 years ago) For me I wanted to know mAh consumed and shown on my TX.. Really thought it would be able to do that
I've held off buying the quanum as wanted it all in one unit..

the new sensor and the current sensor will not be changing.
There will not be 'accumulation' added to either due to technical and hardware limitations that Andy pointed out.

Quote:

Originally Posted by davidmc36

How would it be such a big hardware addition? The current sensor is there and there has to be a clock pulse somewhere in the telemetry module already. Current vs time= accumulated mah. I am really missing something here??? Shouldn't make the sensor any more expensive.

Based on a few people in a forum who actually say something about it would lead me to believe there are a lot of people who want it but just are not on the forums.

I wouldn't hold my breath waiting for them to come out with such a sensor. Andy responded to many ideas/requests for additional features in the DX18 that they were in the database for consideration and six months in now and their have been few additions that I can see.

New Features & Improvements
• Enabled telemetry sensor for GPS, JetCat, and High Current (Amps).
• Enabled up to 32-pole motors for the Brushless RPM sensor.
• Enabled access to more switches as telemetry log starters.
• Enabled French and Italian languages. Note that these are two separate
downloads (English/German/French or English/Italian).
• Improved interchange with DX10t-created SPM files.

Some may argue some of those should have been there in the first place.

the new sensor and the current sensor will not be changing.
There will not be 'accumulation' added to either due to technical and hardware limitations that Andy pointed out.

Well I never really expected there to be any change to the "current" sensor. But it's bogus to say it could not have been done in the first place. Hardware limitations....blah blah blah....should be interpreted as "We chose not to do it." Maybe the current telemetry module can't do it, but it should have been given the ability in the first place, they chose not to do it.

More than one competition are doing it. And the competition are doing lots of other things that will negate the need for you to buy the next greatest radio that comes out with a few more desirable features doled out, .....and the next one with a few more features graciously doled out.

I've been waiting for this to come out for one year, since it was shown at Nuremberg this time last year.

The unit we showed at Nuremberg has only ever been intended to monitor power into low-current applications such as a PowerSafe receiver. That' has been clearly pointed out numerous times on this forum.