Jump to content

tonto

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About tonto

  • Rank
    Newbie
  1. We have an application that requires frequent (1 to 4 times a second) logging of time, target, and actual value. Is there any difference in speed of writing to a data table compared to writing to MIs? I am wondering which is the best way to perform the write tasks to the data table, either: 1. Every time we receive a new actual value (which happens 1 to 4 times a second) we write the current RTC, target and actual value into the table, or 2. Store the sequence of values into MIs and then once we have say 10 then write all of them into the data table instead. Furthermore, we'll eventually be needing to get this data out into a PC over ethernet (within a minute of it being recorded), probably with a c# program; is there any significant difference between pulling the information out of data tables vs a sequence of MIs?
  2. Wonderfully, you need to repeat it every time. Still haven't quite nailed configuring the TPDOs and RPDOs but think I'm getting there.
  3. Turns out the eNod3 manual failed to mention that you needed to set the heartbeat producer value before it would move into pre-op after bootup.
  4. Thanks for the reply. I have set the baud rate at 500k and the ID of the PLC to 1 and the device to 2. I have configured the CANopen FBs as indicated in attached image. I have reviewed the included examples and it seems that NMT status should be automatically transmitted from any CAN node. My NMT receive bit will never change. The eNod device is supposed to go from boot to pre-op automatically. Is it therefore correct to assume that either the eNod device is faulty? Or have I just mis-configured the PLC?
  5. Hey there, I have a vision V290 and a Scaime eNod3-C A/D loadcell device and am having serious issues getting the two to talk to each other. I've done a whole lot of searching, read these and the old forums (thanks to the users who posted CANopen info there too by the way, it has been enlightening), read the help files and documentation and contacted Scaime's distributors all to not a whole lot of avail. It's kinda funny they use Unitronics and themselves in their application examples and advertising media then don't provide support between the two. Teaches me for assuming things again. Anyway, if someone were able to help me out with a couple of questions here I'm sure I can get the rest of the way on my own. First of all, the eNod3 comes with configuration software but all that you can change with regard to the CANopen protocol is the ID and the baudrate and it must be done with a PC through the serial port. Secondly I don't have a sniffer (and one doesn't seem to be included with v290 OS) or software like CANmagic but I do have a scope. So first question is if I do the CANopen configuration net as shown in the numerous examples and help files (set PLC ID, initialise com port to CANopen, and configure the node info on the PLC side) then is it correct to assume that provided the node ID and the node ID set in the PLC match (and baud rate) I should be able to read the NMT or error statuses from the eNod device in the PLC operands without any extra ladder code? If not, what are the most absolute basic blocks required to be able to confirm that the PLC and the node are in fact communicating? Using the check comms tool in visilogic only works for the PLC too. I know for sure that both are sending signals down the CANBus line thanks to the scope, but whichever way I look at it I can't match the bit pattern to fit into any sensible frame. All the NMT status and error operands stay at 0 unless I reverse the wiring on one end and then the manufacturer specific bytes return the code for 'no error' but everything else stays blank. I've been stuck on this for a while and am at the point now where I'm looking at sacrificing speed and going down the MODBus route since I know that works. I have attached the EDS file in case someone with a whole lot more nouse can see something glaring obvious I've missed. If anyone is able to help I will be eternally grateful. All I am trying to do at this stage is confirm there is a communications link between the two devices. 403-en-eNod3-C_EDS_165718-I.zip
×
×
  • Create New...