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

Pages: [1] 2
1
General Discussions / comparing value of two DM
« on: April 03, 2021, 12:34:52 PM »
I have DM[1] witch is the current position on a linear encoder. I want to know if DM[1] is = to or not greater than+ or- 4 cnts when at rest. If statement is true set Home flag.

2
Technical support / Re: Custom function
« on: April 12, 2020, 06:20:37 AM »
The 9999,90 is a mistake in the post only. It does run the drill up but not down. Is it possible to run the drill up and then down within 1 function. Would it work with the RFEFRESH and TESTIO removed.

3
Technical support / Custom function
« on: April 11, 2020, 12:23:56 PM »
Compiles correctly but won't work.

STEEPSPEED 1, DrillRate, DrillAccel
STEPMOVE 1, DrillSteps, 9, 9999, 90  //flag 9 = DrillComplete
REfRESH
IF TESTIO (DrillComplete)
THEN
STEPSPEED 1, 9999, 90
STEPMOVEABS 1, 0, 13
ELSE ENDIF

I do have a working program calling a second CusFn for the Stepmoveabs using flag 9. However when a stop command is used
we never know where the drill is. The goal is to make the drill cycle up and then down with 1 cusFn. Can't get the then, goes up not down.

4
General Discussions / settimer sv
« on: November 23, 2018, 07:29:17 PM »
I have been using SETCTRSV 6, DM[100] and entering a value via touch screen.
Will SETTIMERSV 7, DM[101] work as well.

5
Technical support / Re:HST
« on: October 05, 2017, 03:04:00 PM »
I have HSC I want High Speed Timer

6
Technical support / HST
« on: October 05, 2017, 06:59:20 AM »
How do I use a Cf to create 2 HST and keep that setting with loss of power or reset. I understand that I need HSTIMER 2. I have this CF called on 1st scan
 // Initialize parameters
Setsystem 4,3 ' Enable enhanced high-speed counter modes

// Setbaud 1, 6
Setbaud 3, 4  '19200 baud to HMI panel

DM[200]=192
DM[201]=168
DM[202]=0
DM[203]=210
DM[204]=9080

//Set_IPAddr 200

DM[205]=255
DM[206]=255
DM[207]=255
DM[208]=0

//Set_Subnet 205

//SetSystem 252,0
Can I add syntax here ?

7
Technical support / relay not latch Random
« on: July 26, 2017, 05:28:07 PM »
I have 2 identical machines running same program. They have been working fine for over a year. Now they will fail to latch a relay at
random. The PLC sees the input and will work if I latch it on line. I am using a CusFn to update parameters from a touch screen every .5 sec. If nothing has changed does it still record the setting and use up the memory record limits. I also have one machine that a counter will not count down to zero even thought the PLC sees the trigger.

8
Technical support / Re:DM[1]
« on: September 12, 2016, 09:12:59 PM »
 I control/set SetCtrSV 2, Eosplugs with DM[100] from HMI. I want to further manipulate this data with an expression.

If I understand the "mechanics"   The PLC program is pointed to DM[n] by a CusFN. Lable name " Value" from the define table points to DM[1]. "Value" is an easier way to say  DM[1] = DM[100] - 1.
Numerical values from HMI are PLUG DIAMETER and KERF WIDTH.
CusFN:
EosPlugs= EosLength/(PlugDiameter+Kerfwidth). // = DM[100]

Lable Name      Variable
EosPlugs            DM[100]
Value                 DM[1]

Add to CusFn
Value = EosPlugs -1
SETCTRSV 6, value //This should be a CRTSV 1 less than CTRSV 2  by DM[100].

To make this work in the sample program "simulation" I need to enter a value in the view variables table for DM[100] not DM[1]??????????              
.

9
Technical support / Re:DM[1]
« on: September 12, 2016, 08:10:03 AM »
Missed something. I am trying to get this to work.

Label name= value
Variable = DM[100] -1
This expression is the SetCtrSV 6, value "CuSfn"

[100]  is EosPlugs = EosLength/(PlugDiameter+KerfWidth)

10
Technical support / Re:DM[1]
« on: September 12, 2016, 08:01:30 AM »
Thanks! Is the problem in the fact that I am simulating the program and there is no value applied to DM[1]? If I edit the DM and enter 5 in the variables table it still doesn't work. It's like it doesn't read the DM.
I've tried all your suggestions

This program is just a learning tool. I don't want to ruin/corrupt a very important program.

11
Technical support / DM[1]
« on: September 11, 2016, 06:33:03 PM »
Does anyone know why it does not read the DM[1]. I am using DM variables/constants in a more complicated program that work but I don't understand why. I am trying to understand how to right them so I can modify another program. This program works if I enter a value in the View variable table. What am I missing????

12
General Discussions / DM[n]
« on: September 11, 2016, 06:04:33 PM »
Does anyone know why it does not read the DM[1]. I am using DM variables/constants in a more complicated program that work but I don't understand why. I am trying to understand how to right them so I can modify another program. This program works if I enter a value in the View variable table. What am I missing????

13
General Discussions / HSC in cusfn
« on: February 20, 2016, 03:39:48 PM »
what is the purpose of // in a cusfn.
 I am measuring the thickness of my material with an encoder. Desired control thickness is set with HMI and stored in DM[309]. When HSC2 < SV I want to send step pulses until it is > SV.
CusFn #13 see attached file.









14
Technical support / H11l2
« on: June 27, 2015, 08:30:04 PM »
Wired H11L2 as per diagram in manual (24v to 5v). When I test it by grounding pin #2 to simulate sink from PLC I only read .1 vdc (multimeter) to the stepper driver. shouldn't I read 5v Pin #4 to grnd.

15
Technical support / Re:Rencoder encoder RHS21D P1
« on: June 11, 2014, 09:42:19 AM »
The 1781 definitely will not work. Moving on to the ULN2003.
Thanks for all the help

Pages: [1] 2