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 - MrBi11

Pages: [1]
1
Thank You, that worked without issues

2
No Errors, just building (install from CD option) and using setup.

Everything installs (or seems to) but no displays update and I'm assuming that the PLC isn't seeing switches (as motors don't start etc.)
Had to debug when I'm programming (DF1) thru same serial port the HMI is on), SO I have an option of doing one or the other.

Nothing major in my programming on the HMI, mostly just using stuff directly out of the toolbox. (Only fancy is I change the label text color on selector switches based on status of PLC)

3
I have a control built on a touchscreen computer (XP) that runs a bottle filling line.
My interface works fine in development (Start/f5 in VS). Doesn't seem to connect when compiled (Built and installed)
.
I copied everything to a flash drive and built the app on a different system (Win10) and installed on the control system with the same results.

Any ideas on what to look for to resolve?

4
Support Questions / Re: Multiple DF-1 interfaces on same form
« on: October 20, 2014, 01:27:01 PM »
Well, YES

Reboot and deleting and rebuilding the files seems to have corrected it, Thanks

5
Support Questions / Multiple DF-1 interfaces on same form
« on: October 01, 2014, 08:58:28 PM »
Archie, I seem to be having some issues with haveing my program talking to 3 separate micrologix 1500 PLC.

I've included 3 copies of the df-1 driver (using 3 different comm ports)  attempting to control 3 machines on the same line.
Each machine (head) needs to be setup every time the line is powered up to synchronize them (all revert to 'head 1' and need to be 1,2 &3)

I made the interface and it controls a single head fine, I simply copied all the 'devices' to another tab on my form and linked them to dfcomm2. trouble is now both 'controls' seem to be working with the comm2 driver (not comm1 & comm2)

Is there shared logic with the drivers getting confused?

Also on a side note: I can't address R6:0.LEN as .LEN isn't recognized. I did a 'work around' but using R6:0.PRE (which does address the proper word offset, even though it's a control not a counter/timer)

Thanks for your support (and awesome interface).

Pages: [1]