To test this feature, visit your live site.

Dual Dome Setup Automation

I am working up a building with dual nexdomes on it. The setup has 2 of the arduino versions of rotators/tracks. (Older Style) and the one dome has a arduino shutter system already. I converted it to a dual track/motor system and works good.

I am looking to build/acquire the other shutter and I'm wondering if the arduino xbee system is going to work with 2 shutters in proximity to each other? I wasn't sure if anyone has input, but are these shutters paired in anyway, or is it just a signal in proximity that it detects and runs?

This may cause a hiccup in the plan.

I've asked several questions via email, but I never get any response from NexDome on these questions, not sure if anyone monitors these forums either, but give it a go. Or a phone number would be great.

41 comments

41 Comments

James Myres

Feb 04

Thanks Josh for leading me to the docs in the firmware.

Very curious though...

The XCTU configuration files NexDome Rotator.xpro and NexDome Shutter.xpro both had the DL settings to FFFF and FFFE respectively which is to address each others MY settings FFFE and FFFF respectively.

Also the A2 for the Rotator was set to 5 while the A1 was left at 0 and the A1 for the Shutter was set to 5 while the A2 was left at 0. This is similar to what I found on my own while fiddling in XCTU to get reliable communication.

The problem seems to be that the firmware first uses the RE, WR and AC command to factory rest to the defaults and then set everything including both A1 and A2 to 7 for both Xbees and then does not set the DL settings from 0 to FFFF and FFFE.

I'm in favor of either not letting the firmware reconfiguring the Xbees, or having the firmware set the DL, A1 and A2 properly. Better yet, leaving the A1 and A2 to 0 so the channels and pan Id's do not float. Floating these settings could be problematic for a multi dome setup if the rotators and shutter are powered cycled incorrectly or there is a stronger signal from other compatible devices.

I'm going to setup the firmware in Visual Studio as you suggested.

James Myres

Jan 30

Glad to hear you were successfull.

I've finally got the shutter communication after swapping XB's. It is still unreliable and will disconnect at unpredictable times.

I'm think I may have a bad Xbee but dont know whuch of the newer available XBee's are compatible with the firmware.

James Myres

Jan 21

I updated my pre 2021 rotation and shutter automation firmware to 4.0 after the shutter would not connect. I've tried other versions as well after using the firmware clearing hex file. Still nothing works. Going to check both Xbee3 pros that came with it for the same frequency and channel ID with the USB adapter with XCTU before doing anything else. The adapters should be here today.

josh

Jan 22

Replying to

I also got XCTU and will see if it works to redo channels. I have 2 rotators/2 shutters working and operational side by side, so be interesting to see if it can be easily configured this way.

James Myres

Jan 21

I've added a PDF of my single drive modification that did the trick at https://www.nexdome.com/forum/general-topics/pre-2021-2-2-dome-shutter-automation-issues.

James Myres

Jan 20

I'm having issues with the Xbee3 Pro communication to my shutter. It loops the following from the rotator in Putty about every minute:

XB->WaitAT

XB->Config

XB->Detect

It never gives the XB>-Online message, so I believe this is all a rotator message. I can't really see how the rotator can change the shutter frequency or channel ID without a connection first. Supposedly this has been set before by Nexdome before shipping or set possibly at the firmware installation of both.

It appears that the frequency and channel ID can to be set using a Windows, Mac or Linux using the XCTU utility that can be downloaded here at https://www.digi.com/products/embedded-systems/digi-xbee/digi-xbee-tools/xctu.

To use XCTU an Xbee Adapter is needed such as the following at https://www.amazon.com/gp/product/B07V7GB5XZ

I'm going to check the settings using these to see if there are the same before I explore any Xbee replacements.

In the mean time if anyone has any updates on the issue, it would be greatly appreciated.

josh

Jan 30

Replying to

And just to finish up here, this is did appear to solve the issue. Changed that ID and flashed new firmware so now both dome and shutter are running unique Pan ID's and don't talk to each other while next to one another.

I should also note if anyone else is reading through this and wanting to compile own Arduino v4.0 codebase off github, you have to go back and use arduino AVR 1.8.2 version. If you use newer versions it's just a fraction to large to load up and lower versions seem to be missing some content. caveat that took me a few hours to figure out why or where.

josh

Feb 28

Replying to

So I thought I had this sorted out but I now have 2 nexdomes running next to each other and combating themselves over control... lol. These are both arduino v4.0 setups.

I had changed this and recompiled though and thought it worked on the bench, but my guess is it just took control of which it sees first. Any ideas as I changed the ID here.

rotator v4:

const char* initSequence __ATTR_PROGMEM__ = "RE,WR,AC,MYFFFE,ID6FC0,CH0B,A17,A27,RR6,RN2,CA30,PL4,SM0,CE1,AP2,WR,FR,";

Shutter v4:

const char * initSequence __ATTR_PROGMEM__ = "RE,WR,AC,MYFFFF,ID6FC0,CH0B,A17,A27,RR6,RN2,CA30,RO10,PL4,RO10,SM0,CE0,AP2,WR,FR,";

only change was ID6FC0 which I thought changed the network pan ID, but maybe that isn't enough?

josh

Mar 04

Replying to

Just to put a close on this and if anyone else does read this and want to have 2 shutters, 2 domes all next to each other using the arduino based board system... finally got it figured out and the code change below.

This process uses the 4.0 code on Github.
You have to compile the project with visual studio. I used 2022 here.
I did have to make sure I use arudino AVR 1.8.2. The newer stuff doesn't work.
I changed 4 files. (Both shutter/rotator XBeeConfgiureState.h and version.h

Shutter Code change: This is changing the Pan ID, Channel, and then also the setting A1 and A2 which means it won't listen to any Pan ID. (This is what stumped me). I had to shut this off and make it honor the Pan ID and Channel or else it keeps scanning and connecting.

//const char * initSequence __ATTR_PROGMEM__ = "RE,WR,AC,MYFFFF,ID6FBF,CH0B,A16,A26,RR6,RN2,CA30,RO10,PL4,RO10,SM0,CE0,AP2,WR,FR,"; //Dome 1

const char * initSequence __ATTR_PROGMEM__ = "RE,WR,AC,MYFFFF,ID6FC0,CH0E,A16,A26,RR6,RN2,CA30,RO10,PL4,RO10,SM0,CE0,AP2,WR,FR,"; //Dome 2

Rotator Code Change: Same thing, change Pan ID, Ch, and A1, A2.

//const char* initSequence __ATTR_PROGMEM__ = "RE,WR,AC,MYFFFE,ID6FBF,CH0B,A16,A26,RR6,RN2,CA30,PL4,SM0,CE1,AP2,WR,FR,"; //Dome 1

const char* initSequence __ATTR_PROGMEM__ = "RE,WR,AC,MYFFFE,ID6FC0,CH0E,A16,A26,RR6,RN2,CA30,PL4,SM0,CE1,AP2,WR,FR,"; //Dome 2

Essentially A1 has to be 6 (not 7) and A2 has to be 6 (not 7) so that it will not do a scan of the pan ID and channel and connect to anything.

Also, nothing is changed on the XCTU or XBee's themselves, it's all set here and a stock S1 Xbee will work here. I did update the version.h to so that I could easily do a @FRR and @FRS to read the unique version code I set on each of them. That is an easy way to tell which shutter is connecting and that it's not accidently connecting to the other.

anyway, hopefully that helps....

josh

Dec 17, 2024

and just to update for others, I did get word back from Babak that the dome shutters are different designs, so not able to upgrade to track system. So, that answers that.

josh

Dec 17, 2024

Oh, and does anyone know if the new track system would work with any nexdome? If I have the old shutter motor system with chain driven track, could I smooth out the system using this kit: https://www.observatory.store/NEXDOME-22m-Dome-Shutter-REPLACEMENT-Tracks_p_45.html

I wasn't sure if these will attach to any shutter or dome. Comes with the brackets and roller wheels for shutter?

I've emailed several times but been weeks with no response to sales@nexdome.com

Edited

Steven Green

Dec 13, 2024

•

We do monitor this forum. However, I can’t help with your question but I do know many of the nexdom replies end up in spam. Happens to me too and I have the email address in my contacts. Unfortunately there isn’t a phone number to reach them.

Have you posted on the facebook group?

Also, if you could lead me to the specs/instructions to change from a single sided shutter system I’d greatly appreciate that.

Thanks and good luck.

josh

Dec 14, 2024

Replying to

I would be happy to share some of that setup on facebook, but I believe I was added to a block list by former admins. You can certainly try to add me though, not sure why that ever happened...

The second motor system works really good on these. Perhaps you have person to reach out to for facebook group? I used to be a part of that group and share information like this.

Steven Green

Dec 14, 2024

•

Replying to

I have no idea how you got blocked. My fb footprint is tiny, only subscribe to 4 groups and don’t have any personal info on my account other than my name.

See if you can join again. I will reach out to the fb group.

Thanks

Steven

josh

Dec 17, 2024

Replying to

ya, reach out to the group if you can, I can't see the group anymore, been years since I was on there.

Rodolphe

Dec 13, 2024

•

Each XBee has a channel ID... but they are all set to the same ID when shipped from NexDome as this is set in the Arduino firmware..

I don't remember if there is a way to change the ID via some command. You might have to edit the code and reflash the arduino pair (rotator/shutter) with a firmware using a different ID.

Now if the 2nd one you want to purchase is the newer model of the controller using the Lunatico Beaver, this doesn't use a XBee so there will be no issue.

James Myres

Feb 04

Replying to

The readme.pdf answers a lot of questions.

The firmware does indeed change channels if it does not connect right away. However,in my case it might be hindered by a stronger signal. The xbees came with only the pcb antenna.

Also, I did not see the DL set for the address to match the MY setting of the opposite xbee. As the rotater to shutter (FFFF) or the shutter to the rotator (FFFE). This setting was not in the firware.

When I set the DL values it was able send and receive packets both ways in the XCTU software. I'm going to put the xbees back in the rotator and shutter and see if this did the trick.

I was also unable to get the A1 7 and A2 7 settings to not arbritarily change the pan ids and channels until I also set the RR, RN and RO values as well.

James Myres

Feb 06

Replying to

I purchased these 3 new xbees on ebay:

https://www.ebay.com/itm/186313526301

I programed them with the Rotator.xpro and Shutter.xpro files in the zipped firmware 4.0 with the XCTU software. This did the trick. The shutter syncs up with the rotator in less than a minute consistantly. You have to upgrade the xbee firmware to the 802.15.4 first and not the digimesh or zigbee versions of the firmware.

So ultimately it was not the rotator or shutter xbee configuration routine. It was the the Xbee3 pro chips that were included with the Nexdome rotator and shutter that were not compatible eith 3.0 or 4.0 versions of the firmware.

Edited

josh

Feb 06

Replying to

makes some sense... I think the xbee's I have are S1 and S2C like this as well, I have not tried anything newer... but they seem to work good.