Increase In Wireless Issues

[petrolhead]

With what? White noise? Carrier only? Sinusoidal tone? I'm going to try this on an enforcer.

[cybergibbons]

Most of the systems use 2-FSK, so pick a signal that approximately matched the bit-rate of that and toggle between the two.

 

So you end up with:

• FSK signal modulated at 9600Hz or something - this interferes with the signal itself
• Switch that on and off at 0.05s (i.e. 20Hz) - this stops the jamming detection being triggered, but is often enough to interfere. Might have to up the frequency a bit here for some systems.

The problem is that with the 2-way RF gear, they have two types of jamming detection:

1. Signal strength or RSSI based - this is what the standard describes and is all that 1-way can do.

2. Pings - send a message to detector, if it doesn't come back, get worried.

 

The Enforcer will almost certainly do both.

 

There's loads of interesting stuff you can do with jamming, but probably not for discussion in public.

[The Arab]

Here's a copy of a bulletin I got in June hope it helps someone

 

To highlight reports from the field, of “RF Jamming” and still slow responses from the DO8M on the G2 panel with the new RF portal sw version 3.00

 

Issue:

 

This is similar to an earlier issue on the RF portal whereby an issue which can occur as a result of the RF Portal acknowledging the DO8M transmission.

Delays of up to three seconds can be experienced between the DO8M activation and the RF portal processing the signal.

 

In addition to this “RF Jamming” now appears once the portal has been installed.

 

The issue lies with the RF portal V3.00 only.

 

Solution:

 

The RF portals can be upgraded in the field using the flash programmer (A221) and the associated sw file. 

[GalaxyGuy]

What is the new version for the V3.00 based module ?   Pretty peeved at Honeywell support, as they did not provide this to me as part of my investigations into RF issues. They only updated on the other two F135 firmwares. Very poor comm's.  I also think that the panel firmwares need to at least be adjustable on the 31 second front, otherwise there is no last resort...

 

Just to clarify that there are now three versions of the G2/Flex/Dimension portal available (as far as compatible firmware goes that is):

 

1. The original C079 which can have rotary address dial or fixed jumpers: V1.08

2. The Rev F2 C079 portal which has pcb trace aerial: V2.11

3. The latest Rev A2 C079 portal with optional Russian frequency and test mode for visual (LED) signal strength: V3.0X

 

-- For those who have purchased one of my G2 USB leads - As well as programming the G2, this lead can be used to flash upgrade the RF modules.

 

I am also releasing an updated firmware for the LCE-01 Ethernet module to resolve a (very intermittent) protocol issue when the virtualkeypad is used alongside the RF portal. The LCE is  V2.20

 

Dimension Firmware is at: V6.92 (enables outputs on apps)  (although 520 and 264 cannot be used with the app until a new app release is available - Ethernet modules drop offline with the current app)

G2 Firmware: V1.56

Galaxy G3: V5.55

E080-2 Ethernet: V2.11

E080-4 Ethernet: V3.05

Flex V3:  V3.18

IB-Ethernet (Flex V3): V1.02

Edited November 15, 2015 by GalaxyGuy

[marx]

I have installed flex20 3weeks ago and after day2 have a loads of rf100 jam's. Something is jamming portal, moved to to different location and its just same. Problem is that site is in other country. is there any way i can sort that firmware problem over network? i have gx remote control access to site. Or i can send them new portal with new firmware and return that for warranty? flex20 is 3.18, portal is V 3.00. i have another site with G3 v6.84 and portal v2.11 and working very well, no problems at all.

 

thnx

 

M

Edited November 27, 2015 by marx

[marx]

reading some older posts, looks like other people had problems when fitted portal and rio on flex. and thinking back i think that thats what happened. First day everything was ok, second day i connected rio in garage and thats when rf jam's started. Good that i have spare cables to garage, might need to get some one to connect some zones straight back to panel.

[GalaxyGuy]

Does the portal report JAM + Tamper in the logs, or just JAM on its own ?

[marx]

only RF JAM RF100.

[GalaxyGuy]

In the log, how much time between the +JAM and the -JAM events ?

I am trying to determine if this is the same type of protocol issue that I found with concurrent JAM+Tamper when the portal is fitted with the Ethernet module.

[marx]

less then a minute.