Hi everybody,I have a problem with the FSKEY board of FSBUS. I think once again it's the beta software to blame, but I want to be sure. Using latest Beta of FSBUS2.I'm using normal GreyCode Rotary Encoders along with the REDEC circuit.In the FSBUS documentation it states that you can define one (1) or more Rotary 2 inputs per row and that the row(s) using this kind of input (Rotary2) cannot be used with anything else. Fine and logic.The problem that I have is that while the first Rotary2 functions perfectly, any subsequent is not recognized nor functions properly.Here are the details.Rotary2 CID x, ROW 2, SubID 0. Connected to connections 0 & 1. Works fine.Rotary2 CID x, ROW 2, SubID 1 (?). Connected to connections 2 & 3. Only the down function works. Up function ignored.If I more the 2nd rotary to another ROW Sub 0 (i.e. ROW 1, Sub 0) it will work fine.I think the mistake is that the Router recognizes the 2nd Rotary2 to SubID 1 while it should be SubID 2?? If I change manually the SubID to 2, the 2nd Rotary is not functioning at all.As I understand each Rotary2 input occupies 2Bits.So, it's either the Router or the Flashed software into the PIC.Anyone else observed this?I'm loosing tons of connections this way and I will need 5x the KEY card I would need otherwise!Thanks!George DorkofikisAthens, Greece

We are seeing the same here. Looks like a software bug.Tuomas

This is known problem from older FSBus versions. I notified Dirk about this earlier this year but it is not fixed yet.I use different solutions. I attached all ALPS, knitter style rotaries, to first two connectors on every row. Rest 6 is used for normal buttons and so on.I know, documentation says that this won't work. But it does...- J

Hmmm...How have you declared them? Tried to declare switches to the rest of the connections in a Rotary2 row, but they didn't work.I hope it's fixed soon, otherwise I will need much more key than normal which will increase the cost. PICs are bit expensive here.George DorkofikisAthens, Greece

>Hmmm...>>How have you declared them? Tried to declare switches to the>rest of the connections in a Rotary2 row, but they didn't>work.>>I hope it's fixed soon, otherwise I will need much more key>than normal which will increase the cost. PICs are bit>expensive here.>>George Dorkofikis>Athens, GreeceYou can always use FSBUS software v1.3 for now - it is harder to configure, but doesnt have much bugs.Tuomas

By that you mean that this is a Ver2 problem that did not occur on 1.3?So I can have multiple up/dn switches (as named in v1.3) in the same row without problems?I'll give it a try.Thanks.George DorkofikisAthens, GreecePS. And I just LOVE the easy configuration of V2... :-)

>By that you mean that this is a Ver2 problem that did not>occur on 1.3?>So I can have multiple up/dn switches (as named in v1.3) in>the same row without problems?>Not sure about that. But V2 has many new bugs that are not present in 1.3, because in 1.3 everything is much more simple from the programmers perspective as the hard work is left to the user.Of course it is also good to *test* and use V2 since that's the only way to give Dirk important bug reports. And please let him know of the bugs - otherwise they will never get fixed :)Tuomas

Just put ALPS to positions 0 and 1. Buttons to rest of them. Got FSBUS2b2 and autoconfigured them. Works fine...I didn't do anything special with them.- J