1747-NC13
This is a basic straight through cables. Pin 1 to 1 etc.
This cable is male to female.
| Male Head | Female Head |
|---|---|
| 1 | 1 |
| 2 | 2 |
| 3 | 3 |
| 4 | 4 |
| 5 | 5 |
| 6 | 6 |
| 7 | 7 |
| 8 | 8 |
| NC | NC |
In this cable pin is not connected.
Example uses:
- Linking TD36 to KE cards
This is a basic straight through cables. Pin 1 to 1 etc.
This cable is male to female.
| Male Head | Female Head |
|---|---|
| 1 | 1 |
| 2 | 2 |
| 3 | 3 |
| 4 | 4 |
| 5 | 5 |
| 6 | 6 |
| 7 | 7 |
| 8 | 8 |
| NC | NC |
In this cable pin is not connected.
Example uses:
Please note this does not apply to the newer QxUD range, as it isn’t required.
MOBC is multiple block online change. When you are doing a online program change MBOC will allow for larger change to be done, or more smaller changes, without needing to redownload the PLC code. The MBOC reveres a sections of space at the end of program, which is shuffles me code into.
This is done by (noting that the below complete wipe all program, variable and parameters).
To check if a PLC has had the MBOC set up, you need to go
So the hardware works by having the echo high for the time it take for the pulse to return. The software blip the trigpulse on, and then time the duration of the echo pulse. Then a bit a maths is done and the function returns a distance in cm.
So you need the following hardware:
Noting that mine had 1 pin for pulse, and 1 pulse for distance.
So the ultrasonic sensor has 4 pins, (or at least the version I’ve got does)
Connect VCC to VCC
Connect GND to GND
Connect Trig to the pin you code has for pulse_req_pin
Connect Echo to pulse_return_pin
long measure_distance(int pulse_req_pin, int pulse_return_pin)
{ //based upon https://www.arduino.cc/en/Tutorial/Ping?from=Tutorial.UltrasoundSensor
// establish variables for duration of the ping,
// and the distance result in inches and centimeters:
long duration, cm;
// The PING))) is triggered by a HIGH pulse of 2 or more microseconds.
// Give a short LOW pulse beforehand to ensure a clean HIGH pulse:
pinMode(pulse_req_pin, OUTPUT);
digitalWrite(pulse_req_pin, LOW);
delayMicroseconds(2);
digitalWrite(pulse_req_pin, HIGH);
delayMicroseconds(5);
digitalWrite(pulse_req_pin, LOW);
//HIGH pulse whose duration is the time (in microseconds) from the sending
// of the ping to the reception of its echo off of an object.
pinMode(pulse_return_pin, INPUT);
duration = pulseIn(pulse_return_pin, HIGH);
// convert the time into a distance
// The speed of sound is 340 m/s or 29 microseconds per centimeter.
// The ping travels out and back, so to find the distance of the
// object we take half of the distance travelled.
cm = duration / 29 / 2;
return(cm);
//Serial.print(cm);
//Serial.print("cm");
//Serial.println();
}
I haven’t tried this a module yet, but it works as a function.
Firstly you need the following equipment:
To upload from the HMI, you need to know the password, and follow these steps:
The card needs to be formatted to FAT16
Let start with the basic, Eye-fi can’t use a FTP, on a local private network, or any other method due to requirement of the files being send to their server first and then being send to that FTP. This was a fail in my attempt to get this working.
So, using the following website, and some brain power:
The following are to be done on a Windows 7 Machine
C:\Users\User_Name\AppData\Roaming\Eye-Fi\Settings.xml
So once the above is done, the following needs to be done on the PI
.
|-- etc
| |-- eyefiserver.conf
| `-- init.d
| `-- eyefiserver
|-- usr
| `-- local
| `-- bin
| `-- eyefiserver.py
`-- var
`-- log
`-- eyefiserver.log
e.g.
sudo cp /home/pi/etc/eyefiserver.conf /etc/
sudo cp /home/pi/etc/init.d/eyefiserver.conf /etc/init.d/
etc
sudo chmod a+x /usr/local/bin/eyefiserver.py
sudo chmod a+x /etc/init.d/eyefiserver – just in case (I did this first so was unable to test just the py mode)
sudo update-rc.d eyefisever 98 02
Possible issue – if you have enabled pass through on your PI to your wider network (i.e. Windows machine) then the photos might end up on the Windows PC instead of the PI, there no logic to where it save to (as far as I can see).
To create and insert a graph into WordPress from Google docs, the following steps need to be done:
I would like to know why the interactive graph doesn’t work, but this does the job.
During this guide I will be using the phrase ‘host machine’ to define the actual computer operating system, and ‘virtual machine’ to define the virtual computer.
On Virtual Box this is achieve by the following steps:
Now the device should be usable for virtual machine.
Below is only one possible method, and there are many more.
This requires the following to be able to find it
So to do this
You must be logged in to post a comment.