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.


Messages - abslcplc

Pages: [1]
1
Directly under each line of code with the "Visibility" is the line with the "Visible", so I just deleted the 4 lines.

Thanks.

2
I just downloaded version 399a & added my existing project into it, then when I did a Rebuild (before I opened any forms) I got 4 errors that PLCaddressVisibility is not a member of AdvancedHMIControls.pilotLight3Color.

Do I have to change something, or just delete the lines in the VB code, because I don't use that entry at all?

3
Feature Request / Re: HMI Command To PLC #2 Based on Signal From PLC #1
« on: September 24, 2015, 09:47:47 PM »
Now it doesn't crash, but I get a pop-up that the "Input String was not in a correct format."

I can close the pop-up & continue but the 5/05's status is not making it to the 5/03 - and I am communicating with both PLC's on the same screen, showing valid status & values from both.

4
Feature Request / Re: HMI Command To PLC #2 Based on Signal From PLC #1
« on: September 24, 2015, 09:26:27 PM »
Archie, (sending this from my day jobs account)

Did I put the line in the correct area? Or do I replace all the email coding with this line? I only have one DataSubsciber so I don't know why the code has two listed.

Tried it as shown here & when the screen comes up VS crashes with an error pop-up wanting to quit the program.

+ Private Sub DataSubscriber1_DataChanged_1(sender As Object, e As Drivers.Common.PlcComEventArgs)
       
+  Private Sub DataSubscriber2_DataChanged(sender As Object, e As Drivers.Common.PlcComEventArgs)
       
-    Private Sub DataSubscriber1_DataChanged(sender As Object, e As Drivers.Common.PlcComEventArgs) Handles DataSubscriber1.DataChanged
        DF1Com5.Write("B13:1/15", e.Values(0))
    End Sub

5
Open Discussion / Re: Visual Studio Community 2015???
« on: September 23, 2015, 11:11:19 AM »
You just need to make sure .NET 4.0 or later is installed on it. If you install all of the Windows updates, which can sometimes take hours, it will pull the latest .NET framework...

Archie,

Got the tablet, 10" Windows 10 32 bit; had to go to Settings - Turn Windows Features On/Off to turn on .NET 4.0 & it works.

The only thing is the screen has a default resolution of 1280 X 800, so I set a sample HMI at 1200 X 760 & when I ran it the window was about 150% bigger than the screen & I had to scroll over & down. I reset the windows in VS to 900 x500 & move the objects into that area  & it shows OK now. Have you ever seen something like this? Is this something in Visual Studio or the tablet's display?

6
Support Questions / Re: V3.99 Release Notes
« on: September 06, 2015, 09:01:29 PM »
Archie,
;
Thanks, I got all the PLCSLC driver errors taken care of, now however I keep getting 4 errors saying:
'PLCaddressVisibilty'is not a member of 'AdvancedHMIControls.PilotLight3Color' & I don't have a bit address in the entries.
Should I remark out these lines, or how would I add the member?

7
Support Questions / Re: V3.99 Release Notes
« on: September 06, 2015, 02:15:48 PM »
I just tried to add my existing 398t project into 399 & got hundreds of errors about the PLCSLC, so I decided to not upgrade that project (my pet project I am using to control a 2 rack SLC5/05 & 2) SLC5/03's for home automation control & Christmas lights - mostly as a test to see what I & AdvancedHMI are capable of).

8
Open Discussion / Re: Vote For Your Favorite
« on: August 21, 2015, 05:47:11 PM »
My vote sent AdvancedHMI to the lead. See if I can vote from home on a different computer & skew the result.

9
I have a Moxa N-Port Ethernet serial port on my network, and on 2 desktops & a laptop it is configured as a COM port  & I can use the regular DF1 driver to access it from either of the desktops without any modification of the driver.

Pages: [1]