576XE Posted September 29, 2014 Share Posted September 29, 2014 Recently I tried to investigate the ability to make SIO2PC connection remotely through TCP/IP and WiFi. Monthes of experiments and Monthes of disappointments. But I believe that it's POSSIBLE! IP connection works. COM not works at all. Is it possible that voltages are inverted and + is - but - is +. Quote Link to comment Share on other sites More sharing options...
pixelmischief Posted September 29, 2014 Share Posted September 29, 2014 (edited) Couldn't an adapter make one of these work? Serial Over Wi-Fi Edited September 29, 2014 by pixelmischief Quote Link to comment Share on other sites More sharing options...
576XE Posted September 30, 2014 Author Share Posted September 30, 2014 Hello, pixelmischief. I used HLK-RM04 but WITH it's Devboard. The reason is that HLK-RM04 is LvTTL ie 3,3 V I/O board itself. Devboard instead is real 5V TTL. Until now I get access to device through WiFi. And nothing more. Quote Link to comment Share on other sites More sharing options...
1050 Posted September 30, 2014 Share Posted September 30, 2014 I don't think it's a case of reversed voltages to answer that question. Sounds like a job for Max232 chip, search for "atari max232", lots of schematics show up under images link. Quote Link to comment Share on other sites More sharing options...
576XE Posted September 30, 2014 Author Share Posted September 30, 2014 Hi, 1050. Connection was HLK DevBoard - stright COM cable - SIO2PC(Serial) from Steven. I think SIO2PC(Serial) has Max232 onboard. I think there are something in my misunderstanding of processes in HLK and SIO. Please look at my real settings of module... http://atariage.com/forums/topic/227876-wifi-bridge-to-periphersl-emulators/ Quote Link to comment Share on other sites More sharing options...
1050 Posted September 30, 2014 Share Posted September 30, 2014 Mismatched IP numbers? I see your host (ezserv) at 192.168.1.255, the VSP at 192.168.1.155 and a suggestion (?) for using 192.168.1.244 for the VSP. Just how you got any of those numbers is well beyond me. Not the network guru by any means, I do know that they are supposed to match each others' expectations in order for each entity to talk with each other. Try setting the VSP to be 192.168.1.244 and try again? At home my host computer IP is 192.168.0.1 when configured manually to run the home LAN. Other computer is then 192.168.0.2, and is set accordingly - they find each other and talk very nicely at times and it's a real pleasure to hear my printer two rooms away go to printing from here. When I want to use my DSL modem, I disable the LAN and set the host computer to get it's IP from the modem automatically which winds up being 192.168.0.6. My understanding of subnet mask use is in conflict with your use. 255.255.255.0 allows you to ONLY change the last digit for your own use. So 192.168.0.255 is valid - 192.168.1.255 is not. Unless you want to change subnet mask to 255.255.254.0 - then you become valid again for 0 and 1 use only - I know, clear as mud, but that's my take on it so far. Still no joy try ezserv at 192.168.0.254 VSP at 192.168.0.255 with subnet mask of 255.255.255.0 Quote Link to comment Share on other sites More sharing options...
576XE Posted September 30, 2014 Author Share Posted September 30, 2014 Hi 1050 . I'm glad to see you again. Mask role is simple. It divide comps from networks. 0- means available. 1- means masked. Thus 255.255.255.0 is the mask for 256 natural computers excluding networks. Really the protocol needs broadcasting and gateway addresses. So only 254 are available. On the pictures I showed working environment. If all goes right then messages from COM goes to IP and vice versa. If testing program is slightly broaken then I have no chance to do all task. Steven said that modern devices like COM<->USB are very bad for SIO2PC. May be it's a case. Quote Link to comment Share on other sites More sharing options...
BillC Posted September 30, 2014 Share Posted September 30, 2014 You say you are aware that only 254 IP addresses are available with a 255.255.255.0 subnet mask, but still use 255(the broadcast address) for one of your devices! Quote Link to comment Share on other sites More sharing options...
576XE Posted October 1, 2014 Author Share Posted October 1, 2014 Hi, BillC. Here is working settings of testing environment http://atariage.com/forums/topic/227876-wifi-bridge-to-periphersl-emulators/ On 4-th picture we can see normal interconnection between COM part of testing program and it's Networking part. Please look at first picture. You can not find there 192.168.1.255 address. Quote Link to comment Share on other sites More sharing options...
BillC Posted October 1, 2014 Share Posted October 1, 2014 Hi, BillC. Here is working settings of testing environment http://atariage.com/forums/topic/227876-wifi-bridge-to-periphersl-emulators/ On 4-th picture we can see normal interconnection between COM part of testing program and it's Networking part. Please look at first picture. You can not find there 192.168.1.255 address. Sorry, it was post #6 by 1050 showing IP addresses using 255 as the final digit that got me mixed up. Quote Link to comment Share on other sites More sharing options...
576XE Posted October 1, 2014 Author Share Posted October 1, 2014 2 BillC Don't mention it . As I can understand, in AspeQt environment ATARI is requestor (CLIENT) and SIO2PC is listener (SERVER). While loading, ATARI sends request for availability of SIO2PC and if so then interoperability is begin. In the WiFi Client - Serial environment I even can't imagine the logic of settings. I know that WiFi Client is the thing that connects to WiFi network, obtaining IP address (In my case it's Static). I beleive that Serial settings concern only COM-Port settings (8,none,1). And the question arise What role will play VSP (TCP Server or Client mode). I absolutely lost. Quote Link to comment Share on other sites More sharing options...
kogden Posted October 1, 2014 Share Posted October 1, 2014 With WiFi->Serial you'd most likely want to use it with an RVerter or 850. The device basically acts like a modem. It treats inbound connections like an inbound modem call and you connect to hosts with something like "ATDT192.168.0.1:23" and "dial" the IP address. The WiFi->Serial box can handle telnet negotiation/control or you can just use raw socket connections and deal with application layer protocol in your software. Doing it this way, the "WiFi adapter" does the heavy TCP/IP lifting and you only worry about the application-layer protocol. Not so useful for peripheral emulation but a good way to add a network interface in a cheap and compatible manner. Would work in a similar fashion to the Lantronix or iPocket Serial->Ethernet adapters, just over 802.11 instead. For peripheral emulation, I've had the best luck with the simple cheap FT232RL USB->TTL Serial breakout boards. Basically a 1-chip SIO2PC. My experiments over bluetooth, WiFi, etc with peripheral emu all seemed to suffer from timeouts or weird handling of certain signals. If you have a UNIX desktop (Linux/BSD/OSX/etc) or reflashed embedded Linux router life is easier because of the full featured CLI environment and UNIX tty layer. You can install lots of CLI toys like Lynx for Web Browsing and PINE for e-mail so you can get around on the net easier when sitting at the Atari. And lrzsz so you can transfer files between PC/Mac and Atari using ZModem. Quote Link to comment Share on other sites More sharing options...
1050 Posted October 1, 2014 Share Posted October 1, 2014 Sorry everybody, I knew I made a mistake after posting with 192.168.1.155 instead of 192.168.1.151, but completely missed the 255 for 254 mistake that tripped up BillC, all my bad there. Still don't understand the 'remote server domain IP' at 192.168.1.244 shown in the first picture as in 'who be dat one, anybody I know?', but it's all over my head at this point anyway. It seems my youtube network education is worth exactly what I paid for it, my only hope now is to have you guys get it going and then see if any of it makes sense then... Quote Link to comment Share on other sites More sharing options...
576XE Posted October 2, 2014 Author Share Posted October 2, 2014 Hello kodegen, Hello 1050. There are some discrepancies in understanding of WEB interface parameters. (I guess they used Google Translator for interpreting ) Really this device is very universal. It has 2 UARTs onboard. (While only one COM port available through DevBoard.) Also it has 2 IP connectors (DevBoard has 2 RJ45 I/O one for ETH and one for DMZ) And it has WiFi I/O, which may be used as Client of Router FE or as AP itself. Default working mode assumed that ALL above mentioned components are in use and connected together. So the phrase Remote server domain IP means that when device is used as WiFi Access Point then behind it's assigned address may be some little subnet (The call it Domain) or little server-device (Like temperature reporter FE). In the case when device is used as WiFi or IP (RJ45 i mean) Client then Remote server domain IP parameters are not used at all. I think that there are weird timeouts or handshaking too. But these China boys said that the device FULLY NEED NOT ANY UARTs ADJUSTMENTS. (They never said it about DevBoard!!!) Really I think that APE or AspeQt or HW SIO-Transmitters MUST be more tolerant to their terminal devices. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.