writing an hmi from scratch using VB

ganutenator

Lifetime Supporting Member
Join Date
May 2002
Location
kansas
Posts
1,440
Anyone have any experience doing this?
Is this too much of an undertaking to consider?
What are the biggest hurdles?
My guesses of the biggest hurdles:
SSL email, text message api
alarm history
modbus tcp driver
 
Lots and lots of machine tool manufacturers us VB for the operator interface, but those controls are usually all PC based.

So, to answer your question it depends. If you had a giant production line I’d say you’d be reinventing the wheel. If you had a stand alone machine I’d say go for it.
 
The answer to your question is me
I have completed quit a few VB and Net Studio HMI's
i actually prefer it. It's far more flexible
the attached is a main screen done completely in Net Studio

CRC Main.jpg
 
The cost/time of making an HMI from scratch is probably not worth it.
I have done this for a company for a standard piece of plant but it got a bit too much regarding protocols for different PLC's depending on customers requirements etc. after all, why re-invent the wheel.
 
The answer to your question is me
I have completed quit a few VB and Net Studio HMI's
i actually prefer it. It's far more flexible
the attached is a main screen done completely in Net Studio

is this vb forms??
Did you design your own driver for communication?
I would like to play with this and have so experience in vb studio
 
OT but related

OT


I have read that VB (Visual Basic) is approaching end of life. Do the various VB-using technologies (FT, AdvancedHMI, etc.) have a migration plan e.g. Visual C/C++ or Visual C#?
 
Last edited:
VB was rolled into Net Studio some time back
Net Studio is what Rockwell used to create Logix5000 and Panel View
Many other applications are created using it.
the one shown on the earlier post is actually Net Studio
i would venture to say the base program for most of the HMI programs is Net Studio
so don't think it's going where
 
According to Paul Thurrott's article (link) ...
Microsoft is not killing vb.net, but will not develop any new features or evolve the language.
 
According to Paul Thurrott's article (link) ...
Microsoft is not killing vb.net, but will not develop any new features or evolve the language.




Yes, I overstated the case. I found one article that quoted VB (VB6?) as "the ****roach that can't be killed."
 

Similar Topics

Why are there empty screens in between full screens are there supposed to be empty screens like 1, 2are full 3 is empty and 4 is empty and 5 is full
Replies
16
Views
5,278
hello all, I was wondering if there were anyway to write values to my plc micrologix 1000 from the HMI using the advancedhmi software nad not my...
Replies
9
Views
4,263
Is this example really the easiest way to write to an HMI tag in VBA? I've been playing with this for a couple hours and so far this is the only...
Replies
4
Views
16,743
I'm gradually replacing a Windows 2000 PC running Wonderware with a 15" Red Lion HMI. The application is a large plastic extruder. Right now, the...
Replies
0
Views
3,135
Has anyone ever used an input device like this? I looking for an option for an operator to hand write info on a trend to be printed. any help...
Replies
0
Views
2,758
Back
Top Bottom