First, a big thank you for this great device! My two WiModem232 Pro units arrived a few days ago and I have been having a fun and largely successful time trying them out. Getting them connected to my Wi-Fi and updated to the latest firmware was straightforward. Initially I thought that having to use an external power supply might be an annoyance, but it is quite useful to be able to turn the WiModems and the computers on and off independently (e.g. for leaving a nullmodem connection active while the computers are powered off).
One of my main use cases is to provide wireless TCP/IP access for an Amiga, using a pair of WiModems in nullmodem mode (one on the Amiga and one on a Linux machine in another room). Using MiamiDX on the Amiga and Linux pppd on the server I was able to get a PPP connection working, with file transfers at 5-10 kbyte/s depending on the protocol, and seemingly flawless reliability. 115200 baud seems to be as fast as my A1200s will reliably go (in general, not just with the WiModem); one has a 30 MHz 68030 and the other a 50 MHz 68060, both with Fast RAM.
The other main use is to more conventionally "dial" a telnet connection using the WiModem. I had some problems in this mode with output from the remote machine (such as long file listings) sometimes being truncated. I wondered about changing some buffer or timing settings on the WiModem (note that I have set telnet mode on for this).
For anyone else using an Amiga, I should mention that I had problems with Amiga Term hanging at times (menus not responding), requiring powering off the WiModem to get it to wake up, but I think that's been resolved by switching from the stock serial.device to the 8n1.device replacement. With an Amiga-to-Amiga virtual nullmodem over the WiModems, I got ZModem file transfers of 9,000-10,000 chars/s, no errors.
I did have problems initially running the AT*UTC+12 command (it would just return ERROR, even though AT*TIME worked OK), but later on it started working, so I'm not sure what the problem was there. Initially I was concerned that I wouldn't be able to set my local time zone (UTC+13 during daylight time) but I found that the range of UTC offsets wasn't as limited as the product manual made out!
Speaking of the manual (and this might be beyond your control), but Google Search makes it very hard to find the Pro version of the PDF, which stymied my nullmodem setup efforts until I discovered the separate manual for the Pro (and that the Pro uses AT*CABLE instead of AT*NULLMODEM).
The other thing I wondered about is whether the WiModem should honour the default search domain as handed out by DHCP - it doesn't seem to on my home network and I have to enter the full domain name instead of just the hostname.
Thanks!
One of my main use cases is to provide wireless TCP/IP access for an Amiga, using a pair of WiModems in nullmodem mode (one on the Amiga and one on a Linux machine in another room). Using MiamiDX on the Amiga and Linux pppd on the server I was able to get a PPP connection working, with file transfers at 5-10 kbyte/s depending on the protocol, and seemingly flawless reliability. 115200 baud seems to be as fast as my A1200s will reliably go (in general, not just with the WiModem); one has a 30 MHz 68030 and the other a 50 MHz 68060, both with Fast RAM.
The other main use is to more conventionally "dial" a telnet connection using the WiModem. I had some problems in this mode with output from the remote machine (such as long file listings) sometimes being truncated. I wondered about changing some buffer or timing settings on the WiModem (note that I have set telnet mode on for this).
For anyone else using an Amiga, I should mention that I had problems with Amiga Term hanging at times (menus not responding), requiring powering off the WiModem to get it to wake up, but I think that's been resolved by switching from the stock serial.device to the 8n1.device replacement. With an Amiga-to-Amiga virtual nullmodem over the WiModems, I got ZModem file transfers of 9,000-10,000 chars/s, no errors.
I did have problems initially running the AT*UTC+12 command (it would just return ERROR, even though AT*TIME worked OK), but later on it started working, so I'm not sure what the problem was there. Initially I was concerned that I wouldn't be able to set my local time zone (UTC+13 during daylight time) but I found that the range of UTC offsets wasn't as limited as the product manual made out!
Speaking of the manual (and this might be beyond your control), but Google Search makes it very hard to find the Pro version of the PDF, which stymied my nullmodem setup efforts until I discovered the separate manual for the Pro (and that the Pro uses AT*CABLE instead of AT*NULLMODEM).
The other thing I wondered about is whether the WiModem should honour the default search domain as handed out by DHCP - it doesn't seem to on my home network and I have to enter the full domain name instead of just the hostname.
Thanks!
I will try that at home tonight, thank you.