 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : Networking Hell...
  Page 2 of 3   |
|||||
| Author | Message | ||||
| WhiteWizzard Guru  Joined: 05/04/2013 Location: United KingdomPosts: 2944 |
In the previous thread that Grogster refers to in his first post here, cpx2001 post included the following: [quote] Does anyone have played with this module, want to have comment about. you only have udp, tcp, new one is cloud ready, buyed one, speedy test seem to work great. [/quote] I have also come across reference to cloud ready modules when googling this thread, so hence my question! So from reply so far, is it effectively referenced by a 'static' IP? WW __________________ "Using CGmm Color Maximite ,Duinomite-Mega,Duinomite-mini,CGmmStick" |
||||
| JohnS Guru Joined: 18/11/2011 Location: United KingdomPosts: 4044 |
Thanks. I wonder what they do mean! John |
||||
Grogster Admin Group  Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
Hi folks. After lots of playing around, I still cannot work out why we are gettting half a reply from the uM, and why the uM keeps acknowledging with the prompt, but not actually following through with the command - very odd. 
I still plan to try the Xport Pro module too(will order one today), so will put all results in this thread as I experiment. The Xport unit is very intelligent - pretty much a computer in and of itself - so perhaps I will have better luck here. Smoke makes things work. When the smoke gets out, it stops! |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
OK, another update for you all. When I put a pager transmitter on this 107, as the 107 is an RS232 unit, and so is the pager transmitter, I can directly connect them, and I can talk to it fine. NO ERRORS AT ALL. 
So, the uM is not liking the module, or could it be that the 232-USB chip used on WW's 44-pin uM module, being still connected on the PCB, is upsetting things? I will now hook up a full size CMM, and set console to COM1, and see if I can talk to it without issues. Smoke makes things work. When the smoke gets out, it stops! |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2944 |
Grogs, Could you not simply try with a 28-pin MicroMite on a breadboard first? This will then eliminate any potential issues of the FTDI chip on the 44-pin MicroMite Rx/Tx pins. WW |
||||
psergiu Regular Member  Joined: 09/02/2013 Location: United StatesPosts: 83 |
Your "half-duplex" issues are not network-related. If it were, you would have got a "disconnect" message the telnet protocol uses TCP connectivity which is sending acknowledgement messages for each received packet. If one end suddenly stops transmitting, the connection will timeout at the other end and close. More likely there's a serial timing issue between the WizNet an uM - try dropping to 9600 bps |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
@ WW - Yes, that is a good idea - I will do that if I can't get talking on the full size MM. It's just easier for me to hook up the full size MM, as I don't have any 28-pin uM's on breadboards ready to go, so would have to set one up. Not that this is much trouble, but I can connect the 107 to a full-size MM quicker. @ psergiu - Thanks for that information. I can rule that side out then, and just concentrate on the serial side of things. You may well be right with the serial speed thing, cos the pager transmitter is a 9600 baud device, whereas the uM is 38k4(by default). as a quick experiment with the uM, I will slow it to 9600 and see what happens there too. Several ideas to try - thanks guys!  Smoke makes things work. When the smoke gets out, it stops! |
||||
TassyJim Guru Joined: 07/08/2011 Location: AustraliaPosts: 6284 |
set the MM to autorun a program that simple PRINTs something to the serial port in a loop. That will let you see if the link is working in that direction. I would autorun so that if the MM is resetting for some reason, you can see that happen. The fact that you are getting the sign-on message from the MM suggests that the baud rate is OK. Jim VK7JH MMedit |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
Hi folks.
Connection to full size CMM seems to work fine. 
The errors in this screenshot are cos my first test was "Hello World" as you can see, then I tried to open the com port as console without closing it, so it looks a little confusing there, but the MM is happily responding fine in both directions. This is the CG CMM2, on COM1 for the purposes of testing. I don't think that the CMM can go faster then 19k2, as both COM ports on the CMM are software driven - can't remember - will try some higher baud rates, and will probably get an error from MMBASIC if I exceed the maximum baud rate. NOW I will hook up a standard 28 pin uM on a breadboard and hook that into the mix, as perhaps the USB chip on the 44 was upsetting the serial timing. Does not matter really, as it was a full size MM I was wanting to talk to on the net rather then a uM anyway - I just got my hands on a 44 before the MM board. Smoke makes things work. When the smoke gets out, it stops! |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
Hi there again.
Now that I have correct operation over the network fron TT to the MM, I started playing with other things. VT100 mode does not seem to work in TT via network. This is what I get when I type edit: 
I included the TCP/IP window, so you can see that I had it set correctly for VT100. EDIT: Nevermind - TT window too small. When I maximized the TT window, edit works, shows the code etc fine. OK - so that is the LAN side of things. Now I will see if I can setup the WAN part. Smoke makes things work. When the smoke gets out, it stops! |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
This was from a post back on page 1 of this thread, but I am now ready to start doing this kind of stuff, now that the LAN side of things is working OK. I follow you with respect to port-forwarding port 5000 in my ADSL router to the module's IP address - seems logical enough. However, how do I find my public IP address? ipconfig does not tell me, nor does ipconfig /all I will have a hunt on the net now.... EDIT: Nevermind - found it via "What is my IP address" google search and following link to said website. Also found it listed in the router, once I logged in there. I've NEVER had to do any of this port-forwarding stuff, so it is all new to me, so I am a little bit of a newbie here!  Smoke makes things work. When the smoke gets out, it stops! |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
OK, I have HOPEFULLY setup port-forwarding correctly on my router - a TP-LINK unit, and according to the web and a few searches, TP-LINK now call forwarding Virtual Server. 
This shot SHOULD allow port 5000 to be routed to the module from the WAN - correct? I am not stating my public IP address for obvious reasons, but I know what it is, so I will double-check it has not changed(it is DNS according to the router) before I go to my workshop and see if I can talk back to the MM on the 107 module from there. Smoke makes things work. When the smoke gets out, it stops! |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
SUCCESS!!!
I can talk to the MM from my workshop machine, via the Internet. I CAN'T ping the IP or the IP+port, which is probably a good thing. I expect that the router is refusing the ping command from a WAN location. But all up and running, and I am really pleased, and I have also taught myself some new technology, so all is good. The only thing left to test here, is the uM chip by itself, but I will do this next. Smoke makes things work. When the smoke gets out, it stops! |
||||
| TassyJim Guru Joined: 07/08/2011 Location: AustraliaPosts: 6284 |
Getting there! Re port forwarding. Did you choose Telnet from a list or add a new server? If you chose from a list, the modem might be forwarding external port 5000 to port 23 You may have to create a new server and call it anything you like. You should then have the option to set the destination port(s) I much preferred modem/routers when they didn't try to be so 'helpful' and you could just enter the correct details. Hopefully, you can use another internet connection to test the port forwarding. Some modems will let you address your external IP and do the forwarding correctly but others will not. Jim VK7JH MMedit |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2944 |
Please do try the 44-pin MicroMite BUT I do suggest isolating the FTDI chip first. Should be ok to just cut the MicroMite Rx pin from the FTDI as MicroMite Tx shouldn't interfere (UNLESS high impedence switching used on your lan/wan module.) I am burning midnight oil to solve CRC issue for someone. Just cracked this too at 4am! Success all round  |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
@ Jim - I named a new service - called it TEST, and selected TELNET. When I did that, TEST turned to TELNET, and APPLICATION became blank - I guess the router though it knows best? I will call my buddy, and see if I can get access to his PC for a few minutes to try that from another location, as you suggest. @ WW - Don't wanna start hacking tracks. I do have a couple of un-populated boards of yours(as you also have sent me kits), so I might just solder up one WITHOUT the FTDI chip for the purposes of testing - but then again, it would be even quicker to just setup a 28 on the breadboard.Smoke makes things work. When the smoke gets out, it stops! |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
More info for you all. Tried to talk to the MM from a couple of friends PC's at their houses now, and can talk to the module fine - excellent, and I am learning some up-till-now unknown network configuration stuff too.
Still can't make the password thing work, so I am gonna ask WizNet forums about that one - not sure what I am doing wrong there, but it just don't work with that set. As soon as you type anything(even the first character of the password), the connection is closed by the module.
But, that's about all there is to fix now. EDIT: In making the module WAN, it is now refusing connections from the LAN - TT just keeps saying "Connection refused." as soon as I put in the IP and port number. I suspect I need to change something/add something to the router, as port 5000 is on port forwarding now, but I figured that the LAN side would not be affected - perhaps I need to use my own router IP address just as I did from other houses.... EDIT: Yes, using my routers IP address and port number as I did OUTSIDE this house, works, and I can talk to the module in a kind of loop-back, by referencing my own router here, to come back here to talk to the network module - curious. I wonder why I can't reference it by it's IP anymore? It has to be cos the router is port-forwarding to that IP now, so perhaps that stops things working. I wonder if I can ping it? EDIT: Yes, I can ping the module's IP address fine from the LAN. Smoke makes things work. When the smoke gets out, it stops! |
||||
| TassyJim Guru Joined: 07/08/2011 Location: AustraliaPosts: 6284 |
Good to see it working. This networking stuff can be a real pain sometimes. Re Dynamic DNS Mine changes rarely. I have to force a change or be off air for 30 minutes or so. Some ISP's change it every 24 hours just to be a bugger. It all depends on you ISP You can use one of the free services: www.noip.com/free/ or https://www.dnsdynamic.org/ and others... My modem sends me an email whenever the IP changes. I also run a script every hour to check it and automatically update some files as required. Jim VK7JH MMedit |
||||
| TassyJim Guru Joined: 07/08/2011 Location: AustraliaPosts: 6284 |
The port forwarding will only stop you from connecting if someone else is already connected. Usually, you can only have one connection at a time. Does the module have a 'connected' LED or preferably a pin that can be monitored by the maximite. Password: You may need to send it in one packet. The easiest way to do that is do a 'paste' or change TT back to 'line at a time' mode. Jim VK7JH MMedit |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
Hi Jim - not that I am aware of. It has the standard green and orange LED's on the RJ45 socket though. EDIT: OK, will try changing TT back to line mode, but it is a pest to not be able to see the echo back from the MM. I am guessing you could change the INI for local echo - I seem to remember seeing that in the INI... Smoke makes things work. When the smoke gets out, it stops! |
||||
| Page 2 of 3 |
|||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
