Does activate ”pin" Fxxk up the
Virtual console? After activating the pin
The screen only have pixels? On all 4 heaters, i used virtual console to activate pin, so it worked before.
I made a ‘deployment’ on the EMQX Platform, but the Afterburner won’t connect.
The log says ‘TCP disconnected’ when using the 8883 port.
The 8084 port is for connecting via browser/websocket, and that works wel.
(When using 8084 for the Afterburner, the log says ‘TCP aborted’ or something like that.)
I enclosed some screenshots.
Anyone an idea what is going wrong and how I can fix this problem?
By the way, I first connected with EMQX’s public mqtt broker. That did work. Halas, the connection was not reliable.
I have been researching for a few months to integrate a heater into my smart caravan system, which I have developed myself. After searching everywhere, I finally discovered Afterburner. I read the codes and tested the protocols on my existing boards, but unfortunately, I couldn't get any results. The worst part is that the boards I have are listed as incompatible in the PDF documentation.
The biggest issue is that these incompatible boards are widely sold in the Turkish market, while the compatible ones are unfortunately unavailable. When trying to procure them, they can only be found on platforms like eBay and AliExpress, which impose high customs duties.
Would it be possible to add support for these incompatible boards? What approach should we take to analyze and decode the protocols? What are your recommendations and suggestions?
A small addition: When we couldn't decode the protocol, we examined the board more carefully and traced the connections leading to the STM8S chip. Later, we took control using an Arduino, but due to a lack of experience, I put this function on hold. (How many pumps are needed at a certain RPM? – Maybe 5 per second for 4000 RPM?)
To share knowledge and help others, I am sharing the pin connections on the STM8S.
Thank you in advance, and I wish everyone a good forum experience.
I've been enjoying my afterburner thermostat for a little over a year now and it's been a lifesaver ( and energy saver) in use for basement heating duty as an alternative to electric heat. My only issue with the setup has nothing to do with the thermostat but is due to the fact that so much heat gets wasted out of the exhaust pipe. I had been toying with some ideas to fix that when I came across some newer units that had dual brushless motors.
Essentially this allows for separate control of the combustion and blower fan speeds. By all accounts this helps enormously with efficiency (reports are that it reduces exhaust temperatures by over 200° ) and also allows greater blower speeds for better circulation.
Any chance for afterburner to support the setup anytime in the future with software updates and or Hardware if necessary?
I have a bit of a strange issue... After 2 or 3 days of my Afterburner being powered on it disconnects from the Wifi for no aparent reason...
The wifi still works from other devices (phone, laptop, tablet etc).
If I power cycle the router all devices re-connect apart from the Afterburner.
If I power cycle the Afterburner it re connects to the wifi immediatly and will stay connected for another 2 or 3 days, afterwhich it will disconnect....?!
Has anyone else had this problem, any idea how it may be rectified...??
I want to use my CDH as a portable heater that sits outside of my little camper and is ducted inside. The AB obviously provides much better control than the factory controller. But to use it I need temperature readings from inside the camper. I've searched the forums and read the user manual but haven't found anything that covers this. All I can find is how to wire extra temperature sensors. Is there a remote wireless temperature sensor or a way to accomplish this?
Is there an ideal body temperature we should be looking for that would indicate proper combustion? Or is it too dependant on air temp, temp sensor, etc? Or maybe an ideal range?
Ian here.
Long time user off the Afterburner. Fantastic bit off kit, than good I made 3 myself with the guidance off Ray. Top guy with extended knowledge off electronics and off cause the CHD
Very happy with the afterburner but got stuck on getting remote controlling to work.
My setup is rasberry running mosquitto broker, connected to wifi-1 and afterburner connected on wifi-2, and the webbcontent on https://mrjones.id.au/afterburner/mqtt.html for access. I use a dyn-dns service for getting current ip to wifi-1 even if changing, and I use port forward on wifi-1 to the rasberry. One forwarding for tcp port and one for websocket.
I have managed to configure the afterburner to connect to the broker on the tcp port and I can subscribe and receive status topics from the afterburner using mosquitto_sub to the broker so that seem to be working fine working.
But I can not connect webbcontent to the broker on the websocket port.
Now doing a test setup on wifi-1 location without the afterburner and was thinking I should see successful connection status in the webbcontent and in mosquito broker log (all logs enabled) even though afterburner not connected(it and wifi2 is currently off-line when I'm testing), and even though no afterburner topics are pusblished. Correct?
I could verify that the brokers listener on the websocket port is working, by using python paho and creating a websocket connection to the dyn dns address with the port(3030) I forward to the websocket listener port (8000). And I can publish topics and subscribe to see them when subscribing on the tcp port (1883).
Both my test-subscriber, test-pubslisher, broker and the webb content are on same wifi wifi-1, but broker and test subscriber are on one machine while test publsiher and the webbcontent are on another machine.
I have mqtt user and pasword configured in broker. And I have put same in webbcontent dialog as in my test connection.
Webb content keeps trying to connect but fail.
In the webbcontent i see print Socket error AMQJS0007E Socket, and then it changes to Connection Timout
I can see the JS webbcontent fails on mqttws31.js:979 "this.socket = new WebSocket(wsurl, ["mqtt"]);", but I only see failed connection. Noting in the mosquitto broker log about the webbcontent trying to connect.
If I use chrome I get wss and if firefox ws, but looks same error.
Can anyone shed some light on an error message briefly shown on the AB's start-up? See image
It is only on for a second or two, and I only noticed it as my temperature set point seemed to be much lower than previously set. As you can see from the second image the sensor seems to be operational and functioning as would be expected.
