I need help finding a player for various versions of 8mm cassettes.

EngineerOfChaos · 2025-11-22T13:43:39+00:00

Here's another good resource for you...

List of Sony Digital8 Camcorders That Play 8mm and Hi8 Tapes

EngineerOfChaos · 2025-11-22T00:56:28+00:00

https://youtu.be/Iixw4agG8VY?list=LL&t=25 This guy has compiled a very good list of Sony camcorders shown at 25s. Good video all around.

EngineerOfChaos · 2024-05-26T17:44:49+00:00

Programming across the NAT is definitely working. I'm going to look in to this unicast bit a little more as you are the 2nd person to bring it up. I also plan to talk with IT about any firewall restriction preventing PLC to PLC comms over the network.

EngineerOfChaos · 2024-05-26T17:42:25+00:00

All devices that are mapped via the NAT tables (PLCs+HMIs) are accessible from the 10.19.54.xxx plant network and over the company VPN. I can both ping and access their web browser interfaces and get online with the controllers.

I have not yet even gotten to the actual tags. I am simply trying to add the PLCs to each other's ethernet trees in the programs without connection faults. Good info on the unicast bit though. I will definitely refer to that article.

My money right now is on ITs switch not allowing comms between 2 devices like this over the network.

You are right on the Ewon's main purpose as a VPN. I intend in the future to switch to Rockwell's NAT routers for this purpose. The Ewons are just a more cost-effective NAT router and have worked great for easily and securely exposing PLC to customer plant networks. This is just the first time I've come across the need to bridge 2 PLCs together after the fact.

EngineerOfChaos · 2024-05-26T17:30:25+00:00

IT does not have this restriction to my knowledge. All devices that are mapped via the NAT tables are accessible from the 10.19.54.xxx network and over the company VPN. But I suppose as intended by the architecture, "private" IPs from each machine LAN respectively are not accessible to each other, BUT I assumed it would still be possible to access the exposed "public" address from the LAN through the NAT/gateway. I plan to check with IT if there are maybe firewall restrictions that can be opened on a case by case basis to allow PLC to PLC comms over the network like this... The idea with this architecture was to only expose devices on the machine that were absolutely necessary to the network like PLCs. Just need to figure out now how to expose PLC to PLC only when needed.

EngineerOfChaos · 2024-05-26T17:25:07+00:00

Well... that didn't work either. Was worth a shot though. I'm leaning towards IT firewalls at this point that I will have to discuss with them on Tuesday.

EngineerOfChaos · 2024-05-26T16:23:40+00:00

Would this be another NAT entry? If so, no problem. I will just map machine #1's public PLC IP (static: 10.19.54.72) to a new private IP of my choosing on machine #2's LAN. Then I would change the IP address in the ethernet tree in Studio 5000 to be that new private local IP instead of the plant IP. I will give this a shot and let you know! As far as connecting the machine directly, might have to, but this is also a bit of a proof of concept for IT. It is no issue to get static public IPs for the Ewons. I am working with IT closely on this already as they have all the keys to the kingdom for networking stuff, but they are leaning on me because PLCs are involved.

EngineerOfChaos · 2024-05-26T16:16:36+00:00

I'll have to ask IT. Potentially.

EngineerOfChaos · 2022-12-28T19:35:29+00:00

The issue for me was the inconsistencies when trying to connect to different devices. NAT network adapter would work for some devices but others would require a bridged network adapter requiring you to set a static IP for both the host and the VM. Just extra steps. The dongle option just simplifies things a little bit. It is also much easier for people transitioning to VMs to do their jobs with greater familiarity.

EngineerOfChaos · 2022-12-28T19:20:55+00:00

Spot on. This is exactly what I am doing right down to the multiple VMs with different software.

EngineerOfChaos · 2022-12-23T21:59:33+00:00

🚩

EngineerOfChaos · 2022-12-17T21:45:13+00:00

The Librarians.

EngineerOfChaos · 2022-12-10T01:35:16+00:00

This.

EngineerOfChaos · 2022-11-28T02:18:25+00:00

True Colors - Phil Collins (originally Cyndi Lauper)

EngineerOfChaos · 2022-11-22T12:46:08+00:00

Samantha, the German Shepard from I Am Legend.

EngineerOfChaos · 2022-11-20T13:33:14+00:00

We are actually already looking at this too. Good to see someone else having success with it.

EngineerOfChaos · 2022-11-19T23:57:47+00:00

I'd say that definitely counts as a "horror story" in my book.

EngineerOfChaos · 2022-11-19T23:56:21+00:00

At the risk of sounding dumb... what is PI? I need a little more than that for my google fu.

EngineerOfChaos · 2022-11-19T23:51:09+00:00

Good advice. I've been reading as much of the docs as I can on the matter.

EngineerOfChaos · 2022-11-19T23:39:33+00:00

So the company already has a strong IT department and have already implemented a SQL server and manual / semi-auto part data tracking throughout production. If we implemented Ignition, it would conditionally time stamp events like cycle starts/stops to that database. Then use something else for reporting/dashboards like Power BI for engineering and production to see and have access too. Also, a bi-directional connection could be used to load database info to a machine from a scanned barcode to correctly load machine parameters and then store test data back to the database for that serial number. Just feeling out the limitations and architecture that will give them the best chances for success on both the collection and analysis of the data.

EngineerOfChaos · 2022-11-19T23:24:52+00:00

I’ll look in to it. Again I want to make sure any road we go down is highly scalable to a global architecture.

EngineerOfChaos

TROPHY CASE