It’s a very interesting project, thank you @stephan19 to have taken the time to share it with us!
Out of curiosity, i have a question for you. Did you try to use the serial link of the ESP in order to do the half duplex RS485 without success or you were just pragmatic and played it safe (which is most probably the most efficient way to go!!!)? Either way, as far as I can tell now : good job there.
I am not very familiar with the ESP familly but its seems the EPS API has this capability (see espressif git repo example.
I will try to build my own and post my feedback here.
Hi @hpopols,
RS485 is not the main problem. The main problem is the required sync break (according to LIN standard) which has to be send in front of every message. As far as i know the ESP cannot generate sync breaks.
Under the following link you can find a project for Raspberry Pis which solved this issue by changing the baudrate, after i finished my project. https://github.com/raintonr/hormann-hcp/issues/1
Moreover the raintonr project seems very promessing. If the baudrate trick works, this could be a deal breaker as it will only need a USB<>RS485 half duplex FT232 like cable directly wired to any HA box. I will definitely buy one of those cable and give a try toward this solution. However, I will definitively keep in mind your “hardware based” solution if the effort needed to have a working solution exceed my skill/patience/free time.
I come back here to share with you my though. I did received my USB<->RS485 cable and successfully used the “raintonr” software with my garage door.
However as advertised on the raintonr’s project page this is not usable as it is. I suspect some timing issues due to the sync packet “trick”. Moreover my garage door now displays the error code “4” (and time to time an error code 7) and won’t work anymore even without the cable wired and the software running. If I understand correctly, once the communication is done once the hormann motor remembers the attached device and won’t work anymore if the device is not porperly attached and responding to the slave status request packet.
Is anyone knows how to make the hormann motor reset the error 4 for good? A power cycle does not do the trick…
For this reason, the computer only solution is not a good solution has the computer is not reliable nor always powered up. Finally, the hardware route might be the best solution for me!
As far as i know you have to perform a factory reset to make the door “forget” the UAP1.
To perform a factory reset see the door manual chapter 12.
ATTENTION:
After a factory reset the door forgets everything and needs to be taught in again (see manual chapter 5). If you don’t know how to teach your door again it will not be usable anymore.
Thank you, the factory reset did solve my issue. I did not want to do it because I was worried to be unable to properly tune my garage door after that but it is quite easy and straightforward task to do!
If you are still interested, i could sell you mine. The current PIC16 firmware does not support my Hormann door. As a result it is useless to. PM me if you want it.
First I would like to thanks @stephan19 for sharing this great work !
The schematics are amazing and the code is so clean ! Great Job !
Concerning PCB production, due to the global shortage, some components like the PIC are not available for the moment. Also none of the drop’in alternative are available neither.
So, to be produced today, the board should be reviewed to use other at least PIC model (which might require code adjustement) or another form factor (like TSSOP).
Hello,
Amazing work from @stephan19 !
My garage door will be soon replaced by an Hormann one, with a Supramatic 4 motor.
I am not completely sure but from what I’ve understood so far, Hormman changed the protocol for the 4th generation motors. This project is made for 3rd generation motors so it won’t work for Promatic/Supramatic E4 motords?
Am I right?
It would be useful if people who are using this project could share what is the motor model they own.
Thank you very much for your quick answer.
It seems that a reverse engineering has been made for the protocol used by HORMANN with version 4 drives (which is version 2 protocol).
It should be doable to adapt the code with these data in order to make it works for version 2 protocol. But some hardware adaptations would be also required. At least the RJ12 connector is wired differently.
