-
Notifications
You must be signed in to change notification settings - Fork 74
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
LUBA USB driver query #120
Comments
Yes, that should do it. (You can see it as part of the Commissioning sequence.) |
I did the test but it seems not working as I isolated the code for doing that.. What would be the Brocast() value for that ? 255 ? |
Could you describe your setup in more detail? |
I've 2 dali light, everything is working fine with your python scripts. Now I try to clear their short address. So I isolated this code
But nothing seems happen, this is the sequence writed on dali bus
|
That should do it. The two sends of 0x7f 0x80 must occur within 100ms of each other, with nothing else being sent in between — are you managing this? |
I'm using lunaton USB DAlI2 device, i'm able to see both request:
Only 15ms between 0x7f 0x80 . Is this normal ? Are the command correct ? After sending thos commands, I'm still able to get ballastStatus if I target the short address THanks for your help, that's realy appreciate ! |
They look correct, and 15ms between the two repetitions looks normal. What do you get for |
Hang on, I might be being stupid. So you should look into how the wrong frame is being sent. |
Oh yes that was a test.. 0xa3 0xff But no changes :( The funny fact is that i've only 2 ballasts and I can ask "ballasts status" on all addresses (means 20.21...40...63). They are all responding... How it's possible ? Do you've to call "Terminate" after ths reset or Initialise before ? |
Something strange with DTR0, always increasing, I send the command 0x98 for getting the DTR0 and this is the response:
I send again
Every time I ask for DTR0 value, the value is increasing. this is the request frame : "0x0f 0x98" |
Oh this is the case for all queries x) Asking if ballast exists: Request : 0x03 0x91 on short address 1 Request : 0x03 0x91 |
It sounds like you might have both units set to the same short address? Or there might be some other hardware issue interfering with communication. What happens if you disconnect one of the units and only have one on the bus at a time? |
I got the issue... Seems that you are treating the request id feedback as an answer with Luba USB It's why it's increasing... any new request a new id + 1 Maybe something wrong with Luba status ? |
Oh! Probably worth opening a new issue for that and mentioning @sl-wallace — he wrote the LUBA driver. (I don't have one so can't test it.) |
Interesting, I'll have to take a look into it. I haven't got my LUBA test hardware with me at the moment but I should be able to within the next week or so. |
Hello there,
first at all, thanks for your awesome job !
I would like to know the sequence for removing all short addresses of a dali bus ?
is that the correct sequence ?
Thanks for your help !
The text was updated successfully, but these errors were encountered: