cjbassman2

Members
  • Content Count

    20
  • Joined

  • Last visited

Community Reputation

0 Neutral

About cjbassman2

  • Rank
    Member
  1. cjbassman2

    DAQ crashing/closing down

    Thanks for your quick response. This has generally been running as a runtime without problem on another PC in the factory. I'm now adding some more stuff. My development computer died and I've replaced it but I can't see how that is related. I'll email you the file and try out some of the samples. TBH it seems so random. It's been working OK for a couple of hours now but keeled over in a matter of minutes a few times before that. What's the best email address?
  2. cjbassman2

    DAQ crashing/closing down

    I'm working on a DAQ application with a pro dongle license. The problem I'm having is that DAQ just closes every few minutes or maybe up to half an hour or so. There are no messages, or prompts to save work (which is annoying as I keep losing work). I've tried moving the dongle to different USB ports to no avail. Would you have any suggestions what it might be/what I should look for. I've seen some posts mention memory leaks but I've watched the memory in task manager and everything looks stable. I've attached my application for your reference. ESG4.rar
  3. cjbassman2

    Touchscreen buttons

    Thanks for your advice. I'll have a play around with those points.
  4. cjbassman2

    Touchscreen buttons

    I've developed an application to work on a touchscreen. It works fine and when using a mouse the buttons depress up/down when they are 'clicked' ok. However when the operation is performed with a finger on the touchscreen the buttons don't generally go up/down. I've seen them move occassionally but generally they don't move. The button functions perfectly but it would be nice for the operators to get then response from the buttons. Any ideas?
  5. cjbassman2

    DAQ 18.1 licensing

    Thanks. The two workarounds have now solved my problem.
  6. cjbassman2

    DAQ 18.1 licensing

    Do the problems you describe explain why whenever DAQFactory starts up on this PC it thinks there are two versions of it running (although there isn't)? It also seems to always start up in development mode despite me entering the runtime license info. As this is now on the shop floor I only want it to start up in runtime. Is there no work round? I'm happy to run version 17.1 but as I developed the app in 18.1 it won't run in 17.1. Could I install 17.1 on my development PC along with 18.1 and copy and paste everything over to make a 17.1 operable version of my app?
  7. cjbassman2

    DAQ 18.1 licensing

    Hi, I've developed an application in version 18.1 before it went to beta because of the issues. I now need to roll it out to the factory. It won't run under version 17.1 and I have issues with development and runtime licenses on the factory PC. It seems to always start up in development despite me entering the runtime license code. It also says I'm running two versions of DAQ which I'm not. I've tried uninstalling and re-installing but it doesn't fix it. Can the application be tweaked to work with version 17.1 as I'm not using any new features? Alternatively can the install be forced to run only one instance and as a runtime only version? Thanks in advance
  8. I am developing a HMI interface where there will be two or three HMIs talking to the PLC. The problem I have is I can't seem to fully initialise the knob components. If the PLC is running the line and the HMI is powered up I need it to pick up the comveyor speeds and initialise the speed adjustment knobs without affecting the PLC. When I fire up the HMI it does seem to initialse OK when looking at the variables in the watch window. However when I switch to the page with the knobs on it resets to zero and writes it to the PLC. Can you advise how I can solve this please? I've included a screen shot of the initial page and the variables in the watch window and everything is stable. I've then also included a screen shot of what happens when I switch to the page with the knobs on. knob_initialisation.zip
  9. That makes sense. Many thanks.
  10. Hi, I've found that when a component is part of a group the component name becomes invisible to references in my sequences. Is this a bug or just something I need to live with? Thanks Colin
  11. cjbassman2

    Initializing Knob component

    I am developing a HMI interface where there will be two or three HMIs talking to the PLC. The problem I have is I can't seem to fully initialise the knob components. If the PLC is running the line and the HMI is powered up I need it to pick up the comveyor speeds and initialise the speed adjustment knobs without affecting the PLC. When I fire up the HMI it does seem to initialse OK when looking at the variables in the watch window. However when I switch to the page with the knobs on it resets to zero and writes it to the PLC. Can you advise how I can solve this please? I've included a screen shot of the initial page and the variables in the watch window and everything is stable. I've then also included a screen shot of what happens when I switch to the page with the knobs on. knob_initialisation.zip
  12. cjbassman2

    Justifying variables

    Thanks, that does work. It seems to also change default colours and draw order on screen but I'll work around that.
  13. If there a way to right justify variables on screen? By default they left justify. I'm trying to align numbers so the least significant digit is always in the same position.
  14. cjbassman2

    PC spec

    Thanks that does help. I'm not doing any trending, graphing or indeed maintaining any historical data, it is just displaying current status. It's unlikely to be doing any control as that will be left to the PLC. It will be the operator interface for them to interact with the PLC. The main thing is it will be fetching about 600 MW of data about once per second via Modbus TCP to display on the screen. It will be a 100MBit network. From what you've written I reckon the Atom will be up for the job. Many thanks for your advice.
  15. cjbassman2

    PC spec

    Hi, I'm just starting to develop HMIs for our next lot of factory automation. I imagine there will be around 10-12 screens of 1920 x 1024 resolution with a lot of Modbus TCP coms going on between HMI and PLC. I would like some guidance of whether a PC with an Atom E3845 and 4GB ram would be sufficient or whether an i7 would be necessary. The Atom is preferable as it's cheaper and probably will be cooler running in its enclosure but no good if it would be struggling. Any advice appreciated.