EISY WiFi >> Click the button two (2) times > now what ?

[jim_]

As per the UD bible,  [Eisy:User Guide]

Go to WIFI Setup or Leave WIFI Setup mode
> Click the button two (2) times.

Now what ??? 
The HDMI is connected to a monitor ... nothing appears on the screen
On the Admin console, setting / Network ... there is just the normal DHCP mask

Information is non existent on how this works  

 

 

[Techman]

What exactly are you trying to accomplish?  Is your eisy currently on ethernet or WiFi

[jim_]

I disconnected LAN and pressed the button x2 as per the guide ... so now what happens, where do you do the configuration for the SSID / Key as there is no method to edit on the EISY (Network is greyed out)  ?   

Like most dual connected platform / OS, if LAN fails, WiFi can assume connection, so I wanted to test it 

Again, the [Eisy:User Guide] fails to guide the reader on how WiFi connection is established 

Edited December 15 by jim_

[Techman]

Do you have the UD Mobile app installed your phone, it has the WiFi configuration/setup for the EISY

Edited December 15 by Techman

[jim_]

I have the Mobile and found the eisy's WiFi via bluetooth

After adding the SSID and Password, the screen pop's up an error " Could not get BLE Connection "

repeated the proceedure several times with same result

[Geddy]

19 hours ago, jim_ said:

Again, the [Eisy:User Guide] fails to guide the reader on how WiFi connection is established 

The portion of the wiki you quoted is related to the multi-function button. You press it twice and enter or exit wifi setup. 

To use the UD Mobile app to connect to the eisy and to setup wifi you should refer to the UD Mobile documentation:

https://wiki.universal-devices.com/UD_Mobile

If the device was already setup and on your LAN then why did you want to change it? 

 

On 12/14/2024 at 3:32 PM, jim_ said:

Information is non existent on how this works

You need to read the installation information:

https://wiki.universal-devices.com/Eisy:User_Guide#Installation

 

[jim_]

2 hours ago, Geddy said:

The portion of the wiki you quoted is related to the multi-function button. You press it twice and enter or exit wifi setup. 

Agreed, however the document which is the isy:User_Guide#Installation fails to direct the reader to the UD_Mobile 

2 hours ago, Geddy said:

If the device was already setup and on your LAN then why did you want to change it? 

I'm bench testing to be come familiar with the new platform before permanent install replacing my 994. During my testing, I found that if the LAN is disconnected for a period of time, this causes a NTP issue in the eisy network stack. I have the eisy connected to a monitor and you will see a constant ntpd error, unable to resolve pool.ntp.org. (AKA can't sink with external NTP clock), I've found some other issues as well, but will investigate later

So, why install WiFi ?  Do you have a laptop that supports both LAN & WiFi, if LAN fails, WiFi restores the connection and your still connected to whatever is required

I have read the UD_Mobile and now even more confused ..

I am NOT an existing portal user, therefore I jump to section Local Connections and Local VPN

The very next line states Before starting verify you are connected to the same WiFi network as your UD Hardware.

The next line > Go to Settings Tab > Systems > your-system-name, etc etc 

When opening settings, (hamburger wheel) nowhere do you find the word "Systems", I could scroll down to App Settings and add a NEW Controller ?

There is also the Admin section, WiFi Configuration , Configure eisy's WiFi Adapter ... which always fails with the same error " Could not get BLE Connection "

There is no straight forward document explaining how to enable WiFi on this eisy !!!

 

 

 

 

 

Edited Monday at 08:23 PM by jim_

[Geddy]

1 hour ago, jim_ said:

the document which is the isy:User_Guide#Installation fails to direct the reader to the UD_Mobile 

Quote

Installation

Installation is quite easy

• You can use UD Mobile which walks you through the setup. If not:
• Connect a Cat5e cable to eisy's Network Port and the other to your network. Note: the network must initially be DHCP auto enabled
• Connect the power supply

(bold added for emphasis)

1 hour ago, jim_ said:

There is no straight forward document explaining how to enable WiFi on this eisy !!!

I get what you're saying. UD has always said that documentation is probably their weakness. I think as Michel has claimed "they're developers, not document writers". While it might be a pain to sort stuff out on the fly it is sometimes easier for trial and error than trying to read/guess what the documentation is saying. Seems that you are taking testing to an extreme of getting things figured out before going live. Some of the more detailed questions/issues you might have might be something that only you have faced (at least recently). Many that made the switch when the eisy came out had a difficult  time with the process as it was super green and new to everybody at the time. 

But the basic answer to this "question" is (if I recall) that if there's no network cable connected when the eisy boots up then wifi is enabled by default. If a network cable is connected then the wifi is disabled. I never setup the wifi on my eisy since it sits next to my router. For me there's no need to have the wifi as a "fall back". If my LAN goes down then probably my whole WAN connection is toast. I don't see a need to have it as an option (for my situation). 

1 hour ago, jim_ said:

I have read the UD_Mobile and now even more confused ..

I'm with you on this. UD Mobile has been undergoing some UI changes and I expect that the documentation hasn't kept up with the changes. It's probably still referring to items that were there when UD Mobile and eisy were released (two years ago). 

For your issues it might be something that is better handled through the UD Support ticket path if they're stacking up and you're just looking for issues in the system. 

https://www.universal-devices.com/my-tickets

Otherwise, for a user-to-user forum for support we're here to help, but understand that just making comments about the documentation without asking an actual question or describing what you're attempting to do probably won't garner much help/support because nobody knows what it is you're looking for help on. That's probably why your initial post didn't get a reply for a couple of days. 

[Guy Lavoie]

1 hour ago, Geddy said:

...UD has always said that documentation is probably their weakness. I think as Michel has claimed "they're developers, not document writers"...

I agree, and furthermore, the people developing the software shouldn't be the document writers! The usual problem is that they're too familiar with how it works, so they'll overlook stuff and can't always anticipate some of the questions that some of the users will ask themselves. I say that from experience. The Applied Digital Ocelot controller was a great little controller, but with gaping holes in it's documentation. The way the logic operates, order of precedence, etc wasn't properly explained. When they brought out the next major revision of C-Max (the equivalent of the admin console), they actually hired me, a user living in another country who had never set foot in their offices, to rewrite the manual for it. 150 pages later, it really made a difference, and they were very happy with it. It didn't happen by magic. I sent countless emails back and forth with the software developer, and we really figured out how everything worked, down to the size of the internal command output buffers, etc. and put words to it. That's the kind of thing that would need to happen with the eisy.

[jim_]

Thanks for both comments

With my many decades of engineering and operations, my world was all about DOCs and following standard equipment deployments. Having designed IP networks, we look at all the connected devices we live with daily. Hardware manufactures now include both wired and WiFi to offer more flexibility and redundancy. That's my rant

Geddy,  your right, I need to bring this back to user helps user,  I got caught in the frustration of poor docs.

After studying the guide tonight  https://wiki.universal-devices.com/UD_Mobile#eisy_WiFi_Configuration for hours, I gave up and picked up my mobile.

Starting with a freshly reset eisy, powered up with no LAN and logged in to watch the messages on the console

On my mobile, I just opened the 3 dots top right, selected WiFi config for eisy, followed the prompts  (not adding new node)

It took a while, and after a few refreshes, the system messages started rolling on the console, it rebooted and I could ping the internet from the eisy 

The method UD is using is magical, looks like virtual NAT as ifconfig does NOT match the new local IP or the MAC found in DHCP server ... but its working 

Now, here's the test ... reconnect the LAN cable, does it reconverge, NOPE,   but you will see the eisy teardown the 2 interfaces associated with WiFi "wifibox0" and "tap0"

If you reboot (sudo reboot), with the LAN connected, it works ... if you reboot with the LAN disconnected, WiFi works, BUT be aware, each time it restarts, it acquires a new / different IP from the previous in WiFi mode (this is wrong)

My Linux is ok, I know enterprise linux distro and all the commands, but the openBSD is different, I'll get my son to poke at this beast 

I ran a hardware query on the unit, there is an Intel WiFi 6 AX201 present, but unassigned  ...  but I'll poke at it on a rainy day 

Now, I can only master migration 

[Geddy]

8 hours ago, jim_ said:

Now, I can only master migration 

That "should" be the easy part. It's been made simple over the past couple of years. As long as you have a "simple" system it should be easy to just make a backup of the ISY994 and restore on the eisy. If you've got a more complicated system the pitfalls are still there.

I always suggest users make a copy of the program root folder and save it as a text file. If you right click on the Programs root folder the option near the end of the list should be "COPY folder to Clipboard" (Be sure you use the "COPY" option...NOT the export (you'll think too much computer speak and go for the "export" option, but you really want "COPY"). Then, open a simple text editor (no word processing...in Windows just use Notepad). PASTE the clipboard to the text editor and SAVE that file. This records all your program information in a "simple" to read file in case your programs go crazy in the migration (it's been known to happen on some systems). The text file will have the names of nodes in programs as well as indicate if the program was disabled.

Glad it seems the rest of the stuff worked out for you. The rest is over my head of worrying about. Good luck with the migration! 

[jim_]

Thanks Geddy, I agree, I've been keeping txt files for decades of configs. Cant count the number of times people came to me begging for a copy to restore switches or appliances ... but I did earn lots of beers

Migration complete, UD support provided a slightly modified set of steps as I was migrating from 994 with serial PLM direct to eisy with USB PLM.  The doc was about  8 single lines of steps, far easier to follow than the public guide