Download here: http://gg.gg/nzs9i
PDW Paging Decoder Software
*Pocsag Decoder Software Free Windows 10
*Pocsag Decoder SoftwareIntroduction
Since 2003, Peter Hunt has developed PDW to the most important (free!) application to monitor POCSAG and FLEX. PDW has many users worldwide, from radio enthusiasts to professionals. After 10 years, Peter considers PDW as finished and he has stopped development. Peter, thank you for all your efforts! Meanwhile, PDW is Open Source. You can read more about that below.
’Free Acronym Decoder lets you ’Crack The Secret Code’ your teen uses online, in Chat Rooms, online chats,Instant Messages, & Text Messages. This is an awesome software for parents because it gives you an inside look into your teenagers online life.’ Alphapoc 601, 602R X4 – frequency and RIC can be hand programmed (see above), proprietary USB cable is required to program via free software Ganray (Chinese AlphaPoc 602 clone) – frequency and RIC can be hand programmed (see above), proprietary USB cable is required to program via free software.
As of March 2013, this site is the official host for PDW.Download The latest PDW version can be found here:
*PDW v3.2b01 (zip) - Beta version with SSL support for SMTP mail client. Executable only
*PDW v3.12 (zip) - Current stable Open Source release
*PDW v3.1 (zip) - Final version developed by Peter Hunt
*LogBrowser (zip) - descriptionOpen Source
Zvei decoder free download. Win-BOS-Dekoder The Win-BOS-Dekoder is developed do be able to decode ZVEI-, POCSAG- and FMS-transmissions used in G. Signal decoders category is a curation of 10 web resources on, iPhone DTMF Decoder, Digital Speech Decoder, Globe-S for RTL1090. Resources listed under Decoders category belongs to Software main collection, and get reviewed and rated by amateur radio operators.
RadioRaft, official site. RadioRaft is an automatic decoder of numerous modes of radio data transmission on shortwaves, VHF or UHF. RadioRAft decodes RTTY Baudot, NAVTEX, ACARS, DGPS, GMDSS-DSC, POCSAG, PACTOR, PACKET, SITOR, numerous ARQ and FEC modes, CW Morse, RUM-FEC, ASCII, CIS-11, HNG-FEC, AUTOSPEC, SPREAD, 1382. It requires an interface connecting the receiver to the PC, known.
Since April 2013, PDW is available as open source software. This enables others e.g. to enhance the functionality, or to develop a Linux version.
You can find the Github project repository here.Support
I lack the time to give individual support with PDW. Please refer to the Forum on this site.Donations
Since Peter Hunt took over PDW in 2003, it has been freeware. Although Peter never wanted to earn money with PDW, some people kept on pushing him to offer a donation option. Version 3.12 (28 July 2013)Bugfixes:
*Fixed some deprecated coding techniques so PDW can be compiled with Microsoft Visual Studio 2012
*Fix to prevent filter array overrun when moving items in window
*Fix in POCSAG parsing prevent buffer overrun
*Fixed truncated messages in MobitexCosmetic:
*Link to PDW-website points to this page
*Copyright reflects Open Source licenseVersion 3.1 (26 September 2010)Bugfixes:
*Due to a small mistake, Mobitex could not be decoded via the soundcard. Block Duplicate Messages
This existing option has been extended and can now be configured in three ways:
*Previous address+message is the same (no timer)
*Previous message is the same (no timer)
*Previous address(+function)+message is the same
The first option compares the current capcode and message with the previous. The second only checks the message text.The last option compares the address (and when monitoring pocsag, also the function number) as well as the message text.This last option also enables a timer (1-9 minutes). If a message is repeated within this period, it will be blocked.
Also, you can now enable or disable the blocked.txt file to which blocked messages are logged.Version 3.0 (10 August 2010)Bugfixes
*In ERMES, sometimes the message text was copied after the previous message RS232
As some of you probably already know, RS232 is a standard for serial data communication. The well-known 2 and 4 level slicerswhich can be used with PDW don’t observe the RS232 standard. This is the main reason why additional drivers are needed(comprt.vxd or slicer.sys) and why Serial-to-USB converters are useless. These converters don’t only convert the hardware,they also convert the RS232 data to USB-level.
An RS232 interface has been developed especially for PDW, which does observe the RS232 standard. No more drivers are needed, which can solveproblems with serial PCMCIA cards, and the interface also allows conversion to USB.
Below are the modes/bitrates which are currently being supported:
*Pocsag (512/1200/2400bps)
*Flex (1600bps)
*Mobitex (8000bps)
Using two DIP switches on the interface, 4 data speeds can be selected:
*512bps (Pocsag)
*1200/2400bps (Pocsag)
*1600bps (Flex)
*8000bps (Mobitex)
This means that ERMES and ACARS are not supported and when Flex and Pocsag are combined on one network,only one mode can be decoded at once. Only a combined Pocsag 1200/2400 network can be decoded withouthaving to change settings.Invert Data
In the Interface Setup window the data’s polarity could be inverted, or set to Auto.This automatic detection will now allways be used, you can’t select a manual setting anymore.RX-Quality
One of the things which could be found in the Debug window (F12) was the RX-Quality (decoding quality).This value is now being shown below the signal indicator and is an indicator for decoding errors.These errors can be either visible (garbled messages or coloured characters), or invisible (correctedby the error correction). If the signal is strong enough (without noise), an RX-Quality of 100% shouldbe possible.Version 2.60 (24 March 2010)Bugfixes
*When using the command file, memory would slowly run short.Filters
The filters.ini layout has been changed. The numbering has been removed and the FilterCount is not more than an indication.
Loading of the filters should be a bit faster, maybe only noticable on slower systems.
7-digit capcodes can now also be saved without two preceding zeros.
When searching for ’duplicate filters’, PDW will keep on running on the background.
After searching a filter, F3 could be used to find the next filter. SHIFT-F3 can now be used to search backwards.SMTP port number
The default SMTP port number is 25. You can no also define a custom port number.Wordwrap
The word wrap option has been removed. Internally it is now always enabled, except when monitoring Mobitex.Logfile
The two icons to open/close the logfile are merged into one icon. This will open the Logfile Dialog in which thelogfile can be enabled or disabled. ALT-L can be use as shortcut to this dialog.Version 2.53 (11 January 2009)Bugfixes
*When monitoring ERMES, it didn’t seem to be possible to change the color for time/date. By mistake, PDW seemed to use the color of the Paging time/date (Pocsag/Flex).
*The daily statistics (ALT-S) were logged to the wrong file (the next day in stead of the previous). Double click / text selection
Before, at the second click the text below the mouse cursor would be selected, regardless of the position of the first click.Both clicks should be at the exact same position, otherwise you can rapidly click on two different words, causing thesecond to be selected. Should be fixed now.
The double click speed in PDW was fixed, although you can set the double click speed in Windows’ Control Panel.This timer is a bit different than the timers in PDW, but I’ve tried to use about the same time for double clicks in PDW.Find Filter window
I’ve made several changes in the Find Filter window. When this window will be closed after searching, you can use F3 to searchagain, using the same search string.
Because of above change, but also on request, PDW will remember the the ’Case Sensitive’ selection for as long as it runs.Before, the selection would disappear when the Find Filter window was closed.
The option ’Search while Typing’ has been removed. PDW will now always search while typing. Also, the number of hits will appear,the number of times the search string appears in the filters. This number will be updated after each key stroke.Filter window
Some extra keys can be used in the Filter window. As in other software, the space bar will scroll down, just like the ’PageDown’ key.If you wanted to delete a non-consecutive number of filters, this was possible with the ’Delete’ button, but not with the ’Delete’ key,which should be fixed now. The ’Enter’ key would close the Filter window, but now the selected filter will be opened for editing.I don’t think you will have to use the mouse often anymore.Version 2.52 (12 October 2008)Bugfixes
*If more than one groupcall was sent in frame 00/000, there was a slight chance that not all of them would be displayed.
*When selecting more than one filter in the filter window (using SHIFT), sometimes the wrong filter would be used as the starting point.
*After copy/pasting one or more filters, the last selected filter would remain selected, instead of the pasted filter(s).Date format
Besides the date formats DD-MM-YY and MM-DD-YY you can now also select YY-MM-DD. (Options -> General)Block Duplicate Messages in Filter Window
Once again, a little change regarding this option. It seemed desirable to block duplicate messages in the filter window also.Before, PDW only checked for duplicate messages in the monitor window, which could cause situations like this :
1234567 09-10-08 14:57:49 Message-1 7654321 09-10-08 14:57:50 Message-2 1234567 09-10-08 14:57:51 Message-1
Nothing would be blocked in the monitor window, the first and last message are no duplicate because of the middle one.If you wanted to filter Message-1 (code 1234567), but not Message-2 (code 7654321), Message-1 would appear twicein the filter window. This is solved now, a separate comparison will be made for filtered messages. The onlyoddity could be that the second instance of Message-1 would appear in het monitor window, but not in the filterwindow, causing the message to be blocked ’partially’. However, this change will lead to less duplicated messagesin the filter window.Version 2.51 (16 August 2008)Bugfixes
Mobitex Base-IDs
In the previous version I’ve made lots of changes regarding Mobitex. Unfortunately, I’ve made a littlemistake in decoding the BaseIDs, causing them to be displayed wrongly. So if you have already startedcollecting IDs of base stations in your area, I’m afraid that you will have to start all over again :-(Double mouse click / text selection
With a double (left) mouse click you can now select a word or address, which you can add to the clipboardusing CTRL-C (or a right click and ’Copy Selection’), so you can easily paste it somewhere else.Block Duplicate Messages
Regarding this option, I received a request to only check the message text. Before, PDW compared-if this option was enabled- the current address and message with those of the previous.If there was a match, the second would not be displayed. However, it seemed desirable if only themessage text could be compared, so consecutive messages with the same text, but different addresses,could also be blocked.
Next to the option ’Block Duplicate Messages’ you will now find ’Only check message text’ which willmake PDW only check the message text.
Regardless of this change, the option ’Block Duplicate Messages’ blocked a bit too much in Mobitex.Messages with the same MAN, but different TYPEs would also be blocked. This would only occur withso-called status messages when the Mobitex option ’Verbose’ was enabled.Mobitex Verbose / Sweep Frames
If the Mobitex option ’Verbose’ was enabled, status messages and sweep frames (containing base stationinformation) would appear. Sweep Frames can now be showed apart from status messages. In the Optionswindow you will now find ’Show Sweep Frames (BaseInfo)’ next to ’Verbose’.Version 2.5 (19 July 2008)Mobitex
In the previous versions I already made the first changes regarding Mobitex. This version contains onlyMobitex changes. Not everyone likes to monitor Mobitex, since most data is unreadable. But I discoveredthat lots of issues were decoded wrongly.
MANs
Already in the previous version, I was wondering how the ’messages’ were addressed. Every message (package of data)has to have a destination, the receiver has to know what data is his, and what isn’t.
Mobitex seems to use MANs (Mobitex Access Numbers), 7-digit numbers which can represent the destinationand also the sender. In all previous versions this data was already visible, but was displayed as the firstpart of the data. This first part is in fact a header, which contains the MANs, datatype, amount of dataand can also contain controlling and network information.
Both MANs will now be displayed, along with the data type. This means that I had to get rid of 3 other items,allowing the new items to be displayed. Frame and Bit Sync have been moved to the title bar and you will notfind CRC information anymore. On the one hand, the CRC OK/BAD was based on wrong information, sometimes itwould show OK when the message contained errors, or BAD when the messages seemed OK. On the other hand,the RX-Quality (F12) should offer enough information about bit- and CRC errors. Also, the RX-Quality forMobitex has been improved a bit, so it should be more reliable.
Data Types
Mobitex supports 4 different data types :
*DATA
*HPDATA
*TEXT
*STATUS
By default, they will all be shown. You can enable/disable these items in the Options window (CTRL-O).TEXT should mostly contain readable text, I’ve never actually seen the type STATUS myself, and DATAand HPDATA mostly contain unreadable data, with sometimes a little bit of readable text.HPDATA stands for Higher Protocol DATA, which allows the user to use their own data protocol.The decimal identification of this protocol (HPID) can be displayed by enabling ’Show HPID’ in theOptions Window.
Mobitex Packets (MPAK)
Like GSM and other cell switched networks, a radio device doesn’t only communicate with another device,but also with the network. After all, when switching on a device, it sends a notification, so the networkknows that this device is available and via which base station the data has to be sent.These ’Mobitex Packets’ (MPAK) can be enabled via the Options window.
Controlling / network information
Since Mobitex is two-way traffic, things as acknowlegdements also need to be transmitted.These are very short messages, which also were displayed in a wrong way. I don’t want to go into thistoo deeply, but you can enable this type of information by enabling ’Verbose’ in the Options Window.
People who already monitor will certainly know the periodic, long and unreadable messages which always seem tocontain about the same data. Again, a wrong interpretation, in fact these are so-called ’Sweep Frames’ whichcan contain network parameters, or neighbour channel information.
Unfortunately, I don’t know the exact meaning of all parameters, but what gets to be shown in the newversion comes a lot closer to reality. What also should be displayed correctly are the neighbour channels.Again, like in other digital networks, each base station transmits his neighbour channels once in a while.This offers the mobile stations to periodically check these neighbours to see if one of these signalsbecomes stronger than the current base station. This prevents the mobile from checking all availablechannels, which of course takes a lot more time.
Base-IDs
Once again, like in other digital networks, each base station transmits its own unique identification.Mobitex uses so-called Base and Area-IDs. These two will be shown in the title bar as one hexadecimal ID.When knowing the exact location of different base stations, this ID can let you know on which base stationyou are currently tuned. It would be even better if it would be possible to link a name to these IDs,well that is possible! The file base-ids.txt offers the possiblity to enter BaseIDs and a label, suchas the location.
Junk at the end of messages
More or less a bugfix, but again a bad (or missing) interpretation. The earlier mentioned headersalso contain the length of a message. Since Mobitex data is transmitted in blocks, the last charactersof the last block would be filled with junk characters. Now, knowing the exact amount of data, thisissue should be solved.Version 2.4 (16 March 2008)BugfixesBugfixes
*Some advanced soundcards are being listed as two virtual soundcards. One for input, one for output. PDW would display the wrong one (output), but now the input will be displayed
*Mousewheel scrolling didn’t work from all screen positionsColumn order
In previous versions the mode/type/bitrate column could be hidden. This option is now replaced by Display ->Screen Options which allows you to enable/disable any column in any order you like. Ofcourse, one columncan only be selected once and at least the message column has to be visable.
For FLEX networks which use dynamic groupcalls the options Use ’FLEX Group Mode’ and ’Log groupcodes,but don’t show them’ can be selected. But as far as I know, dynamic groupcalls are only used in the Netherlands.Commandfile / commandline
Using the commandfile external software can be called. The number of characters which could be sent throughthe command line had a certain limitation, but should now be encreased.
Also the commandfile can now be used with monitor-only messages. Before, this was only possiblewith filtered messages.2x PDW via the serial port (VXD)
Through the years I received lots of questions if it would be possible to run 2 sessions of PDW viatwo serial ports. The problem is that a VXD-driver can only be loaded once, on one serial port.It has to be possible to install Slicer.sys more than once, but somehow this also doesn’t seem to work.However, someone tipped me that the driver Slicer.vxd (originally used with other software) could possiblybe used for the second comport. After some testing this seemed to work, and after renaming it to Comprt2.vxd,PDW would automatically use this second driver if the first (Comprt.vxd) was already loaded on an otherserial port. In this way it is now possible to run two PDW sessions using two comports with W98 or ME.MOBITEX
All those years Mobitex didn’t change a bit. Recently I noticed that not all characters were beingdisplayed. PDW would skip non-printable ASCII (ASCII-31 and below). In fact, these characters are’non-printable’ and shouldn’t be displayed, but it seems that these characters are being useddifferently in Mobitex, causing some messages to be displayed shorter than they should be.In this version these non-printable ASCII is being replaced by other characters so all messageswill keep their original length.
Also, the RX-Quality should now be more correct in Mobitex.Fragmented FLEX messages
Since FLEX messages are being sent in ’frames’ (numbered data blocks), there is a maximum number ofcharacters that

https://diarynote.indered.space

コメント

お気に入り日記の更新

テーマ別日記一覧

まだテーマがありません

この日記について

日記内を検索