Recent Posts

11

TED5000 Support / Re: Unrealistic High readings on my dashboard and histories.

« Last post by jlsoaz on January 29, 2019, 05:03:08 PM »

The cause of the problem is, almost certainly, as Support7 said, power-line fluctuations and glitches, which are inevitable in anything connected to the mains. [...]

Is that the cause of the problem?  Perhaps we are looking at related-but-not-the-same problems? 

My hope would not be to stop the occasional spike but simply to be able to go into historical data that is the basis for some charts, get rid of or revise to some sort of middling estimate the occasional outlier kWh data point that clearly has nothing to do with reality, and thus once again be able to read the charts and make some of use of them.  In effect, if a major use for me of TED would occasionally be to review some long-term historical charts, then much of this goal cannot be attained due to just a few claimed-uneditable data points. 

Perhaps if you or someone else could mention a path to export the data to some generally accepted data format (.csv, or some-such) I could try again.   Perhaps it is more easily discovered than I realize as to how to do that export/workaround type of procedure, but it has been too many years since I set this aside, so I don't know.

12

TED5000 Support / Re: Unrealistic High readings on my dashboard and histories.

« Last post by pfletch101 on January 21, 2019, 06:41:07 PM »

As Support7 said, last year, the Ted5000 is now very old technology, and you should not be looking for any significant change in its firmware or for new standalone software for it. I can testify that this problem is much rarer with the Pro device, but I have also written a 'saved data editor' for the Pro which I have made available to deal with any residual problems. Unfortunately, this application, which operates on saved backup data, only works on the files saved by the newer devices.

Thanks.  I think at this point I do realize that the company is not going to address things, and that the Ted5000 equipment I have is very old tech.  The thing is, when something comes across as a software issue and not a hardware issue, it is tempting to think that the company could fix it, if it wanted, with just a bit of work from a programmer, even if the matter is dated.

The cause of the problem is, almost certainly, as Support7 said, power-line fluctuations and glitches, which are inevitable in anything connected to the mains. The 6000 series has been made more resistant to these, but, short of building in heroic spike protection and a UPS, at very substantial additional cost, it is not possible to prevent them entirely. To build anything like the correction facilities that my editing Application provides into the firmware would take up much more space than they have available, for what is now a rather unusual problem. I think that they made a reasonable call.

Maybe they'd say it's not fully a software matter.  I don't know if that would be true, but even if it is, why not fix it in then in the latest hardware iteration?  The fact that, to this day, even with the latest software and hardware, a user is still having to write a workaround tells me:
a) Maybe I was right not to buy the latest tech - it would have been nice to have what are undoubtedly improvements, but it doesn't come with a really obvious matter fully addressed.

If by "fully addressed" you mean that you want no problems, ever, good luck with all your software and hardware purchases!

b) if the matter can be addressed by a user writing a workaround, then it sounds like it could have been addressed by a programmer, if the company really wants.

This 'user' is a very experienced programmer, but I assume that you did not intend to be insulting. The company did not think that spending time and resources on this was cost-effective. Given the very small amount of interest that I have had from other users since I completed the Application, I would have to agree with their judgement. They did, however cooperate enthusiastically with me as I was developing it.

c) maybe the company just does not understand that the matter is both important to some users, and could have been addressed.

They and I believe that it has now been addressed!

So, yes, I understand it's old tech, but it sounds like it's possible (maybe not probable, but possible) that the company, with a bit of prodding, might be able to take improved action on this, at least for the newer models, if not for the older ones.

They (and I) think not, within the limits of what is cost-effective.

13

TED5000 Support / Re: Unrealistic High readings on my dashboard and histories.

« Last post by jlsoaz on January 20, 2019, 12:30:32 AM »

As Support7 said, last year, the Ted5000 is now very old technology, and you should not be looking for any significant change in its firmware or for new standalone software for it. I can testify that this problem is much rarer with the Pro device, but I have also written a 'saved data editor' for the Pro which I have made available to deal with any residual problems. Unfortunately, this application, which operates on saved backup data, only works on the files saved by the newer devices.

Thanks.  I think at this point I do realize that the company is not going to address things, and that the Ted5000 equipment I have is very old tech.  The thing is, when something comes across as a software issue and not a hardware issue, it is tempting to think that the company could fix it, if it wanted, with just a bit of work from a programmer, even if the matter is dated.

Maybe they'd say it's not fully a software matter.  I don't know if that would be true, but even if it is, why not fix it in then in the latest hardware iteration?  The fact that, to this day, even with the latest software and hardware, a user is still having to write a workaround tells me:
a) Maybe I was right not to buy the latest tech - it would have been nice to have what are undoubtedly improvements, but it doesn't come with a really obvious matter fully addressed.
b) if the matter can be addressed by a user writing a workaround, then it sounds like it could have been addressed by a programmer, if the company really wants.
c) maybe the company just does not understand that the matter is both important to some users, and could have been addressed.

So, yes, I understand it's old tech, but it sounds like it's possible (maybe not probable, but possible) that the company, with a bit of prodding, might be able to take improved action on this, at least for the newer models, if not for the older ones.

14

TED5000 Support / Re: Unrealistic High readings on my dashboard and histories.

« Last post by pfletch101 on January 09, 2019, 11:38:26 PM »

As Support7 said, last year, the Ted5000 is now very old technology, and you should not be looking for any significant change in its firmware or for new standalone software for it. I can testify that this problem is much rarer with the Pro device, but I have also written a 'saved data editor' for the Pro which I have made available to deal with any residual problems. Unfortunately, this application, which operates on saved backup data, only works on the files saved by the newer devices.

15

TED5000 Support / Re: Unrealistic High readings on my dashboard and histories.

« Last post by jlsoaz on January 09, 2019, 07:20:35 AM »

[...]
You can clear the high number from the dashboard totals by going to Footprints > Advanced > Reset Totals to Zero. This won't delete your history but it does reset the totals on the dashboard essentially like starting the month on your meter read date.

It's roughly the same question from me that Jasline had, so digging up this old thread.  In this last bit of the response above, there is something about resetting totals to zero.  I can do that, but suspect I'll get out of this what I get out of the TED5000 software every few years now, which is totally losing all my data.  What I'd like is the ability to go in and remove data points that are obviously wrong.  For me they happen about once or twice per year and totally ruin any ability I might have to view a long term chart that incorporates the offending dates.  I'm guessing there is no feature in the software that allows for manually changing an individual day or hour or month data point, but if there isn't, then I'm just noting what I'd like for future repairs of my data.

16

TED Pro Support / Re: TED Commander Error: No Monitoring Points

« Last post by tedteam on January 04, 2019, 11:38:58 AM »

Did you get your issue resolved?  We have been making some adjustments to the way we cache the post before writing to the Location, but it should only cause a few minutes of delay.

17

TED Pro Support / TED Commander Error: No Monitoring Points

« Last post by sumocomputers on December 29, 2018, 11:57:05 AM »

I keep getting the TED Commander Error: "No Monitoring Points".

I am pretty sure I have everything setup correctly, as shown in this video:

https://www.dropbox.com/s/2b9y4p9wm59d9yl/TED-Commander-02.mp4?dl=0

18

TED Pro Support / forum.theenergydetective.com

« Last post by Stevendib on December 20, 2018, 10:26:23 AM »

hi all

19

TED Pro Support / Re: TED Commander Advisor "Not Posting Alert"

« Last post by tlveik on December 16, 2018, 12:37:22 PM »

It's looking a lot better now.  Even some of the past data that was missing has been filled in.  Looks good.

By the way, I like to look at line plots of watts using Minute data in Commander.  On the page where you select the date range, you can select either Energy or Demand.  Those two labels, Energy and Demand are swapped.  I have to select Energy to get line plots to plot watts.

20

TED Pro Support / Re: Data error every 15 minutes

« Last post by Support7 on December 13, 2018, 04:16:40 PM »

Glad to hear its working correctly.
The Min Count is a representation of successful Minute Packets received from the MTU since the ECC has been powered up.
Uptime in the Upper table is how long in seconds that the MTU has been powered up. Power cycling the MTU resets this number.
Uptime at the bottom of the page is how long the ECC has been powered up. A restart or power cycle of the ECC resets this number.