System Variables for Interface Signals
Hello all, I'm trying to figure out how to read a pmc address from a program on a 21iTB control..from looking through the operator's manual I think variables #1000-#1015 & #1032 are for this, but I'm not sure how it works...It says for detailed info refer to connections manual B-62523EN-1, which of course I don't have and can't find anywhere...Does anybody know how to do this...I'm trying to read to state of G1217.0 or relay R0031.0...Thanks.
Similar Threads:
I don’t think you are going to be able to read those addresses thru the system variables. The #1000 and #1032 ranges read input and output signals typically setup by the MTB for various uses. You are going to need the experts jump in and explain in detail if you can read the G and R stuff.
Stevo
You would need to tie these to one of the custom macro variables as you have said.
you would need a line in your ladder some thing like:-
R0031.0.......G54.0
---| |----------O-
Relay1........UI000
This would write 1 to #1000 when R0031.0 is on
I have attached the relevant documentation.
I am unsure if the variable will revert back to 0 when R0031.0 goes off, this needs to be tested. (I would expect it to.)
****************************************************************
*~~Darwinian Man, though well-behaved, At best is only a monkey shaved!~~*
****************************************************************
*__________If you feel inclined to pay for the support you receive__________*
*______Please give to charity [url]https://www.oxfam.org.au/get-involved/______*[/url]
****************************************************************
the correct number is B-63523.......Originally Posted by JMS4287
FANUC Series 16i/160i/160is-MODEL B
FANUC Series 18i/180i/180is-MODEL B
FANUC Series 21i/210i/210is-MODEL B
FANUC Series 20i-MODEL B
CONNECTION MANUAL (FUNCTION)
B-63523EN-1/03
it's 2258 pages!
Thanks
Thanks MysticMonkey, That looks like everything I need...time to have some fun playing with the ladder...
Fordav11, your right...I typed it wrong..that's probably why I couldn't find it anywhere...
I need to bring this topic to life, I getting mad with this stuff over here, do you guys now whatever reason why #1000 doesn't have its state changed by setting g54.0 to 1 over PMC exactly how it's showed on bellow replies?
On PMC:
X12.4-------------g54.0
--||----------------O--
On CNC:
WHILE[#1000EQ0]DO1
G98G01W0.050F100
END1
G99
The #1000 never changes even when g54.0 became 1.
Please Help me
What is your control , are you sure that G54.0 is UI0?
Hi,
test to do
#500=#1000,if you get a 1 in #500, then you experience a buffering condition.
if not, you don't have macro B.
to solve the buffer problem, insert a line with a "G4x0.1" before the END statement.
Hallo Norbert,
In fact I already tried this, and more, I tried to start the program with the g54.0 already 1 by starting the program with the machine over the switch.
About Macro B, I have it, at least par 9933#1=1 and all macro functions works fine.
I worked around the problem by using maths and storing the last requested ram bar position on a variable #500 (that will be kept even when the control is down) in this way I'll everytime know where the switch is except if the machine coordinate system changes, that is not usual once I have absolute pulse coders at the machine axes. It works well, but I'm still intricate about why #1000 doesn't became 1.
Thank you,
Eduardo
Hallo Eduardo,
did you check if G54.0 on the pmc>status screen show 1 ?
when an adress written too at more than one place, the ladders screen is then misleading.
Yes, in the status the g54.0 changes to 1
is the same true for G54.1 > G55.7 ?
if yes, what about F54.0 (#1100) > G55.7 , are they working ?
I have the 18i and 21i manuals if you need them.
Have a look here: - Post #3
http://www.cnczone.com/forums/fanuc/...programme.html
If I understand it correctly (doubtful) there may be a G-code available that does exactly what you want.
DP
Have just actually read the whole thread and realised that the original problem was already solved.
DP
Re: System Variables for Interface Signals
I had the same issue and got around it by placing an M1 before the statement.
Reply with Quote
