-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Via ETS: Programming the physical address only works very rarely. Mostly never. At some point, with luck, it works. #287
Comments
Its hard to say what the problem is. You probably have compare the telegrams ETS sends and receives with the one the devices sends and recieves. The hex codes are hard to read. It might be good to add a toString() method to the CemiFrame class and print them out in |
Here the Debug: AddressType is not GroupAddress or Destination is not 0 CemiFrame Received:
|
I added more logging in the devel branch. If you set the ApplicationLayer Logger to Info you should be able to spot the difference between ets monitor and the telegrams that reach the device. |
Hello everyone.
I have a question.
I have the example knx-demo.ino working in Platform IO.
knx-demo-ip.knxprod works.
I have already made my own project.
Not much changed. Just adapted the channels. But everything is still on a demo basis.
Via ETS: Programming the physical address only works very rarely. Mostly never. At some point, with luck, it works.
Then I can transfer the application program over and over again. Always works perfectly. No matter how often, it works great.
I delete the ESP. Then I can no longer get the device programmed via ETS With a lot of patience and luck, it works at some point. Can't say what the problem is.
Can anyone tell me where I could look? What information do you need? Possibly my project?
The text was updated successfully, but these errors were encountered: