Looks like I am the first customer to post regarding the latest modem release. I finally had some time to sit down with it today and test it out.
When I first powered it up, there was nothing shown on the display but I did see the brightness level go up. I was concerned at first because I recall that my other two WiModems displayed something by default. I quickly remembered about the brightness setting and that a value of 0 would likely mean it was off. Sure enough, at*help showed no value here. I set it 2 and the display came to life. Phew!
Next up was connecting it to my router. No trouble here. Just as easy as it was for my other WiModems.
I then set my preferred baud rate of 38.4kbps. Done.
When I went to try my first BBS connection attempt, it spit the word "ERROR" back at me. Ehh? Mind you, I am entering the same command string I have done successfully many times before...i.e. "atdt particlesbbs.dyndns.org:6400" Just for giggles, I even tried the example "atdt google.com:80" ALL CAPS was tried too. Same ERROR response given.
Two different Amiga terminal programs were tried. Both with ANSI terminal emulation. The modem is currently connected to a GVP I/O extender (incorporated into a GVP GeForce '040 board).
My older "WiModem232" (non-Pro) connected to the same hardware and using the same software accepts dial commands just fine as expected
Suggestions? Factory reset perhaps? Although I do not know how it could have got borked so soon when every step in the setup was uneventful. It simply refuses to accept a dial command string. I also added a phonebook entry. Dialing from the phonebook also returns "ERROR".
When I first powered it up, there was nothing shown on the display but I did see the brightness level go up. I was concerned at first because I recall that my other two WiModems displayed something by default. I quickly remembered about the brightness setting and that a value of 0 would likely mean it was off. Sure enough, at*help showed no value here. I set it 2 and the display came to life. Phew!
Next up was connecting it to my router. No trouble here. Just as easy as it was for my other WiModems.
I then set my preferred baud rate of 38.4kbps. Done.
When I went to try my first BBS connection attempt, it spit the word "ERROR" back at me. Ehh? Mind you, I am entering the same command string I have done successfully many times before...i.e. "atdt particlesbbs.dyndns.org:6400" Just for giggles, I even tried the example "atdt google.com:80" ALL CAPS was tried too. Same ERROR response given.
Two different Amiga terminal programs were tried. Both with ANSI terminal emulation. The modem is currently connected to a GVP I/O extender (incorporated into a GVP GeForce '040 board).
My older "WiModem232" (non-Pro) connected to the same hardware and using the same software accepts dial commands just fine as expected
Suggestions? Factory reset perhaps? Although I do not know how it could have got borked so soon when every step in the setup was uneventful. It simply refuses to accept a dial command string. I also added a phonebook entry. Dialing from the phonebook also returns "ERROR".
So, now if there is a router selected it still shows the message until ALL of the setup steps are completed. This is just an internal change for me so this doesn't happen in the future.