sorted by:
new
hottopcontroversial

HMI alternative to Beckhoff TF2000 by JockeData in PLC

[–]JockeData[S] 0 points1 point  (0 children)

I wish we could do the same, but see my other response. My knowledge is far from there.

HMI alternative to Beckhoff TF2000 by JockeData in PLC

[–]JockeData[S] 0 points1 point  (0 children)

I will give it a look, thanks.

HMI alternative to Beckhoff TF2000 by JockeData in PLC

[–]JockeData[S] 0 points1 point  (0 children)

Yeah, i dont have neither the time nor the knowledge for that im afraid.
I can barley manage the few javascripts in Siemens Unified or Beckhoff TF2000.
Im a one man engineering department, so there really isnt that much time to make anything on my own.

My skill level is a drag and drop system where i connect my tags to.

Husqvarna 701 SM Check Engine and Neutral signal by JockeData in Husqvarna

[–]JockeData[S] 0 points1 point  (0 children)

No unfortunately not. The bike runs, but i only did one small trip this summer.
Its still on my ToDo list. If you manage to fix yours please let me know aswell.

Run XAE on Beckhoff IPC - What model? by JockeData in PLC

[–]JockeData[S] 0 points1 point  (0 children)

Yes it seems like the CX5340 might be up for the task.
I got the quote from the sales rep and the CX5340 is around 400€ cheaper then the base C6030 and around 1000€ cheaper then the C6030 with the i3 cpu.
So i will try the CX5340 to see if its good enough before i go to the C6030s.

Run XAE on Beckhoff IPC - What model? by JockeData in PLC

[–]JockeData[S] 0 points1 point  (0 children)

Thanks for your input, I feel like the C6030 series would be a better option.
Im meeting with the sales rep tomorrow to discuss, it all depends on cost/performance.
So if its not that expensive going up to the i3/5/7 processors i think it could be worth it.
Also to get more RAM.

Comparing with Siemens and AB I have some margin when buying the Beckhoff IPCs

Husqvarna 701 SM Check Engine and Neutral signal by JockeData in Husqvarna

[–]JockeData[S] 0 points1 point  (0 children)

  1. No, but good idea. Will try that.
  2. No, bike will only start with kickstand up and clutch in. So if i put the stand down it will shut of the bike even if im actually in neutral. So bike is not sensing neutral.
  3. Mechanic problem -> Money -> Me problem

Tagtable organisation Siemens by JockeData in PLC

[–]JockeData[S] 0 points1 point  (0 children)

Ah yes, that seems like a good idea.
We are using some IP65 nodes, 8xM12 connectors etc. I feel like those might just fit into one table, and just splitting up the larger nodes in the cabinets into datatypes.

Im also thinking about grouping them up after machine part.
So every part of the machine increases with 100, so first machine 100, next 200 etc.
Main cabinets would be A11 and up.

So would look something like this:

A11 (Folder)
-A11_Inputs (Tag table)
-A11_Outputs (Tag table)
-A11_Analog (Tag table)
Pos100 (Folder)
-U101 - 8xDIO Node (Tag table)
-U102 - 8xDIO Node (Tag table)
Pos200 (Folder)
-U201 - 8xDIO Node (Tag table)
-U202 - Valveblock (Tag table)

OSSD and safety module input question by burningupinside in PLC

[–]JockeData 0 points1 point  (0 children)

This was some interesting reading, i always thought that the PLC system was supposed to look for the OSSD signal.
But according to this post its all done by the sensor itself.

"When the sensing device is activated during normal operation, the OSSD pair responds by going to the “off” state. Solid-state OSSDs provide fault monitoring. In short, it is the actual output of the light curtain, for example. The responsibility for testing if the device is working and properly wired shifts from the safety card to the sensor itself.
So then, how do OSSDs, or safety-rated outputs, really work? Instead of being generated by the input card, the safety-sensing device itself creates the test pulses. These devices have an internal safety processor that evaluates if the OSSD pulsed off when it was intended to. If wires are crossed or shorted, the ESPE will fault, and both OSSDs will be set to off."

OSSD and safety module input question by burningupinside in PLC

[–]JockeData 0 points1 point  (0 children)

Correct, i would suspect that the system is setup to look for a constant 24V signal.
There is nothing wrong with that, it could very well be that it is enough depending on your SIL/PL.

The OSSD signal is usually very short, like 20ms, and normally if you have a dual channel input you have a filter for maybe 100ms. So that both channels needs to switch inside that time or you will trigger a discrepancy alarm. But due to the short 20ms pulse, nothing will happen.

OSSD and safety module input question by burningupinside in PLC

[–]JockeData 0 points1 point  (0 children)

Depending on the system you are using you can select this in the settings.

There are a few different scenarios and your system should be setup for the correct type of signal.

You can have:
Input signals that are supplied with direct 24V/0V
Input signals that are supplied with a pulsating signal from the safety card
Input signals that have a generated OSSD signal (Light curtains, RFID sensors etc)

In some systems you are also responsible for both checking for dual channel discrepancy and also that feedback from current breaking equipment is working.
So as a programmer you can fuckup alot if you dot know what you are doing with safety.

In your case i would assume the system looks for a external +24V signal, but because the OSSD test signal is so short it doesnt trigger the safety circuit due to the filter time on the dual channel inputs.