AzeoTech

Administrators
  • Content Count

    5,650
  • Joined

  • Last visited

Community Reputation

0 Neutral

2 Followers

About AzeoTech

  • Rank
    Guru

Recent Profile Visitors

50,252 profile views
  1. AzeoTech

    Modbus tcp and rtu master and slave

    You are talking about Modbus Master? Then yes, it doesn't matter. The ports are handled by the remote device. 192.168.0.1 port 502 and 192.168.0.1 port 503 are two completely different connection points so are no different than 192.168.0.1 port 502 and 192.168.0.56 port 502. To connect to a device you need the IP and the port. Any changes in either of these are a different connection, even though a change of port is still the same device. I like to think of it like a telephone to an office building. The IP address gets you to the main office line, and the port # is the extension. So calling the telephone number (IP address) gets you to the right building (device), but you also need to know the extension (port) of the person (protocol) you want to talk to. If your device has both 502 and 503 open and available to receive calls (sockets), then DAQFactory can certainly connect to both simultaneously using two different DAQFactory "ports" and "devices".
  2. AzeoTech

    "p-Modbustcp 0010: Timeout" Error

    OK, glad you sent it. You actually have two Ports in your application, even though presumably only one is assigned to a device. You have one called "Ethernet", and one called "TOUCHPRO". Both point to the same device, same place. This is apparently causing an issue, probably because DAQFactory tries to establish both connections simultaneously on startup and your device can't handle it, but if you disconnect and reconnect, DAQFactory staggers the reconnection. Or it just never reconnects the one that isn't used. Either way, if you delete the connection you aren't using, or at least set the IP to blank and the Port to 0, the probably will likely go away. On a side note, 200.200.200.190 is a routable address and so should not be used for internal networking. Use something in the 192.168.x.x, 10.x.x.x or 172.16-31.x.x subnets, as these ranges are non-routable addresses and won't be confused for Internet addresses by Windows. If you don't then when Windows (and thus DAQFactory) can't find the device at 200.200.200.190, it will go to your gateway router and then through it, up into the Internet looking for a device at 200.200.200.190, which appears to be somewhere in Brazil... If you actually meant to use a routable address, don't. There are huge security issues with placing an automation device directly on the Internet.
  3. AzeoTech

    "p-Modbustcp 0010: Timeout" Error

    Please post or email your .ctl doc so I can take a look. If its reading data on the one channel, then there must be some other connection inside your document.
  4. AzeoTech

    "p-Modbustcp 0010: Timeout" Error

    I meant more than one device / software connected to the remote device. Does it do it from a fresh boot? Does the Ethernet comms light light up when the ethernet is plugged in but DAQFactory won't communicate? Does your remote device use DHCP to get its IP address?
  5. Channels look just like variables with some exceptions. So, if you have a digital output channel called "LED", you could have a sequence like this: LED = 1 delay(5) LED = 0
  6. Alarms with expressions that are invalid won't trigger, nor will they generate an alert, so you should be fine.
  7. AzeoTech

    "p-Modbustcp 0010: Timeout" Error

    Are you sure you don't have another piece of software or another device communicating with device? Many devices support only one connection at a time. Disconnecting and reconnecting would drop an existing connection and give DAQFactory a chance to connect.
  8. To avoid bogging down your system by accidentally specifying a big array, DAQFactory will only display the first 20 values in any array. So if you do: myChannel instead of myChannel[0] you'll only get the first 20 values of myChannel, not the entire history, which would chew up a lot of CPU time to display, over and over again. So, you are running up against this. What you'll have to do is display two sets of 16: (To.Bit(x))[0][0,15] and (To.Bit(x))[0][16,31]
  9. AzeoTech

    "p-Modbustcp 0010: Timeout" Error

    First, does the error keep reappearing, or is it simply left over from when the cable was unplugged? Errors in the command/alert don't go away unless you explicitly clear the command/alert window by right clicking and selecting Clear.
  10. Yup, you can do a lot with Filter() and since it is internal, it is fast and DAQFactory can do it in real time. I like Search() too. Its a quick way to find certain things in your data.
  11. What you have won't work because of the way stream works. Stream sends data in blocks, and so it is hard to process every data point as it comes in. Also, your while() loop lacks a delay(), which will cause the CPU power to spike. You should pretty much always have a delay() inside a while() loop. There are exceptions, but this is a good general rule. Now to your question, it is probably easier to just use the filter() function on the whole incoming data. You can make a V channel that is a calculated v channel (meaning there is an Expression associated with it). That expression would be something like: filter(UE9_11, UE9_11 > var.kw1min) Then whenever you reference that V channel it will perform the filter, which will remove all values that don't match the criteria. Filter() is an internal function so is pretty darn fast.
  12. AzeoTech

    convert hex to decimal on temp sensor.

    Hex is just another form of a decimal number. 0x0f (hex) and 15 (decimal) are the same number. Those docs simply show 15 as 0x0f instead of 15. So it's not really a "hex" device, it just takes numbers. The hard part for this device is going to be the CRC. Its not particularly hard, but you are going to have to convert that sample CRC generation code into DAQFactory script. You might see if there is a way to disable the CRC on the device.
  13. AzeoTech

    Document Licensing

    Nope. That would defeat the purpose of the licensing mechanism. As the docs say: "Do not lose your password! We cannot recover it for you! If you lose the password you will not be able to use your application on systems that aren't otherwise licensed and you won't be able to install your application on any new computers. Once again, while we can recover document editing passwords for a fee and subject to proof that you created the document, we CANNOT recover the licensing password for you as there is no way for you to prove to us that you are the owner of the document other than knowing this password. That all said, we do offer a document registration service. You provide us with your document before you enable the license feature, or at least before you have forgotten the licensing password, along with the emails of people authorized to retrieve the password, and in the case of a lost password, we can retrieve it for these individuals or the president / owner of the company it is registered to. There is a fee for this service and for any password recovery. We have to have your document ahead of time to retrieve an internal unique identifier. This identifier stays with your document even after you edit it and is what gets registered with the recovery email addresses. Please contact us to set this up."
  14. I don't know. It works for me when I create a channel, then in Command / Alert do: ? format("%.6f", myChannel.time[0]) It prints something like: 1556486246.000109 The time is stored internally as a 64 bit floating point value, so you should be able to get 6 decimals places.
  15. AzeoTech

    DDE client crashing

    DDE is pretty ancient technology and not particularly well supported in Windows. I think we have a slightly more updated driver if you'd like to try it, but no guaranties. Please contact us directly for it.