LOL. Zilog z80 (8080+, IIRC) and 8085 early experiences here.
I still have that Heathkit H-8--soldered together by my father and I. Reviving it is on my bucket list. /:
LOL. Zilog z80 (8080+, IIRC) and 8085 early experiences here.
Meh, I don't think that is much more dangerous than any other online edits.My wild guess is that it's even more complex than that. In single rung mode, the PLC can assemble/test the logic while the routine isn't being scanned.
But with AOIs scattered everywhere throughout the code, when can that happen? How do you ensure that the scan isn't in the middle of an AOI call when it's paused, so that you aren't effectively causing BOTH pre- and post edits to solve, creating wild results that could break the machine?
Yeah I was told similar, bumped form January time frame to April-June timeframe. No official slides on what's new yet.Local distributor says release is around August 2022.
What they said so far. There's some other bits and pieces of bug fixes in the knowledgebase if you search for v34 there.Yeah I was told similar, bumped form January time frame to April-June timeframe. No official slides on what's new yet.
The PanelView 5000s are becoming more interesting. Not sure what is meant by the EN4TR.
- PanelView 5000’s will support Web Browser via HTML5 webpages and IP cameras with V8 of View Designer (View Designer is part of Studio 5000)
- Possible HART device configuration directly from Studio 5000
- No Windows 7 and 32-bit OS support (same with FactoryTalk View, AssetCentre, Historian latest releases)
- 1756-EN4TR support in main chassis
Not sure what is meant by the EN4TR.
As for the EN4TR, currently it cannot reside in the same chassis as a 1756-L8xE processor.
The “support in main chassis” is what I meant.
Got a reply:
There may be a corner case or something, then. Perhaps it's outdated information.
I've yet to use an EN4TR and L8x together.
I’m eagerly awaiting any new feature news or release notes. I’m going to email our distributor for anything they might know.
From a programming POV:
- I cautiously welcome more object-oriented features. It demands more programmer responsibility, but so be it.
- I want to be able to write actual functions and not AOIs masquerading as them.
- Function overloading. I don’t want an AOI for a DINT array, INT array, and so on.
- Support for adding more routines than prescan/postscan/enableinfalse to AOIs. This ought to be easy.