Client Suite 2.2

Community contributed apps
agentgreen
Posts: 97
Joined: Wed Jul 06, 2011 6:45 am

Re: Client Suite 2.2

Post by agentgreen »

Looks like I have the proper .NET prereqs installed.
Attachments
framework.jpg
framework.jpg (61.24 KiB) Viewed 8494 times
chridijon
Posts: 26
Joined: Mon Sep 12, 2011 11:06 pm

Re: Client Suite 2.2

Post by chridijon »

hello guys. i now have a big problem, thanx for sending me the new usb cord Roberto that was the trick, ok so i installed the RAGen and the client suite, uploaded my code and the lcd screen was black and only would turn on for a split second. so i try and open the client suite and it poped up with some error ablut not working right, so i try and uninstall it and it wouldnt uninstall. so beings that i am just computer savy enough to really screw things up, i just open windows exploer and manually delete the file from the c:/program files(86) folder. then try and go and unistal it from add/remove program list and now...... it cant find files so it wont uninstall and when i try and repair.....it says error 101. the specified service already exists, error 1001 could not find C./ program files(x86)/reefangel\reefangel client suite\listener\reefangelWCFListener.installstate, C./ program files(x86)/reefangel\reefangel client suite\servicedash\service dashboard.installstate, C:\users\chris\appdata\roaming\reefangel\client\reefangelclient.instalstate, C./ program files(x86)/reefangel\reefangel client suite\reader\reefangelserialreader.instalstate, C./ program files(x86)/reefangel\reefangel client suite\installsetupAppConfig.installstate, fatal error during installation.

now my question is. what do i do now :D LOL
Image
dmolton
Posts: 182
Joined: Tue Mar 22, 2011 11:08 am

Re: Client Suite 2.2

Post by dmolton »

When you deleted the folder from program files, installstate files were removed that windows uses to complete the uninstall process. You're on the right track, trying to repair. Once repaired, windows should be able to uninstall. You will need to:
-manually uninstall the services
-run installer again to repair.
-uninstall properly from control panel.

Open an "administrator command prompt" and type in the following two commands:

sc delete ReefAngelListener
sc delete ReefAngelLogger

After that run the installer again and attempt to repair. What version of windows are you running?
cain
Posts: 81
Joined: Tue Aug 02, 2011 10:59 am

Re: Client Suite 2.2

Post by cain »

can you use the client suite without wifi?
i didnt install any suite, can i go directly to 2.2?
dmolton
Posts: 182
Joined: Tue Mar 22, 2011 11:08 am

Re: Client Suite 2.2

Post by dmolton »

cain wrote:can you use the client suite without wifi?
i didnt install any suite, can i go directly to 2.2?
Correct and correct.

No matter how you are connecting though, wifi or usb, you WILL need the line "#define wifi" inside the features.h file.

You can download the latest installer here to start from fresh, no need to upgrade: https://github.com/davemolton/Client-Su ... all/master
chridijon
Posts: 26
Joined: Mon Sep 12, 2011 11:06 pm

Re: Client Suite 2.2

Post by chridijon »

I'm running windows 7 64bit. I will try that when i get home tonight. Thanks for the help
Image
dedvalson
Posts: 140
Joined: Tue Oct 04, 2011 5:49 am

Splitting Client Suite between two machines

Post by dedvalson »

Hi,

I was curious about how I might go about running the Windows services of the Client Suite on one computer and the GUI on another.

I have a Windows web server that I have full control of. I would like to run the services on the web server to log the data and then view it on my laptop when I need to. The idea is that the server is running 24/7 so the logging could be also.

I have file system access from my laptop to the server, so I could read the database file on the server from my laptop.

Is this feasible? How does the GUI currently access the database?

Thanks.

Don
binder
Posts: 2865
Joined: Fri Mar 18, 2011 6:20 pm
Location: Illinois
Contact:

Re: Client Suite 2.2

Post by binder »

It may not be feasible right now. I'm trying to get dave to allow the client suite to connect to any database provided the proper database structure exists. I'm thinking he is working on making it more modular but I cannot confirm it. Guess we will have to wait for him to chime in. :)

curt
dmolton
Posts: 182
Joined: Tue Mar 22, 2011 11:08 am

Re: Splitting Client Suite between two machines

Post by dmolton »

dedvalson wrote:Hi,

I was curious about how I might go about running the Windows services of the Client Suite on one computer and the GUI on another.

I have a Windows web server that I have full control of. I would like to run the services on the web server to log the data and then view it on my laptop when I need to. The idea is that the server is running 24/7 so the logging could be also.

I have file system access from my laptop to the server, so I could read the database file on the server from my laptop.

Is this feasible? How does the GUI currently access the database?

Thanks.

Don
It should be possible to achieve what you're talking about, Don. I was able to run that same setup once before quite awhile ago on version 2.0, I think. There is some limitations, though.

First step would be to install the suite on your 24/7 server and configure it correctly so you can see incoming data on the Client portion.

Unfortunately, I don't have just a Client installer setup yet for stand-alone client machines. This means you will also need to install the whole suite again on your laptop. You can disable the Listener and Logger services from running, though. Once completed, you will need to do some config file tweaking. In C:\Users\YourName\AppData\Roaming\ReefAngel\Client locate the ReefAngelClient.exe.config file, modify the following fields:

<add key="DBLocation" value="C:\\Users\\Dave\\AppData\\Roaming\\ReefAngel\\ReefLogDB.sdf" />

<client>
<endpoint address="net.tcp://localhost:8733/Design_Time_Addresses/ReefAngelWCFListener/ReefAngelListener/"
binding="netTcpBinding" bindingConfiguration="NetTcpBinding_IReefAngelListener"
contract="ReefAngelService.IReefAngelListener" name="NetTcpBinding_IReefAngelListener">
<identity>
<dns value="localhost" />
</identity>
</endpoint>
</client>

You might need to open the port 8733 on your web server firewalll for this to work. I believe the two parts noted in red are the only thing you need to change. I will be able to test this out further in a couple days to see if there's anything else that's needed for sure, though. The service dashboard won't work properly on your Client so you won't be able to update Listener settings. Also, in the settings dialog, the Listener settings shown from your laptop will also be incorrect. There was a lot shortsightedness on my part in the beginning of this project and unfortunately a lot of important settings are stored in a series of config files that get updated by other applications. I've since dropped this method of configuring the applications and now utilize WCF operation contracts and the database file much more to handle important settings which will be available in version 3.0 which I hope to have released very soon.

Let me know how it works out for you.

-Dave
dedvalson
Posts: 140
Joined: Tue Oct 04, 2011 5:49 am

Re: Client Suite 2.2

Post by dedvalson »

Dave,

With the setting changes you suggested things worked great.

I did have a couple of surprises.

1. Apparently the Relay names come from the listener, not from the local config file since the app on my laptop displays the relay names set on the server.
2. I had to share the folder where the database lives with Read / Write access. At first I tried only providing read access since I figured the client only read it.

As a general question. If you are configured for email or SMS notifications, are those done by the client GUI or by the listener service? It seems like they ought to be in the listener but it appears they are in the client. Also where are web banner updates done?

Thanks

Don
dmolton
Posts: 182
Joined: Tue Mar 22, 2011 11:08 am

Re: Client Suite 2.2

Post by dmolton »

Don, glad it worked out well for you. Thank you for letting me know what issues you ran into. It will help out in the future when others look to do the same setup.

Version 2.2 of the suite unfortunately has the web banner updating and email/sms notification happening from the Client. So it needs to remain running on your laptop. That functionality absolutely doesn't belong running on the Client and was yet another shortsighted implementation on my part :oops:

I've already pulled out the email/sms/webbanner functionality and created a new "ReefAngel Notification Service" that also subscribes to the Listener and based on user settings, will email or update the web banner for you.

I'm quite close to another release that will be much better served for your kind of setup, so hang in there for just a bit longer :)
jemw
Posts: 41
Joined: Sat Oct 08, 2011 9:21 am

Re: Client Suite 2.2

Post by jemw »

Dave,

A couple of things I have discovered:

When the WifiAuthentication is set - the Client Suite errors out with (log file entry):
Message:
Inside WifiSend:
The remote server returned an error: (401) Unauthorized.
StackTrace:
at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
at System.Net.WebClient.DownloadString(Uri address)
at System.Net.WebClient.DownloadString(String address)
at ReefAngelWCFListener.ReefAngelListener.WifiSend()
Is there a place to store the login and password for passing when connecting?

When values are passed to the functions from the .pde file the Memory tab displays the defaults that
were downloaded initially. Is there a way to display the real values that the controller is using?

Thanks!!
Jim
_____
Jim
rimai
Posts: 12857
Joined: Fri Mar 18, 2011 6:47 pm

Re: Client Suite 2.2

Post by rimai »

How is WifiAuthentication working for you so far?
I'm curious to know because we have a thread about it and the more information the better.
http://forum.reefangel.com/viewtopic.php?f=7&t=372
Would you mind sharing your experience in the above thread?
Back to this thread, the WifiAuthentication has not been implemented in any of the apps we currently have available. Mainly because of issues that are reported in the thread above.
I'm gonna dig deeper to see if I can find anything that would be causing this sporadic behavior.
Roberto.
alexwbush
Posts: 327
Joined: Tue Mar 22, 2011 12:45 am
Location: San Diego, CA

Re: Client Suite 2.2

Post by alexwbush »

dmolton wrote:When you deleted the folder from program files, installstate files were removed that windows uses to complete the uninstall process. You're on the right track, trying to repair. Once repaired, windows should be able to uninstall. You will need to:
-manually uninstall the services
-run installer again to repair.
-uninstall properly from control panel.

Open an "administrator command prompt" and type in the following two commands:

sc delete ReefAngelListener
sc delete ReefAngelLogger

After that run the installer again and attempt to repair. What version of windows are you running?
Dave, this solved my problem. Apparently the ReefAngelLogger was somehow already installed, so I would get an error saying services already exist. Thanks!
dedvalson
Posts: 140
Joined: Tue Oct 04, 2011 5:49 am

Re: Client Suite 2.2

Post by dedvalson »

dmolton wrote:Don, glad it worked out well for you. Thank you for letting me know what issues you ran into. It will help out in the future when others look to do the same setup.

Version 2.2 of the suite unfortunately has the web banner updating and email/sms notification happening from the Client. So it needs to remain running on your laptop. That functionality absolutely doesn't belong running on the Client and was yet another shortsighted implementation on my part :oops:

I've already pulled out the email/sms/webbanner functionality and created a new "ReefAngel Notification Service" that also subscribes to the Listener and based on user settings, will email or update the web banner for you.

I'm quite close to another release that will be much better served for your kind of setup, so hang in there for just a bit longer :)
A couple of thoughts I had for the new release, you may already be thinking along these lines.

1. Running the client GUI on my laptop and the services on my server is working OK, but the file sharing is slow and pretty insecure. Have you considered allowing the client to access the database as a sqlserver client instead of opening the file?

2. I have noticed that if my laptop is asleep for a while and then I turn it on it starts picking up new updates in the graph but the only way to get the updates that were missed while the laptop was asleep is to exit the GUI and restart it.

Thanks,

Don
dmolton
Posts: 182
Joined: Tue Mar 22, 2011 11:08 am

Re: Client Suite 2.2

Post by dmolton »

So I think accessing the database like that would require the user to have at least SQL Server Express installed, yeah? When looking at options for the database I originally opted for the SQL Server Compact because its very small, portable and only needs 6 MS SqlCe libraries to be included with the installation in order to use the data driver. No extra prerequisites required.

I know Curt was asking for the ability to connect to any type of database so long as the table structure is the same. Maybe I can have some extra options in the .config file to allow users to define the database type and then through reflection maybe, access it. I'll look into that option a little further.

For updating the GUI when you resume from sleep, instead of restarting the Client, you can use the radio buttons above the graph to change the viewable date range. Go to "Past Week" and then back to "Live (24hr)". Each time you swap those ranges, it goes to the database for the most recent information.
slipperysam
Posts: 16
Joined: Thu Sep 29, 2011 6:25 am
Location: England

Re: Client Suite 2.2

Post by slipperysam »

that would be a cool idea.

also it would be cool to have it on a web host so all the data is connected with your host (i.e go daddy).

so the client will run as a website rather then a local client.

sam
User avatar
Xender
Posts: 105
Joined: Sun Mar 20, 2011 12:38 am
Location: France

Re: Client Suite 2.2

Post by Xender »

Agree with Sam ;-)
Fresh Water Aquarium 180*60*80
Salt Water Aquarium 60*60*60
Click Here to see the Video of my Fresh Water Aquarium
Image
dedvalson
Posts: 140
Joined: Tue Oct 04, 2011 5:49 am

Yet another request

Post by dedvalson »

Hi,

You are probably getting tired of requests for features, but here is one anyway :D

I have noticed that once in a while (2-3 times a week) I will get an email / SMS message indicating that my pH is too high or low. When I look via at the graph it is generally fine. It appears that occasionally an erratic pH value gets read (they are pretty far off, like suddenly I'll get a 9.0 when the reading 15 seconds earlier was 8.3). Perhaps you could hold off on sending the email till you see two or more bad readings in a row or a timeout has taken place?

Along this line, an email notification if you haven't heard from the ReefAngel in a while might be interesting.

Don
wolfador
Posts: 241
Joined: Sun Sep 04, 2011 9:59 am
Location: Pittsburgh, PA

Re: Yet another request

Post by wolfador »

dedvalson wrote:Hi,

You are probably getting tired of requests for features, but here is one anyway :D

I have noticed that once in a while (2-3 times a week) I will get an email / SMS message indicating that my pH is too high or low. When I look via at the graph it is generally fine. It appears that occasionally an erratic pH value gets read (they are pretty far off, like suddenly I'll get a 9.0 when the reading 15 seconds earlier was 8.3). Perhaps you could hold off on sending the email till you see two or more bad readings in a row or a timeout has taken place?

Along this line, an email notification if you haven't heard from the ReefAngel in a while might be interesting.

Don
Are you using the latest .19 libs? pH averaging was added in, I think that would fix that error.
John
ReefAngel and ReefAngel-HD developer
If the RA iOS app has helped please consider a donation
Image
dedvalson
Posts: 140
Joined: Tue Oct 04, 2011 5:49 am

Re: Client Suite 2.2

Post by dedvalson »

I have version 0.8.5.19 of the libs.

Don
ahmedess
Posts: 173
Joined: Sun May 22, 2011 2:29 pm

Re: Client Suite 2.2

Post by ahmedess »

I m getting this error msg when i try to change values in the memory using client 2.2

Code: Select all

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at ReefAngelClient.Form1.SetMemoryValues()
   at ReefAngelClient.Form1.btnSaveMemory_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
ReefAngelClient
    Assembly Version: 2.2.0.0
    Win32 Version: 2.2.0.0
    CodeBase: file:///C:/Users/Ahmed/AppData/Roaming/ReefAngel/Client/ReefAngelClient.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Windows.Forms.DataVisualization
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.116
    CodeBase: file:///C:/Users/Ahmed/AppData/Roaming/ReefAngel/Client/dlls/System.Windows.Forms.DataVisualization.DLL
----------------------------------------
System.ServiceModel
    Assembly Version: 3.0.0.0
    Win32 Version: 3.0.4506.4926 (NetFXw7.030729-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.ServiceModel/3.0.0.0__b77a5c561934e089/System.ServiceModel.dll
----------------------------------------
System.Runtime.Serialization
    Assembly Version: 3.0.0.0
    Win32 Version: 3.0.4506.4926 (NetFXw7.030729-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Serialization/3.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Data.SqlServerCe
    Assembly Version: 3.5.1.0
    Win32 Version: 3.5.8080.0
    CodeBase: file:///C:/Users/Ahmed/AppData/Roaming/ReefAngel/Client/dlls/System.Data.SqlServerCe.DLL
----------------------------------------
System.Data
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Transactions
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
ReefAngelException
    Assembly Version: 1.1.0.0
    Win32 Version: 1.1.0.0
    CodeBase: file:///C:/Users/Ahmed/AppData/Roaming/ReefAngel/Client/ReefAngelException.DLL
----------------------------------------
System.EnterpriseServices
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.4926 built by: NetFXw7
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
Manometers
    Assembly Version: 1.0.3975.30783
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/Ahmed/AppData/Roaming/ReefAngel/Client/dlls/Manometers.DLL
----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
SMDiagnostics
    Assembly Version: 3.0.0.0
    Win32 Version: 3.0.4506.4926 (NetFXw7.030729-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/SMDiagnostics/3.0.0.0__b77a5c561934e089/SMDiagnostics.dll
----------------------------------------
System.Web
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
System.WorkflowServices
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.594.4926
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.WorkflowServices/3.5.0.0__31bf3856ad364e35/System.WorkflowServices.dll
----------------------------------------
System.ServiceModel.Web
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.594.4926
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.ServiceModel.Web/3.5.0.0__31bf3856ad364e35/System.ServiceModel.Web.dll
----------------------------------------
System.IdentityModel
    Assembly Version: 3.0.0.0
    Win32 Version: 3.0.4506.4926 (NetFXw7.030729-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.IdentityModel/3.0.0.0__b77a5c561934e089/System.IdentityModel.dll
----------------------------------------
System.ServiceProcess
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Deckoz2302
Posts: 149
Joined: Tue Nov 01, 2011 11:05 am

Re: Client Suite 2.2

Post by Deckoz2302 »

Hmm caqnt figure. Out why it won't pull any parameters? It connects and sees the ra on com3 baud 57600 through usb but no info is pulled
dmolton
Posts: 182
Joined: Tue Mar 22, 2011 11:08 am

Re: Client Suite 2.2

Post by dmolton »

ahmedess wrote:I m getting this error msg when i try to change values in the memory using client 2.2
Are you seeing correct data from the controller on the main tab? Temps/pH/Relay statuses?
dmolton
Posts: 182
Joined: Tue Mar 22, 2011 11:08 am

Re: Client Suite 2.2

Post by dmolton »

Deckoz2302 wrote:Hmm caqnt figure. Out why it won't pull any parameters? It connects and sees the ra on com3 baud 57600 through usb but no info is pulled
1.) Do you have "#define wifi" in your ReefAngel_Features file? Double check this.
2.) Do you have any other applications running that my have a lock on the COM Port? i.e. Arduino IDE.
3.) Have a look at the error log and report back any findings. There may be something useful in there: View -> Error Log
Deckoz2302
Posts: 149
Joined: Tue Nov 01, 2011 11:05 am

Re: Client Suite 2.2

Post by Deckoz2302 »

1 no I don't have define wifi - no wifi module using usb, should I define it?
2 this is more then likely my problem, I had aurduino open but did not think it was connected as I wasn't uploading or using the java status monitor.
3 I did check the error log and the only thing in it was the original log from not finding the sql.....35.dll which was fixed by installing the necessary dll
ahmedess
Posts: 173
Joined: Sun May 22, 2011 2:29 pm

Re: Client Suite 2.2

Post by ahmedess »

dmolton wrote:
ahmedess wrote:I m getting this error msg when i try to change values in the memory using client 2.2
Are you seeing correct data from the controller on the main tab? Temps/pH/Relay statuses?
Yes everything is perfect except when i try to update any value in the memory i get this error msg and then i have to choose between closing the client or continue using it. If i choose to continue the memory window stays frozen without any info onit
rimai
Posts: 12857
Joined: Fri Mar 18, 2011 6:47 pm

Re: Client Suite 2.2

Post by rimai »

I've seen this happening before. It happened to me and I forgot to comment.
I had something to do with one of the values being out of range, if I'm not mistaken.
If you go ahead and load one of the internal memory PDE files, it should correct the problem.
I think what happens is the Client pulls a value in the memory that was never initialized and it falls out of range of what the Client is expecting and it just generates an error.
Roberto.
ahmedess
Posts: 173
Joined: Sun May 22, 2011 2:29 pm

Re: Client Suite 2.2

Post by ahmedess »

rimai wrote:I've seen this happening before. It happened to me and I forgot to comment.
I had something to do with one of the values being out of range, if I'm not mistaken.
If you go ahead and load one of the internal memory PDE files, it should correct the problem.
I think what happens is the Client pulls a value in the memory that was never initialized and it falls out of range of what the Client is expecting and it just generates an error.
I'm using Celsius temperature mode and I've set the internal memory values related to heater and chiller in celcius. could that be the problem?!! cause also on my client the values are not shown at heater and chiller temperature section.

I really dont want to go back to using Fahrenheit because of this. I hope its something that I could fix fast.
dmolton
Posts: 182
Joined: Tue Mar 22, 2011 11:08 am

Re: Client Suite 2.2

Post by dmolton »

Deckoz2302 wrote:1 no I don't have define wifi - no wifi module using usb, should I define it?
2 this is more then likely my problem, I had aurduino open but did not think it was connected as I wasn't uploading or using the java status monitor.
3 I did check the error log and the only thing in it was the original log from not finding the sql.....35.dll which was fixed by installing the necessary dll
Yes, #define wifi must be in your Features file, even if you're not using the wifi adapter and instead want to communicate with the Client over USB. "wifi" in the context of the features file, is a little misleading. "#define comm" might be more appropriate. With wifi defined in the features file, all you're really doing is enabling the controller to receive commands and output xml. The controller doesn't care if a usb cable is plugged into it or a wifi adapter. In fact, it outputs the exact same response no matter whats plugged in.

From here, I would:

1.) Stop the Listener service.
2.) add the #define wifi into your features file and try to recompile/upload from Arduino IDE. You might have to remove some other features from your file because wifi takes quite a bit of memory space.
3.) Upload your sketch with the fixed features file.
4.) Exit the Arduino IDE.
5.) Start the Listener up again and launch the Client.

When you want to reupload another sketch, you will need to stop the Listener to release the COM lock, open/upload/close Arduino IDE. And finally start the Listener again.

This should get you up and running.
Post Reply