• Content Count

  • Joined

  • Last visited

Everything posted by Jos

  1. Hi Kristoff, I saw you released 1.296.0 to github, so I used this one in OpenScope assuming it is the latest - still, the effect is the same as mentioned above. Have you been able to find out the root cause from the posted debug actions or do you need more information? cheers, Jos
  2. I finally found time to debug as per your instructions, Kristoff: --- snip --- OpenScope v1.4.0 Written by: Keith Vogel, Digilent Inc. Copyright 2016 Digilent Inc. File Systems Initialized MRF24 Info -- DeviceType: 0x2 Rom Version: 0x31 Patch Version: 0xC USB+: 5010294uV VCC 3.3: 3300360uV VRef 3.0: 3001465uV VRef 1.5: 1500732uV USB-: -4979611uV Using calibration from: flash Found parameter for AP: XXXXXXXXX@XXXX Error Connecting to WiFi, Error: 0x90403E00 --- snap --- I masked my wifi ESSID for security reasons, but it is plain lower case letters. You may notice firmware version 1.4.0; after letting the device update to the latest version it claimed to be 1.296.0, I noticed that the offered firmware versions listed are sorted by plain numbers, so 296 is higher and therefore chosen by WFL as the latest; on the other hand the website offers 1.4.0 as the latest. I now chose 1.4.0 and at least it already connected two times with the WIFI automatically, but in 99 out of 100 times it gives the above error. Looking forward to your comments! regards, Jos
  3. Hi Kristoff, sorry for the delay. Wasn't able to do further testing as per your suggestion but will do so on the weekend, hopefully. But for completeness I can try to answer your question from the other thread out of my head: Can you provide some details about the network: Does it broadcast the SSID (ie is the network visible when you scan?) - yes What is the SSID (are there any special characters like spaces, etc)? - 14 characters containing one "@" What encryption type does the network use? - WPA2 CCMP/TKIP, PSK How are you powering the OpenScope? - both power bank and 2A power supply Is there anything unique about your setup? Lots of wifi noise, unique network setup, etc? - 2 ESSIDs managed by one FritzBox and 2 LAN connected repeaters
  4. update: I tried hot spot mode of my tablet and OpenScope connected successfully to it. I changed SSID of my Fritz!Box to something without an "@", to no avail. I changed encryption of the Fritz!Box from "WPA+WPA2" to "WPA2 (CCMP)" - it connected! At least it got an IP address and red and orange LEDs blinked. But WFL on a tablet or from browser wasn't able to connect to this IP address. I then tried the 3rd encryption option "WPA (TKIP)", again to no avail, no IP address, no connection. So, my conclusion is that either firmware or even the Wifi chip itself are not capable of connecting to a Fritz!Box, at least mine (model 7390). I just wonder why it did connect at the very first try, but then refuses to connect to the very same network afterwards. Is there any way to extend compatibility on the firmware level?
  5. Yes, scanning works, I can see all networks. Latest firmware available (as of Saturday) installed. Update: it is version 1.37 which is the latest according to WFL. See attached screenshots for firmware and Wifi.
  6. Hi Kristoff, thanks a lot for your reply; I did try to set up Wifi using WaveForms Live again and again, using different access points of my network, even a different (guest) network my Fritz!Box provides - the OpenScope didn't connect to any Wifi anymore. I also checked all advanced parameters, all were set up correctly. cheers, Jos
  7. Hi, after setting up my OpenScope initially, it connected successfully to my home wireless lan and I could access it from the tablet or browser as expected. Then, I disconnected the scope from power and tried to run in on a power bank. The blue light wouldn' stop blinking, so no connection to Wifi anymore. I re-attached to the computer assuming the power bank had not enough power, but also there the scope wouldn't re-connect to Wifi. I checked my Fritz!Box if the channel had changed to something above channel 11, but it is a safe channel 1. Any idea what may have happened here? Thanks, Jos