Ok we still seem to have a few people experiencing random drops of there Classic from the App. I would ask that you give us as much info as possible on the system to help us find this issue some are having.
I need to know:
Is the IP address in the Classic Static or DHCP?
Is the Modbus port still 502 or was it changed?
Local App version?
Classic code Revision?
A description of the network. As descriptive as you can tolerate. Make and Model of switches etc so we can acquire these devices and recreate the network here.
A description of what you where doing in the app if anything to cause this.
Is the dropping reproducible?
Thank you
Ryan
Ryan;
Application Version 0.3.15
Classic Firmware:
- Classic Rev: 1181
- Network Rev: 1122
Ubuntu 11.10
Not sure how to find what version of air is installed?
Network;
Linksys wrt54G Wireless router with Firmware: DD-WRT v24-sp2 (07/22/09) mini on it, 8 foot cat5 cable to router from Classic, Laptop wireless to Linksys router.
About 15 or so devices using the LAN. Other devices mostly wired through no name switches to the router spread across 2 buildings with a wired cat5 link between buildings. Classic and my Laptop use the Linksys exclusively, as in not any other hardware between them.
Classic is static with 192.168.2.129 IP on a 192.168.2.xxx network.
Dropping connections to Classic while in the Data -->live tab. Not 100%% reproducible but does it more often than not. Seems to take a few minutes to happen. Often triggered by trying to change the date range.
Otrherwise it seems rock solid simply monitoring the dashboard. I will just watch the dashboard awhile see if it stays connected but I am fairly certain it has to do with the live data tab as that is the only time it drops since .15
More as it develops.
Tom
Ryan: I basically went and re-installed the latest updates for the whole shooting match - MNGP, classic, local app. I'll see what shakes from there.
Quote from: Halfcrazy on February 21, 2013, 06:27:19 PM
Ok we still seem to have a few people experiencing random drops of there Classic from the App. I would ask that you give us as much info as possible on the system to help us find this issue some are having.
I need to know:
Is the IP address in the Classic Static or DHCP?
Is the Modbus port still 502 or was it changed?
Local App version?
Classic code Revision?
A description of the network. As descriptive as you can tolerate. Make and Model of switches etc so we can acquire these devices and recreate the network here.
A description of what you where doing in the app if anything to cause this.
Is the dropping reproducible?
Thank you
Ryan
Is the IP address in the Classic Static or DHCP? Static 192.168.1.100 DHCP Range starts at 192.168.1.110-192.168.1.160 I have now disabled DHCP but don't think that will change anything. Is the Modbus port still 502 or was it changed? 502 not changes Local App version? V0.3.15 Adobe Air V3.6.0.5970 Classic code Revision? MNGP1042 (12/11/2012) Classic 1333 (2/19/2013) Beta A description of the network. - Linksys wrt54G V3.1 Wireless router with Firmware V4.00.7 Apr 26, 2005 - 8 foot Cat5 cable to router from Classic, Laptop wireless to Linksys router WPA2. No other devices on this LAN. Network is strictly for Classic at this location. Single Classic with no Follow Me. A description of what you were doing in the app if anything to cause this. - Dropping connections to Classic while in the Data Live tab. Reacquires connect within a few seconds. Is the dropping reproducible?- Not 100%% reproducible but does it more often than not. Often triggered by trying to change the date range. Have only seen one drop out while monitoring in Status Tab
Hi,
No Time this morning to describe all my network configuration, but among Dell switch, Netgear routers, I also have two Linksys WRT54 GS Wifi Access points with DD-WRT firmware V24.
Yann
Hm I am seeing a pattern here Linksys WR54G Routers? I will find one somehow and set it up here.
Ryan
QuoteHm I am seeing a pattern here Linksys WR54G Routers? I will find one somehow and set it up here.
Ryan
Ryan,
I have the classic connected to a Asus router that I use as a repeater with static IP at 192.168.15.200:502 and did not see dropping connection at this time. No Linksys here.
Do we need to uncheck insomnia in the loc app as I don't need to use it in the classic?
Erik
Ok Andrew thinks he knows what it is and it has to do with the way he requests Live data from the PC's hard drive or something. He is working on it and we will keep everyone posted.
Ryan
Hi all,
having no more dropped connections since I installed the latest level in Firmware and LocalApp.
But a new Update Error Event different from the precedent.
Yann
I'm also dropping regularly using a WRT54G2. Using the beta local app.
Just to be a pain in the keister, I haven't dropped since the double upgrade (local app/firmware, beta.)
Quote from: Vern Faulkner on February 23, 2013, 06:37:50 PM
Just to be a pain in the keister, I haven't dropped since the double upgrade (local app/firmware, beta.)
Vern,
Try this and let us know if the Local App drops. Go to the DATA tab select the LIVE tab and then to the right of the calendar select MONTH from the pull down then Click on EXPORT. I get the port closing 100% of the time with this sequence. See log of port monitor at 2sec intervals attached. You can see that port 502 goes closed-waiting.
John
Quote from: Resthome on February 27, 2013, 05:42:10 AM
Vern,
Try this and let us know if the Local App drops. Go to the DATA tab select the LIVE tab and then to the right of the calendar select MONTH from the pull down then Click on EXPORT. I get the port closing 100% of the time with this sequence. See log of port monitor at 2sec intervals attached. You can see that port 502 goes closed-waiting.
John
John;
I see this, too. Only thing is I get it any time I open the "data" tab.
I am using a dated version of Air so I have tried to stay out of this because it may be my older version of Air on Ubuntu that is the problem in my case and the Midnite guys don't need false leads wasting their time. (Quiet rant on Adobe proprietary software and lack of broad support for same)
You are not alone in that closed connection bit, John.
Tom
Hm I just tried that with no issue? But Andrew says he is working on the logging because something he does now can pull way to much data at once from the hard drive? So if that is the case a PC that is already running hard may show this sooner than a fast pc running very light??
Ryan
Quote from: Halfcrazy on February 27, 2013, 09:12:04 AM
Hm I just tried that with no issue? But Andrew says he is working on the logging because something he does now can pull way to much data at once from the hard drive? So if that is the case a PC that is already running hard may show this sooner than a fast pc running very light??
Ryan
Well Ryan your correct I just went back to try it and after 10 attempts not one dropped connection. Go figure, so it is not 100% as I had stated. Sorry for the false lead. My laptop is a few years old but it is an Intel 2 Core running at 2.20Ghz, the HD is 1G – 5400rpm, and the Network connection is Wireless G connected with the router @ 54Mbs running Window 7 with the latest Classic Beta 1339 and the latest Beta app 3.17.
Watching the performance monitor when the Export is initiated I see the initial disk I/O for the Local App monthly file writing at 1,300,000 B/sec + then throttle down to around 350 B/sec Writes. Local Net I/O performance seem to be constant around 130 B/sec Receive and 12 B/sec sends. The local app is only taking 1% of CPU. Just some data points. Not sure what is causing port 502 to close. Seems like it needs a good network sniffer trace when it happens. Hopefully Andrew has a handle on it.
John
Tom, looks like you, and I, will have to stay with an 'old' version of AIR if it can be located...
http://en.wikipedia.org/wiki/Adobe_Integrated_Runtime
It also originally supported Linux, but that support was discontinued.
ADD : V 2.6 is the last one
http://helpx.adobe.com/air/kb/archived-air-sdk-version.html
Quote from: Halfcrazy on February 22, 2013, 09:17:53 AM
Ok Andrew thinks he knows what it is and it has to do with the way he requests Live data from the PC's hard drive or something. He is working on it and we will keep everyone posted.
Ryan
After looking at WireShark network data the Classic is 196.168.1.100 (Static) my computer is 196.168.1.110 (DHCP). DHCP begins at 196.168.1.110.
A screen shot of WireShark network trace of the Classic and Local App connection drops while in the Data tab is attached. Filtering on only the TCP data packets it appears that the Modbus Read Multiple Register commands usually have a query packet from the APP and then a response packet from the Classic. Before the APP sends a Finish Flag there was a Query from the APP but no response from the Classic. So for some reason the Classic is not sending a response. The APP then sends a ACK, FIN (Finish) and disconnects and throws the error message. Not sure if it resyncs without dismissing the error message and clicking the View button. I think it does as the same disconnect happens with the AutoRestart at midnight set to reboot the Classic and the data continues to be acquired while the Error message is still displayed.
Quote from: Resthome on March 13, 2013, 11:23:12 PM
After looking at WireShark network data the Classic is 196.168.1.100 (Static) my computer is 196.168.1.110 (DHCP). DHCP begins at 196.168.1.110.
A screen shot of WireShark network trace of the Classic and Local App connection drops while in the Data tab is attached. Filtering on only the TCP data packets it appears that the Modbus Read Multiple Register commands usually have a query packet from the APP and then a response packet from the Classic. Before the APP sends a Finish Flag there was a Query from the APP but no response from the Classic. So for some reason the Classic is not sending a response. The APP then sends a ACK, FIN (Finish) and disconnects and throws the error message. Not sure if it resyncs without dismissing the error message and clicking the View button. I think it does as the same disconnect happens with the AutoRestart at midnight set to reboot the Classic and the data continues to be acquired while the Error message is still displayed.
Good detective work, John.
We used wireshark too. What a great program !
I'll clue Andrew into your findings.
boB
Hi, everybody,
The dropping in the data tab seems to be an Adobe Air performance issue and kudos to John's excellent wireshark sleuthing. It can't handle the file and networking simultaneously. Usually a missing response packet from the Classic is not grounds for closing the connection unless AIR gets hung up waiting for the disk. This is one of many reasons I'm changing our application framework to leverage some more robust technologies and we'll be dropping AIR like it drops network connections.
Ubuntu and other fellow Linux flavored users, please take note of my disclaimer on the bottom of the app download page:
http://mymidnite.com/
Adobe dropped Linux support at version 2.6 and, regrettably, we have had to follow suit. The app up to version 2.6 is supported for Linux, but any newer revs are use-at-your-own-risk. I've had some luck running the app on Ubuntu 12.10 under wine, but as a small company we don't have the resources to support an unsupported platform. I'm very bummed at Adobe's decision as Linux support was one of the main criteria for using AIR in the first place.
Thanks!
-Andrew
Even the Photoshop suites rarely get bug fixes, just new versions that you have to pay for. And the Elements products are all developed in India and only the Product Manager is in San Jose.
Will be glad to see the new Web Server.
Quote from: atop8918 on March 14, 2013, 03:57:59 AM
Hi, everybody,
I'm changing our application framework to leverage some more robust technologies and we'll be dropping AIR like it drops network connections.
-Andrew
Andrew any comments about the
"more robust technologies" you will use?
Eric
Quote from: Westbranch on March 14, 2013, 08:49:34 PM
Andrew any comments about the "more robust technologies" you will use?
Eric
Probably involves words I can't publish or say on air.
Ahw, pushaw....
We're going to start doing a web-based interface directly on our products like almost everybody else does, although compared to my current solution, a couple of rocks banged together could be considered "robust".
Quote from: atop8918 on March 15, 2013, 12:02:54 PM
We're going to start doing a web-based interface directly on our products like almost everybody else does, although compared to my current solution, a couple of rocks banged together could be considered "robust".
Good the hear!
Every project starts someplace. At least a couple rocks are durable! And change keeps you from getting bored. ;D
Waiting patiently. Well kinda. 8)
Tom
Quote from: atop8918 on March 15, 2013, 12:02:54 PM
We're going to start doing a web-based interface directly on our products like almost everybody else does, ...
Thats the way to go ;D there are plenty of examples of web
servers for embedded processors but i have noted some recent chinese mppt controllers advertising a second ARM cpu just
to provide 'web based user interface'. The LPC236 series ARM processor in the Classic should have the grunt and memory
available (unless boB has used it all in mppting)
Can that MNGP processor and memory be leveraged for web interface use? Is it also an LPC236 type?
I had thought it would be nice to have a web cpu/ram/storage (SD card) module that replaced the MNGP/lite panel if the
Classic resources were just too meagre
But maybe this is going too far for a simple web face just like Cisco Linksys WRT45G
dgd