MC1, TX1, SBC and GX Manuals
Does anyone have a link to the user/programming manuals for MC1, TX1, SBC and GX?
Originally Posted by davem
You have mail.
Originally Posted by snowm0811
I could use a copy of that.
Could I get a copy please
Originally Posted by MatrixTransform
A copy for my library would be appreciated.
When you talk, you are only repeating what you already know. But if you listen, you may learn something new. - Dalai Lama
If possible, could you please send me the link or a copy for our referrence. Your help is appreciated.
I also could use a copy. Currently working with a site where I think some TX01 have been wired wrong since day they were installed.
AAM SAGE to JACE Integration
I need Help! I posted this else where, but thought someone within this thread could help.
Has anyone out there setup a JACE on an American AutoMatrix Network with existing SAGE Units still in operation? I have a customer that has ask for exactly this as Phase I of his upgrade.
I was able to look at the SAGE Unit using ADAM and confirm that all 4 ports are setup as PUP Networks 9600/8/1/N.
What setting do I need to change in the SAGE for it to allow the JACE to set on the same network and see the same points?
I also confirmed that the JACE has 4 network cards all setup with the PUP Drivers.
Can it be done? I believe it can, just really not familiar with the SAGE Units at all.
I have tried to contact AAM with no luck so far?
Thanks for the help.
From my limited experience you can have 1 master type device on the network, either the JACE or the SAGE but never both. Maybe there is a way to make the JACE act as a slave style device and exist but I am not aware of the setup for that.
By default the Sage & PUP devices do not use token passing but it can be enabled. If setup for token passing then there is no sole master and you could have the Sage and Jace online at the same time. This would be a setting on the PUP driver in the Sage as well as all of the field devices. I am with some AAM people today and will ask them to verify it.
Osiyo is pretty sharp on that line.
any chance I could get those reference manuals? Need some more late-night reading material.
Well .... I've sure as heck never tried to do a replacement of a Sage with a Jace the way you're trying to do it. And I've done a lot of Sage replacements, with Jaces or AspectFT systems.
Originally Posted by BMSdude
Technically a person could do something along the lines of what you suggest, tho I sure as heck don't know WHY you'd want to do it that way.
Leave the Sage as is, put Jace on a port as an irresponsible peer ... with a non-conflicting network ID ... that way it won't try to seize the token. Put Jace's network ID on Sage's list of peers. Periodically, in accordance with settings you selected, Sage will pass the token to Jace, and allow N number of transactions.
Pretty much the same procedure you'd use to let any other PUP controller on line and give it the token periodically so it could play Master and send or fetch information.
<Shrug> Never done it that way. Wouldn't do it that way myself. But it should be quite doable. It'll have lousy results. Both will be really slow in fetching or sending data. Which may or may not have adverse results on overall sysem operation. No way for me to know as I have no details of the system setup, how many controllers are on line for each port, how much of the control routines resides at the field controller level as versus at the Sage level.
Typically we'd pre-set up a Jace, and just cut over everything at once. Or, if a larger and more complex installation, we'd do one port at a time. Leaving Sage intact. Pre-setup Jace for one port at a time, pull designated port cable from Sage and plug into Jace. Verify everything is working, tweak and adjust as necessary. If it takes more time than we have, i.e. more than an 8 hour day, remove cable from Jace and plug it back into Sage for over night.
Switching from a Sage to a Jace (or an AspectFT system) isn't just all that complicated as long as one does one's homework and verifies how the existing system really is operating, who's doing what and how, etc.