Messages

1

Tips & Tricks / Re: AdvancedHMI on a Raspberry Pi

« on: April 15, 2015, 06:59:59 PM »

Sounds like a mission statement that I have heard in the past a time or two. I prefer to get my motivation from here:

http://www.despair.com/

2

Support Questions / Re: Read/Write AOI tags

« on: April 15, 2015, 06:56:57 PM »

It works great, thanks Archie!

I had tried using "PROGRAM" in my efforts as well, but my mistake was using a colon when I needed a period. Thanks again!

3

Support Questions / Re: Read/Write AOI tags

« on: April 15, 2015, 05:50:03 PM »

Hi Archie, thanks for the reply.

PD_AB300 is the controller name. And AB301 is a program within the PD_AB300 controller. And the tags were created in the AB301 program (I think that you already knew all of this).

The Add On Instruction's tag name is: zaAB301_F2103PT and it was created in AB301 as well.

From reading some of the other posts on this subject, I thought that: "PD_AB300:AB301:AB301_F2103PT.ACtrl.LowFaultSP" would work.


Thanks,

John

4

Support Questions / Re: Read/Write AOI tags

« on: April 13, 2015, 05:31:06 PM »

FWIW, this is what I have:

      EthernetIPforCLXCom1.Write("PD_AB300:AB301:HMI_AB301_F2103PT.ACtrl[0]", CSng(0.09))
      EthernetIPforCLXCom1.Write("PD_AB300:AB301:AB301_F2103PT.ACtrl.LowFaultSP", CSng(0.09))

Which causes a "PLCDriverException was unhandled" fault (without a Try - Catch). With the Try - Catch, it responds with a "CIP Error Path Segment Error".

I've got the PLC address correct, and the slot number is correct as well. The PLC can be pinged with no problem, and I have it up in RSLogix at the moment.


Thanks!

5

Support Questions / Read/Write AOI tags

« on: April 13, 2015, 03:50:18 PM »

Hi guys,

Does anyone know what the syntax would be for reading or writing to a tag in an Add On Instruction?


Thanks!

6

Tips & Tricks / Re: AdvancedHMI on a Raspberry Pi

« on: April 11, 2015, 09:30:09 PM »

Thanks,  But it's kinda small for my needs, I bought the 15.6" one...

I'll getto it up for the time being (using plastic cardboard comes to mind), but it's going to have to have a more permanent home.

7

Tips & Tricks / Re: AdvancedHMI on a Raspberry Pi

« on: April 11, 2015, 02:49:58 AM »

Well, I got my touchscreen in and it consists of the bare essentials. Meaning that the glass is not in a frame, and has no protection whatsoever. I'm not even going to attempt to wire it up until I come up with something to put it in.

8

Tips & Tricks / Re: AdvancedHMI on a Raspberry Pi

« on: March 23, 2015, 07:57:33 PM »

I'll definitely do that. But at the moment they are out of the big ones. I just sent them a message inquiring about when they expect to have it back in, we'll see what they have to say.

9

Tips & Tricks / Re: AdvancedHMI on a Raspberry Pi

« on: March 21, 2015, 04:55:41 PM »

Wow! Now this is some cool stuff! I've got my new Pi already, and I'll be getting one of those touchscreens as well. Thanks guys!!

10

Open Discussion / Re: Thanks

« on: January 01, 2015, 08:24:21 PM »

Thanks Archie! I've used AdvancedHMI for a couple of apps at work. *Much* nicer than anything else that I've worked with.

11

Open Discussion / Re: Connect to MODBUS device through USB port

« on: January 01, 2015, 08:21:40 PM »

It's not open source, but it will work with AdvancedHMI:

https://sites.google.com/site/shortbusdll/

12

Open Discussion / Re: Connect to MODBUS device through USB port

« on: November 19, 2014, 07:21:30 PM »

I seen in this thread mentioning Modbus Ascii.  I have a tool that I need to communicate to via USB, Modbus Ascii.  Will the ModbusRTUCom work for this?  I have the commands for the unit.  I just need to know if this will work or do I actually have to have the Modbus addresses such as the 30000, 40000, etc.

Thanks,
Jim

For Modbus ASCII & .Net, I would go with something like this:

http://www.modbustools.com/modbus_wsmbt.asp

13

Application Showcase / Re: Appreciate this application

« on: June 10, 2014, 10:43:17 PM »

Awesome!

14

Open Discussion / Re: Exception of type Mfgcontrol.........PLCDriverException

« on: June 10, 2014, 10:41:13 PM »

I've got one that accesses 80 PLCs. I just open a connection, read what I want, and then close (dispose of) the connection. I did have to modify AdvancedHMI to get it to work (See: http://advancedhmi.com/forum/index.php?topic=366.0), but that shouldn't affect you.

Have you tried reading just those tags that are giving you problems? Do they fail consistently?

And I would recommend opening just one connection to a PLC, reading what you want, closing it, and then going on to the next PLC.

 My other AdvancedHMI program reads 40 or so tags at once, loads them into a bunch of LED displays, and goes back and does it again. To make it easy for AdvancedHMI, I bunched all of the tags into a single array in the PLC. Have you tried that?

15

Open Discussion / Re: Connect to MODBUS device through USB port

« on: June 10, 2014, 04:28:21 PM »

Modbus ASCII or RTU? The timing constraints of Modbus RTU make it pretty tough to implement, but Modbus ASCII is very straightforward.

But a better way to do it might be to get yourself a Modbus gateway to do the heavy lifting for you. Such as:

http://gridconnect.com/media/documentation/grid_connect/GC_XPORT-MBTCP_DS_001.pdf