AP and STA Mode BUG Fixed Statement - ASIAIR [v1.8.3 - 9.12]: Page 5

AP and STA Mode BUG Fixed Statement - ASIAIR [v1.8.3 - 9.12]

PMTeam@ZWO

pderby Hi, it seems that mac address is abnormal. Please try to reset the WIFI of ASIAIR device. You can find the RESET button on ASIAIR. Power on, press and hold it to reset WiFi. After reset, the WiFi name and password will become the initial one (name: ASIAIR_xxxxxxxx; password: 12345678). I hope this will help you.

LyonsRasa

@asiair@zwo#54090 yes i will submit the log next time. Thanks for your response.

RGCasper

I am still dead in the water and awaiting someone to help me address this issue. I've spent about $100 so far for an Ethernet cable and 2 micro SD chips. TJ Connelly is the only one who has contacted me. I've tried my best to follow the forum fix and what TJ suggested. How many months is it going to be before I have a functional unit again???!!!!???

pderby

@asiair@zwo#54100 Following ZWO advice I reset the WiFi on my ASIAIR Plus. I can connect my iPhone to the ASIAir WiFI and ping the ASIAir with no packet loss. However, the ASIAir App 1.8.3 (9.12) does not find the ASIAir. I cannot connect to 10.0.0.1 manually, either. But using network utility programs on the iPhone I can ping the ASI Air at 1.0.0.1. Something is not working between the IP stack and the ASIAIR code. Any other ideas to try? Connecting the ASI AIR to my LAN using an ethernet cable and connecting the ASIAIR IOS APP to my LAN works fine. The APP automatically finds the ASIAIR and the connection work perfectly. I submitted a log and some screen shots via the IOS App earlier today.

pderby

I solved my problem. On the iPhone 13 (and maybe other models) with T-Mobile (and maybe other carriers) you an multi home WiFi and Cellular service if the WiFi doesn't have internet connectivity. When I connected directly to the ASIAIR PRO or PLUS the iPhone networked to the LAN on the ASIAIR and networked to T-Mobile for internet. I use this feature all the time with an eVscope during outreach events. I can capture images and text or forward them to public attendees mobile phones during events. The ASIAIR APP seems to default to the internet cellular connection rather than the LAN WiFi connection when both are present, so the ASIAIR isn't found even though you can ping and scan the device with other applications with cellular internet active. Would be nice if ZWO fixes the code in the ASI APP to look for the ASIAIR on the WiFi connection and ignore the cellular network connection.

pderby

My initial experience with 2 new ASIAirs: a Pro and a Plus running 1.8.3(9.12), neither of which will work with station mode WiFi connections to my iPhone 13. The iPhone 13 (and maybe other models) with T-Mobile (and maybe other carriers) the phone automatically provides multi home WiFi and Cellular service when the WiFi connection doesn't provide internet connectivity. When I connect directly to the ASIAIR PRO or PLUS WiFi (station mode) the iPhone correctly connects to the ASIAIR WiFi and also connects to T-Mobile for internet. Then I launch the ASIAIR APP which searches and fails to connect to the ASIAIR Pro or Plus.

A manual connection attempt to the ASIAIR's 10.0.0.1 IP address also fails even though I can connect and ping and scan the 10.0.0.x network with other iPhone applications. I am able to see that the ASIAIR assigned 10.0.0.28 to my iPhone WiFi connection. The attached 3 iPhone screenshots show the results of a scan for network services broadcast by the ASIAIR PLUS or PRO.

Changing the phone's SETTINGS / CELLULAR / and turning off CELLULAR DATA solves the problem. Then the ASIAIR APP immediately connects to the ASIAIR PLUS or PRO. The ASIAIR PLUS or PRO 10.0.0.1 network broadcast info stays the same whether the CELLULAR DATA setting in the phone is OFF or ON.

If you turn CELLULAR DATA back to ON after the connection is made, the ASIAIR immediately loses the connection to the ASI AIR APP but the WiFi connection to the Raspberry PI side of the ASIAIR still work just fine.

Turn the CELLULAR DATA back to OFF and the ASIAIR restores the connection to th ASIAIR code on the raspberry Pi.

ZWO needs to fix the code in the ASI APP to correctly look for the ASIAIR on the 10.0.0.1 connection and ignore the cellular network connection so that cellular service could remain active while ASI APP is actively communicating via WiFi.

Kgunessee

I thought I'd chip in with some recent connection issues I've been having too.

I'm using and ASI Air Plus, 533MC Pro, EAF, running 1.8.3 on Android and up until recently it's been working fine in STA mode. I had to disconnect it from my rig to plug into my PC, but when I reconnected it just would not connect to my phone.

I tried resetting the WiFi multiple times to AF mode to no avail - it either would not be recognised, or fail to connect. It finally connected by chance after 20 mins of trying.

Last night I had a similar issue and wasted about 2 hours trying to sort the same issue.

I've narrowed down the issue to the power port. When the adapter is wiggled in the 12v power input, it either connects or reconnects depending 9n its current state. Even rotating the whole unit (it's mounted by a single screw underneath), this also can connect or disconnect it.

All of my devices stay powered however with no loss of actual power.

I've no clue if this could be a hardware fault or software, based on the above issues. It's been fine up until now, and when it's connected works fine, it's just when it disconnects it's a real pain to fix.

Any advice would be appreciated here!

pderby

Kgunessee You might possibly have the wrong power adapter. There are two configurations of 5.5mm power plugs, one with a 2.1mm inner plug and the other with a 2.5 mm plug. Normally, the 2.5mm central pin variety is used for higher current needs. You should not mix them, as a 2.5mm central pin male plug, for example, will most likely not make electrical contact - or make very poor electrical contact - with a 2.1mm female plug.

Walf@ZWO

Kgunessee Check if the usb 3.0 cable is close to the antenna

ParamountObservatory

So with recent updated v1.9-9.53, I can advise the same issue of the air plus, with cameras connected to usb 3 ports, the device WiFi fails and device just keeps rebooting.

I am using the 533mc pro and 120mm mini, both core ZWO products, so very disappointed that this is still a problem 3 months on.

It's hard enough getting clear skies, so having to battle with faulty equipment just makes getting opportunities to image very limited, come on guys you can do better than this?

Tech@ZWO

ParamountObservatory
Could you tell us your connection details? such as what devices do you connect to the ASIAIR Plus and Pro, how did you power the ASIAIR, camera and mount, please also tell us the specification of your power supply.
Thanks.

ParamountObservatory

I can also confirm update v1.9-9.53 has introduced the rebooting issue to my ASI AIR PRO. Now when I start the device it just keeps rebooting if the cameras are attached.

To confirm I am using USB3 ports with 533mc pro & 120mm mini, so core ZWO products. So now have no device working !

As I have recently purchased the air plus, I am going to return and get my money back.

Please fix this issue ASAP.

astrosatch

ParamountObservatory
Sorry to hear that you have problem with this issue. Mine has been finaly resolved with latest beta. Its puzzling how one user system starts working ok and another grows the same issue that former had. I'll definately backup this version for future insurance.

ParamountObservatory

astrosatch
Yes, it could be a good option to backup existing profile before applying to new one, @ZWO please note

ParamountObservatory

@tech@zwo#55265
My connections are:

Power input

Input : 100-240V, 0.8A, 50-60Hz
Output : DC 12V 2.5A
2.1mm centre-tipped 5.5mm outer plug

Power output

Port 1 - Cooler for ASI 533MC PRO
Port 3 - ZWO DC to RCA Y Splitter Cable 2 X Dew bands
Port 4 - ZWO DC to RCA Y Splitter Cable 2 X Dew bands
USB3 - 1 533 MC PRO
USB3 - 2 120MM MINI
USB2 - 1 Lynx Astro FTDI EQDIR USB Adapter for Sky-Watcher EQ6
USB2 - USB storage device
Wired Ethernet connection
EAF Focuser - to 533 MC pro USB1
ZWO 5x Electronic Filter Wheel (EFW) -to 533mc pro USB2

My setup is a permanently fixed observatory

w7ay

ParamountObservatory
Port 3 - ZWO DC to RCA Y Splitter Cable 2 X Dew bands
Port 4 - ZWO DC to RCA Y Splitter Cable 2 X Dew bands

I would recommend (1) powering the cooler separately, and not through the ASIAIR power port. Make sure it is powered a second or two before booting the ASIAIR.

(2) likewise, moving the dew heaters off of the ASIAIR power outlets. If moving the dew heater outlets works, and you still want remote control of the dew heaters, what you can do is use a relay between the 12V source and the dew heaters, and energize the relay with one of the ASIAIR power ports.

Then (3) [although this is not your immediate problem, it may eventually become a problem, and will cause you to make frequent walks out to your dome], find a USB 3 powered hub (which does not back-power the Raspberry Pi). Use a single shielded USB cable from the ASIAIR to the hub. Do not connect anything else to the ASIAIR. Then let the hub connect to your other USB devices. You do not have to worry about USB 2 vs USB 3 since a UBS 3 hub will allow them to coexist (unlike the USB 2 days, where the Hub need to be an MMT to allow coexistence of USB 2 and USB 1).

Most hubs will come with a shielded cable that you can use to connect to the ASIAIR. Make sure it is shielded. USB and WiFi co-interferes, and any USB cable that is close to the WiFI antenna (or internal WiFi circuitry when they are not properly shielded) can cause the USB connection to fail.

Do not, ever, ever, use the flat USB cables that comes from ZWO. They are not shielded and should not be allowed anywhere near where there is a strong WiFi signal. I throw mine away each time I open a ZWO box, just to be sure I don't get tempted to use them.

The hub that I found to not back power is this Anker one (also listed in one of the web sites that discuss Raspberry Pi back powering):

https://www.amazon.com/gp/product/B005NGQWL2

It is important that the powered hub does not back power the Raspberry Pi (you can find lots of articles about it on the web). The cheaper powered hubs simply tie the input and output +5V USB pins together. They either don't allow the Raspberry Pi to boot, or becomes flakey with temperature drops (when the 5V in the hub exceeds the 5V bus in the Raspberry Pi).

You can use a back power preventor (simply severs the 5V line) with cheaper powered hubs. But I have not found any USB 3 back power preventor (there are a number of USB 2 ones at Amazon); I had constructed my own with a trivial board layout with AutoDesk Eagle. I use one with my INDIGO Sky/ Raspberry Pi 4 set up.

Chen

ParamountObservatory

@tech@zwo#55265 any advise or suggestions, I currently have 2 devices I cannot use!

ParamountObservatory

Hey,
Thanks for your feedback, but I am somewhat confused about your USB reference, as the USB is essentially for the cameras, nothing to do with powering. The pro and plus, are powered by 12v power supply from mains, what are you referring to with respect to USB hub.

I can remove the dew bands from the device as I have a dew controller, but it was aimed at improving the cable management.

w7ay

ParamountObservatory I am somewhat confused about your USB reference

Notice that I mentioned "[although this is not your immediate problem, it may eventually become a problem, and will cause you to make frequent walks out to your dome]" i.e., for now, it will probably be sufficient to supply 12V to the camera directly, to fix your boot problem.

If you still have USB connection problems, route all the USB devices through the hub, instead of connecting them to the ASIAIR. Cleaning up the USB cables, and keeping them away from the ASIAIR, will help with RFI.

For now, just make sure that the 12V power is supplied to the Camera before you boot ASIAIR. Otherwise the Camera may pull too much current from the ASIAIR's USB port, especially with something like an ASI2600 or ASI6200.

If you add a powered USB hub, be sure to supply power directly to it too, and not through the ASIAIR's power outlet.

You will find that the fewer things you connect directly to the ASIAIR, the more reliable it will be. In my case, even the antenna of my third generation ASIAIR has been removed, and terminated with 50 ohms, and I use an Ethernet cable to connect the ASIAIR to a router. This further reduces any chance of interference between USB and WiFi.

Check your power supply voltage, too. I had posted a warning on this forum a few months ago that the power supply specs that ZWO published is bogus. I check two different third generation ASIAIRs, and found that both of them will not boot if the power is over 13.75 volts. ZWO's specs say they will work up to 15 volts. So, make sure that your power supply is below 13.5 volts or so (i.e., if you are using a lead acid cell, make sure it is not fully charged, and if you are using a mains supply make sure it is also below 13.5 volts; many industrial grade supplies standardize on 13.8 volts; the voltage of a fully charged 12 volt lead acid battery).

Chen

« Previous Page Next Page »