Universal ADX - Building Payloads - Datalogging List

Disassembly, Programming, Coding, Assembly, Binary information and all hacking discussions belong here.

Universal ADX - Building Payloads - Datalogging List

Unread postby Pym » Mon Aug 07, 2017 7:08 am

I am trying to understand, what is required for Universal ADX to work properly and to build adapted Payloads - Datalogging Lists for my definition.

If I have well understood, Universal ADX expects a fixed 55 word registers addresses, 14 byte registers addresses and ? byte flag registers addresses.
So Datalogging lists should always contain this quantity, even filled with FFFF or FFFE. A template like 55x FFFE, 0000, 14x FFFE, 0000, ?x FFFE, 0000 could be a good start.
Am I right ?

In attachment the related table, generated by GUFX Patch, that does not match this requirement.
You do not have the required permissions to view the files attached to this post.
Pym
Hacker
 
Posts: 90
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby decipha » Mon Aug 07, 2017 8:04 am

post your bin and disassembly
User avatar
decipha
Tooner
 
Posts: 12919
Joined: Mon Jul 15, 2013 5:29 pm
Location: New Orleans, LA
Name: Michael Ponthieux
Vehicle Information: Supercoupin' x10
90 (4x 5spds) - Dante, Ruby, Daja, Ava
91 4r70w - Skarlett
92 (2x) 5spd & auto - Bianqa, Andrea
93 auto - Danika
94 5spd Rionda
95 auto Aisha
Vehicle 2 Information: Others:
00 Lincoln LS - Luanda
98 Camaro SS - Bounquisha
02 Harley F-150 - Sasasha
03 Marauder - DyShyKy
00 Explorer 5L - Bernyce

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby decipha » Mon Aug 07, 2017 8:44 am

These are the basic steps to implementing the universal adx

1) find and remove the set raminit flag from the console routine, put the call there to the patch code
The console routine can be found very easily by searching for 1f1c, the raminit flag is the next operand

2) find the end of code and make sure u can put the universal adx patch code there, then make sure yiur call is jumping to that address

3) put the set raminit flag at the front 3 bytes of the patch code, if its a single bank ecu copy the universal adx patch code from gufx, if its a multi-bank copy the universal adx patch code from RZASA

4) find a chunk of free assessible rom to put the list of registers to datalog, i.e. the "payload addresses"
I usually use 0xEE00 or 8xEE00 if u have the free rom, otherwise stuff it where u can fit it

5) update the patch code for the address of the payload list if not using what I had it set to

6) setup your payload addresses using the datalog listing table I have there for you, make sure u update the address to that table if u moved it

The order of the payloads must follow the order I have outlined in the disassembly write up, heres the direct link

http://www.efidynotuning.com/dis.htm#ram

The first list is words, if theres only a byte of that word u need to log then out FFFF so the patch code skips that address, if u dont know that payload address put FFFE so the patch code 0s out that value. At the end of the words list put 0000 so the patch code breaks the word lookups and does bytes next.

7) Do the bytes just as you did the words, except now u have to put the address where the byte is to be copied to.
for example, ect and act are bytes at offset 4 and offset 5, you would do something like so:

00 B1 1F 24 00 B0 1F 25

1F20 is the beginning address for shadowing payloads, thus its offset is 0x0, which is the engine run timer ATMR1 (for reference)

and the same applies for bytes as words, use FFFE to 0 unknown or unused bytes

8) after you have all your bytes and shadowing addresses done put a 00 00 so the patch code breaks the bytes lookup and goes to bit flags

9) for the bit flags u have to put the address of the flag as the first word, then the next byte is the shadowing offset (1F is already added in the code) then the next byte is the bit position of the flag to compare to. The code does an and comparison to that bit , if true it sets it if false it clears it. So for example, lets say the WOT flag is bit 0 at register D0 you would do the following:

00 D0 4F 01

00D0 is the address to the flag, 4F is the offset to shadow to (0x1F4F) and 01 is the first bit to compare

Dont quote me on that 4F for the wot flag as im sure thats not it im on my mobile so i cant check im just giving u that as an example.

follow the outline in the disassembly write up for the order of the bits

Be sure to put double 0 words to end the patch code 00 00 00 00

10) save the table and bin file, then open it with the hex editor in tunerpro and scroll down to where u wrote the payload list. Copy that block of hex and edit the universal adx patch, paste that block in there at the address u wrote the payload list to do its put in with the patch

11) save the xdf, make sure the patch shows that its applied, if it doesnt that means u screwed up somewhere

12) run the bin through your disassembler and verify your call to the patch code is correct and that the raminit flag is correct and that the patch code is looking up the correct address for your payload list, if its a multi bank bin and u put the list in a different bank than what i used youll have to go through the patch code and change the bank calls to the bank u put it in

13) open up the latest eec-iv universal adx from the homepage, if u have a multi bank binary then go to edit and commands >> request patch a, you'll have to change the QH poll slot from 3 to 1 or vice versa, I have it listed in the comments of the adx, thats the ONLY difference between the eec-iv adx and eec-v adx
User avatar
decipha
Tooner
 
Posts: 12919
Joined: Mon Jul 15, 2013 5:29 pm
Location: New Orleans, LA
Name: Michael Ponthieux
Vehicle Information: Supercoupin' x10
90 (4x 5spds) - Dante, Ruby, Daja, Ava
91 4r70w - Skarlett
92 (2x) 5spd & auto - Bianqa, Andrea
93 auto - Danika
94 5spd Rionda
95 auto Aisha
Vehicle 2 Information: Others:
00 Lincoln LS - Luanda
98 Camaro SS - Bounquisha
02 Harley F-150 - Sasasha
03 Marauder - DyShyKy
00 Explorer 5L - Bernyce

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby Pym » Mon Aug 07, 2017 10:04 am

I have followed your tutorial.
Still not found the raminit flag, but the console routine should be at 0x4170, even if I put the hack at 0x6798 calling the classical 0xd4f0 address.
But my question is on this Datalogging table, are all registers required (55 word registers, 14 byte registers, ...)
or using a simple 00 70 00 00 00 72 00 00 00 EA 44 08 00 00 00 00 will work with Universal ADX ?
You do not have the required permissions to view the files attached to this post.
Pym
Hacker
 
Posts: 90
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby decipha » Mon Aug 07, 2017 10:39 am

no, when u put the 0 word u break the word list A, then another 0 word will break the byte list B then another 0 word will break the stacking bitmask list C marking the end of the shadowed addresses

that example u gave is faulty

0070 will shadow 0x70 to 1F20 (offset 0)

00 00 will break the word lookup

00 72 is in the byte lookup
00 00 is the address your trying to shadow 0072 which is faulty
User avatar
decipha
Tooner
 
Posts: 12919
Joined: Mon Jul 15, 2013 5:29 pm
Location: New Orleans, LA
Name: Michael Ponthieux
Vehicle Information: Supercoupin' x10
90 (4x 5spds) - Dante, Ruby, Daja, Ava
91 4r70w - Skarlett
92 (2x) 5spd & auto - Bianqa, Andrea
93 auto - Danika
94 5spd Rionda
95 auto Aisha
Vehicle 2 Information: Others:
00 Lincoln LS - Luanda
98 Camaro SS - Bounquisha
02 Harley F-150 - Sasasha
03 Marauder - DyShyKy
00 Explorer 5L - Bernyce

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby decipha » Mon Aug 07, 2017 10:39 am

can u post your xdf too
User avatar
decipha
Tooner
 
Posts: 12919
Joined: Mon Jul 15, 2013 5:29 pm
Location: New Orleans, LA
Name: Michael Ponthieux
Vehicle Information: Supercoupin' x10
90 (4x 5spds) - Dante, Ruby, Daja, Ava
91 4r70w - Skarlett
92 (2x) 5spd & auto - Bianqa, Andrea
93 auto - Danika
94 5spd Rionda
95 auto Aisha
Vehicle 2 Information: Others:
00 Lincoln LS - Luanda
98 Camaro SS - Bounquisha
02 Harley F-150 - Sasasha
03 Marauder - DyShyKy
00 Explorer 5L - Bernyce

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby Pym » Mon Aug 07, 2017 10:52 am

decipha wrote:no, when u put the 0 word u break the word list A, then another 0 word will break the byte list B then another 0 word will break the stacking bitmask list C marking the end of the shadowed addresses

that example u gave is faulty

0070 will shadow 0x70 to 1F20 (offset 0)

00 00 will break the word lookup

00 72 is in the byte lookup
00 00 is the address your trying to shadow 0072 which is faulty

Yes only one word, one byte and one flag to datalog, this is also possible with 00 70 00 00 00 72 1F 24 00 00 EA 4F 08 00 00 00 00. Excellent.
Pym
Hacker
 
Posts: 90
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby decipha » Mon Aug 07, 2017 10:56 am

yes you can log only one word one byte and one flag if you wished

what word what byte and what flag address and bit do you want to log?

----------------------------------------------------------------------------------------------------------------------------------------------------------
i see what your saying, your console routine is much different than the american roms, it wouldnt be easy to put the call in there

it looks like you got the patch in there correctly and the payload list as well, you just have to edit the list now as outlined in the disassembly write up
User avatar
decipha
Tooner
 
Posts: 12919
Joined: Mon Jul 15, 2013 5:29 pm
Location: New Orleans, LA
Name: Michael Ponthieux
Vehicle Information: Supercoupin' x10
90 (4x 5spds) - Dante, Ruby, Daja, Ava
91 4r70w - Skarlett
92 (2x) 5spd & auto - Bianqa, Andrea
93 auto - Danika
94 5spd Rionda
95 auto Aisha
Vehicle 2 Information: Others:
00 Lincoln LS - Luanda
98 Camaro SS - Bounquisha
02 Harley F-150 - Sasasha
03 Marauder - DyShyKy
00 Explorer 5L - Bernyce

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby Pym » Mon Aug 07, 2017 12:22 pm

I am just trying this registers list :
8C 00 98 01 FF FF 74 00 12 01 12 01 70 00 76 00 F0 FF 52 01 F0 FF F0 FF F0 FF F0 FF F0 FF EC 02 24 01 F0 FF FF FF FF FF 22 01 FF FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF FF FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF F0 FF BC 02 EE 02 6E 01 00 00 72 00 24 1F 73 00 25 1F 00 00 16 00 01 44 16 00 02 44 16 00 04 44 16 00 08 44 16 00 10 44 16 00 20 44 16 00 40 44 16 00 80 44 17 00 01 4A 17 00 02 4A 17 00 04 4A 17 00 08 4A 17 00 10 4A 17 00 20 4A 17 00 40 4A 17 00 80 4A 00 00 00 00 FF FF
To test this, I get a throttle body, a CO adjuster and an ECT sensor from the attic.
I am not able to reproduce PIP signal for now, my function generator can not generate more than 10v and I think the signal works at 12v.
Pym
Hacker
 
Posts: 90
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby decipha » Mon Aug 07, 2017 3:01 pm

offset 8 and A your polling the same address???

why do u keep polling FFF0 ?

if u tell me what your trying to do i may b able to help
User avatar
decipha
Tooner
 
Posts: 12919
Joined: Mon Jul 15, 2013 5:29 pm
Location: New Orleans, LA
Name: Michael Ponthieux
Vehicle Information: Supercoupin' x10
90 (4x 5spds) - Dante, Ruby, Daja, Ava
91 4r70w - Skarlett
92 (2x) 5spd & auto - Bianqa, Andrea
93 auto - Danika
94 5spd Rionda
95 auto Aisha
Vehicle 2 Information: Others:
00 Lincoln LS - Luanda
98 Camaro SS - Bounquisha
02 Harley F-150 - Sasasha
03 Marauder - DyShyKy
00 Explorer 5L - Bernyce

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby Pym » Mon Aug 07, 2017 3:58 pm

decipha wrote:offset 8 and A your polling the same address???
why do u keep polling FFF0 ?
if u tell me what your trying to do i may b able to help

Yes, it was a mistake and the first time, I had forgotten the byte parts. But anyway, I can now obtain results.
I keep FFF0 values in the right places to fill them properly when registers will be well identified, if they exit in this strategy.
And it is required for words, to keep a complete list to fill in MAP sensor voltage an the last 2 values, to check sensors or other values.

I still have some registers to identify for this strategy, monitoring them will really help, so I will have to update this list often.
Pym
Hacker
 
Posts: 90
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby decipha » Mon Aug 07, 2017 8:58 pm

FFFE is what u want to use not FFF0
User avatar
decipha
Tooner
 
Posts: 12919
Joined: Mon Jul 15, 2013 5:29 pm
Location: New Orleans, LA
Name: Michael Ponthieux
Vehicle Information: Supercoupin' x10
90 (4x 5spds) - Dante, Ruby, Daja, Ava
91 4r70w - Skarlett
92 (2x) 5spd & auto - Bianqa, Andrea
93 auto - Danika
94 5spd Rionda
95 auto Aisha
Vehicle 2 Information: Others:
00 Lincoln LS - Luanda
98 Camaro SS - Bounquisha
02 Harley F-150 - Sasasha
03 Marauder - DyShyKy
00 Explorer 5L - Bernyce

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby motorhead1991 » Mon Aug 07, 2017 9:21 pm

Commenting so I can find this later. M0M2 isn't far enough along for this to be necessary quite yet.
motorhead1991
General Poster
 
Posts: 34
Joined: Mon Apr 03, 2017 6:46 pm
Name: Anthony Cox
Vehicle Information: 1990 Ford Ranger FLH2 conversion. Ford forged/dished pistons, Total Seal file-fit rings, Clevite rod and main bearings, Clevite cam bearings, IHI turbo, Siemens Deka 60lb/hr injectors, Ford slot MAF in custom 3" housing. Moates Quarterhorse with Binary Editor, using the PAAD6 database.
Vehicle 2 Information: Stock 1990 Ranger. ICM relocation

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby Pym » Tue Aug 08, 2017 2:09 am

decipha wrote:FFFE is what u want to use not FFF0

Right, I had 0 as target, so ... I will replace them with FFFE.

Another thing, I have seen 2 more updates in GUFX patch for Datalogging.
They force rewriting of console routine. What are their purpose ?
Pym
Hacker
 
Posts: 90
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby decipha » Tue Aug 08, 2017 8:54 am

to overwite the old logging code so not to coerupt the tune, u can disregard them
User avatar
decipha
Tooner
 
Posts: 12919
Joined: Mon Jul 15, 2013 5:29 pm
Location: New Orleans, LA
Name: Michael Ponthieux
Vehicle Information: Supercoupin' x10
90 (4x 5spds) - Dante, Ruby, Daja, Ava
91 4r70w - Skarlett
92 (2x) 5spd & auto - Bianqa, Andrea
93 auto - Danika
94 5spd Rionda
95 auto Aisha
Vehicle 2 Information: Others:
00 Lincoln LS - Luanda
98 Camaro SS - Bounquisha
02 Harley F-150 - Sasasha
03 Marauder - DyShyKy
00 Explorer 5L - Bernyce

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby Pym » Wed Aug 09, 2017 2:57 pm

decipha wrote:to overwite the old logging code so not to coerupt the tune, u can disregard them

Ok, it is noted.
outside topic, I have just discovered patches with quarterhorse, it is really, really useful for many other things, like testing tunes or small updates, having a rollback and so on.

One more time, thank you for the information, the patches, the Universal ADX and for the time behind that. I can not imagine starting from nothing.
Pym
Hacker
 
Posts: 90
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby Pym » Thu Aug 10, 2017 7:48 am

First test with all sensors connected, in the car, it is more easy.
I have added my own dashboard and its values, to dispatch the values I wanted to analyse.
Everything is OK, except for registers shadowed at 0x1F86 (ECT sensor AD value => Volts), 0x1F88 (MAP sensor AD value => Volts), 0x1F8A (CO Pot. AD value => Volts) and 0x1F8C (Another unknown sensor AD Value => Volts).
ECT value from its translated register is OK, same thing for MAP. For the others I have not duplicated information.
No issue for ACT or TPS , I have both AD values and translated values.
Can it be linked with their position in the Datalogging list ? Can it be a conflict with the existing values from the Universal ADX ?
I will put them in another place to check.
Pym
Hacker
 
Posts: 90
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby decipha » Thu Aug 10, 2017 10:49 am

yea no prob Im always glad to help out

yep, the disassembly write up has the order the payloads have to be configured in to follow the universal adx outline

the order you list the addresses is going to determine the offset that payload is saved at

Ive been planning on putting a full diagnostic menu in the universal adx, when I do that will be a tremendous help to those doing development as u can see the bidi ports actuate and raw ad counts for inputs

The only logical way to implement it is to have a second logging list patch.

ill post more info when i get some time
User avatar
decipha
Tooner
 
Posts: 12919
Joined: Mon Jul 15, 2013 5:29 pm
Location: New Orleans, LA
Name: Michael Ponthieux
Vehicle Information: Supercoupin' x10
90 (4x 5spds) - Dante, Ruby, Daja, Ava
91 4r70w - Skarlett
92 (2x) 5spd & auto - Bianqa, Andrea
93 auto - Danika
94 5spd Rionda
95 auto Aisha
Vehicle 2 Information: Others:
00 Lincoln LS - Luanda
98 Camaro SS - Bounquisha
02 Harley F-150 - Sasasha
03 Marauder - DyShyKy
00 Explorer 5L - Bernyce

Re: Universal ADX - Building Payloads - Datalogging List

Unread postby Pym » Thu Aug 10, 2017 2:11 pm

I confirm, that shadowing this registers at other addresses, gives the right result.
Something should be wrong with these addresses, in the patch code, in the ADX, with the Quarter Horse or in my ECU Ram (EEC IV VM-120).
It works fine until address 0x1F82, not tried 0x1F84.
Pym
Hacker
 
Posts: 90
Joined: Sat Mar 04, 2017 4:29 am
Name: Pierre-Yves
Vehicle Information: Ford(EU) 91 Fiesta RS Turbo / EEC IV VM120 0FAB
TunerPro on Moates chips
Vehicle 2 Information: Ford(EU) 97 Puma 1.7 VCT / EEC V LP2-110 MUFF AXPDCB4
Vehicle 3 Information: Ford(EU) 97 Mondeo V / EEC V MLP-427 REED ATAFHE3
Additional Vehicles: Ford(EU) 91 Fiesta XR2i / EEC IV SD111 1AFA
Ford(EU) 98 Cougar V6 / EEC V ?


Return to Programming & Coding

Who is online

Users browsing this forum: No registered users and 1 guest