03-12-2009, 10:42 PM
Here's the story. I am stuck with a TAC i/net system that has a 7798 keypad and a handfull of Micro Regulator fan coil controllers. For some reason, my room setpoints have weirded out and are all stuck at 76°-80°. First thing I tried was the dipswitch ram kill procedure, but all the setpoints revert back to what they were. I can overide the setpoints with the 7798 but at midnight, they revert back up again.
I finally obtained a licensed copy of inet7 software that was supposed to be given to the customer after startup. After the exciting installation, setup, configuration and learning to navigate an unfamiliar control software today, I finally achieved connecting to the 7798 through the serial direct connect and voila, username and password incorrect.
I tried the default tac/dacs to no avail. Now I've got phone calls out to everyone I know, but so far, nothing.
Does anyone know a trick to getting around the password issue? All I want to do is make a simple change to the room setpoint. I've got 3 bad controllers as it is and just want to rip the existing controls out, but as usual the customer wants to get the existing system working. I feel like I'm beating my head against the wall here because I'm almost at the cost in labor that I could have sold them a new system.
Any input would be greatly appreciated, though I don't expect the answer that the customer wants to hear.
03-13-2009, 10:40 AM
DACS is the default host password
your issue is the controller password needed to change the setpoint or to access to the 7798 controller.
I think you are screwed
03-16-2009, 12:50 AM
From reading your post, I do not think I-net was installed properly and the user name and password problem is comming from sql server, If the computer you are installing i-net on has never had i-net the user name and password tac-dacs will work. after you entered the site name, location, and serial #, it should have installed sql server 2000, Then rebooted your computer, and then installed I-net, after I-net completes the installation, it asks you to create a user name and password for sql server, What did you enter for the user name and password ? it will ask twice for a user name and password, if they are not the same each time you will get the problem you are having you should have put in "sa" as user name and "sa" as password.(the password can be what you want but the user name should be "sa". it will then create a default database. after it finishes, it will ask if you want to upgrade from a i-net 2000 database. choose no. I-Net is finished installing, Next you have to create a configuration profile, choose new profile, in the top left corner when creating a profile, you need to choose your connection type, choose Direct", next choose what com port your serial port adapter is on, next choose the connection baud rate, it is either 9600, or 19200. choose one. if we don't get communication established with one try the other, the box below you will need to enter the Link info, name it dc, and leave both the link and lan address at 0, to the right side of this is a box that says, i/o server maintain or shutdown on program close, choose shutdown, next click ok, and exit, before you exit the main configuration box, make the profile we just made active, exit the box, next start i-net, when i-net starts, it will ask for a user name and password, it is tac, dacs. Now do you have connection? look in the bottom right of the computer screen , i/o server will be running, and there will be a i/o server indicator light flasing in your taskbar, if it is flashing green, you have connection, if not, shut down i-net, go back to your configuration profile and change the baud rate from either 9600 or 1900, now save and exit, make sure i/o server shuts down in your taskbar because if it does not, it will not make the changes you made just now. Now restart i-net, do we have connection ? look at the i/o server in the taskbar, if so you are good to go, if not do you have the correct cable from your computer to the 7798b ? If none of this works, email me at firstname.lastname@example.org and I'll give you my #, And when you get to the job call me and I'll walk you through where your problem is and how we will fix it. hope this helps!!!!!Sorry so long but it's all in the details.
03-16-2009, 10:20 AM
Ok I got to the office this morning and did a few test, and recreated The problem you are having. When you installed i-net, it installed sql server correctly, but where things went wrong is when the program finishes installing, it sets up sql server, YOU DO NOT enter tac, dacs. that is for i-net only. Use "sa" for both the user name and password. Here is a set of instructions to get sql server working again.
Changing the SQL SysAdmin password on MSDE
If you are wanting to change the SQL password, you need to do this. You will not have to completely remove the Inet seven system only the MSDE.
1) Go into task manager and process 2) End process on these two files a) sqlservr.exe b) sqlagent.exe 3) Make sure you have a backup of the SQL database outside of Inet. 4) Go to control panel & Add\remove programs 5) Select the Microsoft SQL Desktop Engine program 6) Remove this program 7) Go back into windows explorer again. Go to programs files\Microsoft SQL file folder 8) Highlight the Microsoft SQL file folder and delete entire folder. 9) IMPORTANT go into the recycle bin and delete the Microsoft SQL folder from the BIN 10) When finished place the Inet Seven CD in the PC. It will try to auto start, cancel the install. 11) Go into windows explorer and go to the CD and double click the MSDE file folder. 12) Click on the Setup.exe file to reload the MSDE program again. 13) After this is loaded, then do a reboot of the PC. 14) Before starting Inet Seven again, go to the DbCreate Editor. 15) Once you open this editor you will be asked again for a new SQL password and confirm of that password. 16) Remember the "SQL User Name" is SA.
03-19-2009, 12:13 AM
You are the man. I'm probably going out to the site tomorrow morning. With the info you provided, I'm sure I'll be able to figure my way through the system. If not, I might email you. I may have figured out the password issue which happened to be a configuration mishap with the software supposedly. Right now my brain is fried from getting thrown to the wolves on a tracer summit system for the first time.
I've been ripping out trane controls for 10 years now, never had a customer actually want to keep them till today. My head hurts. You'd think a company that can somewhat master passing lon messages through the controllers on a system to a bacnet front end could actually make controlls that work rather than lock out constantly. :D
Powered by vBulletin® Version 4.2.0 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.