Carrier Infinity

Pretty quiet in here.
 
One thing I was considering recently is that register permissions could be based on device address.  For example some devices may be allowed to read/write registers that other devices are not.
 
Likely were waiting for the SAM testing. Seeing that the SAM interfaces via Rs232 serial (I think) wouldn't it be nice to create a remote connection where the SAM could be interfaced and monitored to our remotely connected systems.
 
Sorry guys, my adapter went to Buffalo, NY, but I do not live there...
A second one on its way, at least that's what I am told...
All the other ones I found on amazon seem also to be shipped from China, so for now testing will have to wait
 
OK, so finally got my adapter. This is a VID_067B&PID_2303 or "Prolific USB-to-Serial Comm Port" with two screw terminals.
From here on I will need some hand holding as I am venturing on unfamiliar areas.
 
I have access to Windows XP or Ubuntu 32-bit 11.04 (IIRC) running on a old Thinkpad T23
The SAM is near my computers and it is powered separately, i.e. the D (red on my system) wire on the bus in not connected, only A, B and C
 
I would like to avoid any damage to the system or control, especially since the cold is setting in and any time without heat could end in a revolt within my family.
 
These are the steps I am planing.
1. Power down CARRIER system from shut-off switch.
2. extend the bus from the SAM terminals A and B with 16 gage wire to USB-RS485 adapter. (there are not markings on the adapter which side is considered A or B
     a. does it have any importance how am I connecting to the adapter?
 
3. Install the driver package on Windows XP.
4. Plug in connected adapter
5. Start HyperTerminal
     b. what terminal settings? the adapter shows off as COM4
     c. what is the preferred way capturing output?
 
5. Turn on Carrier system
6. Wait for start-up to complete.
 
Phase II: run initial install command on control, I plan to add 4 remote sensors that I already have to wire them in parallel-series and connect them to main thermostat for temperature averaging in 4 bedrooms.
As a recap, I have a NG fired furnace+Greenspeed Heatpump with Zone controller and 2 zones, Air Filter, Humidifier and SAM. No UV light. One zone has the main control, the other has a Smart Sensor.
 
Coincidentaly, I am having the dealer that installed it servicing the system tomorrow morning.
The young guy that was here before seemed knowledgeable, so if there is any question a tech may be able to answer, I can ask tomorrow.
Please comment on the above or suggest steps to be performed. 
 
 
 
 
Sounds good.  I was referring to RS232 port on the laptop to connect it to.  That laptop may be old enough to have one built in.
 
Don't see any problems with what you posted. Terminal A is likely on the left.  Settings are 38400bps 8bit no parity 1 stop bit.
 
For logging you can try something like http://www.eltima.com/products/rs232-data-logger/ or http://www.docklight.de/ or you can use python or perl.
 
Once you're up and running I'm sure one of us can put something together that will let you pass in a text file of ASCII commands to send to the SAM and capture the results on the bus so you're not typing them all in by hand
 
So I hooked up the  RS485 adapter and restarted the HVAC system. The serial port logger seems to work and captured data from the RS485 bus.
I have problem with the SAM serial port though. I disconnected it from the ELK panel, and with a serial cable connected it to the laptop.
I tried different terminal programs including hyperterminal and various settings beside 38400baud, 8N1, no flow control to no avail.
I suspected the cable, but than the same happened with a cable connecting my Brultech ECM to CQC, which there at least was working.
The SAM is working and it is accessible through the LAN port. I also tried to disconnect the LAN, than restart with disconnected LAN, which lead to a red LED light on SAM, meaning no connection to Carrier server from the SAM documentation.
 
At this point I am out of ideas how to troubleshoot the serial connection. If the SAM is bad, it may explain why I gave up on programing it with ELK, although IIRC I was able to get thermostat temps in ELK and CQC.
 
The RS232 port should be 9600, 8N1.  The terminal should be configured to send CR LF when you press enter, I believe this is already default in docklight & hyperterminal. 
 
Well, what do you know, your karma and good spell did it... :-)
I swear I tried this setting, but I based my assumption for 38400 since this is what ELK has specified for connecting SAM to M1XSP, I am wondering if this is a mistake in their docs, or can it be that ELK communicates directly RS485?
 
In any case, all is good, getting :NAK CMD on emty CR and response for proper query like S1MODE?
Answer  "S1MODE: AUTO"
 
Ok, excellent.  The ELK documentation is wrong if it connects to the same RS232 port.
 
Now we just have to put together a list of commands as a docklight sequence that you can run while you log the results.  Then we'll get to work decoding them.
 
A bit of data to wake you guys up:
 
2001,003003,128 bytes
B16-B23: Z1-Z8 Heat Setpoint
B24-B31: Z1-Z8 Cool Setpoint

2001,003005,128 bytes
B0-B11: Z1 Name
B12-B23: Z2 Name
B24-B35: Z3 Name
B36-B47: Z4 Name
B48-B59: Z5 Name
B60-B71: Z6 Name
B72-B83: Z7 Name
B84-B95: Z8 Name

2001,003B02,29 bytes
B3-B10: Z1-Z8 Current Temp
B11-B18: Z1-Z8 Current Humidity (same value, single sensor)
B20: Outdoor Air Temp
4,B21: Zone Unocc Bitflags
5,B22: Mode (0=heat, 1=cool, 2=auto, 5=off)
10,B28: Displayed Zone

2001,003B03,150 bytes
1,B3-B10: Z1-Z8 fan modes? (0 = auto, 1 = low, 2 =  med, 3 = high)
2,B11: Zone Hold Bitflags
3,B12-B19: Z1-Z8 Heat Setpoint
4,B20-B27: Z1-Z8 Cool Setpoint
5,B28-B35: Z1-Z8 Target Humidity?
6,B36: Fan Auto Cfg
8,B38-B53: Z1-Z8 Hold/Override Duration (2 bytes each)
9,B54-B149: Z1-Z8 Name (12 bytes each)

2001,003B04,11 bytes
2,B4-B5: Vacation Hours Remaining
3,B6: Vacation Min Temp
4,B7: Vacation Max Temp
5,B8: Vacation Min Humidity
6,B9: Vacation Max Humidity
7,B10: Vacation Fan Mode

2001,003B05,11 bytes
1,B3: Filter Level
2,B4: UV Level
3,B5: Humidifier Level
4,B6: Filter Remider
5,B7: UV Reminder
6,B8: Humidifier Reminder
7,B9: Vent Level
8,B10: Vent Reminder

2001,003B06,52 bytes
1,B3: Backlight Setting
2,B4: Auto Mode
4,B6: Deadband
5,B7: Cycles per Hour
6,B8: Schedule Periods
7,B9: Programs Enabled
8,B10: Temp Units
10,B12-B31: Dealer Name
11,B32-B51: Dealer Phone

2001,003B07,163 bytes
Monday Schedule Data
1,B3-B7: Z1 Wake
2,B8-B12: Z1 Day
3,B13-B17: Z1 Evening
4,B18-B22: Z1 Sleep
1,B23-B27: Z2 Wake
2,B28-B32: Z2 Day
3,B33-B37: Z2 Evening
4,B38-B42: Z2 Sleep
1,B43-B47: Z3 Wake
2,B48-B52: Z3 Day
3,B53-B57: Z3 Evening
4,B58-B62: Z3 Sleep
1,B63-B67: Z4 Wake
2,B68-B72: Z4 Day
3,B73-B77: Z4 Evening
4,B78-B82: Z4 Sleep
1,B83-B87: Z5 Wake
2,B88-B92: Z5 Day
3,B93-B97: Z5 Evening
4,B98-B102: Z5 Sleep
1,B103-B107: Z6 Wake
2,B108-B112: Z6 Day
3,B113-B117: Z6 Evening
4,B118-B122: Z6 Sleep
1,B123-B127: Z7 Wake
2,B128-B132: Z7 Day
3,B133-B137: Z7 Evening
4,B138-B142: Z7 Sleep
1,B143-B147: Z8 Wake
2,B148-B152: Z8 Day
3,B153-B157: Z8 Evening
4,B158-B162: Z8 Sleep

2001,003B08,163 bytes
Tuesday Schedule Data

2001,003B09,163 bytes
Wednesday Schedule Data

2001,003B0A,163 bytes
Thursday Schedule Data

2001,003B0B,163 bytes
Friday Schedule Data

2001,003B0C,163 bytes
Saturday Schedule Data

2001,003B0D,163 bytes
Sunday Schedule Data

Schedule Data
5 bytes each
Time - 2 bytes
Heat Setpoint
Cool Setpoint
Fan Mode
 
For table 003B, the only one the SAM writes to, the first 3 bytes of a write command are important parameters specifying what data to overwrite (i.e. not the whole record).  I haven't tried to decode them yet. 
 
At this point, you should be able to dump the tables listed above and verify that your data matches these patterns.
 
Back
Top