Ken

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Ken

  • Rank
    Member
  1. After re reading my post, I juts want to be sure I explained myself correctly. If I had 4 monitors running from the same computer, and I have 4 Daqfactory programs running like this Daqfactory1 Daqfactory2 Monitor 1 monitor2 Daqfactory3 Daqfactory3 Monitor 3 monitor4 What I would like to do is have all the pop ups from Daqfactory 1, only show on monitor 1, all pop ups from Daqfactory 2, to show up on monitor 2. I do not want all pop ups to appear on "the same" monitor. Currently, it doesn't matter which monitor I have Daqfactory running on, they always reference themselves from the 0,0 of the primary monitor and all pop ups appear on the primary monitor. If you understood this from the first message, then I thank you for your time and response.
  2. We have a multi monitor setup and I wish to have multiple instances of Daqfactory running on each screen and be able to tie the associated popups to the same screen. I have tried making an "anchor" as a component, and then using the PositionTop and PositionLeft from the component to set the position but this did not work. When I moved the instance of DF around, this value did not change. Is it possible to do this?
  3. LOL... yes right..sorry shellexecute option was what I meant, the extern was from a different reply I read of yours for something else.... Obv in need of more coffee... Yes, I will probably just time a sequence to run calling the shellexecute for a single ping to the end device for now, and test the Ethernet device option at a better suited time. As always thanks for the time and support.
  4. Is it possible to ping from within Daqfactory? or would it just be easier to use the extern() function and call a batch file? The need for the ping is to have DF basically be a "keep alive" for the vpn tunnel. With this particular setup ( dynamic to static ), the end device on the dynamic side , needs to reinit the tunnel if for any reason the tunnel goes down. Even a simple ping to the static device will re-establish the tunnel.
  5. After reading the Guru blog about recursive, I started to wonder if it would be possible to have DAQFactory installed on a separate partition/drive other than C: So if you were logging and exporting data would there be a way for it to know which drive to store the files? So rather than having C:\logging\ You could have something like \\logging\ Could the same be done with writing and opening files?
  6. This is VERY exciting news! The time it will save projects is substantial. As always Azeotech support and willingness to work with clients is astounding.
  7. Ken

    Daylight Savings Time

    Thank you for such a quick response, resolution, and also taking the time to reiterate the pit falls and other issues. I will discuss this with our engineering department again to inform them of what we are giving up to do this. Obviously our preferred method is to just use DF as intended, but to provide the customer their request we will have to do some hard testing to ensure there are no issues. Again thank you for the amazing support.
  8. Ken

    Daylight Savings Time

    On the topic of system time and DF only looking at the time prior to starting, would it be possible to provide the option, if the coder so decides to use the system time ? The reason for this request is because a client is looking for a means of using NTP (http://en.wikipedia.org/wiki/Network_Time_Protocol) so that they can sync all computers/ethernet enabled devices on the network for fault condition analysis. This way they can find out what first caused the fault based on synchronized timing.
  9. Ken

    Reset Modbus after cannot bind Socket

    Just to let you know this has not been forgotten about on our end, we are still waiting for the runtime to re-create the problem. They are currently in the field (out of country ) and should be back shortly.
  10. Ken

    Reset Modbus after cannot bind Socket

    The master is another piece of software running on a separate computer/server ( redundant servers ). We are waiting for for a runtime of this software to help in diagnosing the problem. Thank you
  11. Ken

    Reset Modbus after cannot bind Socket

    There is absolutely no problems at all. Actually, if we make a sample program using DaqFactory to be a master we never run into this problem.
  12. Ken

    Reset Modbus after cannot bind Socket

    We are not re-initializing the port in our code, and we have not been able to determine what is causing the conflict, other than we have only ever seen it with the third party Master. We were going to do as suggested, and change the port from the default 502 to another and back again but it is not offered as an option we can see for the server side, only client side. ie. device.ModbusTCP_Client.Port ( is offered ) device.ModbusTCP_Server ( no option for port ) Perhaps it is something I am missing or need to download an update. As always so very appreciative of your support that has been above and beyond!
  13. Ken

    Reset Modbus after cannot bind Socket

    Unfortunately, no we do not have a cause/affect here. Communications are running fine between the one system and DF and for some reason communications stop ( hours later ). If we have have DF in development mode we can see the error come up in the command window. I have been able to "re-create" the problem by: -Starting a Modbus communications setup -Once successful communications between the units is up and running. I type this into the command window device.ModbusTCP_Server.ConfigureComm() This provides us with the Ethernet popup. Once this appears you just hit save and do not change the port #. If you do that you will also get the error. Another way is to open a second instance of the same program. It appears to be coming from the third party program, but I would like to be able to ( if possible ) code something to "fix" the issue. Other information: The third part program continues to send.
  14. Condition: While using DaqFactory as a slave on modbus and this error occurs "Ethernet Server failure: Unable to bind listening socket." Background: We are able to run 2 instances of DaqFactory ( one as a slave and one as a master ) and have yet come across the error above. However, when we use DaqFactory as a slave connected to a "Third Party" Master, on occasion we get the above error. So far the only way we have found to have communications restored is to close DaqFactory and re-start it. We can catch the error using OnAlert, and as a temporary solution we stop all sequences, save the document and reboot the computer when we come across this error. Is there a way to correct this issue other than our current solution? I know when we have an issue with our serial communication and we catch it, a re-initialization of the port seems to work ( initcomm()) Thank you