1
Support Questions / Re: Error on 2nd load of solution... 26: Me.EthernetIPforSLCMicroCom1 = New Advanced
« on: November 09, 2019, 06:02:39 PM »
Of course I find the answer as soon as i post this. SMH
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
Support Questions / Error on 2nd load of solution... 26: Me.EthernetIPforSLCMicroCom1 = New Advanced
« on: November 09, 2019, 06:00:58 PM »
I have a consistent problem. Whenever I open the solution file for the first time, it works as expected. Does not matter what changes I make, on the 2nd opening of the solution file, there will be an error from Visual Studio. See attached. This error will persist each time the solution is opened. after the error appears, Most times the MainForm will only partially load, occasionally it will load completely.
Please advise...David
System Info:
AdvancedHMIv399xR1.zip
Microsoft Visual Studio Community 2019
Version 16.3.5
VisualStudio.16.Release/16.3.5+29411.108
Microsoft .NET Framework
Version 4.8.03761
Installed Version: Community
Azure App Service Tools v3.0.0 16.3.285.24939
Azure App Service Tools v3.0.0
C# Tools 3.3.1-beta3-19461-02+2fd12c210e22f7d6245805c60340f6a34af6875b
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Common Azure Tools 1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
IntelliCode Extension 1.0
IntelliCode Visual Studio Extension Detailed Info
Microsoft JVM Debugger 1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines
Microsoft MI-Based Debugger 1.0
Provides support for connecting Visual Studio to MI compatible debuggers
NuGet Package Manager 5.3.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/
ProjectServicesPackage Extension 1.0
ProjectServicesPackage Visual Studio Extension Detailed Info
Visual Basic Tools 3.3.1-beta3-19461-02+2fd12c210e22f7d6245805c60340f6a34af6875b
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Visual F# Tools 10.4 for F# 4.6 16.3.0-beta.19455.1+0422ff293bb2cc722fe5021b85ef50378a9af823
Microsoft Visual F# Tools 10.4 for F# 4.6
Visual Studio Code Debug Adapter Host Package 1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio
OS Name Microsoft Windows 7 Ultimate
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DAVID-PC
System Manufacturer LENOVO
System Model 41789RU
System Type x64-based PC
Processor Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz, 2301 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date LENOVO 83ET82WW (1.52 ), 6/4/2018
SMBIOS Version 2.6
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "6.1.7601.24524"
User Name David-PC\David
Time Zone Central Standard Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.89 GB
Available Physical Memory 1.70 GB
Total Virtual Memory 15.8 GB
Available Virtual Memory 7.69 GB
Page File Space 7.89 GB
Page File C:\pagefile.sys
Please advise...David
System Info:
AdvancedHMIv399xR1.zip
Microsoft Visual Studio Community 2019
Version 16.3.5
VisualStudio.16.Release/16.3.5+29411.108
Microsoft .NET Framework
Version 4.8.03761
Installed Version: Community
Azure App Service Tools v3.0.0 16.3.285.24939
Azure App Service Tools v3.0.0
C# Tools 3.3.1-beta3-19461-02+2fd12c210e22f7d6245805c60340f6a34af6875b
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Common Azure Tools 1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
IntelliCode Extension 1.0
IntelliCode Visual Studio Extension Detailed Info
Microsoft JVM Debugger 1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines
Microsoft MI-Based Debugger 1.0
Provides support for connecting Visual Studio to MI compatible debuggers
NuGet Package Manager 5.3.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/
ProjectServicesPackage Extension 1.0
ProjectServicesPackage Visual Studio Extension Detailed Info
Visual Basic Tools 3.3.1-beta3-19461-02+2fd12c210e22f7d6245805c60340f6a34af6875b
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Visual F# Tools 10.4 for F# 4.6 16.3.0-beta.19455.1+0422ff293bb2cc722fe5021b85ef50378a9af823
Microsoft Visual F# Tools 10.4 for F# 4.6
Visual Studio Code Debug Adapter Host Package 1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio
OS Name Microsoft Windows 7 Ultimate
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DAVID-PC
System Manufacturer LENOVO
System Model 41789RU
System Type x64-based PC
Processor Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz, 2301 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date LENOVO 83ET82WW (1.52 ), 6/4/2018
SMBIOS Version 2.6
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "6.1.7601.24524"
User Name David-PC\David
Time Zone Central Standard Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.89 GB
Available Physical Memory 1.70 GB
Total Virtual Memory 15.8 GB
Available Virtual Memory 7.69 GB
Page File Space 7.89 GB
Page File C:\pagefile.sys
3
Open Discussion / Re: Memphis, TN area users?
« on: October 19, 2017, 10:58:10 PM »
Just north, Jackson Area
4
Open Discussion / Re: Writing app to trooubleshoot machine issue, need help/ideas.
« on: October 10, 2017, 08:46:53 AM »
Thanks for the help, it is appreciated!
5
Open Discussion / Re: Writing app to trooubleshoot machine issue, need help/ideas.
« on: October 09, 2017, 12:13:51 PM »
So, taking this code:
"""
Private Sub Timer1_Tick(sender As System.Object, e As System.EventArgs) Handles Timer1.Tick
'* Retreive the value from the PLC
Dim Value1 As String
Try
Value1 = EthernetIPforCLXCom1.Read("MyTag")
Catch ex As Exception
MsgBox("Failed to read")
Exit Sub
End Try
'* Create a file writer that will append
Using sw As New System.IO.StreamWriter("LogFile.txt", True)
'* Write the data with a time stamp
sw.WriteLine(Now & " - " & Value1)
sw.Close()
End Using
End Sub
"""
I would edit this line - Value1 = EthernetIPforCLXCom1.Read("MyTag") - with the proper driver name and use the (bit address) instead of ("MyTag")?
-or-
I would edit this line - Value1 = EthernetIPforCLXCom1.Read("MyTag") - with the proper driver name and use the ("bit address") instead of ("MyTag")?
DC
"""
Private Sub Timer1_Tick(sender As System.Object, e As System.EventArgs) Handles Timer1.Tick
'* Retreive the value from the PLC
Dim Value1 As String
Try
Value1 = EthernetIPforCLXCom1.Read("MyTag")
Catch ex As Exception
MsgBox("Failed to read")
Exit Sub
End Try
'* Create a file writer that will append
Using sw As New System.IO.StreamWriter("LogFile.txt", True)
'* Write the data with a time stamp
sw.WriteLine(Now & " - " & Value1)
sw.Close()
End Using
End Sub
"""
I would edit this line - Value1 = EthernetIPforCLXCom1.Read("MyTag") - with the proper driver name and use the (bit address) instead of ("MyTag")?
-or-
I would edit this line - Value1 = EthernetIPforCLXCom1.Read("MyTag") - with the proper driver name and use the ("bit address") instead of ("MyTag")?
DC
6
Open Discussion / Writing app to trooubleshoot machine issue, need help/ideas.
« on: October 09, 2017, 02:04:30 AM »
AdvancedHMI is awesome!
I have an older machine that is experiencing an issue at random times for no clear reason.
There are three carts that must move in sequence with each other, positioning is tracked via proximity switch.
The carts will, without warning, lose position and crash into each other. The frequency is random as well, from not at all to a couple times an hour.
So far we have identified no problem that will stop the issue from occurring.
There is no error log on the machine, and even if there was the error message are too vague to amount to much.
Motor drives check out fine. Visual inspection of wiring uncovers no problems. Any mechanical issue related to the carts has been corrected. Validation of prox adjustments found no problems.
At this point I am stumped. I feel like it is either a short in a wire or a timing issue. So, I am writing an app to track the prox activation's vs time. There are 24 prox switches of immediate interest and 32 of secondary interest, plus some other braking and drive functions I would like to keep track of vs time.
A simple datalog that I can then import into excel for analysis is my goal.
The processor is an SLC5/04 and its RS232 port is in use. I have the DH+ and DF1 port available. I also have a card, Prosoft I think, to convert from DH+ to Ethernet.
With about 75 values I need to get out of the processor, what is the best route to take? I have been looking at the simple datalog example and like the concept, just not sure how to apply it to the SLC. Would I use the bit address in place of the tagname when writing data to the file? Should I use a ...? A little prod in the right direction would be great!
TIA!
I am fairly familiar with VB having used it off and on for years. Most of my AdvancedHMI is on compact logic processors though.
DC
I have an older machine that is experiencing an issue at random times for no clear reason.
There are three carts that must move in sequence with each other, positioning is tracked via proximity switch.
The carts will, without warning, lose position and crash into each other. The frequency is random as well, from not at all to a couple times an hour.
So far we have identified no problem that will stop the issue from occurring.
There is no error log on the machine, and even if there was the error message are too vague to amount to much.
Motor drives check out fine. Visual inspection of wiring uncovers no problems. Any mechanical issue related to the carts has been corrected. Validation of prox adjustments found no problems.
At this point I am stumped. I feel like it is either a short in a wire or a timing issue. So, I am writing an app to track the prox activation's vs time. There are 24 prox switches of immediate interest and 32 of secondary interest, plus some other braking and drive functions I would like to keep track of vs time.
A simple datalog that I can then import into excel for analysis is my goal.
The processor is an SLC5/04 and its RS232 port is in use. I have the DH+ and DF1 port available. I also have a card, Prosoft I think, to convert from DH+ to Ethernet.
With about 75 values I need to get out of the processor, what is the best route to take? I have been looking at the simple datalog example and like the concept, just not sure how to apply it to the SLC. Would I use the bit address in place of the tagname when writing data to the file? Should I use a ...? A little prod in the right direction would be great!
TIA!
I am fairly familiar with VB having used it off and on for years. Most of my AdvancedHMI is on compact logic processors though.
DC
7
Open Discussion / Re: Memphis, TN area users?
« on: September 07, 2017, 07:26:29 AM »
Sorry I missed it, any chance there is a video?
Pages: [1]