openpdc Issue Tracker Rss Feed

Commented Issue: Error On adding new device . [10942]

ritchiecarroll — Tue, 23 Apr 2013 14:07:57 GMT

Hi,
I am getting error on adding new device stating " Object reference not set to an instance of the object" and on clicking OK over the error . I have attatched the files in the link below .

Regards
Shripad.K

https://www.dropbox.com/sh/x7abcmdqlswez57/DbbkwC_VCi#/
Comments: ** Comment from web user: ritchiecarroll **

Having trouble replicating your issue. Can we get a copy of the configuration XML file (can be generated with PMU Connection Tester) to see if we can replicate issue from your test PMU? Also, what database are your using?

Created Issue: Error On adding new device . [10942]

Shripadkapse — Sat, 20 Apr 2013 03:48:04 GMT

Closed Issue: Error while connecting through PMU Connection Tester [10936]

ritchiecarroll — Fri, 19 Apr 2013 13:41:30 GMT

Hi,
Im finding error while connecting through PMU connection tester as " IP V6 Stack is not available for socket creation" though im using IP Stack V4 as default system. Im attatching the screen shot of the error here , u can also access the snapshot of error from the link below. Kindly help in this matter.

Regards
Shripad.K
Application Engineer
ERL India

https://www.dropbox.com/s/w24sm5mtjdrgt34/Open%20PDC%20Error.bmp
Comments: Resolved - configuration issue.

Commented Issue: Error while connecting through PMU Connection Tester [10936]

Shripadkapse — Fri, 19 Apr 2013 03:41:05 GMT

Hi Ritchie,
Thank you for your immediate reply and yes the issue is fixed now.

Thanks
Shripad.K
ERL-India

Commented Issue: Error while connecting through PMU Connection Tester [10936]

ritchiecarroll — Thu, 18 Apr 2013 13:43:02 GMT

Go to the "Settings" tab and set "ForceIPv4" to True.

Does this fix the issue?

Thanks,
Ritchie

Created Issue: Error while connecting through PMU Connection Tester [10936]

Shripadkapse — Thu, 18 Apr 2013 06:19:17 GMT

Created Issue: Historian web service returns NaN in JSON [10894]

atmurray — Thu, 04 Apr 2013 02:10:46 GMT

The historian web service returns values as NaN, usually when the data is of bad quality:
{"HistorianID":398,"Time":"2013-04-04 02:07:05.120","Value":NaN,"Quality":14}

NaN is not a value JSON value, as per http://json.org/ valid values are:
* string
* number
* object
* array
* true
* false
* null

This causes many JSON parsing engines to fail.
NaN and other exceptional floating point values probably should be returned as null.

Created Task: Remote console unaware of disconnect over WAN connection [10876]

ritchiecarroll — Wed, 20 Mar 2013 12:05:43 GMT

When using the remote console to connect to an openPDC over a wide-are-network and/or lan-to-lan VPN style connection, the socket connection may not be notified of a disconnect from the server due to a loss of connection in one of the routers or network equipment in between the console and the openPDC.

Suggest that the console monitor for "no data received in defined period" so that it can automatically reconnect once it detects it has received no data from the server in a while.

Closed Issue: no connection could be made because the target machine refused it [10836]

ritchiecarroll — Wed, 20 Mar 2013 12:00:39 GMT

can anyone can solve this..
first, the connection is correct because i am pinging it reply..
second i try to connect the Open PDC to the device this message "no connection could be made because the target machine actively refused it 120.0.0.1:4712 1 connection attempted"

fyi: when i connect in the same LAN network no problem..

please help for this problem

regards

Dimas Dityagraha
Comments: No able to replicate.

Commented Issue: no connection could be made because the target machine refused it [10836]

salveraniket — Tue, 26 Feb 2013 19:03:56 GMT

Sure we can help you with that..!!

Please let us know more about the issue, I would like to know, What are you trying to connect to. What Ip address is in Alternate command channel. And to which IP address are you try to connect to.

Thanks..!!

Created Issue: no connection could be made because the target machine refused it [10836]

dimas_ditya — Mon, 25 Feb 2013 08:29:05 GMT

Created Issue: Column Header for Debug Capture CSV [10817]

idallasj — Thu, 14 Feb 2013 19:37:06 GMT

What are the column headers for the Debug Capture .csv file?

Closed Issue: Renaming Node leaves old system stats [10531]

salveraniket — Tue, 12 Feb 2013 20:56:27 GMT

When you change the name of a node, all the old stats remain - these need to be removed.

Perhaps data operation can validate deletes and/or rename instead of blindly adding...
Comments: Issue Resolved ..!!

Commented Issue: 'Missing Frames' statistic fluctuates from normal or reasonable to the thousands [10804]

patpentz — Thu, 07 Feb 2013 15:55:40 GMT

The 'Missing Frames' statistic fluctuates very very quickly from 'normal' values such as 0, 1, 6, etc, to very large numbers such as 22000. Do these numbers mean anything, or?
Comments: ** Comment from web user: patpentz **

BTW this was openPDC 1.4 SP2 using Alstom's 20130817 version on the 'master' side (my view). The TO's vary with versions, all with openPDC 1.4 SP2, most with the May patch, a few with 0817 patch.

Created Issue: 'Missing Frames' statistic fluctuates from normal or reasonable to the thousands [10804]

patpentz — Thu, 07 Feb 2013 15:54:02 GMT

The 'Missing Frames' statistic fluctuates very very quickly from 'normal' values such as 0, 1, 6, etc, to very large numbers such as 22000. Do these numbers mean anything, or?

Created Issue: FNET devices report numerous issues [10788]

arkrohne — Thu, 31 Jan 2013 18:11:47 GMT

Tested in openPDC 1.5.189

When conned to an FNET device, openPDC reports repeated errors, such as 'Bad data stream, expected start byte 0x01, got 0x30' and 'Bad data stream, invalid number of data elements.. Got 15 elements, expected 8'. These errors appear nearly continuously for the duration of the connection, which is usually fairly short as the 'Allowed Parsing Exceptions' is reached quickly.

Interestingly, I'm unable to reproduce this issue in an older PMU connection tester (4.2.12.0)

Created Issue: FNET devices report angle differently than others [10786]

arkrohne — Thu, 31 Jan 2013 16:18:50 GMT

While most devices report angles between -180° and 180, FNET devices report from 0° to 360°.

This prevents simple comparison with other devices in Graph Measurements, among other issues.

Tested in openPDC 1.5.189

Created Issue: 'Client is not connected' exception on start of openPDC manager [10780]

arkrohne — Tue, 29 Jan 2013 20:51:14 GMT

After running the Configuration Setup Utility, the openPDC manager was launched. The exception listed below occurred, and openPDC manager was terminated. Starting openPDC manager again did not replicate the issue.

I've not figured out how to replicate the issue; the only difference I can think of is that the 'Next' and 'Finish' buttons were clicked faster than normal, possibly causing a race condition.

---- Stack Trace ----

[29/01/2013 3:37:54 PM] (Inner Exception)
Date and Time: 29/01/2013 3:37:54 PM
Machine Name: VMTESTING13
Machine IP: ::1
Machine OS: Microsoft Windows NT 6.1.7601 Service Pack 1

Application Domain: openPDCManager.exe
Assembly Codebase: c:/program files/openpdc/openpdcmanager.exe
Assembly Full Name: openPDCManager, Version=1.5.185.0, Culture=neutral, PublicKeyToken=null
Assembly Version: 1.5.185.0
Assembly Build Date: 16/01/2013 12:42:02 AM
.Net Runtime Version: 4.0.30319.18034

Exception Source: TVA.Communication
Exception Type: System.InvalidOperationException
Exception Message: Client is not connected
Exception Target Site: SendAsync

---- Stack Trace ----
TVA.Communication.ClientBase.SendAsync(data As Byte[], offset As Int32, length As Int32)
openPDCManager.exe: N 00102
TVA.Communication.ClientBase.SendAsync(data As Byte[])
openPDCManager.exe: N 00031
TimeSeriesFramework.UI.CommonFunctions.SendCommandToService(command As String)
openPDCManager.exe: N 00181
openPDC.UI.UserControls.HomeUserControl.HomeUserControl_Loaded(sender As Object, e As RoutedEventArgs)
openPDCManager.exe: N 00390
System.Windows.EventRoute.InvokeHandlersImpl(source As Object, args As RoutedEventArgs, reRaised As Boolean)
openPDCManager.exe: N 00624
System.Windows.UIElement.RaiseEventImpl(sender As DependencyObject, args As RoutedEventArgs)
openPDCManager.exe: N 00334
MS.Internal.FrameworkObject.OnLoaded(args As RoutedEventArgs)
openPDCManager.exe: N 00034
System.Windows.BroadcastEventHelper.BroadcastEvent(root As DependencyObject, routedEvent As RoutedEvent)
openPDCManager.exe: N 00412
System.Windows.BroadcastEventHelper.BroadcastLoadedEvent(root As Object)
openPDCManager.exe: N 00328
System.Windows.Media.MediaContext.FireLoadedPendingCallbacks()
openPDCManager.exe: N 00047
System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
openPDCManager.exe: N 00046
System.Windows.Media.MediaContext.RenderMessageHandlerCore(resizedCompositionTarget As Object)
openPDCManager.exe: N 00223
System.Windows.Media.MediaContext.RenderMessageHandler(resizedCompositionTarget As Object)
openPDCManager.exe: N 00047
System.Windows.Threading.ExceptionWrapper.InternalRealCall(callback As Delegate, args As Object, numArgs As Int32)
openPDCManager.exe: N 00094
MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(source As Object, method As Delegate, args As Object, numArgs As Int32, catchHandler As Delegate)
openPDCManager.exe: N 00071
System.Windows.Threading.DispatcherOperation.InvokeImpl()
openPDCManager.exe: N 00641
System.Threading.ExecutionContext.RunInternal(executionContext As ExecutionContext, callback As ContextCallback, state As Object, preserveSyncCtx As Boolean)
openPDCManager.exe: N 00645
System.Threading.ExecutionContext.Run(executionContext As ExecutionContext, callback As ContextCallback, state As Object, preserveSyncCtx As Boolean)
openPDCManager.exe: N 00009
System.Threading.ExecutionContext.Run(executionContext As ExecutionContext, callback As ContextCallback, state As Object)
openPDCManager.exe: N 00087
System.Windows.Threading.DispatcherOperation.Invoke()
openPDCManager.exe: N 00113
System.Windows.Threading.Dispatcher.ProcessQueue()
openPDCManager.exe: N 00673
System.Windows.Threading.Dispatcher.WndProcHook(hwnd As IntPtr, msg As Int32, wParam As IntPtr, lParam As IntPtr, handled As Boolean&)
openPDCManager.exe: N 00179
MS.Win32.HwndWrapper.WndProc(hwnd As IntPtr, msg As Int32, wParam As IntPtr, lParam As IntPtr, handled As Boolean&)
openPDCManager.exe: N 00330
MS.Win32.HwndSubclass.DispatcherCallbackOperation(o As Object)
openPDCManager.exe: N 00128
System.Windows.Threading.ExceptionWrapper.InternalRealCall(callback As Delegate, args As Object, numArgs As Int32)
openPDCManager.exe: N 00094
MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(source As Object, method As Delegate, args As Object, numArgs As Int32, catchHandler As Delegate)
openPDCManager.exe: N 00071
System.Windows.Threading.Dispatcher.LegacyInvokeImpl(priority As DispatcherPriority, timeout As TimeSpan, method As Delegate, args As Object, numArgs As Int32)
openPDCManager.exe: N 00700
MS.Win32.HwndSubclass.SubclassWndProc(hwnd As IntPtr, msg As Int32, wParam As IntPtr, lParam As IntPtr)
openPDCManager.exe: N 00320
MS.Win32.UnsafeNativeMethods.DispatchMessage(msg As MSG&)
openPDCManager.exe: N 00000
System.Windows.Threading.Dispatcher.PushFrameImpl(frame As DispatcherFrame)
openPDCManager.exe: N 00274
System.Windows.Application.RunInternal(window As Window)
openPDCManager.exe: N 00378
System.Windows.Application.Run()
openPDCManager.exe: N 00103
openPDCManager.App.Main()
openPDCManager.exe: N 00344

(Outer Exception)
Date and Time: 29/01/2013 3:37:54 PM
Machine Name: VMTESTING13
Machine IP: ::1
Machine OS: Microsoft Windows NT 6.1.7601 Service Pack 1

Application Domain: openPDCManager.exe
Assembly Codebase: c:/program files/openpdc/openpdcmanager.exe
Assembly Full Name: openPDCManager, Version=1.5.185.0, Culture=neutral, PublicKeyToken=null
Assembly Version: 1.5.185.0
Assembly Build Date: 16/01/2013 12:42:02 AM
.Net Runtime Version: 4.0.30319.18034

Exception Source:
Exception Type: System.Exception
Exception Message: UnhandledException

---- Stack Trace ----

Commented Issue: error dialog on pdc manager start [10741]

salveraniket — Mon, 28 Jan 2013 13:48:06 GMT

See attachment. No way for me to even start the Manager.
v1.5 SP 1

WinXp SP3, openPDC on .mdb

v1.5 had same problem.
Comments: ** Comment from web user: salveraniket **

Me and my college have tested under the same circumstances and we could run the application with no error, Please check back again and let us know if you still have problems with it.

Recommending to download the latest build and try back again .

Thanks..!!

Commented Issue: error dialog on pdc manager start [10741]

salveraniket — Thu, 24 Jan 2013 19:23:21 GMT

See attachment. No way for me to even start the Manager.
v1.5 SP 1

WinXp SP3, openPDC on .mdb

v1.5 had same problem.
Comments: ** Comment from web user: salveraniket **

Can you please send us more details about this.

Also please try to attach error log with it.

Thanks..!!