Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • in reply to: “Lookup” style selection for writable register #19449

    John, do you have any example .csv files or an updated manual for the new features?

    in reply to: “Lookup” style selection for writable register #19448

    just updated my iPad install, going to test the new feature immediately. Thanks john!!

    in reply to: 1.4.2!!! #19849

    Now I have to convince my wife that I need the latest generation iPod touch to test the multitasking features!!! Maybe I can convince my boss to let me expense it!

    in reply to: Alarm Notification #20003

    I like dutch’s suggestion too….

    in reply to: Alarm Notification #20001

    Yes, that makes perfect sense. I agree that it might be to annoying having the alarms window pop up constantly, especially when first testing, or commissioning a system when there might be many nuissance alarms in the system….

    in reply to: Scrolling on Page causes registers to shift #20010

    Hi Joan,

    Thanks for all your time on helping me with this issue. It turns out my datasize setting (in RTU) and register addressing were wrong. This is the format I started with:

    The description of the datasize parameter in my RTU config:

    A value of 9 indicates that 32-bit floating-point data is to be used with each floating-point value taking up two register addresses. In this mode, the selection is also used on Preset Single Register and Preset Multiple Register commands. The count in the Modbus message will be twice the value of the count defined in Parameter 3. The address in the Modbus message will be equal to the address defined in Parameter 2.

    Then I switched to this datasize setting:

    A value of 7 indicates that 32-bit floating-point data is to be used with each floating-point value taking up two register addresses. In this mode, the selection is also used on Preset Single Register and Preset Multiple Register commands. The count in the Modbus message will be twice the value of the count defined in Parameter 3. The address in the Modbus message will be twice the value of the address defined in Parameter 2.

    And now it works perfectly. So I’m happy.

    If you’d like I can put together a quick instruction article for connecting SM to a Bristol ControlWave RTU. Let me know if you’d like this for the website and I’ll get it done for you.

    Cheers!

    Clint.

    in reply to: Scrolling on Page causes registers to shift #20009

    Good morning John…..

    Thanks, but I’m definitely running Modbus TCP/IP on the slave. Strange thing is I can get some values perfectly, then others just show either 0.0 or some random number, and on some pages I still have numbers changing as I scroll. I’ve tried all the combinations of word order, register addresses etc. I’m running into a wall now….. We should maybe come up with some way for me to demonstrate what I’m seeing. I’ve been working on getting my RTU available via the internet, but my port forwarding doesn’t seem to be working. If you can skype I can likely show you via the webcam what I’m seeing.

    Let me know if you’re availabe. Or if you want me to send you any files or any more info.

    Thanks again.

    Clint.

    Here is a file that I’m testing with, the first 9 tags work perfectly, the last shows 0.0 even though the RTU register contains a value of 178.8.

    diffR1 REAL HR101 slave_id:=2;page:=”Flow Run Summaries”; section:=”Run 1″; label:=”DP”; comment:=”Differential Pressure”;suffix:=” kPa”; format:=1.1; word_swap:=false;
    mrpR1 REAL HR103 slave_id:=2;page:=”Flow Run Summaries”; section:=”Run 1″; label:=”MRP”; comment:=”Static Pressure”; suffix:=” kPa”;format:=1.1;
    rtdR1 REAL HR105 slave_id:=2;page:=”Flow Run Summaries”; section:=”Run 1″; label:=”Temperature”; comment:=”RTD Value”; suffix:=” C”;format:=1.1;
    flowrateR1 REAL HR107 slave_id:=2;page:=”Flow Run Summaries”; section:=”Run 1″; label:=”Flow Rate”; comment:=”Uncorrected Flow Rate”; suffix:=” E3M3/D”;format:=1.1;
    dvolR1 REAL HR113 slave_id:=2;page:=”Flow Run Summaries”; section:=”Run 1″; label:=”Today’s Volume”; comment:=”Uncorrected Volume”; suffix:=” E3M3″;format:=1.1;
    dtopR1 REAL HR115 slave_id:=2;page:=”Flow Run Summaries”; section:=”Run 1″; label:=”Today’s TOP”; comment:=”Time of Production”; suffix:=” Hrs”;format:=1.1;
    pdtopR1 REAL HR133 slave_id:=2;page:=”Flow Run Summaries”; section:=”Run 1″; label:=”Yesterday’s TOP”; comment:=”Time of Production”; suffix:=” Hrs”;format:=1.1;
    pdvolR1 REAL HR135 slave_id:=2;page:=”Flow Run Summaries”; section:=”Run 1″; label:=”Yesterday’s Volume”; comment:=”Uncorrected Volume”; suffix:=” E3M3″;format:=1.1;
    pmtopR1 REAL HR151 slave_id:=2;page:=”Flow Run Summaries”; section:=”Run 1″; label:=”Last Month TOP”; comment:=”Time of Production”; suffix:=” Hrs”;format:=1.1;
    pmvolR1 REAL HR153 slave_id:=2;page:=”Flow Run Summaries”; section:=”Run 1″; label:=”Last Month Volume”; comment:=”Uncorrected Volume”; suffix:=” E3M3″;format:=1.1;

    in reply to: Issue reading multiple REAL registers #20014

    Hi John,

    Thanks for the reply. After you mentioned that each 32 bit float is stored in 2 registers I realized my problem. By default my RTU setting was to have each float take up one 32 bit register. So I’ve made the change to store the floats in 2 registers and I have them all working now.

    Cheers!

    Clint.

    in reply to: Plot range of Registers #19456

    Hi John, thanks for your prompt response.

    The OPC idea is a fantastic one, can’t wait to see where you go with that.

    We deal with customers who have sites, mostly natural gas wells that are extremely remote and don’t have reliable means of communicating back to a central SCADA for historical data archiving. By law they have to collect the flow data at set intervals, and if SCADA comms is down or not possible an operator must drive, fly, or snowmobile out to the site to collect the data. This could be in -40C with mittens on, trying to pull out his laptop, start up all the softare for data collection etc….. Our RTUs can sample data and store it in local archive files in the flash memory of the RTU, so even when power is down the historical data is retained. Programmatically we could pull data from those archives and store them in runtime memory, like in this example a range of modbus registers. So for a simple example, if we are totalizing flow from a well daily and storing it in the RTU flash memory I could then make it available in a range of modbus registers that would always provide me with the last 30 days of flow totals. So then with your application I could configure it to read back all those registers, which could be plotted on a graph. Part of the configuration of that graph would be to assign it a period, like 30 days over which to plot the data.

    The graphing is more of a luxury, a handy tool for quickly assessing a site’s performance, but not essential. The ability to extract the data in something like a .csv to be saved/emailed would be much more useful. So you could use the same example where we read back 30 holding registers with daily flow totals, and then dump them into a .csv. I guess your tool would allow me (as part of the configuration) to set the range of input/holding register adresses to read back, what to name the .csv file etc. Then the operator only has to run Scadamobile, select the configuration file, go to some page with a button that says something like “Collect Daily Archives” and then saves it locally on the iphone or ipod…….

    Hope that helps clarify my suggestion…..clearly this may not be something that every user would find useful, and therefore might not be worth your time in development. But if you ever get it done I know many users that would make good use of it. I’m just in the process of developing/testing two new applications for distribution in Canada, where we will be selling thousands of units in the next 3-5 years. There will be hundreds of personell (integrators and end users) working with the units and a good percentage of them carry iphones and ipod touch devices. If I had a really comprehensive solution ready for those devices I could see a good number of people buying your application. I also train nearly every integrator and end user in Canada that uses our brand of gas flow computers, so I can greatly influence how they go about interfacing with our devices for things like configuration and data collection as I described.

    If you would like to chat more about this you can email me directly or we could chat on the phone or skype….I believe you have my email address as part of my registration.

    Cheers,

    Clint.

Viewing 9 posts - 1 through 9 (of 9 total)
Copyright © SweetWilliam, S.L 2009-2013. All rights reserved.
Science and Technology Park of the University of Girona, Emili Grahit, 91 (NarcĂ­s Monturiol building, Office P3-B03) 17003-Girona. Phone +34972183244