Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

MA00's Achievements


Newbie (1/4)



  1. Hi Andrew, I have tried Firefox this morning and can confirm this does work, and does not present the problem encountered with Chrome, IE and Edge. Many thanks for your help.
  2. Hi Andrew, I have just tried the latest build WFL as suggested - this worked first time on my home PC - will try with the other board on works PC's tomorrow. For my understanding, (& to allow me to explain the issue to my boss) Is this summary correct - A change in the browser has prevented access to the live version of the software, as such I have resorted to an outdated version of the hosted WFL which does not function as intended with the open logger. Updating the hosted version (or changing browser) has/will correct the issue. Many thanks for taking the time to get to the bottom of this issue and the explanation. Much appreciated. Martin
  3. Hi, Both of my boards have now been tested on five W10 computers, on one I get a 404 error. On all the others I now get same behaviour. Board is not recognised by waveformslive, but is detected if localhost is used. However, I cannot progress past the first screen: Instrument panel briefly displays connecting to device before returning to same screen. Configure does not respond in any way Documentation reports device model unknown Remove seems to function as normal On the initial connection I am able to reinstall firmware. (1.3.0) as have been using all along. Nothing is shown for Wifi status, and if I select Wifi, no connections are detected. If I manually my own network details it reports an error. Have tried (re)re-installing agent and running as admin. Tried software on XP and Vista machine but these do not run Agent - trying to get win 7/8 machine to try. Computer I am currently using reports FTDI driver - which I believe is correct? I am not sure what I need to do enable WFL logging - is there an up to date guide I can follow. One of the boards was set for standalone boot operation, and still performs this function correctly. I have operated and downloaded valid data today. The other board was put away as a (tested/working) spare several weeks ago. I am very puzzled why I have two boards, used in different scenarios, which appear electrically OK, are recognised by USB, can accept firmware update - but neither of which can now work with agent/waveforms live to allow me to get to a point to update the configuration. (sample rate & duration). I have seen a reference to using Putty to talk to a board - is this something I could try? The documentation suggests only W10 environment to run the software, but lists Mac/Linux version of Agent. Is there another platform I could test on? Any further suggestions very gratefully received. Thanks, Martin
  4. quick update on this. Have found using http://localhost:42135 direct into browser works now, but took a couple of attempts to see the board. Same setup through webpage still does not work, at home and work (different security settings). Have tried fully disabling AV and firewall with no success. Still be interested to know if anyone else has encountered same. Thanks Martin
  5. Hi, Is anyone else having new problems communicating with an Openlogger device using Digilent Agent. I can't get past the Error connecting to Digilent agent message. I have two boards, both of which used to work on three W10 computers. Neither of these boards work on any of those PC's now. However, both still work on an old (not recently updated) W10 laptop. (Same cable used on all tests). Edge, and Chrome browsers both tested. Device manager reports same USB driver on working and non-working machines. Same version of Agent 1.2.3 on all machines and have tried uninstall-reinstall. Beginning to suspect a Windows update is interfering with the operation of Agent software - anyone else experienced the same or can shed any light? Many thanks for any thoughts. Martin
  • Create New...