Red Lion HMI and Toshiba PLC Help

well the +big means I did not make the format with enough space to show the whole number. That might be a clue. Apparently 16 bits is not enough to display the binary tags. Maybe a "Word as Word" and default integer from the Toshiba is 32 bits... Try doubling the size on the format tab of the display objects... Or dump my version r002 in there...32 bits and 8 digits for the hexadecimal views...

Also, tell us what the Toshiba is saying for those values.

As for picking a free address in the Toshiba...wish I could help, but my only Toshiba experience is with a 22" television.
 
Last edited:
Okay, I will try it out tomorrow as I'm no longer at work.

Haha alright. I will look into how to do it myself so we can still use it for testing.

Thank you for all of your help thus far!
 
Sorry it's taken me so long, but here is what the screen displays:

D0100: -12032
D0100 Hex: FFFF-D100
D0100 Binary: 1111-1111-1111-1111-1101-0001-0000-0000

D0101: 43
D0101 Hex: 0000-002B
D0101 Binary: 1111-1111-1111-1111-1101-0001-0000-0000

When hooking up to the Toshiba, the numbers I am seeing are as follows:

D0100: 5370
D0101: 479

I've also included this link which is a screenshot of what I am looking at, just in case I am reading the PLC's ladder logic incorrectly.

http://i.imgur.com/QZAu56a.png
 
Well, it looks like both binary readings are pointing to the same tag D0100. I am not seeing a correlation yet.

Let's try several combinations at once...

I added Long as Long versions of the tags, fixed the reference in the binary view and added one with the bits reversed for each tag (word as word).
 
Okay, here's what the HMI is displaying:

D0100 Word as Word: -788529093
D0100 Hex: D100-003B
D0100 Binary: 1101-0001-0000-0000-0000-0000-0011-1011
D0100 Long as Long: -788529093
D0100 Invert Bits: 788529092

D0101 Word as Word: 3866634
D0101 Hex: 003B-000A
D0101 Binary: 0000-0000-0011-1011-0000-0000-0000-1010
D0101 Long as Long: 3866634
D0101 Invert Bits: -3866635

I just noticed though that the ones that were supposed to be Word as Word are actually Long as Long, so changed that and here are the new values the HMI displays.

D0100 Word as Word: -12032
D0100 Hex: FFFF-D100
D0100 Binary: 1111-1111-1111-1111-1101-0001-0000-0000
D0100 Long as Long: -788529093
D0100 Invert Bits: -53505

D0101 Word as Word: 43
D0101 Hex: 0000-002B
D0101 Binary: 0000-0000-0000-0000-0000-0000-0010-1011
D0101 Long as Long: 3866634
D0101 Invert Bits: -44

The changes I made was simply changing data tags D0100, D0100_1, D0101, and D0101_1 to be Word as Word.
 
Have you gotten Red Lion on the phone yet? Or use their online help system?

I thought we'd find a simple byte swap thing here, but it is not looking like that's the case.

I am not understanding why a "word as word" returns 32 bits with the uppermost 16 of them set. That is why I thought maybe we need to read them as Longs. And ... these values in your last post are nothing at all like they were before even on the base tag that is still set word as word...

:confused:
 
Yes I have, I am constantly working with them as well, but the best they've been able to come up with is to try to get some sort of register data mapout for the PLC, but Toshiba doesn't seem to have anything like that.

And ... these values in your last post are nothing at all like they were before even on the base tag that is still set word as word...

Do you mean the first set or second set of values from my last post? The first set can be ignored. I thought the second set was similar to what they were before.
 
I don't know how to view and edit data in Toshiba software, but I would suggest finding an unused data register that you can manipulate with their software. Then you can put a known value in that register and it won't bounce or move when you view it with the red lion. I think that might help us out. Starting out with numbers like zero and one should simplify things...key word *should*...
 
Last edited:
Maybe. Like most of Red Lions tech notes, it's sparse. I think something might be broken in the driver. we specifically ask for "word as word" and get back 32 bits of data when we should only get 16.

You need to come up with a group of addresses that are not changing that we can read and then display for comparison.

Do you have links to the Toshiba manuals?
 
Hmm okay.

Yes, I've attached the manual for the PLC itself here. I've also got a manual for the software/programming of the PLC, but I can't find it online, so I would have to upload it somewhere (even in a .zip file it is too large to send on this forum).

Edit: I found a way to upload the second .pdf, so here is the manual for the software/programming of the PLC.
 
Last edited:
I learned how to add a register to the PLC, and set its value to 1, and then after changing up the crimson program you sent me a bit, I was able to collect the following data:

D0200 = 1

Long as Long
D0200: -771751893
Hex: D200-002B
Binary: 1101-0010-0000-0000-0000-0000-0010-1011
Invert Bits: 771751892

Word as Word:
D0200: -11776
Hex: FFFF-D200
Binary: 1111-1111-1111-1111-1101-0010-0000-0000
Invert Bits: -53761

Real as Real / Word as Real:
D0200: 2871808
Hex: 002B-D200
Binary: 0000-0000-0010-1011-1101-0010-0000-0000
Invert Bits: -2871809

The address I used (in the PLC programming) is D0200, and I started out with the value set to 1. After getting this data, I changed the value to 2, 0, 3000, 459, and no matter what value I gave it, the numbers the HMI displayed were always the same. I've also been noticing that in the Hex format, it will always contain the name of the address (in this case D200, which I think is the same as D0200, because the 0 is ignored, as well as in past cases when I was dealing with D0100 and D0101). I'm guessing that this means the HMI is simply displaying the address as the value, instead of actually showing the value at the address.

What do you think?
 
I think there is something fishy going on with the driver. I think Red Lion needs a copy of this thread, your database and perhaps a PLC of the same make and model you are using so they can find and fix a problem which is likely on their end.
 
Hmm okay. I've told the tech I'm dealing with at red lion exactly what I just told you, and they seem to think that I "may need to adjust manipulation or digits before and after the decimal." But I don't see how that would possibly change anything when the displayed numbers haven't been different when the PLC's value was changed. Do you think this could help?
 
No, not really. Especailly since you are not even using the tags as floats.

Red Lion tech support has always been very good to me, and I am not quick to blame them for a problem, but this time I think it is on their end.

Toshiba PLCs are not common as far as I know and you may be the first person to try this particular combination of hardware and software.
 

Similar Topics

I am having issues getting a Red Lion HMI and Micro830 controller to communicate. I am using the cable here to connect the controller to the RS232...
Replies
0
Views
119
Hi I need to send a null command down a comms port. But in the crimson software when i used /x00 it coming back "Cannot use null character is...
Replies
2
Views
423
Hi Everyone, I am hoping a Red Lion Expert can point me in the right direction. I am experimenting with data logging on a CR3000 10" screen...
Replies
4
Views
605
I have a Red Lion G09 scanning 8 Invertek P2 VFDs via modbus RTU - I've setup necessary comms and tags and all works well. I have a 'Settings'...
Replies
3
Views
1,878
Has anyone ever replaced a touch screen on a legacy Red Lion G3 series HMI?
Replies
12
Views
1,458
Back
Top Bottom