mse3000

Members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mse3000

  • Rank
    Member
  1. Is there a known bug in DAQ Factory that stops the graph export function working in Windows 7? The print / export graph funtion works fine in XP and Vista but when exporting a graph and clicking on "browse" to select a file destination, DAQ Factory locks up in 7. Regards, Mark
  2. mse3000

    Alarm Events

    Hopefully a quick question to sort out. I think I am misinterpreting the alarm events. I am trying to set an output based on an alarm firing in order to send a signal to a gsm device. My problem is what ever I do, nothing I seem to put in the alarm fire event is actually taken account of when the alarm fires. I have taken this back to simply setting test bits to equal 1 when the alarm fires but still nothing. I see the manual says the following; and from the first three lines it seems I should be able to do what I require but the last two lines are confusing. Is the event a condition? Events: Alarms also have three events, sequence steps that will be executed when a particular event occurs. There is one for when the alarm fires, when the alarm resets, and when the alarm is acknowledged. Each has its own tab in the alarm view. If you return(0) from the event, then the alarm fire, reset or ack will be ignored. Many thanks, Mark
  3. mse3000

    Timing Lag

    Thanks. I do currently use the device delay on several of our systems running 485 and find 20ms usually works well. Interestingly yesterday I set up a new computer and came across the advanced settings for power plans under Windows 7. As this was also our first system setup on windows 7 I decided to have a look back and found two settings that concerned me: usb selective suspend setting was enabled sleep - allow hybrid sleep Since we are running a usb to serial converter I thought this may have something to do with the cause. Since modifying these the system has now run without error for nearly 24 hours. I am hoping this was perhaps the cause and not the comms setup. Failing that I will continue to increase my device delay. Reagrds, Mark
  4. mse3000

    Timing Lag

    Thanks for the advice, I have now modified the TCP timing to a 0.5 second offset and modified the 485 to poll every two seconds and this runs fine. Looking back at the file i sent before another line has come to my attention where the transmit and recieve times are the same. Surely this is not possible. Do you think this would be caused by DAQ Factory or the device? Would this have any adverse affects on DAQ Factory? Tx (17:13:54.587): 1103000500032196 Rx (17:13:54.587): 11030611000000000094\174 My second problem now arises where the data seems to become completely scrambled. I have again attached the relevent file displaying some of the transmit and recieve data. The requests seem to be correct but data coming back I am guessing is meaningless as the device numbers are not even on the system. I am struggling to find the cause of this as the whole system will run fine for 6, 11 or 15 hours for example, before seemingly crashing. The last two data crashes have been at approximately 21:30 and 02:30. Do you think this could be linked to the inverter devices taking 0.4 seconds to respond as we have previously discussed or something else? Once this begins to happen the command alert is also filled with modbus errors 5, 10 and 11; as well as timeouts expectedly. I can appreciate it is difficult to diagnose remotely so I have also attached the .ctl file for your information. Perhaps I am asking too much too quickly? I'm sure my programme is far from perfect! Please do not make the ctl file available publicly to view or download. If you are unable to shed any light on the possible cause for this, is there a way I can accumulate the number of errors in relation to time. Say 5 errors in 20 seconds and ask the computer to reboot in order to bring the system back to a stable position? As this currently seems to sort the problem for however many hours until it occurs again. In the mean time I shall speak with the Inverter manufacturers and investigate if they have experienced problems with modbus requests previously. Best Regards, Mark Modbus_Error_3.txt
  5. mse3000

    Timing Lag

    I am currently reciecing a timing lag error every couple of minutes. According to the user manual this is usually due to the CPU being maxed out for a short period of time. In this case the CPU is running at only 10% and the timing for each request is fairly slow. We have a device delay of 50ms and a polling time of 1 second. I have attached a note pad document with some of the transmitted and recieved data in the hope you may be able to shed some light on things. I have tried increasing polling time to 2 seconds with no avail. We have a fairly simple network setup of four Advantech Adam units and three Invertek Inverter drives running on modbus RTU (RS485) and one E-dam unit running modbus TCP. Several lines concern me in particular: Tx (17:13:53.474): 1103000500032196 Rx (17:13:53.877): 11030611000000000094\174 Tx (17:13:54.293): 0403000600023695 Rx (17:13:54.293): 040304\218\225\220 Rx (17:13:54.294): \11428\248 Tx (17:13:56.390): 10030005000320\177 Rx (17:13:56.390): 10 Rx (17:13:56.390): 030607000000000083\242 Tx (17:13:56.639): 12030005000320\215 Rx (17:13:56.639): 120306070000000000\120 Rx (17:13:56.639): 82 Any thoughts?? Many Thanks, Mark Modbus_Error_2.txt
  6. mse3000

    Large Amounts of Data in Graphs

    We were actually seeing the computer slow when viewing any graphs. Data is however logged every second and maximum x-axis scaling is a month to view. We have since upgraded the computer on site as the client provided a rather old machine and this has made the world of difference. I have also taken one of the graphs out of a pop-up window after reading in another post that graphs did not work well in pop-up windows. Thanks for the clarification on my question above. Regards, Mark
  7. mse3000

    Large Amounts of Data in Graphs

    OK, my question - Is there a way to tell the Y expression within a graph to only display the amount of data within the time frame of the x- axis? I am currently monitoring temperatures in a chicken shed where crop cycles are approximately 40 days but we are monitoring temperature through a heat exhanger every second. I want the farmers to be able to zoom out to show trends of up to one year to let them compare crops. The persistence files are several GBs each which is not a problem and it is obviously reasonable to expect some time delay when looking at all of the data points. But if there is a method to reduce the drawing delay, when only looking for example at a few hours of data, that would be useful. I have scanned through the forums and been through the quickmod pro guide but I'm either missing the answer or I guess this is not possible? Many Thanks Mark
  8. mse3000

    Multiple Devices on Port 502

    Additional - Problem now resolved. Problem has now been solved by E-Senza, they did realise that their modbus request was part of two requests and did recitfy this. The E-Senza device is pre programmed with a modbus start address which was defined as 40001. I think this conflicted with the usual modbus request as when this "start address" was changed to 1 multiple devices can now be successfully communicated with on port 502. Many thanks for your support with this. Regards, Mark
  9. mse3000

    Multiple Devices on Port 502

    Many thanks for the response. Following up on this I sent the transmit and recieve data to E-Senza as follows, as points 1 and 2 made no difference. Data sent and received without other traffic on port 502 first, and immediately after with other traffic. Illegal data address is returned when run in conjunction with other traffic. Tx (08:31:52.501): 000000000006010378370001 Rx (08:31:52.506): 000000000005010302\127\236 Tx (08:31:53.501): 000000000006010300040001 Rx (08:31:53.540): 00000000000301\13102 Now somewhat annoyingly and in no response to the original question their response was as follows. "I just tried to understand what the difference is between the modbus-request sent when it works (e.g. modpoll) and QuickMod. I did this by listening on port 502 on the slave side, i.e. just looking at what comes out there. Working setup: {00}{14}{00}{00}{00}{00}{00}{06}{01}{03} QuickMod: {00}{00}{00}{00}{00}{06}{01}{03}{00}{00}{00}{14} Could we ask Azeotech how QuickMod would need to be configured to make it requesting in same way as modpoll does ?" Can I point out that E-Senza like to test their system using "modpoll" which runs in a command window (Run - cmd) and we are of the opinion they need to make their system work with a fully functional Windows based system. In response to their question we have already asked what it would take them to make the E-Senza gateway respond correctly to DAQ Factory, as we did in the first place, but do you have any ideas based on their question ? Many thanks for your continued support, the aftersales support provided by Azeotech is excellent! Best Regards, Mark
  10. mse3000

    Multiple Devices on Port 502

    I am currently struggling to understand the rules of what connections are allowed on the default modbus port 502. My setup is a computer running Daq factory connected via a hub to two Advantech ethernet Adam units (6024, 6066) and an E-Senza Modbus gateway. Each one has its own Communication Device set up with IP addresses 192.168.22.149 through 151. All are currently set to port 502. My confusion arises because I can communicate with both Adam units with no problems but if I run a channel looking at the E-Senza device, I get illegal data address errors (although data is still sent to and from the device, as displayed by Tx, Rx in the monitoring window). Unexplainable by ourselves or the manufacturers of the E-senza device, we have to poll channels in the range of 20000 to establish modbus comms with the device. Could this perhaps be causing the issue? Regards, Mark Ellis
  11. mse3000

    Port Locked Errors

    That makes almost perfect sense! I am not a computer tech so talk of single and multi threading in windows does lose me a bit, but now the port timeout setting finally has meaning. I had become so engrossed with timing and offsets I completely forgot to even consider the timeout. Could you just confirm one thing for me though to get everything sorted in my head. If I had two blocks of data taking 0.75s each on a 2 second timing. If the output data time exceeded 0.25s in length would this then cause other problems, or would the overall timing just be increased by the time needed to send the extra data. I.e. if the outgoing data took 0.5s to send in a gap of only 0.25s. Would the overall timing effectively become say 2.25s based on one set of outgoing data, or would it remain at 2 seconds with some data failing to be sent/recieved? Many thanks for the replys, I think I should be able to finish off one of the larger systems now once and for all! Regards, Mark
  12. mse3000

    Port Locked Errors

    OK so are you saying that DF is unable to check the status of the port before trying to send outgoing messages resulting from whatever may be in a sequence. If this is the case surely using an offset would make no difference as the time taken to query all devices is the same whether it is split into four sections for example or left as one data block. I was under the impression outgoing data was tagged on to the end of the incoming data stream, hence avoiding locking the port. And as long as the timing was great enough this would not be a problem. If I need to use offsets, is there a timeout that DF uses before trying to send the outgoing data regardless of the port status and is this a value I need my incoming blocks of data to be lower than in order to avoid this problem. i.e. 1000 ms? Regards, Mark
  13. mse3000

    Port Locked Errors

    Not sure if this is in quite in the right section but here goes. I am having a few issues with port locked errors. There doesn't seem to be any regular time intervals between the errors and they are not accompanied by any timeouts. So I am wondering, is it possible that due to the number of sequences I am running, are the outputs from the sequences clashing with the data requests around the system? If this could be the case is there any way to tell DF to prioritise the inbound and outbound traffic to avoid this from happening? I have copied a sample of the errors with time stamps below. 12/14/10 13:46:55.071 P-ModbusRTU 0013: Port locked 12/14/10 13:51:07.428 P-ModbusRTU 0013: Port locked 12/14/10 13:52:03.272 P-ModbusRTU 0013: Port locked 12/14/10 13:57:52.768 P-ModbusRTU 0013: Port locked 12/14/10 13:59:28.578 P-ModbusRTU 0013: Port locked Many thanks, Regards, Mark
  14. mse3000

    OPC Server Connecting with Omron PLC

    Thanks for the pointers. I am now left with just one question. Is DAQ FActory OPC version 2 compatible? I had no trouble using the OPC server provided by software toolbox, but the client wishes to run CX Server OPC, which is unfortunately not detected when searching for OPC servers on the local machine. And hence the only explanation I can find in the CX manual is that the client may not be fully version 2 compatible. Do you think this is the case? Regards, Mark
  15. Hi, I have recently just completed my first two SCADA systems using DF but have not as yet been asked to integrate with a PLC, so... just looking for some general information here to get me started linking DF to two Omron PLCs. Namely a CJ1G-CPU44H and a CJ1M-CPU13. Both of which are connected to their own HMI, again Omron, NS8-TV00B-V2. Following a bit of research am I right in thinking this will have to be done through an OPC server? I have found an Omron Toolbus OPC Server through Kepware.com and also the CX-server OPC avaiable through Omrons CX-ONE package. Would both of these be suitable or is there a simpler / cheaper alternative perhaps? Would you also normally link through the HMI device or straight into each of the PLCs? Anybodies experience or general advice to get me started greatly appreciated. Regards, Mark