RS232 Connection

  • Active since 1995, Hearth.com is THE place on the internet for free information and advice about wood stoves, pellet stoves and other energy saving equipment.

    We strive to provide opinions, articles, discussions and history related to Hearth Products and in a more general sense, energy issues.

    We promote the EFFICIENT, RESPONSIBLE, CLEAN and SAFE use of all fuels, whether renewable or fossil.
  • Hope everyone has a wonderful and warm Thanksgiving!
  • Super Cedar firestarters 30% discount Use code Hearth2024 Click here
C

Citabria

New Member
Nov 22, 2018
20
OS
Hi,
I made a connection on RS232 with my pellet stove and get a constant stream of values as output. Is there somewhere information how to handle this stream?
Thanks
 
What kind of stove? Ive never seen one with a DB9 serial port. Is the db9 on the control board?
 
Austroflamm Clou. I have already done some research and it probably has to do with the baud rate settings. I was hoping someone could help.

It is actually a RJ45 port.
 
Im guessing that you will need software from Austroflamm to interpret the data. It’s probably how they set up the initial installation settings or for troubleshooting issues.
 
Possible, but I found on a website related to Austroflamm Clou, that a program as TERMITE could be used. This is a simple RS232 terminal application. This makes me think it should gives some readouts at least.
 
What are you looking for data wise? Just curious?
 
Have you tried termite? Maybe call Austroflamm support and see if they will tell you if its proprietary software needed or not.
 
I don’t know what to tell ya then.
 
The baud rate is the rate at which information is transferred in a communication channel. If you have recieved running data the baud rate is good. The problem your going to have is decrypting that data, thus you need the software or app to put that data in perspective.
 
Can you putty to it? Also the RJ45/com port cable, was it a cable you had laying around or did it come with the stove? The pinout could be wrong, maybe needs to be null versus straight through, and assuming the pinout is correct you still have to determine all of those settings, such as baud rate, data bits, parity, stop bits, flow control.
 
  • Like
Reactions: Ssyko
tadmaz said:
Can you putty to it? Also the RJ45/com port cable, was it a cable you had laying around or did it come with the stove? The pinout could be wrong, maybe needs to be null versus straight through, and assuming the pinout is correct you still have to determine all of those settings, such as baud rate, data bits, parity, stop bits, flow control.
Click to expand...

Sorry, I didn't see your reply. I am just using a standard console cable which I also use for my routers and other network devices. I am not using putty, but termite, as this is what I am found on the internet on a dealer website. Sadly enough they don't share any connection settings, and they are also not willing to answer this question for me. It think it is bad if your customer support is so protective in their information. I keep on looking...

The prime reason I am trying to connect to it is because the stove goes in error after random times. It show the error "Connection problem between control and motherboard". As a solution in the user manual Austroflamm says that this happens during an update of the motherboard and it should go away after the update is completed. It doesn't. At random times, at least once a day, it happens and the stove shuts down. After disconnecting the current, it works again. I want to check if I can change or see something on the console. Probably this is similar to other Austroflamm pellet stoves, so if someone gets a recent technical manual, the answer might be in there. My guess is that the battery is bad and that they stove cannot store it's state properly. They major problem is that opening this stove to get to the motherboard is a challenge without a proper manual.
 
Yep you need a null modem cable. The one you have is a through put cable.
 
Ssyko said:
Yep you need a null modem cable. The one you have is a through put cable.
Click to expand...

I do use a null modem cable. The cable you see it simply a serial port for a PC as they now lack serial ports, they use USB instead. So I use a null modem cable from the serial port, which is on this cable and stove.
 
Citabria said:
I do use a null modem cable. The cable you see it simply a serial port for a PC as they now lack serial ports, they use USB instead. So I use a null modem cable from the serial port, which is on this cable and stove.
Click to expand...

Your cable is "USB to Straight-Through RS232 DB9 Serial Adapter". Straight-through is different than a null modem cable. The converter I suggested might do the trick. Then again it may not :)
 
  • Like
Reactions: Ssyko
Yes, but once again, this is not a cable, this is a port emulator. To avoid having too much focus on this adapter I found a very old system with a hardware serial port and connected my null modem cable, NOT the RS232 cable mentioned here above, a normal DB9 to RJ45 cable, direct in the COM port of the computer and the other end in the RJ45 of the stove. Result is the same. Random text output.
 
Can you post some of it here?
Maybe someone knows the pattern
 
Are you sure the new DB9 to RJ45 cable is a null modem cable? Usually those are labeled "NULL MODEM" on the DB9 connector. If it doesn't say that, it may also be a straight-through cable. I've seen the garbage text before, and got it fixed by buying the custom pinout cable, where it wasn't straight-through or null modem, it was its own proprietary pinout.
 
It depends on the connection settings I give it. It looks complete random but I might try.

This is a log in HEX:
Terminal log file
Date: 3/12/2018 - 23:17:45
-----------------------------------------------
0F 00 F7 17 00 FA 17 00 F7 17 00 D7 17 00 F0 17
00 F7 17 00 D7 17 00 F7 17 00 D7 17 00 F7 17 00
F7 1B 00 F7 17 00 F7 17 00 DB 1B 00 D7 17 00 F7
17 00 D7 17 00 F7 17 00 D7 1B 00 F2 1B 00 F7 17
00 F7 1B 00 F7 1A 00 F7 17 00 F7 17 00 D7 1B 00
D7 1F 00 FB 17 00 F0 17 00 D7 17 00 F7 17 00 D7
17 00 F7 17 00 F7 17 00 D7 17 00 FB 1B 00 F7 1A
00 F7 17 00 FF 17 00 D7 17 00 F7 17 00 D7 17 00
F7 17 00 D7 17 00 D7 17 00 F8 F7 F0 17 00 F0 F7
F0 1F 00 F0 FB F0 00 00 D7 17 00 F7 17 00 F7 17
00 D7 1F 00 F7 1B 00 FB 1B 00 F7 17 00 D7 17 00
DB 17 00 F7 17 00 F7 17 00 DB 17 00 FF 17 00 D7
17 00 D7 1B 00 DB 1F 00 FB 17 00 F7 17 00 D7 1F
00 F7 17 00 D7 17 00 DB 17 00 F7 17 00 F7 17 00
F7 17 00 DF 17 00 DB 17 00 F7 1B 00 F0 1B 00 F7
17 00 D7 17 00 F2 17 00 D7 17 00 F0 17 00 D7 17
00 FF 00 00 D7 17 00 F2 1B 00 F7 17 00 DA 17 00
F7 1A 00 D7 17 00 F7 17 00 F7 17 00 DB 17 00 D7
1F 00 FB 17 00 D7 17 00 D7 17 00 D7 17 00 F7 F0
17 00 FC D7 FC 17 00 F0 DF F0 17 00 F0 FF 17 00
D7 17 00 FA 1B 00 D7 17 00 F7 17 00 FA 17 00 D7
17 00 FA 17 00 D7 00 00 F7 17 00 F7 1F 00 F7 17
00 FA 1B 00 D7 17 00 D7 1F 00 D7 17 00 D7 17 00
F7 17 00 F7 1B 00 F7 17 00 F0 17 00 D7 17 00 FF
17 00 F7 17 00 F7 17 00 F7 17 00 FB 17 00 F2 17
00 F7 17 00 D7 17 00 F7 17 00 D7 17 00 F7 1B 00
F7 17 00 DF 17 00 F7 17 00 D7 17 00 F7 1F 00 F7
00 00 D7 17 00 F7 17 00 F0 17 00 F7 1B 00 F7 17
00 D7 17 00 F7 17 00 FB 1B 00 F7 1B 00 F7 17 00
D7 17 00 FB 1F 00 FA D7 FA 17 00 F0 FA FD 17 00
F0 D7 F0 17 00 D7 17 00 F7 17 00 FF 17 00 D7 17
00 D7 17 00 D7 17 00 F7 1B 00 F7 17 00 F0 17 00
FF 17 00 DA 17 00 FB 17 00 F7 17 00 F0 17 00 FF
1A 00 D7 1B 00 FB 1B 00 D7 17 00 F7 17 00 FF 17
00 D7 1A 00 F7 17 00 F7 17 00 D7 17 00 F7 1B 00
D7 1B 00 F7 17 00 F7 17 00 D7 00 00 D7 1B 00 D7
17 00 F7 17 00 FA 17 00 D7 17 00 F7 17 00 D7 1A
00 FB 17 00 F7 1B 00 D7 17 00 DB 17 00 D7 17 00
F7 1A 00 F7 17 00 D7 00 00 F7 17 00 FB 1B 00 D7
17 00 D7 17 00 D7 17 00 F7 17 00 FA FA 17 00 F0
FB FC 1B 00 FC D7 F0 17 00 FC FA 17 00 F7 17 00
F2 17 00 F7 1B 00 F7 1F 00 D7 17 00 F7 17 00 F2
17 00 D7 17 00 F7 17 00 DA 17 00 F7 1A 00 D7 17
00 D7 1A 00 F7 17 00 D7 17 00 F7 17 00 F7 1F 00
DB 17 00 F7 17 00 D7 17 00
-----------------------------------------------
Date: 3/12/2018 - 23:17:58
End log file


This is one in ASCII:
Terminal log file
Date: 3/12/2018 - 23:27:54
-----------------------------------------------
ccÿŸ
‰<0>|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{üccÿŸ
‰<0>|`¬¬Ÿ
{øccÿŸ
‰<0>|`¬¬Ÿ
{ü_°¬¬Ÿ
þccÿŸ
‰<0>_°¬¬Ÿ
ü|`¬¬Ÿ
{ø_°¬¬Ÿ
þccÿŸ
‰<0>_°¬¬Ÿ
þ|`¬¬Ÿ
{ø_°¬¬Ÿ
üccÿŸ
‰<0>_°¬¬Ÿ
þ|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{ðccÿŸ
‰<0>|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{øccÿŸ
‰<0>|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{üccÿŸ
‰<0>|`¬¬Ÿ
{üccÿŸ
‰<0>|`¬¬Ÿ
{üccÿŸ
‰<0>|`¬¬Ÿ
{øccÿŸ
‰<0>|`¬¬Ÿ
{àccÿŸ
‰<0>|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{øccÿŸ
‰<0>|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{øccÿŸ
‰<0>|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{üccÿŸ
‰<0>|`¬¬Ÿ
{ðccÿŸ
‰<0>|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{ðccÿŸ
‰<0>|`¬¬Ÿ
{üccÿŸ
‰<0>|`¬¬Ÿ
{üccÿŸ
‰<0>|`¬¬Ÿ
{üccÿŸ
‰<0>|`¬¬Ÿ
{üccÿŸ
‰<0>|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{üccÿŸ
‰<0>|`¬¬Ÿ
{üccÿŸ
‰<0>|`¬¬Ÿ
{üccÿŸ
‰<0>|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{ðccÿŸ
‰<0>|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{üccÿŸ
‰<0>|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{üccÿŸ
‰<0>|`¬¬Ÿ
{üccÿŸ
‰<0>|`¬¬Ÿ
{üccÿŸ
‰<0>|`¬¬Ÿ
{þccÿŸ
‰<0>|`¬¬Ÿ
{üccÿŸ

-----------------------------------------------
Date: 3/12/2018 - 23:28:10
End log file
 
tadmaz said:
Are you sure the new DB9 to RJ45 cable is a null modem cable? Usually those are labeled "NULL MODEM" on the DB9 connector. If it doesn't say that, it may also be a straight-through cable. I've seen the garbage text before, and got it fixed by buying the custom pinout cable, where it wasn't straight-through or null modem, it was its own proprietary pinout.
Click to expand...
I am using this exact cable: https://produto.mercadolivre.com.br...om-cisco-rj45-x-db9-femea-novo-_JM?quantity=1
 
I have just tried yet another cable. This time from Cisco, same result. But then I found a very old DB9 connector that once came with some very old network device. When I plug a normal network cable in that DB-9 connector and the other end of the network cable in the stove, I get at baud 2400 a constant return of FF in HEX. Whatever that means, as I expect that a normal CAT5 cable isn't the correct cable for this job.
 
You must log in or register to reply here.

Similar threads

S
Disconnecting Sections of Duravent Stove Pipe Installed 2 Seasons Ago
Replies
2
Views
146
The Pellet Mill - Pellet and Multifuel Stoves
bogieb
bogieb
P
Roko Streaming Stick - Replaced with a Fire stick
Replies
19
Views
1K
The Inglenook
EbS-P
EbS-P
D
Harmon XXV blowing internal fuse
Replies
2
Views
79
The Pellet Mill - Pellet and Multifuel Stoves
Dave22
D
jonher
Vapor Fire 100 manometer install
Replies
0
Views
245
The Boiler Room - Wood Boilers and Furnaces
jonher
jonher
A
Single to double wall adapter?
Replies
2
Views
196
Classic Wood Stove Forums (prior to approx. 1993)
acaro99
A
Top Bottom