OkiePC
Lifetime Supporting Member
Crimson is safe, easy to get off the web. Fits on a 256 megabyte thumbdrive.
That would be cool. I'd have to get him to drop off the software too, on disc, outside of the compound. Hand it all over to IT/Security and wait. I don't know. Might be possible.
Just the hardware. I.T. don't care about no "panel meter salesman".
Yes, and you can even make your own eds file so it does not look like a yellow question mark. You don't need it to show up in RSLinx. RSLinx doesn't need to be involved. You will use a PC to transfer your files to it. The method depends on the model.Going back to the original post a little bit and on the DH485 thing. If you can get a redlion to talk to SLC500s via DH485, does that mean the redlion HMI will show up in Rslinx???
I'm sure someone has tried this already and knows.
Can you dry run the redlions and test the screens without having them wired up to and accessing the PLC? I know with the older Panelviews and panelbuilder32, unless you have it hooked up to the PLC, accessing that node and addresses within the tag editor, you end up with a node error pop up on the screen that will not go away making it very difficult (impossible) to just test out your screens to make sure they flow correctly.
I've had a couple of instances where I've downloaded an HMI revision to only find out later that the operator was stuck in a new screen I made with no escape. I swore I but a previous screen button on there! Honest!
I have a conversion method like so:
1) clean up the tags in PB32 first. I am anal about comments and address formatting. Don't be havin' no b3/382 and B3:10/6 in the same table! All the PLC comments and the HMI comments must match.
2) export the PB32 in SLC format (assuming RSLogix500 target PLC(s) )
3) get the sample file I have in the download section that has all the SLC status messages done for you and start with it. (another ASSumption about the target). Convert it to your size screen. If using a Micrologix, some of the status messages may be inaccurate, but the bulk will be there, along with an alarm banner and a screen that shows slot by slot status. You can pick it apart, massage it, delete at will to fit it to your platform.
3) import the tags into Crimson 3.0
4) By importing GOOD tags with GOOD comments, you will have to do little to them in Crimson. Crimson is a whole nuther animal. It is free, installs in seconds and works very very well. It is not perfect, but it is different. Fix your tags in Crimson before you build screens. Pick scaling, colors, formats, labels and units. Then when you drop them on your pages, they will look great already, and if they don't you can alter the appearance with a few clicks. You can rename tags at will and nothing bad will happen. Do not use the underscore followed by a number to end a tag (don't ask me how I learned).
5) run the apps (PB32 and Crimson) side by side and build new screens. You can run multiple instances of Crimson side by side to drag and drop pieces into place.
6) learn about widgets and then teach me
Last edited:
Thumbing through manuals and spec sheets on both the RL line and PV+ line, I'm having a difficult time trying to find a RL HMI equivalent that will fit in my existing PV600 standard location with little modification. I have indicator lights and switches already installed above and below the pre-existing PV600 in the control cabinet. I'm limited on space. The hole cut-out for the PV standard seems huge compared to the RL options. I'd have to go up to like a 10" screen to fit the hole that is already there Then that would offset the price and make the RL HMI a more expensive option than say a PV+700 which is suppose to drop right in. Also, the PV+600 will go in with a special bracket. It will be hard pressed to convince the people with the money to buy into non-Allen Bradley HMIs if they don't see any kind of savings or significant benefit in user operation. They don't really care about how it gets wired in, or how its programmed. 
