Ravelli Francesca Error code 17 No Flow

  • 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.

retiredldo

New Member
Feb 18, 2019
2
US
Hello stove has been cleaned multiple times in last few days, Has been running fine till last night when I got the error code. It is less than 2 years old. Is there a way to bypass the flow sensor, can I replace the flow sensor? lStove not working
 
Hello stove has been cleaned multiple times in last few days, Has been running fine till last night when I got the error code. It is less than 2 years old. Is there a way to bypass the flow sensor, can I replace the flow sensor? lStove not working
I have an RV 100c. I get an 09 air flow sensor problem I've replaced the sensor and it has not resolved the problem. RAVELLI knows this is A problem. So I got the code to shut off the sensor and it has been running fine since November with a sensor off. Ravelli is not responsive at all
 

Attachments

  • 20181009_152649.jpg
    20181009_152649.jpg
    72.7 KB · Views: 1,113
Any News yet ?
I was looking at my Ravelli documentation to see what < error 17 : no flow > could mean.
In the documentation I have , the error messages stop at 16.
Given there are already two or three error codes associated with air flow I would be curious to learn what triggered the new 17 error.
Can someone tell me more , or even better , point me to the latest documentation.
 
  • Like
Reactions: Ssyko
I replaced the small battery CR2032 in the back of my Ravelli 80 and i have not had any "no flow errors" 09 or 17.
Give that a try, it has been about two weeks and seems to have worked for me
 
Touchy unit. Can you just jump the terminals so the sensor 'thinks' it's working, when it ain't?
 
That small battery was probably for the clock.
I suggest that in the process of changing it you managed to clean a contact somewhere which was causing the problem.

Sidecar : no way , the sensor is composed of three analoque components. The firmware might be able to compensate for an open circuit , but a bad contact adding resistance would be hard to detect , thus causing the algorithms to get their nickers in a twist.
 
Just a suggestion, nothing more. Myself, I prefer a more mechanical stove versus an electronic one. Been my experience with electronic controls and lowest bidder scenarios that they tend to be failure prone. Not into complex, I'm a KISS person.